Compiling and uploading

[napierzaza]

Hey, so I programmed my own asm file for the SID application, I compiled it with not errors to speak of. It's about 204KB and seems fine. However, when I uploaded the image it stopped after about 4 upload+checksums. There's not error on the MIOS Studio side, but the Midibox hangs on "REBOOTING MIOS." After that I get a black screen. Thinking it was a fluke, I tried again, same thing. I only had two spare programmed PICS, and my burners not working for some reason. Anybody know any reason why I'd get this problem before I risk bricking my last spare?

[stryd_one]

Bricking? an app upload shouldn't be able to kill the chip.... Are they still sending upload requests?

[napierzaza]

I'm not getting uploade requests. And as I said there is nothing displayed on the LCD, no "READY" or what have you.

Here is the file, it was off RC25 if that is of any value.

setup_6581RC25.hex

[stryd_one]

newbies: don't use that hex file.

I'm not sure why you put a poisoned hex on here mate, I don't wanna fried PIC either! ;)

Hey, so I programmed my own asm file for the SID application,

Why not put the source up? And the logs of the build too...

I compiled it with not errors to speak of.

None at all? or none to speak of?

It's about 204KB and seems fine.

Seems fine?

However, when I uploaded the image it stopped after about 4 upload+checksums. There's not error on the MIOS Studio side, but the Midibox hangs on "REBOOTING MIOS."

Core shouldn't reboot until the upload is complete, and the bootloader should not allow your app to overwrite any code...something is strange here. Are you using smart mode? Are you SURE?

my burners not working for some reason.

Define not working?

[napierzaza]

Yes, of course you shouldn't upload it! Here is the source.

No no errors, It just goes onto compiling the next one. When I was mentioning the size, it was about the same size as the other hex I compiled, as if it might have only compiled halfways or something.

Yeah, I was using smart mode and for some reason it only uploaded for a second, does not say "complete," but when I look at the LCD, it said "MIOS REBOOTING"

For some reason my burning isn't getting good voltages, which is a different problem, I replace the lm317 and the 7805 and for some reason I can't get 5v, which is maddening because it's so simple.

Some days things work out...

newbies: don't use that hex file.

I'm not sure why you put a poisoned hex on here mate, I don't wanna fried PIC either! ;)

Why not put the source up? And the logs of the build too...

None at all? or none to speak of?

Seems fine?

Core shouldn't reboot until the upload is complete, and the bootloader should not allow your app to overwrite any code...something is strange here. Are you using smart mode? Are you SURE?

Define not working?

[stryd_one]

it was about the same size ....as if it might have only compiled halfways or something.

Huh?

For some reason my burning isn't getting good voltages, which is a different problem

Ahh OK.... You've gota corrupt bootloader. I don't think that' a separate problem at all ;)

Think you forgot to attach ;)

[napierzaza]

No no, everything with my setup was fine. I had previously burned 3 PICs with bootloaders that came up as "READY". I plugged in the PIC and flashed it with a generically compiled hex file. The interface displayed properly on the LCD and everything.

Then I recompiled the software and tried uploading via Midi, which is where the problems happened.  :-X

The only reason I mentioned my burner being fritzed is because I can't verify the PICs or reburn the bootloaders until it work again.  :P

I must say that I feel really stupid this stuff keeps happening. I'm suspicious that it's all really just a brain tumour.  :D

midibox_sid_v2_0_rc25.zip

[stryd_one]

I assume yours is the setup_6581.asm?

I plugged in the PIC and flashed it with a generically compiled hex file. The interface displayed properly on the LCD and everything.

Then I recompiled the software and tried uploading via Midi, which is where the problems happened.  :-X

You mean you uploaded one of the hex files from TK via midi and it went OK? or you flashed it with the burner? (that shouldn't work)

[napierzaza]

I flashed bootloader, uplpoaded a TK via midi and everything was kosher, save for the fact the CS is not the same as mine.

Then it was when I uploaded my OWN hex via midi that it didn't work.

[stryd_one]

I assume yours is the setup_6581.asm?

[napierzaza]

Sorry, I only read after the quote.

Yes it is.

Thanks for looking BTW, you're extremely helpful Stryd!

[stryd_one]

Had a look, did a compare....

Found a few minor editing errors but nothing much of note...

OT: LFO costly? it's free software.....?

[stryd_one]

I can't see anything wrong with it. I don't know if your mods should work, but I see nothing that suggests that it should cause the midibox to reboot....

Timeline:

Uploaded TK's hex files from the zip, unaltered, everything works

***

Uploaded your hex, everything dies

What happened in *** ? Mention anything. did you move the box? recable? New drivers on your PC? Just a reboot? Farted? you name it.....

[napierzaza]

Well, the note about the LFO was in regards to my available supply of registers and buttons/switchs/encoders.  I made this box with leftovers from my last project.

In regards to what happened between... Not sure. I guess there were some wiring changes etc. But it was loading up fine and displaying the SID info screen fine. I was able to connect via MIDI without apparent problems. Considering that I get no MIDI messages, I suppose I will have to try burning again.

Thank you very much for having a looky-loo though, I really appreciate it. Would you happen to remember the errors off hand?

[stryd_one]

Would you happen to remember the errors off hand?

Line 255 jumped out first because it's formatting wasn't a match for my code highlighting and it didnt look like a comment (like the others do) but it was definitely treated as a comment by the compiler, it was just a missing space.... Most of them were really minor like that, just a missing space/extra LF/extra tab here and there... nothing worth "fixing"

In regards to what happened between... Not sure. I guess there were some wiring changes etc. But it was loading up fine and displaying the SID info screen fine. I was able to connect via MIDI without apparent problems. Considering that I get no MIDI messages, I suppose I will have to try burning again.

Well it' like this: It was working, you changed something, and it started nuking PICs. Chances are, your next PIC will go the same way, until you figure out what you changed and un-change it ;)

un-change my core..... set me freeeee

</Joe Cocker>

[nILS]

My suggestion would be to treat the changed core like any new core - measure voltages, check everything that can be checked, when all tests succeed - put in a PIC and opto.