ashd Posted September 9, 2007 Report Posted September 9, 2007 I sent the 1.9f update to my midibox, it went fine and rebooted saying 1.9f etc. Then where it used to say Waiting for Ain/Din event... it now says "Bootloader is up-to-date", and doesnt send midi when i move the faders.I have tried using mk_syx and vmidibox64.exe to send configurations to it but it doesnt seem to be doing anything... am i missing something?
seppoman Posted September 9, 2007 Report Posted September 9, 2007 am i missing something?Yes :) after uploading a new MIOS, you always need to re-upload the application.Seppoman
ashd Posted September 9, 2007 Author Report Posted September 9, 2007 i thought the application is made via mk_syx?or do i have to take one of the complete applications from the downloads page, then use mk_syx?thanks in advanceash
seppoman Posted September 9, 2007 Report Posted September 9, 2007 i thought the application is made via mk_syx?or do i have to take one of the complete applications from the downloads page, then use mk_syx?thanks in advanceashI´m not very familiar with configuring mb64, but from the MB64 page: mk_syx.zip.... Creates the configuration dump for MIDIbox64So yes, you have to upload the application. mk_syx is only for configuring it (when it´s already running). How did you get your box running in the first place if you don´t know these things? ;)Seppoman
DavidBanner Posted September 9, 2007 Report Posted September 9, 2007 grab MIOS Studio and use it to upload the Hex file for the project.it's usually called main.hex
ashd Posted September 9, 2007 Author Report Posted September 9, 2007 it was preburnt, however i couldn't add/change the configuration using mk_syx because it didnt do anything/affect the midibox in any way (and for some reason it was only transmitting over midi channel 2)thanks, i will try uploading main.hex and then the mk_syx config and report back
ashd Posted September 10, 2007 Author Report Posted September 10, 2007 that did the trick, thanks alot!looks like the application loaded onto it before the update was a debug app rather than the correct one, which is what got me a little confused...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now