Firmware upgrade disaster!!!

[kurtus420]

dmitri or el, do you think any of my programming issues could be related to the fact that synthex used a pic18lf2550 instead of a pic18f2550? This is the only thing that doesn't line up here. Will winpic work on vista, I could try it again. Try 1 used millenium os wont pull info from pic, try 2 xp os wont pull info from pic, try 3 vista os we'll see?????

[el-dr]

And can you dump with Winpic memory content of PIC18F2550 and post it here?

dumpeda.hex

[dmitri]

Very weird. Can you try Atmega32 with a 16MHz crystal.

Shit It works perfectly. What the heck is going on here??? The 644 has the same fw version as the 32.

I could suspect the 20MHz crystal, but you say it works fine over the standard MIDI port so it should be exclude.
I could suspect PIC18F2550 memory is corrupted, but you say it works fine with Atmega32 so it is not the PIC.
You can try to load the latest version of the bootloader into Atmega644 which allows crystal frequency selection, load it with 16MHz firmware version and try it with the 16MHz crystal.

[dmitri]

dmitri or el, do you think any of my programming issues could be related to the fact that synthex used a pic18lf2550 instead of a pic18f2550?

PIC18LF2550 is identical to PIC18F2550 except it can work at lower voltages. I used either version with no difference.

This is the only thing that doesn't line up here. Will winpic work on vista, I could try it again. Try 1 used millenium os wont pull info from pic, try 2 xp os wont pull info from pic, try 3 vista os we'll see?????

I use XP. With all your tries it can be safely concluded that your problem is not due to OS.

[dmitri]

And can you dump with Winpic memory content of PIC18F2550 and post it here?

dumpeda.hex

It looks good.

[dmitri]

You can try to load the latest version of the bootloader into Atmega644 which allows crystal frequency selection, load it with 16MHz firmware version and try it with the 16MHz crystal.

You can also try it without re-programming the bootloader. With the 20MHz crystal load 16MHz firmware version over the standard MIDI port then switch to the 16MHz crystal and see if the problem the same as with 20MHz crystal.

[kurtus420]

so it's not the os, not the cable, not the pcb board very clean solder job, only thing left is configuration but I'm sure I'm doing that correctly or messed up programming pins. Does it matter if my iscp cable is 2 feet long.

[dmitri]

so it's not the os, not the cable, not the pcb board very clean solder job, only thing left is configuration but I'm sure I'm doing that correctly or messed up programming pins. Does it matter if my iscp cable is 2 feet long.

I use a 1 meter cable with no problems.

[kurtus420]

ok, I really appreciate all the help dmitri, I think I start from scratch when the new pic's arrive and see what happens.

so it's not the os, not the cable, not the pcb board very clean solder job, only thing left is configuration but I'm sure I'm doing that correctly or messed up programming pins. Does it matter if my iscp cable is 2 feet long.

I use a 1 meter cable with no problems.

[el-dr]

You can try to load the latest version of the bootloader into Atmega644 which allows crystal frequency selection, load it with 16MHz firmware version and try it with the 16MHz crystal.

You can also try it without re-programming the bootloader. With the 20MHz crystal load 16MHz firmware version over the standard MIDI port then switch to the 16MHz crystal and see if the problem the same as with 20MHz crystal.

Bingo!!! The Atmega644 works perfectly well @ 16MHz (MCT and all other USB operations + standard MIDI) and so does the Atmega32. I'm still wondering how the 20MHz crystal could go wrong while working well except the USB operation. Strange

Is there any other component that could be the reason, knowing that everything works at 16MHz? Something that can go wrong so that it can't handle the higher clock speed?

By the way, what's the difference between the 644 at 16 and 20MHz in terms of performance (latency etc.)?