Mios upload problem

Antimon · December 20, 2006

I'm true newby to this midibox stuff, so if you could please help me I would apretiate it very much.

I bought stuf from Mike's shop, and soldered everything, checked all voltages, conected PIC, installed mios

studio, but I cannot upload MIOS. Bootstrap loader works fine I think

because it keeps sending me that Sysex message every 2 seconds. My

conclusion is that midiout of Core module works fine, but when I try to

upload hex file of newes MIOS, I keep getting the same error message in Mios

studio:

Error: received unexpected upload request.

In "IN" window of Mios studio, I keep getting the same Sysex message - so I

think Midi In of the Core module isn't working. Midiout of of my sound card works fine because when I start upload of hex file - led light blinks. Also I checked voltage between two pins of the midi cable that are conected to core - the voltage changes in exact moment when packets are sent. Polarity is correct. I checekd everything from

the ucaps page about midi troubleshooting. Also I bought new optocoupler

6N138, but nothing helps. Only one strange thing I noticed is that

resistance on diode is about 6k in one direction, adn about 18 k in other

direction - should it be infinite (this is when core module is not connected

to power source)?

I'm pretty sure that Midi IN of the core isn't working, but I cannot figure why.

Please help

Antimon

Antimon · December 22, 2006

Hi

Here is some more info:

I uplaoded MIOS with hardware programmer, but nothing works. On LCD upper row is fully drawn (there are no characters - just every character rectangle is drawn), and second row is empty - nothing is drawn. When I try to build simple mios application that writes something on lcd or sends midi event - nothing happens. I tried puting it in diferent places, like in Init() or DISPLAY_Tick() or MPROC_NotifyTimeout(), but nothing happens - I get nothing at In window of MIOS Studio.

BUT when I upload sw_loopback_test hex file - than everything works - everything that I send from mios studio, I get back instantly.

I hope that this helps.

Please somebody, help me

Thanks

Antimon · January 3, 2007

I'm sure that I uploaded pic burner, because I get that sysex message every 2 seconds - that says "Pic burner is alive"

I cannot upload anything but burner (nor MIOS, nor app) - with mios studio - all I get on "IN" window in mios studio is that "alive signal" from pic burner. Because there is no confirmation message from burner, I think neither package gets through to pic. I thought that I could do all of that with hardware burner, so I did like this: burned pic burner, then burned mios, than burned app. But it seems that every burning overwrites everything that was before on pic. So I'm stuck with mios studio to burn mios and app, and I cannot get it working.

I also tried it without lcd, but MIOS won't upload neither.

Let me just repeat that I tried burning that loop test - with hardware burner. When I tried it in Mios Studio - everything works ok - whatever I send to pic, I get in mios studio in "IN" window. This means that all midi conections are ok, right?

Please help, because I don't know what else to do. How should I upload MIOS?

Thanks

Antimon · January 3, 2007

Here I am again.

I removed similar topic from programming section on request of audiocommander.

Sorry about that, but as you see, nobody answered me here on this subject.

I searched this forum little more, and I saw that problems I'm having could be due to bad optocoupler, wrong resistor on optocoupler, bad power, etc. I'm going home now, so I'll check those things.

Thanks

audiocommander · January 3, 2007

Hey antimon,

don't worry, I'm just being practical :)

Now the first and most important thing is: don't panic, you are most likely to find the errors if you stay logical:

I cannot upload anything but burner (nor MIOS, nor app) - with mios studio - all I get on "IN" window in mios studio is that "alive signal" from pic burner

I really do not understand what you are trying to do?

the "burner" is the MBHP burner module and you "burn" the bootloader. You cannot send the bootloader by Midi. If you get that 2 sec poll, it means that the bootloader is already on the chip.

Please look at this schematic:

fetch.php?w=&h=&cache=cache&media=http%3A%2F%2Fwww.audiocommander.de%2Fpics%2Fsonst%2FMIOS_Overview.gif

There are plenty of topics here that illustrate that basic concept, think of it like a Computer: (BIOS -> Windows -> Word) ... okay?

But with mios studio nothing works, and I cannot se anything on LCD, but top row (all rectangles are filled).

