[CODE HELP] resetFirmware() question about gc_n64_usb-v3

[raphnet]

Hello,

Calling resetFirmware() is correct. It will cause a re-enumeration as a side effect of resetting.

Based on what you describe, I think the adapter is simply resetting in a loop.

g_eeprom_data.cfg.mode is an ordinary global variable (See eeprom.c for more info) so unless you are calling eeprom_commit() somewhere, just doing g_eeprom_data.cfg.mode = 0; is not permanent and will not survive a reset. So the firmware probably starts, detects that it's not in the correct mode, then resets, ... and this repeats endlessly.

If you knew this already, and simply did not include the eeprom_commit() call in the code excerpt above for brevity, then I'm sorry but I have no idea.

One thing that comes to mind however, since you mention that sometimes it works (i.e. unpredictable behavior), is how your switch is wired to the input pin. Is it a SPST switch to ground? In that case, did you enable the internal pull-up? If the pin is sometimes floating (not connected), the result of PIND & 0x10 will be unpredictable. (Sorry if this is obvious - I don't know how much electronics experience you have...)

[Dignity1337]

Thank you so much. Indeed I forgot to call the eeprom_commit() function. It now works flawlessly. Thanks for your help.