Megadrum stuck after 15-20 secs with new atmega
Posted:
Wed Sep 29, 2010 5:07 amby wegi
I received new atmega from Dmitri yesterday, but I've got some problems with it
I placed it with success in a socket, and connected it via USB to PC.
However, after some time and hits (around 15-20secs) it stuck, and PC no longer receives signals from MD :/ (MD still detects hits as I can see that on the display).
I tried to reinstall the latest firmware, but it didn't help...
Anyone can help?
Thanks in advance,
Dominik
Re: Megadrum stuck after 15-20 secs with new atmega
Posted:
Wed Sep 29, 2010 9:42 amby dmitri
wegi wrote:I received new atmega from Dmitri yesterday, but I've got some problems with it
I placed it with success in a socket, and connected it via USB to PC.
However, after some time and hits (around 15-20secs) it stuck, and PC no longer receives signals from MD :/ (MD still detects hits as I can see that on the display).
I tried to reinstall the latest firmware, but it didn't help...
Atmega and its firmware have nothing to do with USB functionality. Judging from a very short description that you provided you have a problem with PIC.
Re: Megadrum stuck after 15-20 secs with new atmega
Posted:
Wed Sep 29, 2010 11:22 amby wegi
But you've mentioned in bug fix:
1. Fixed a serious bug (which was there since 20100126) which, for no apparent reason, could cause some random inputs to get stuck and not responding to hits and requiring power cycling.
So maybe it has something common with firmware?
However, I will check it on another PC and will make a report.
Dominik
Re: Megadrum stuck after 15-20 secs with new atmega
Posted:
Wed Sep 29, 2010 11:34 amby dmitri
wegi wrote:But you've mentioned in bug fix:
1. Fixed a serious bug (which was there since 20100126) which, for no apparent reason, could cause some random inputs to get stuck and not responding to hits and requiring power cycling.
So maybe it has something common with firmware?
Judging from your description -
wegi wrote:However, after some time and hits (around 15-20secs) it stuck, and PC no longer receives signals from MD :/ (MD still detects hits as I can see that on the display).
- it has nothing to do with it.