To me that sounds like a problem with MIOSStudio and not your hardware. Now forget your burner, and think about the next logical step: finding out where the error is (I mean get the location of the error by testings) :

- Check if you made the right midi-connections inside MIOSStudio (you have to draw connections beween the IN and OUT port!

- Connect something else to your Midi-Out-Port, virtual or real, does not matter: a simple synth or anything â€“ and use the Keyboard of MIOSStudio to see if you can get anything out of MIOSStudio.

If the suggestions above still don't work, you got to check if it's MIOSStudio, so:

- Try if you can upload MIOS with another program (eg. MidiOX, search the forum for upload procedures and see the advanced description)

If that does not work, you should follow the Midi Debug section at ucapps.

Best regards,

Michael

audiocommander · January 3, 2007

As I'm the reason you deleted the other thread :-[ , I just got the window open and think it may be of use to post the old informations:

Hi
I uploaded MIOS with hardware programmer (because uploading with mios studio doesn't work)' date=' but nothing works. On LCD upper row is fully drawn (there are no characters - just every character rectangle is drawn), and second row is empty - nothing is drawn. When I try to build simple mios application that writes something on lcd or sends midi event - nothing happens. I tried puting it in diferent places, like in Init() or DISPLAY_Tick() or MPROC_NotifyTimeout(), but nothing happens - I get nothing at In window of MIOS Studio.
BUT when I upload sw_loopback_test hex file - than everything works - everything that I send from mios studio, I get back instantly.
Please somebody, help me
Thanks

Antimon · January 4, 2007

I tried all tests from Midi Debug section at ucapps that doesn't involve extra parts - like extra led.

I specially tried two loopback tests:

1. conecting Rx and Tx when PIC is not in its case, and that one worked fine: all that I sent from mios studio I also received in mios studio.

2. uploaded sw_loopback_test hex file with hardware burner on pic. This loopback also worked fine: all that I sent was received in mios studio.

Yesterday I was checking resistance with multimeter when voltage is applied to the core and I saw two possible strange things:

1. Resistance between Rx and Tx is about 6k

2. Resistance of that Diode D1 on MIDI IN was 4k in one direction, and 16k in other.

Is there something wrong there?

I tried to diferent optocouplers, and tried uploading without one. In all cases there was an error:

received unexpected upload request, because bootloader (I burned bootloader_v1_2_pic18f452 because v1.1 that came with PIC from Mikes shop showed same signs) sent that upload request signal every two seconds. So it seems that PIC hasn't received anythigng.

But when I try to measure voltage between Rx and Tx - it is very low when nothing is sent, it is about 100mV when bootloader sends that upload request, and it is about 2V when Mios studio sends packages to PIC. That also looks strange to me. Is it?

I think the problem is not related with power supply because even though I use cheap adapter - it is connected on J1 and the voltage is 5.06V all the time, with and without the PIC - and with and without optocoupler. It is measured on all points suggested by ucapps.

Thanks for all help so far

I'm open for any suggestion

audiocommander · January 4, 2007

Hi Antimon,

I tried all tests from Midi Debug section at ucapps that doesn't involve extra parts - like extra led.
(...)
I'm open for any suggestion

What about my suggestions?

http://www.midibox.org/forum/index.php?topic=8201.msg57394#msg57394

I believe you should check the software first...

Michael

Edit:

1. conecting Rx and Tx when PIC is not in its case, and that one worked fine: all that I sent from mios studio I also received in mios studio.
2. uploaded sw_loopback_test hex file with hardware burner on pic. This loopback also worked fine: all that I sent was received in mios studio.

IMHO that means your hardware seems to be okay!

Antimon · January 4, 2007

Hi Michael

Which suggestions - I thought I did it all:

- Check if you made the right midi-connections inside MIOSStudio (you have to draw connections beween the IN and OUT port!

If i didnt make right connections - neither of two loopback tests would work.

- Connect something else to your Midi-Out-Port, virtual or real, does not matter: a simple synth or anything and use the Keyboard of MIOSStudio to see if you can get anything out of MIOSStudio.

Yes - I get stuff out of mios studio, with that loopback test.

If the suggestions above still don't work, you got to check if it's MIOSStudio, so:
- Try if you can upload MIOS with another program (eg. MidiOX, search the forum for upload procedures and see the advanced description)
If that does not work, you should follow the Midi Debug section at ucapps.

Actually I didn't try midiox - I'll try that toonight.

Thanks again for your help

Ante

henrygr · January 4, 2007

Antimon.

Hang in there. First time is always the hardest. Two questions

Any other messages besides the sysex request every two seconds?

What is your power source? (and I mean every aspect of it)

Mark.

Antimon · January 4, 2007

Hi Mark

Thanks for the encouragement.

No there is no other message - only that upload request every two seconds.

My power source is cheap (4-5Euro) power adapter that can give diferent DC voltages on output. I tried it on 6V and 7.5V setting on J1 pins in the core. When it is set to 6V - it gives 5.06 at the core, and when it is set to 7.5V it gives something above 5.1V.

I'm not ready to give up just yet :)

Ante

henrygr · January 4, 2007

I have a niggling feeling that your problem lies here Antimon. It may provide the voltage, but not enough amps. I thought of this because in the past when powering my core with 9v batteries (much handier for setting up you system, as you are not tied down by wires) the unit would behave erratically as the battery started to lose its charge. On inspection with a multimeter, voltage showed up perfectly, but funny enough, i COULD NOT UPLOAD OR DOWNLOAD anything to the mios. Sound familiar?

Also, you say 7.5V, however, you haven't said how many milliamps it provides- another very important factor. You would need, at a guess, to use a 750 m/amp adapter at 7.5v, and about 500 m/amps at 9v. Somehow I have a suspicion that your adapter is only operating at about 150 m/amps (you said "cheap"). Not enough juice, especially where LCD's are concerned.

I also gather that your internet connection is at work, and your core is at home. Som on your way home tonight, get a good Duracell 9v battery, power up your core with that, and try again.

Regards,

Mark.

Antimon · January 4, 2007

Ok

I'll try to find some better suply too - how about pc power supply - connected at J2?

It is 500mA - I forgot to write that in last post.

Also I disconected LCD after initial trouble - so it isn't causing trouble.

Thanks

Ante

henrygr · January 4, 2007

Connecting 5v regulated supplies to J2 is a great idea for final builds- not recommended for troubleshooting. Do the 9v battery. Trust me. 8)

audiocommander · January 4, 2007

It is 500mA - I forgot to write that in last post.

Sounds like henrygr is absolutely right about the power supply ;)

IMHO 500 mA at 7.5 V is much too less.

I've experienced startup problems with 800 mA and 7 V, though 800 mA and 9 V is working great.

I'd get a good stabilized power supply. They aren't expensive. I got mine from Conrad (10 EUR, small size, stabilized) and Pollin (4 EUR, but a bit larger).

I'd watch out for 800 mA power supplies minimum.

Cheers,

Michael

Antimon · January 5, 2007

I tried other power suply's, but no luck:

9V battery

2A power adapter.

I also tried midiox - same trouble - bootstrap loader just keep emitting that upload request message.

I'lll put here just parts of log - whole log would be to big:

SYSX: F0 00 00 7E 40 00 01 F7

0003C1FC 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003D140 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

000C2313 MOX 7 F0 Buffer: 1184 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 02 01 00 01 00 0D 7B 62 5F 00 45 0F

SYSX: 7F 7F 76 39 7C 0F 57 35 4F 61 3D 33 6B 01 73 21 1E 5D

SYSX: 26 1A 0A 0D 49 71 50 4E 6A 00 2D 04 7A 71 07 68 3C 56

SYSX: 42 3E 43 03 45 6C 7F 78 2C 2E 6B 7E 11 00 38 39 7B 4F

SYSX: 57 45 4F 5D 3D 3E 6C 7D 6F 6B 77 67 6F 1E 5F 2E 3E 7B

SYSX: 75 01 70 17 6F 28 13 01 3F 7A 41 38 0C 07 54 24 00 5C

SYSX: 71 3C 1F 7D 6B 0B 62 7F 6E 78 5F 37 7E 79 45 7B 7F 77

SYSX: 5C 2F 57 7F 3E 62 40 7E 0B 7E 14 09 70 60 31 20 5F 00

SYSX: 48 00 08 07 35 4D 6F 14 50 05 34 02 74 07 3E 60 2F 61

SYSX: 32 5E 52 1D 40 67 43 05 57 4F 24 19 59 06 60 1D 4F 13

....

SYSX: 0E 7B 5B 44 00 77 61 5C 0A 00 3D 2A 00 08 2F 53 5F 05

SYSX: 00 1E 55 00 13 40 01 07 40 5C 0F 2A 43 45 5F 7C 1A 5E

SYSX: 28 70 48 00 05 00 72 0A 10 0F 00 07 50 00 03 40 0B 60

SYSX: 04 12 03 37 3F 61 31 10 01 7E 0B 02 40 33 16 78 48 01

SYSX: 72 4F 01 61 6F 33 38 00 0E 7B 5B 40 2F F7

000C2641 MOX 7 F0 Buffer: 1184 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 02 02 00 01 00 10 03 5F 06 70 20 01

SYSX: 75 28 3C 5B 7F 43 2B 65 0E 09 00 00 50 0C 65 22 03 37

SYSX: 04 40 00 04 60 01 1A 74 2C 00 08 47 22 64 00 45 04 40

SYSX: 00 00 38 01 38 00 42 20 0B 50 08 12 03 37 3F 61 31 10

...

SYSX: 00 04 0D 55 1C 72 02 04 44 3B 2A 33 2F 6E 30 74 0C 1F

SYSX: 0B 02 00 12 09 6D 3D 66 0F 31 43 50 30 74 0C 00 4D 50

SYSX: 1B 00 09 78 01 6A 00 53 3B 78 0B 01 78 01 16 50 10 1C

SYSX: 0A 37 02 46 0E 41 40 02 0B 7B 76 20 46 F7

0003E084 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E087 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E089 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E08D 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E08F 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E092 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E095 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E099 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E09B 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E09E 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E0A1 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E0A4 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E0A6 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E0AA 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E0AC 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E0B0 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

000C2970 MOX 7 F0 Buffer: 1184 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 02 03 00 01 00 05 0C 01 13 07 20 61

SYSX: 68 18 3C 5B 1F 42 40 31 60 53 54 3C 3E 60 4F 61 76 67

SYSX: 40 7E 0F 3E 3C 09 70 00 7B 40 0F 05 1B 58 13 78 00 54

SYSX: 03 76 43 5C 6E 7B 0A 5B 0B 27 5C 54 09 03 36 14 00 50

SYSX: 18 12 50 05 04 1E 2E 09 07 21 77 57 03 5A 0F 36 3E 53

SYSX: 7F 00 7B 40 0F 00 0F 58 13 78 3B 4D 60 48 1B 31 20 05

SYSX: 01 41 15 00 28 21 77 70 44 3A 01 0F 38 01 70 5F 3B 02

...

SYSX: 40 34 05 0B 73 58 0F 78 3F 61 68 6F 30 21 70 04 4A 5B

SYSX: 0B 20 24 0D 51 6A 3D 61 60 05 60 11 58 20 75 34 0B 78

SYSX: 07 21 4A 6A 01 1B 03 66 55 7E 0B 53 09 6C 7D 20 2B 30

SYSX: 0F 07 3F 1B 71 46 40 0C 6E 02 76 00 45 F7

000C2C9D MOX 7 F0 Buffer: 1184 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 02 04 00 01 00 07 03 5E 7D 78 19 21

SYSX: 75 6F 44 3A 00 28 06 49 2B 02 74 00 0A 40 0F 20 05 07

SYSX: 27 0D 70 0E 42 38 6B 4E 14 23 0D 6F 23 3F 1C 15 41 41

SYSX: 69 63 0F 73 57 09 00 00 50 0D 19 22 7F 05 77 7B 7F 38

SYSX: 3B 3B 57 50 71 20 3F 05 0B 0A 04 78 28 78 50 2F 40 05

...

SYSX: 74 1C 72 70 27 21 67 15 04 01 6D 49 1B 3F 02 78 03 5B

SYSX: 12 30 0B 20 10 07 39 6D 6E 32 43 5D 2E 06 74 1B 7B 20

SYSX: 27 21 67 17 02 3A 0E 39 28 20 0E 6C 49 5B 78 27 40 1D

SYSX: 59 13 00 5A 01 00 3B 4E 6E 73 14 00 16 F7

0003E795 2 -- F0 Buffer: 9 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0F 45 F7

0003E798 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 45 F7

0003E79B 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E79E 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E7A1 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E7A4 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E7A6 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E7AA 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E7AD 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E7B0 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E7B2 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E7B5 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E7B8 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E7BC 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003E7BE 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003E7C1 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

000C2FCB MOX 7 F0 Buffer: 1184 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 02 05 00 01 00 77 2B 41 5D 06 7E 6C

SYSX: 09 68 39 65 60 4E 43 4E 2A 08 03 5B 12 36 7E 0D 70 07

SYSX: 36 24 60 16 40 20 0E 73 5B 5C 65 07 3A 5C 0D 68 37 77

SYSX: 00 4E 43 4E 2E 04 74 1C 72 50 40 1D 59 13 37 71 0F 00

...

etc.

...

SYSX: 0C 78 0A 5D 70 67 40 05 6F 0A 3C 01 3E 78 53 60 2A 77

SYSX: 45 1E 03 67 3C 29 70 11 7B 62 4F 01 07 5E 14 78 14 1D

SYSX: 71 27 41 29 6F 0A 3C 05 4E 78 27 60 2F 77 42 3E 01 47

SYSX: 3C 19 70 5F 3B 62 3F 00 2F 5E 13 78 3D 1D 71 17 43 59

SYSX: 6F 01 3C 02 20 00 00 00 12 00 00 00 01 10 00 00 00 09

SYSX: 00 00 00 00 48 00 00 00 04 40 00 00 00 24 00 00 00 02

SYSX: 20 00 00 00 12 00 00 00 01 10 00 00 00 09 00 00 00 00

SYSX: 48 00 00 00 04 40 00 00 00 24 00 00 00 02 20 00 00 00

SYSX: 12 00 00 00 01 10 00 00 00 09 00 00 00 00 48 00 00 00

SYSX: 04 40 00 00 00 24 00 00 00 02 20 00 00 00 12 00 00 00

SYSX: 01 10 00 00 00 09 00 00 00 00 48 00 00 00 04 40 00 00

SYSX: 00 24 00 00 00 02 20 00 00 00 12 00 00 00 01 10 00 00

SYSX: 00 09 00 00 00 00 48 00 00 00 04 40 00 00 00 24 00 00

SYSX: 00 02 20 00 00 00 12 00 00 00 01 10 00 00 00 09 00 00

SYSX: 00 00 48 00 00 00 04 40 00 00 00 24 00 00 00 02 20 00

SYSX: 00 00 12 00 00 00 01 10 00 00 00 09 00 00 00 00 48 00

SYSX: 00 00 04 40 00 00 00 24 00 00 00 02 20 00 00 00 12 00

SYSX: 00 00 01 10 00 00 00 09 00 00 00 00 48 00 00 00 04 40

SYSX: 00 00 00 24 00 00 00 02 20 00 00 00 12 00 00 00 01 10

SYSX: 00 00 00 09 00 00 00 00 48 00 00 00 04 40 00 00 00 24

SYSX: 00 00 00 02 20 00 00 00 12 00 00 00 01 10 00 00 00 09

SYSX: 00 00 00 00 48 00 00 00 04 40 00 00 00 24 00 00 00 02

SYSX: 20 00 00 00 12 00 00 00 01 10 00 00 00 09 00 00 00 00

SYSX: 48 00 00 00 04 40 00 00 00 24 00 00 00 02 20 00 00 00

SYSX: 12 00 00 00 01 10 00 00 00 09 00 00 00 00 48 00 00 00

SYSX: 04 40 00 00 00 24 00 00 00 02 20 00 00 00 12 00 00 00

SYSX: 01 10 00 00 00 09 00 00 00 00 48 00 00 00 04 40 00 00

SYSX: 00 24 00 00 00 02 20 00 00 00 12 00 00 00 01 10 00 00

SYSX: 00 09 00 00 00 00 48 00 00 00 04 40 00 00 00 24 00 00

SYSX: 00 02 20 00 00 00 12 00 00 00 01 10 00 00 00 09 00 00

SYSX: 00 00 48 00 00 00 04 40 00 00 00 24 00 00 00 02 20 00

SYSX: 00 00 12 00 00 00 01 10 00 00 00 09 00 00 00 00 48 00

SYSX: 00 00 04 40 00 00 00 24 00 00 00 00 60 F7

0003FDD3 2 -- F0 Buffer: 9 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0F 1D F7

0003FDD6 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 1D F7

0003FDD9 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003FDDD 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003FDDF 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003FDE2 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003FDE5 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003FDE8 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003FDEB 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003FDEE 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003FDF0 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003FDF3 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003FDF6 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003FDFA 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

0003FDFC 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

0003FDFF 2 -- F0 Buffer: 10 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 0E 0B 01 F7

000C460B MOX 7 F0 Buffer: 1184 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 02 0C 00 01 00 09 00 00 00 00 48 00

SYSX: 00 00 04 40 00 00 00 24 00 00 00 10 4E 78 67 60 12 00

SYSX: 00 00 01 10 00 00 00 09 00 00 00 00 48 00 00 00 04 40

SYSX: 00 00 00 24 00 00 00 02 20 00 00 00 12 00 00 00 01 10

SYSX: 00 00 00 09 00 00 00 00 48 00 00 00 04 40 00 00 00 24

SYSX: 00 00 00 02 20 00 00 00 12 00 00 00 01 10 00 00 00 09

SYSX: 00 00 00 00 48 00 00 00 04 40 00 00 00 24 00 00 00 02

SYSX: 20 00 00 00 12 00 00 00 01 10 00 00 00 09 00 00 00 00

SYSX: 48 00 00 00 04 40 00 00 00 24 00 00 00 1F 7F 7F 7F 7F

SYSX: 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F

SYSX: 7F 7F 7F 7F 7F 7F 7C 00 06 29 11 28 14 22 64 5D 45 76

SYSX: 03 7E 00 00 3B 6C 6E 19 43 5E 76 73 53 5E 10 78 3F 7F

SYSX: 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F

SYSX: 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 60 63 F7

0004092C 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

00041870 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

000427B4 2 -- F0 Buffer: 8 Bytes System Exclusive

SYSX: F0 00 00 7E 40 00 01 F7

After this pic keep sending that upload request every two seconds.

I'm sorry that it wasn't power related issue, because I hopped that it was. I'll try toonight with pc power supply anyway.

If you see something in this log please tell mee (it is midiox sysex log).

henrygr · January 5, 2007

That actually looks familiar. Got thinking last night after my last post, and got a hunch that that might happen. It's happened to me once or twice before. It is all total garble that comes about as a result of runnung the PIC, and more importantly- trying to upload to the PIC, at low power. So, what needs to be done is to upload the Bootstrap, and Mios (the bios and the operating system for choice of a better comarison), and this is the method- step by step. Bare with me if you have completed some of these steps- just want to make sure we are singing off of the same hymn sheet.

BTW- Stick with the battery, a 2amp power supply is a bit too powerful!!

a)Get a copy of Mios Studio- http://www.midibox.org/mios_studio/ if you have not done so already, and install. Read the instructions on the page, as it requires Java to be installed on your OS. Also download the lastest vesion of the MIOS skeleton from here http://www.ucapps.de/mios/mios_update_v1_9c.zip. Unzip the file to a folder on your desktop. We will come back to it later.

