Hello,
I eventually didn’t wan’t to post anything, but since i’ve being working on this for a week orso…to get MIOS running and still wasn’t and am able to do this, i was getting so frustrated that i had to…
I know your all busy and know that am probably bothering you as newbie with totally stupid questions, that are really not relevant to you…But before i ask you for help, i had a five day look on the forum.
I found one other post of this problem but the solution was not givin’.
What I have is 5 core’s and 4 Pic’s of 18F452.
I thought i burned the MIOS_bootstrap_loader on all 4 pics… and was able to sysex to the Pic.
Well…not…
I have the LCD (2x20) connected and it’s only giving the black blocks on the first row…
But there should appear the upload sysexstring “FO…” of Mios, am i right?
Since this wasn’t working and I tested each Pic on each core, and not one was sending the command to MidiOx. (or Midiox wasn’t getting any command).
I configured this and which seem to be ok.
* following the guidelines for MidiOX (everything checked ten thousand times or more),
* checking the midi-in with the LED-test,
* three doubling checking the circuit of
all core’s for some short-circuits or failure’s in the PCB/parts,
* by some failure’s i did some reassembling…in the proper way.
* checking the voltages givin’ for the core.
* doing a physical loop on my midi-interface…
So i thought i had to problems with the bootstrap loader, so put PIC for Pic in the JDM programmer and tried again…the verification worked and the device was said to be burned “succesfully”. But still nothing would disappear in MidiOX or the LCD, roulating each pic on each core.
So went again searching for the problem of the JDM-programmer added the resistor (for the 18 F452, 10k pin 31 and pin 38) and the powersupply and burnt “succesfully”, verified and all. Nothing again in MidiOX and the LCD.
I used the JDM on win98, winME, winXP, but none of them seemed to burn the proper Bootstrap_loader…with all different conditions, tried by following the forum or page’s of MIOS.
But something is happened when i burned,because I get different config’id’s then the original bootstrap_hex.file has in the IC-prog, although the checksum stays the same and when you compare them (the buffers) it’s also the same.
Is this coincedence (with 5 core’s and 4 Pic’s) or is this normal way of coping with problems…??
If somebody has a clue, I really would like to hear some feedback or some additional help to this…Like how do i check the Midi-out on the core…, although i don’t think this the problem, although ellimate this for sure…makes the tree of possible errors smaller…distilating the real cause…
I know this is a bit long text, but i did it because, I really am confused…
Somebody…please..??
Thank you for your precious time and the will to listen to me…
Grtz Erik.
