Unable to enter bootloader mode | Intech Studio
💬 general Grid

Unable to enter bootloader mode

virtualHC
virtualHC · · 8 replies

I just received two new modules (PBF4 and EN16) and I'm unable to get them to work in bootloader mode. This is what I did and what I get:

  1. Plugged my two chained modules to my desktop computer and the LEDs on both became illuminated
  2. Opened Grid Editor and it right away showed a warning at the top about firmware mismatch
  3. I unplugged the modules and plugged the PBF4 module while pressing the utility button, the LEDs turned on red then immediately switched to green
  4. The Grid Editor showed "waiting for bootloader to enumerate" but got stock there and froze
  5. I then force closed Grid Editor and attempted to do a manual firmware update by re-plugging the device while holding the button. The LEDs again turned on and changed from red to green
  6. An external drive appeared in Windows Explorer but attempting to open it gave me an error that said "The request could not be performed because of an I/O device error"
  7. In the device manager I can see an Adafruit device under storage devices but there are no volumes defined
  8. I tried the pervious steps with different USB ports but got the same results
  9. I tested the manual bootloader process with my other EN16 device but got the same results
  10. Both modules otherwise work normally and moving the pots or faders makes the virtual ones move in Grid Editor

Replies (8)

kkerti kkerti ·

To me at first sight the Adafruit UF2 device identification seems off - but I used windows a while back with Grid. Removing the driver from Device Manager might be worth a shot.

virtualHC virtualHC ·

So if you are not using Adafruit components in your devices, then I'm suspecting it might have to do with another device (head tracker) that I've used and has Adafruit components. I'll try removing the driver, thank you!

kkerti kkerti ·

We're using ESP32 as primary microcontroller unit and a raspberry co-processor. I don't recall an adafruit component.

kkerti kkerti ·

But I might be mistaken and my peers will be online only tomorrow! So if you are unsure, you can wait until then.

virtualHC virtualHC ·

I just deleted that driver but when I reconnect the device Windows identifies it again as an Adafruit UF2

virtualHC virtualHC ·

I was able to successfully update the firmware using a different Windows computer (laptop). On that computer, the device was also recognized as Adafruit but it was successfully mounted as an external drive. Grid Editor also detected it and successfully updated the firmware. It seems to be an issue with my desktop computer. Let me know if you have any suggestions on how I could fix this problem on my desktop.

kkerti kkerti ·

@user to your attention, I remember a recent case with driver mismatches (Android Studio)

narayb narayb ·

That's unrelated, as in that case the normal firmawre operation was hijacked by the Android ADB component on Win11. Specifically the serial driver.

Discord

View on Discord

This post is from the Intech Studio Discord community.

Open thread →