b)Go to Midi>Midi Set Up and click (or press Ctrl+R)

c)In the left pane select "Mios Studio Out Port", and in the right pane, click the name of the Midi in port of your PC.

d)Click on "CONNECT" at the bottom of the page.

e)In the right pane select "Mios Studio In Port", and in the left pane, click the name of the Midi out port of your PC.

f)Click on "CONNECT" at the bottom of the page.

g)Close this window

h)Click on "Midi>Midi Monitor IN" and "Midi>Midi Monitor OUT" or Crtl+O and Ctrl+I. This will give us ring side seat of all the action. (now where did I put the popcorn....) :D

i)Wipe the popcorn grease off of your hands, and click "Mios>MIOS Hex File Upload" or Ctrl+U

j)On the right hand side, click the checkbox "Manual Mode- Don't use feedback from core"

k)Click on the tab "Hex File", and navigate to where we unzipped our file earlier on the desktop. Double click the folder that is the model of what PIC you have, bouble click "Burner" and select the file.

l)Now, turn on your Core Module, and as soon as you see some infromation appear on the Input Montor of Mios Studio, click on the tab "Start" in the MIOS Hex File Upload window. (This is an opportune time to finish the popcorn, as this takes a wee while...)

m)When all is done, wait about four seconds, then power off the core.

