Based on your description it sounds like the debugger chip is what was corrupted. The USB mass storage device is what the main processor will look like by default. The first time you update the firmware with the tool it has to update the debugger first, and if this doesn't update properly the tool will not find the board. I was able to reproduce this on my end, and it shouldn't be a problem to fix. Try the following:
Open a command prompt (go to
Start and type
cmd in the search bar).
For 32-bit systems run this command (including quotes):
Code:
"C:\Program Files\FRC Gamepad Tool\Tools\mspdebug\mspdebug.exe" tilib --allow-fw-update
For 64-bit systems run this command (including quotes):
Code:
"C:\Program Files (x86)\FRC Gamepad Tool\Tools\mspdebug\mspdebug.exe" tilib --allow-fw-update
If it works correctly you will see it load new firmware, and you will also see an error that says something like:
Code:
tilib: MSP430_VCC: Internal error (error = 68)
tilib: device initialization failed
At this point you should be able to rescan with the tool and see/program the board.