Hi All,
I'm attempting to turn a spare Elegoo R3 I have into a rudimentary ARGB controller using the Hoodloader2 Bootloader, allowing me to use the 16u2 mcu as its own HID. After a successful attempt getting hoodloader2 burned and uploading the necessary Corsair Lighting Protocol sketches to the two MCUs, the board correctly identified as a Corsair lighting device in my PCs hardware settings and on the RGB software.
On attempting to modify the sketch to add some debugging (the board wasn't sending data to my LED Strips), I'm now getting the avrdude error stk500_recv(): programmer is not responding. I followed the Hoodloader2 guidance on using the reset pins to enter bootloader mode, but to no avail, the error persists.
My understanding is that this error can occur if the incorrect board is selected, however I used the same settings as described in the CLP instructions that had worked to upload the sketches prior, leading me to believe that I had potentially corrupted something.
I attempted to reflash Hoodloader2 using my Arduino R3, again successfully, but I am still unable to upload to the board. I tried uploading the basic Blink sketch, and was able to upload that using the Hoodloader2 16u2 board, which works fine, but as soon as I go back to the Hoodloader2 Uno board, the error returns. I am thinking that I have somehow broken the comms link between the 16U2 and the 328 mcus, and my pc can no longer communicate with the latter at all.
In the absence of any other advice, is it possible for me to force the 16u2 back to its original bootloader, returning the elegoo to its factory state?