Problem with firmware getting erased by random!!!

[Synthex]

I'm experiencing "lazy buttons" on my mega. It's like the unit doesn't register every time I push a button.
I'm thinking 47k pullup is too high?
Could this be the case?
Maybe 5-10k is better?
Edit: I bought new buttons that "click". My lazy button problem seems to be gone.

47k pullup is good.
Are you really sure to press your lazy buttons ?

[Synthex]

When you set Megadrum as input and output device, it makes a loop !!!
http://www.megadrum.info/forums/viewtopic.php?f=3&t=151

[slayer666]

I'm experiencing "lazy buttons" on my mega. It's like the unit doesn't register every time I push a button.
I'm thinking 47k pullup is too high?
Could this be the case?
Maybe 5-10k is better?
Edit: I bought new buttons that "click". My lazy button problem seems to be gone.

47k pullup is good.
Are you really sure to press your lazy buttons ?

I'm sure I pressed the button. either way the the buttons that click are way better as they confirm that I've pressed them.
The old buttons were bad quality.

[denis]

Tonight I'm trying to reprogram the atmega since it was erased yerterday.

In ponyprog2000 when I click read device it gives "device missing or unknown device-24" but if I click ignore It reads succesfully and reads 33792bytes, CRC B025h.

When I try to configure bits it gives the same error again and opens the configuration window after a few ignore clicks. But I can not read the bits inorder to change, it gives the same error while tryin to read bits and if I click ignore this time spine appears unselected and I can not start writing the new firmware.

Any idea about what to do?


Also yesterday after Iget firmware update message I disconnected and pluged it again a few times and now it shows squares in the upper row the screen. Today I did the pullup resisto modification also.

In ponyprog:
Device is selected as avr micro-atmega 32.

[Synthex]

Did you follow the instructions from here :
http://www.megadrum.info/faqs.php#Firmware

[denis]

Did you follow the instructions from here :
http://www.megadrum.info/faqs.php#Firmware

Yes sure.. And also plugged the usb cable (tried without plugging it before)

As I said when I click read device gives the error but if I click ignore It reads the pic succesfully. However when it comes to configuring security bits it gives the same error and clicking ignore doesn't work since it can not complete reading the security bits.-spien comes unselected-

I'm sure the settings in prnyprog and cable is ok since I've reprogrammed with tihs setup a mounth ago.

[Synthex]

I'm sure the settings in prnyprog and cable is ok since I've reprogrammed with tihs setup a mounth ago.

If the settings are the same, your Atmega maybe died ...

[denis]

I'm sure the settings in prnyprog and cable is ok since I've reprogrammed with tihs setup a mounth ago.

If the settings are the same, your Atmega maybe died ...

But if I click ignore in the error message after read device command it reads the atmege succesfully. Is it possible if it died?

[Synthex]

But if I click ignore in the error message after read device command it reads the atmege succesfully. Is it possible if it died?

I don't know ... If you already have manages to program it, now there is a problem ...
Do you want that I send you one for test (for free and you send back to me your) ?

[denis]

But if I click ignore in the error message after read device command it reads the atmege succesfully. Is it possible if it died?

I don't know ... If you already have manages to program it, now there is a problem ...
Do you want that I send you one for test (for free and you send me yours) ?

Thanks for the offer but i think its better to wait ofr a solution now. I've lost too much time as you konw=).

May be Dimitri will have an idea.. And tommorrow I'll also try it on a different pc with fresh mind.

Just wanted to complete the box tonight but bad luck=)

By the way I couldn't manage to program it tonight since I couldn't configure the security bits. But ponyprog is able to read the atmega although it gives error in the beginning. I'm writing it again inorder to prevent a misunderstanding