a problem with my MD

[hamedoo]

Hi Dmitri
I built a 32 input mega drum. I spend 1 month to make it! But it's not working
I sent my MD's photos for u!
What i did:
1- Making PCBs for megadrum32 from viewtopic.php?f=3&t=266
2- Soldering everything together and using beautiful wireing
3- Programing Atmega32 by AVR programmer and megadrum32_16_20110316.bin file
4- Programing PIC by PIC programmer and pic18f2550usb_12MHz.hex file
5- Connecting USB to PC
6- Nothing .... LCD is OFF and in windows: USB device not recognized and some parts of circuit are warm

1.JPG

3.JPG

4.JPG

error.JPG

I'm too sad please help me! what did I wrong?
Is it necessary to use DC power source?
Why LCD is off?
Is there any programming problem?
Please help me it was too hard to make for me in my city but I MADE IT
I hope you have a solution
Regards
Hamed

[Firelord]

3- Programing Atmega32 by AVR programmer and megadrum32_16_20110316.bin file

I think Dmitri should put a notice on the website front page about how it is absolutely pointless to do this without the protected bootloader. Preferably by means of a large flashing red-coloured text message.

The last usable unencrypted firmware version is 20100516, you can upload that and see if it works for you.

USB device not recognized and some parts of circuit are warm

Look for shorts on your board. Also it makes more sense to post pictures of your copper side of the PCBs. The component side may look ok, but the primary source of problems is usually the soldering.

[jman 31]

Any reason why there are two pins on the PIC not in the socket? I am not familiar with Dmitri's design, but I can't imagine that that is the proper way to do it?

[dmitri]

I think Dmitri should put a notice on the website front page about how it is absolutely pointless to do this without the protected bootloader. Preferably by means of a large flashing red-coloured text message.

To download MegaDrum firmware anyone would have to go to viewtopic.php?f=3&t=1075 .
There is a warning in red there not to try loading the firmware into non-protected Atmega. If this doesn't work sometimes then no matter how many flashing warnings are spread around the website there still will be someone who will ignore the warnings.

[r0bbie]

Any reason why there are two pins on the PIC not in the socket? I am not familiar with Dmitri's design, but I can't imagine that that is the proper way to do it?

Good call Jman!!

[Firelord]

Perhaps I was a bit harsh in my previous post. And in the light of the latest observations from Dmitri and Jman31, I hope that re-inserting that PIC and flashing the correct firmware into the 'mega will instantly remedy the situation described by the OP.

[hamedoo]

Any reason why there are two pins on the PIC not in the socket? I am not familiar with Dmitri's design, but I can't imagine that that is the proper way to do it?

YOU ARE RIGHT there are 2 pins that not in the socket but it was not working befor that when i was taking photo it happend befor photo there were in socket correctly i dont know why it's not working also i dont understand the meaning of protected bootloader usually we do programming with AVR and PIC programmer

L6343270499401.jpg

I'm really sad for my MD!!!

[Firelord]

Did you read this: viewtopic.php?f=3&t=1251

[hamedoo]

[quote="Firelord"]Did you read this: viewtopic.php?f=3&t=1251[/quot

I have a AVR programmer that programed my atmega succesfully and ofcourse my PIC with files that i downloaded from site (bin,hex). I dont understand the meaning of protected bootloader. it means i should buy special atmega32 from special place???? I did many projects by ATMEGA32 and AVR,PIC programmer and they were succesful too! I think the PCB has some error in designing maybe!!! Is there anybody for helping me? anyway, I built my MD and now, what should I do?

[Firelord]

The .bin files are encrypted MegaDrum firmware. If you flash ATmega with a programmer using these it won't work. Period.

So you need an ATmega chip with a pre-programmed firmware, which contains a bootloader. You will then be able to update with the .bin files, but not using the programmer, but rather via the USB/MIDI interface.

Look for the 20100516 firmware file (hex) and program that, if you wish to test your MegaDrum. This is an old un-encrypted version of the firmware.

I think the PCB has some error in designing maybe!!!

One cannot rule it out. Your boards may contain faults/shorts/etc. but how would we know.