I have problem but I don't know where

[jman 31]

Can you show a picture of the trace side of the pcb showing the problem areas?

[kenben]

i think this BRD img will be better than the image of the actual PCB because components are already soldered... so in the diagram, R16 is connected to the VCC .

[kenben]

hey guys...i have got a new problem that i have been trying to figure for days.... when i programmed the atmega, i got text on the LCD "fw updater 16MHz clock-up down-ok" but then i could not change the clock by the using the keyboard. Dmitri pointed out my mistake: i was using the wrong schematic for the keyboard connector. Now i have fixed the problem yet no luck changing the setting.

i am using synthex's schematic 2.7v. i have checked the connector over 20 times for errors. i got the PCB etched so i assume there are no errors in the traces. i have checked the signals for continuity from ICSP ATmega, keyboard to Atmega. I was thinking the atmega might be faulty then again if it was it would not show me the above text on the LCD...right?

i am so close to get this thing working....any help is greatly appreciated....thanks

[jman 31]

What is the problem exactly? Is r16 not supposed to be hooked to vcc? If not just cut the trace with a sharp knife.

[kenben]

jman 31....thanks but dont worry about that anymore ...lol.... that was just a mirror problem...it is fixed.....

the main problem is this new topic i posted above

hey guys...i have got a new problem that i have been trying to figure for days.... when i programmed the atmega, i got text on the LCD "fw updater 16MHz clock-up down-ok" but then i could not change the clock by the using the keyboard. Dmitri pointed out my mistake: i was using the wrong schematic for the keyboard connector. Now i have fixed the problem yet no luck changing the setting.

i am using synthex's schematic 2.7v. i have checked the connector over 20 times for errors. i got the PCB etched so i assume there are no errors in the traces. i have checked the signals for continuity from ICSP ATmega, keyboard to Atmega. I was thinking the atmega might be faulty then again if it was it would not show me the above text on the LCD...right?

i am so close to get this thing working....any help is greatly appreciated....thanks

[kenben]

never mind guys ...i fixed the problem....had to use a different bootloader

[kenben]

alright..i m back with a new problem... if anyone could help me with this or direct me to the right forum...it would be great...

So i uploaded the latest bootloader to the atmega644. Now i see "<Megadrum.info> (c)D.Skachkov ". it stays on for a few seconds and then displays the VU meter. I can browse through different setting with the left and right buttons and change them with up and down buttons.

Now i unplug and replug the usb and Power up MegaDrum up while holding the key LEFT pressed.. i dont see this text "fw updater 16MHz clock-up.down-ok", it quickly goes to different options (left button still pressed)....any suggestions?

[Firelord]

alright..i m back with a new problem... if anyone could help me with this or direct me to the right forum...it would be great...

So i uploaded the latest bootloader to the atmega644. Now i see "<Megadrum.info> (c)D.Skachkov ". it stays on for a few seconds and then displays the VU meter. I can browse through different setting with the left and right buttons and change them with up and down buttons.

Now i unplug and replug the usb and Power up MegaDrum up while holding the key LEFT pressed.. i dont see this text "fw updater 16MHz clock-up.down-ok", it quickly goes to different options (left button still pressed)....any suggestions?

I think you're still confused with the firmware files.

This is the bootloader archive: http://www.megadrum.info/sites/default/ ... loader.zip
This is the main firmware archive (current): download/file.php?id=2037

You obviously use a hex file from the latter and so you actually don't have a bootloader on your chip.

[kenben]

You obviously use a hex file from the latter and so you actually don't have a bootloader on your chip.

yea...you are right thats what i did...I m a bit confused though, do we ever use the hex file corresponding to my atmega that in the megadrum_20100516.zip file? if so when and where....

[Firelord]

You obviously use a hex file from the latter and so you actually don't have a bootloader on your chip.

yea...you are right thats what i did...I m a bit confused though, do we ever use the hex file corresponding to my atmega that in the megadrum_20100516.zip file? if so when and where....

We usually use a syx file from that archive.

The thing is, we use the bootloader for convenience so we don't have to use a programmer to update the firmware all the time. If you use the hex firmware from that archive (megadrum_20100516.zip) then you will always need to use a programmer to update the firmware. With syx though you can update via USB-MIDI or MIDI I/O.