n)Again, click on the tab "Hex File" and navigate once more to the folder that represents your PIC, Double click "Midi", and choose the file "mios_v1_9c_pic18f***.hex". Steady now son, I can see the grin on your face!! The f*** stands for your model of PIC! (Cheeky git!) >:(

o)Power back on the Core, and as in step 'l', as soon as you see some infromation appear on the Input Montor of Mios Studio, click on the tab "Start" in the MIOS Hex File Upload window. When all is done, wait about four seconds, then power off the core, wait another four, and power back on.

I think that is about the size of it. Sorry if I was long winded, but at least you know the exact routine.

I am, of course, and as ever, open for correction.

Mark. :D

Antimon · January 5, 2007

Hi Mark.

I'm a bit confused about your last post. I did everything from that procedure before. I'm pretty much sure that there is nothing wrong with procedure, nor with Mios Studio - because I tested it with that loopback test - hex file that I burned on pic. Every message that was sent from midi studio to pic was again received in mios studio. That should mean that Mios Studio works. Anyway, I tried MidiOx - and the similar thing happened - pic didn't respond in right way - like it was def or sth.

Don't think that I'm ungratefull or something. I'm very happy that I have a place (this forum), where I can get help, and please continue to help me with any suggestion. :)

henrygr · January 5, 2007

