BTT 42 does not flash.
Connected via USB. Octopus V1.1 flashed fine. Boot button, reset button does nothing. Is a second jumper required?
11 Replies
When you say "does not flash", do you mean it never lets you flash via DFU in the configurator?
@miklschmidt Yes. I’ve tried 2 usb cords. A third is coming today. I am also going to try the USB power off while holding the boot button, in case the reset button is not working. I trust your RatOS.
How strange, haven't heard that before. Which model is it? 1.0, 1.1 or 1.2?
@miklschmidt 1.2
Can you try connecting to the pi and running
lsusb with the EBB connected before and after you've held down the boot button and clicked reset?
like this:
then hold boot and click reset
workin on it
Windows 11 updated today and suddenly I cant get into Mainsail or Putty.
Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2c99:0002 Prusa Original Prusa i3 MK3
Bus 001 Device 003: ID 0c45:6369 Microdia USB 2.0 Camera
Bus 001 Device 005: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
@miklschmidt I'm going to start over. Reinstall RatOS. Go from there.
@miklschmidt from another PI, not RatOS
Yes. The Pi running RatOS is suddenly not responding. I guess I’ll have to reinstall RatOS on it.
Check that. Got mainsail so putty should now work.
Before boot and reset.
Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1d50:614e OpenMoko, Inc. stm32f446xx Bus 001 Device 003: ID 0c45:6369 Microdia USB 2.0 Camera Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After boot and reset.Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1d50:614e OpenMoko, Inc. stm32f446xx Bus 001 Device 003: ID 0c45:6369 Microdia USB 2.0 Camera Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Ran this commandpi@ratos:~ $ ls /dev/serial/by-id/* /dev/serial/by-id/usb-Klipper_stm32f446xx_btt-octopus-11-if00 Only finds the main board. Found another USC A to USB C. No change. Still DFU not detected.
Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1d50:614e OpenMoko, Inc. stm32f446xx Bus 001 Device 003: ID 0c45:6369 Microdia USB 2.0 Camera Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After boot and reset.Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1d50:614e OpenMoko, Inc. stm32f446xx Bus 001 Device 003: ID 0c45:6369 Microdia USB 2.0 Camera Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Ran this commandpi@ratos:~ $ ls /dev/serial/by-id/* /dev/serial/by-id/usb-Klipper_stm32f446xx_btt-octopus-11-if00 Only finds the main board. Found another USC A to USB C. No change. Still DFU not detected.
The EBB42 never shows up. Is it powered?
Yes. Both green and blue LEDs are lit.
I have a USB 3.2 cord coming today. Maybe that will work.
Stupid question, you connected the EBB 42 to the Raspberry Pi right? There was a user the other day that connected it to the octopus, that's why i ask.
Yes, of course but in this space, no question is stupid. I know. I've asked plenty.
@miklschmidt The new USB cable did the trick. Guess 3.2 is the way to go.
Wow that's weird! I have used all sorts of crappy usb cables with no issues, but good you got it sorted!!