01-16-2021, 11:35 AM
(01-16-2021, 06:04 AM)Ralim Wrote:(01-15-2021, 07:51 PM)psychedup Wrote:I wonder if that means it is "soft bricked"? I assume I would need the breakout board to recover from that, but is there any way for me to confirm that it's not a hardware problem first? Or what would be the next logical troubleshooting step?
- If I leave it unplugged for a while (like 10 minutes or so) and then plug it into the PBP, in dmesg I see something like:
[ +1.360001] usb 2-1-port1: Cannot enable. Maybe the USB cable is bad?[ +0.000384] usb 2-1-port1: attempt power cycle(but not the usual message with the USB vendor/device id's like it showed earlier)
- If I hold down "-" while plugging it in, nothing shows up at all.
(1) This is normal as the main firmware does not implement USB (so the computer will see no response).
(2) The bootloader that you trigger with the "-" is burned into the rom of the MCU so you can erase it (as far as I'm aware).
I would suggest trying a different cable / port if you can first (as some cables are not amazing quality, and the mcu isnt amazing usb driving either i suspect).
Also, try holding the "-" when you plug it in, and then continue to hold it for 10 seconds or so. On some devices I have found that it can take a bit for the ROM to initalise and set itself up correctly.
I have found it helpful to run dmesg -wH to watch dmesg while i connect the unit so i can see whats going on.
Yeah dmesg -Hw is what I have been watching. I've tried at least 3 different cables, on multiple PC's/SBC's/ports. They seem to detect that something was plugged in, but nothing else shows up, even if I keep "-" held down for 60 seconds. And of course "dfu-util -l" doesn't find anything.
