gillesdeshays Posted September 21, 2004 Author Report Share Posted September 21, 2004 sorry to pollute the Programming board ...:-[it was a programming question .... then derivate to hardware ... Thanks TK for the inputs .... Quote Link to comment Share on other sites More sharing options...
LO Posted September 22, 2004 Report Share Posted September 22, 2004 I also had alot of problems with MB_link random CC messages would appearBut now im building a LC so dont need it! Not helpful I know.......peace Quote Link to comment Share on other sites More sharing options...
gillesdeshays Posted September 23, 2004 Author Report Share Posted September 23, 2004 No one tested with success MB_LINK ? Quote Link to comment Share on other sites More sharing options...
TK. Posted September 24, 2004 Report Share Posted September 24, 2004 No one tested with success MB_LINK ? Just to point up that this is no software problem: every MIDIbox SID user who has connected one or more MBSID slaves uses the MIDIbox LinkBest Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
gillesdeshays Posted September 24, 2004 Author Report Share Posted September 24, 2004 that's what i thought ... Quote Link to comment Share on other sites More sharing options...
gillesdeshays Posted September 24, 2004 Author Report Share Posted September 24, 2004 ok ... now i'm going to be crazy .... >:(I try to change back the core to id00 with the change_id application ....and now my core is still id01 and doesn't receive any sysex ...it boots up on MIOS V1.7 and stay "READY" ...And i cannot upload anything... i tryed MIOS, MB64e ... without success ... I try to switch the PIC with another one ...the problem is in the PIC .... Must i have to re-upload the bootstrap ?The RX pin of the pic can be damaged ? or it's a soft issue ? Quote Link to comment Share on other sites More sharing options...
TK. Posted September 25, 2004 Report Share Posted September 25, 2004 You can upload SysEx data, otherwise the LCD wouldn't show the dummy message of MIOS (READY) which appears only when no application has been uploaded thereafter. So, it seems that you were able to upload mios_v1_7.syx, and you should also be able to upload any other SysEx dump once you found out what is wrong with your configuration.Reg SysEx ID: at power-on the core sends an upload request which contains the device ID of the core. Which device ID do you see, still 1, or 0? You never wrote how you are trying to upload code, are you using MIDI-Ox? Have you regenerated the .syx file with hex2syx.pl? Or are you using vsysexbox? In this case it's easier, you only have to select the correct device ID in the selector boxBest Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
gillesdeshays Posted January 30, 2005 Author Report Share Posted January 30, 2005 oppps ... i forgot this topic ....I solve my problems on this PICs with reprogramming it with the bootstrap loader ... with the right ID ...I was stuck before 'cause i cannot burn any 452 at this time ... :-[ Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.