Quote:
Originally Posted by matthey
It's almost certainly a bug in WHDload or whatever code is used for co-processor identification.
|
Not necessarily, it can have many reasons, my bet is that either the slave is buggy (wrong keyboard/interrupt handling maybe) so that "corrupted" code is executed or a problem with the maxtransfer settings.