search

bigtreetech / EBB

481 stars 103 forks source link

Sb2209 usb v1 no boot mode #135

Open aee74 opened 1 month ago

aee74 commented 1 month ago

I’ve tried to hold down boot press reset and let go of boot but no change when I loom at lsusb

how to get into boot mode. Is the board defective?

Aibehn commented 1 month ago

I'm having the same problem.

looxonline commented 1 month ago

Could you both list your lsusb results before and after the process?

Aibehn commented 1 month ago

Could you both list your lsusb results before and after the process?

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 1d50:614e OpenMoko, Inc. stm32h743xx Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have a SKR3 EZ connected. I will try disconnecting everthing. This produced no changes. Just removed stm32 line.

I have to mention that I checked continuity between DP & DM pins on the toolhead board all the way to the USB-A connector.

looxonline commented 1 month ago

Could you both list your lsusb results before and after the process?

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 1d50:614e OpenMoko, Inc. stm32h743xx Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have a SKR3 EZ connected. I will try disconnecting everthing. This produced no changes. Just removed stm32 line.

I have to mention that I checked continuity between DP & DM pins on the toolhead board all the way to the USB-A connector.

That lsusb is before or after going into boot mode or is there zero difference between the two?

Aibehn commented 1 month ago

``

Could you both list your lsusb results before and after the process?

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 1d50:614e OpenMoko, Inc. stm32h743xx Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have a SKR3 EZ connected. I will try disconnecting everthing. This produced no changes. Just removed stm32 line. I have to mention that I checked continuity between DP & DM pins on the toolhead board all the way to the USB-A connector.

That lsusb is before or after going into boot mode or is there zero difference between the two?

ZERO difference

looxonline commented 1 month ago

Also what USB-C cable are you using between the SBC and the adapter PCB? Is it the one supplied with the part or your own? Have you tried using other cables?

Aibehn commented 1 month ago

Also what USB-C cable are you using between the SBC and the adapter PCB? Is it the one supplied with the part or your own? Have you tried using other cables?

I'm using the one supplied. But I did also test a different usb-c to usb-a cable. Same results.

looxonline commented 1 month ago

OK, fire off an email to luke@bigtree-tech.com and I'll ask the support team to look deeper into your case.

Aibehn commented 1 month ago

Just a quick update because things escalated quickly.

I was testing it with another host, an RPi2B that I had lying around. At first, no changes, just the same result: no way to get it into DFU mode or recognized by the RPi.

At first, it seemed that the RPi was having power problems. I noticed that plugging in the USB-C cable would cause the power status LED on the RPi to flicker. But then it got worse.

I tried another USB-C cable, and at first, nothing seemed to happen—everything was fine, no magic smoke. After that, it started to smell, and I noticed that the SB2209 was getting hot. Still, no lsusb device, and the status LED was fine.

I tried one more time with the boot/rst button combo, and the LEDs just went off—no magic smoke, nothing. Then I noticed the RPi power LED going crazy. The SMSC chip controller (USB hub & LAN) was getting extremely hot. I disconnected everything, but it was too late.

The RPi2B doesn't boot anymore. The USB hub controller chip gets extremely hot.

The SB2209 doesn't show any LED status anymore. It gets 24V through the adapter board, but nothing happens. No heated components either.

At least It was not the RPi4 and a RPi2B that died. I not hooking anything without a USB isolator or something similar.

tl;dr: SB2209 died and It killed a RPi2B on the process.

looxonline commented 1 month ago

Just a quick update because things escalated quickly.

I was testing it with another host, an RPi2B that I had lying around. At first, no changes, just the same result: no way to get it into DFU mode or recognized by the RPi.

At first, it seemed that the RPi was having power problems. I noticed that plugging in the USB-C cable would cause the power status LED on the RPi to flicker. But then it got worse.

I tried another USB-C cable, and at first, nothing seemed to happen—everything was fine, no magic smoke. After that, it started to smell, and I noticed that the SB2209 was getting hot. Still, no lsusb device, and the status LED was fine.

I tried one more time with the boot/rst button combo, and the LEDs just went off—no magic smoke, nothing. Then I noticed the RPi power LED going crazy. The SMSC chip controller (USB hub & LAN) was getting extremely hot. I disconnected everything, but it was too late.

The RPi2B doesn't boot anymore. The USB hub controller chip gets extremely hot.

The SB2209 doesn't show any LED status anymore. It gets 24V through the adapter board, but nothing happens. No heated components either.

At least It was not the RPi4 and a RPi2B that died. I not hooking anything without a USB isolator or something similar.

tl;dr: SB2209 died and It killed a RPi2B on the process.

Please take the exact connection that you have, remove the EBB USB from one end and the Pi from the other and measure to see if the data pins are shorting to any of the power pins or each other.