Digispunk

yes - thats what TK says in the readme.txt - quote - A) you got a preburned PIC18F452 from SmashTV or Mike with the old Bootloader v1.1b, and haven't installed MIOS yet. In this case, upload -> pic18f452\midi\update_without_installed_mios.hex via MIDI like described at the http://www.ucapps.de/mios_bootstrap.html page. This .hex file contains MIOS V1.9 and the update program. The updater will: - do a CRC check in order to ensure that the whole binary has been uploaded - replace Bootloader V1.1b by Bootloader V1.2 - end - i thought that all i had to do was upload this one hex file to get mios installed, then next i would have to upload the application (eg. midibox64) maybe im missing something, do i need to have any banksticks attatched? i dont have one made yet

OK - so with the latest MIOS STUDIO running, i set up to load the hex file - no luck - i get these messages with the core powered down, and MIOS awaiting request i get this message 'Hex file contains code in MIOS range, forcing reboot!' when i switch the core power on, it begins to upload, but the core returns error message and after 3 attempts MIOS Stuido aborts the upload with this message 'Aborting after 3 errors' i search the forum for references to these errors, but not found anything i couldnt find anything on this in the threads regarding the latest release of MIOS studio, ??? ??? ??? ??? ???

:) great - as soon as i get the OS up and running i will experiment with it and report back! thanks guys.

well - im pleased to say that some progress has been made, but we aint all the way home yet, the problem was the wires between the midi ports and the core board (i am using surface mounted midi sockets - so i had to use wires to extend the length), - so once corrected - i bootup MIOS studio, get the hex file ready - \MIDIBOX\mios_update_v1_9\pic18f452\midi\update_without_installed_mios.hex this was the one recomended to go for, since i have Smash Pic with the bootstrap already burned in the pic (v1.1b) now upon switching on the core, MIOS gets the request signal and begins to load the software, everything seems to be going fine - MIOS reports that 'Upload process complete' then instead of the checksum i get an endless string of sysex requests as pictured below the software doesnt seem to be behaving as planned - any ideas? ??? my troubleshooting logic goes like this - MIOS receives request signal from PIC/CORE = PIC functional / CORE functional / CORE MIDI OUT PORT functional / PC MIDI PORT functional MIOS is sending the software, MIOS MIDI 'in' PORT monitor shows feedback from CORE (but no checksum) - IF MIDI conection from PC to CORE MIDI 'in' is physically disconected, then PIC sends new upload request and MIOS MIDI 'in' PORT monitor stops displaying the 'recieved data' = CORE MIDI IN PORT functional so PIC = Functional CORE MIDI IN/OUT Functional PC MIDI in/OUT Functional Cables OK MIOS OK anything else im missing? hints?

midibox64 = mios application = ;D

midibox64.exe - that would be Serge's editor, otherwise would we have to get into hacking the MIOS version dierctly?

I was wondering how to implement custom MIDI CC values for the 'off' value of a button, with serge's virtual midibox app, at the moment i can only see a way for programming midi CC values the 'on' state, as the 'off' value defualts to 0 and there doesnt seem to be an obvious way to change this to another value ideally i would like to be able to program two values for each button, and each button could have a different pair of values. here's an example - using the toggle function i would like to jump between two distinctive filter cutoff values - 'on' = 99 and 'off' = '23' can this be done in vmidibox.exe ? or do i have to go another route? cheers D

thanks Illogik, and all who have contributed to the knowledge * and the midi part of your core works; do the MIDI-troubleshooting guide step by step to insure your core is working - yes - just no request from the pic - at this point i am beginning to presume that it has not been burned properly or has been damaged in some way, i am going to try to locate another pic and retest - hopefully this will solve the problem * you have your midi device routing properly set up in MIOSStudio - yes i have this done - i am competent with Midi including sysex if there is no need to calibrate the optocouplers - will turning the (optocoupler) pots have any effect on the performance or the MIDI ports? LCD - yes turning up the brightness makes the upper row of bocks turn black - i am using the 40x2 LCD from Voit.Nl cheers - i am going to check all this out tomorrow and report back - hopefully with some good news! :)

The LCD was lighting up - but there was no message or characters displayed,l I have tested the midi connections (in and out) by attatching a synth to it and sending and recieving midi notes and midi cc's in and out of Ableton, i will also check the sysex send and receive for safety. Can you confirm whether i dont or do need to calibrate the optocoupler for the MIDI on the core? - my electronics mate asked me to check this out with you.

Hi Stryd, thanks for the speedy reply, maybe my writing syntax mis-represented what i meant, so what i mean is - I have a Pre-Burned Pic from Smash with the Bootstrap V 1_1b installed into the core its not sending a request in Mios studio - i do have Mios configured correctly please correct me if im mistaken - but if a Core has a Pre-Burned Pic with the Bootloader installed, it should send a request message when its connected to Mios Studio and its Power Switched on? right or wrong?

Hi There everyone, after many months of reading and researching, i took the plunge and built a core and sid board, the first attempts were rubblish, too much bad soldering, so i started a second batch with some excelent help. Now the Core and Sid boards are built, and they all check out with the electricity readings at the various points, these have been checked by a skilled electronics friend and he assures me they are all connecting and reading fine as per the guildlines. I connected the core's midi ports to my computer to upload the Mios software into the Pic - (Bootstrap loader V1_1b from Smash Tv) and the problem is i dont get any requests or sign of life from the pic, when i run Mios Studio and open the Midi monitors there is nothing. The midi interface has been checked in/out signals sent / recieved with synthesisers - everything working The core board has been checked - all correct readings with multimeter My electronics friend asks me to check with you about the Octocoupler calibration - is this necessary to get the message through? Could it be possible that my Pic is dead? Do i need to upload a new bootstrap? This project is a really cool thing and i want to thank Thorsten, Smash and the whole community for making it possible, and i look forward to getting the bleeps out of the SId.