Did you try it last night with the 9v battery connected?

Antimon · January 5, 2007

Yes I tried with 9V as well as with 12V 2A - it seemed all right to try with that - all the voltages were ok - 5.06V

Also I forgot to mention that I have two PIC 18f452- and two opto couplers - on all combinations I get the same behaviour. So I guess it is not problem with those components.

Thanks

Ante

henrygr · January 5, 2007

So. Now we know what it is not.

Next.....

Have you mounted the MIDI plugs to the core that came with SmashTV's package?

CHECK all connections at capacitors and at the voltage regulator.

Any chance of a photo of the soldering on the back?

What version of Java are you using on the PC? (beta versions will 90% of the time cause annoyances).

As Ithink of things for you to check, i'll keep posting....

That okay with you?

Mark :)

moebius · January 5, 2007

Hi.

Core is from Mikes Midibox shop...

One suggestion: Try disconnecting middle (ground) pin from the core MIDI Out port (J12).

Moebius

Antimon · January 5, 2007

Of course it is ok.

Answers:

I bought stuff from Mike's shop. Midi plugs are not mounted - they are connected with 20cm long wires to the core.

I checked and rechecked every single connection.

I'll take picture toonight - I'm at work now.

Java version: jre-1_5_0_06-windows-i586-p.exe

Hear you

Thanks Mark

Antimon · January 5, 2007

Answer to moebius :

- I tried by disconecting whole midiout - that was easier for me. Then I used Mios Studio to upload mios without conformation from the core - just sent packages every 1000ms - That didn't help.

But I'll try to disconect just the ground toonight.

Thanks

Ante

audiocommander · January 5, 2007

SYSX: F0 00 00 7E 40 00 02 01 00 01 00 0D 7B 62 5F 00 45 0F

the syx-code you posted is simply the representation of the sysex file of "mios_v1_9c_pic18f452.syx"

Just to make sure:

You got the bootloader v1.2 burnt onto a PIC18F452, right?

If your Core PCB is from SmashTV: is the chip also from SmashTV? Because you mentioned you burned the bootloader by yourself?

If you burned it yourself: with what MBHP-module have you burned the bootloader (JDM/MBHP-Burner...) and what software have you used â€“ and were there any errors? Have you checked if the loader got burned right? (via compare-functions?)

Best regards,

Michael

ps: do you have another PIC available to swap and test?

Maybe you damaged some part of the PIC while you were trying to burn MIOS? Don't know though if this is possible, just guessing...

Sign In

Mios upload problem

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation