# SKR3 V3 Problem 'ls /dev/serial/by-id/\`

**URL:** <https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257>\
**Category:** General Discussion\
**Created:** [October 7, 2024, 2:23pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257 "2024-10-07T14:23:48Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Seif\_Tama](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@Seif\_Tama](https://klipper.discourse.group/u/Seif_Tama)\
**Post date:** [October 7, 2024, 2:23pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/1 "2024-10-07T14:23:48Z")

</div>

### Basic Information:

Printer Model: Alfawise u20  
 MCU / Printerboard: SKR3 V3 STM32H723  
 klippy.log

### Description :

Hey everyone,

I’ve got an SKR3 board, and I feel like the millionth person facing issues with it. Here’s the situation:

I followed the standard flashing process with the `.bin` file, but ran into problems at a key point.

# Issue 1:

When I flash the stock `firmware-usb.bin` from the official GitHub repo, everything goes smoothly.  
The file changes to `FIRMWARE.cur`, and the status LED turns off as expected.

However, when I try flashing Klipper (after renaming it to `firmware.bin`), the status LED never turns off.  
The file gets renamed to : `FIRMWARE.cur`, but something’s still wrong, and the board doesn’t seem to complete the process.

# Issue 2:

Assuming the flashing with the original file worked, I tried moving forward.  
I used the command `ls /dev/serial/by-id/` to check for the device, but it doesn’t seem to exist.  
When I ran `ls /dev`, there’s no “serial” listed either.

Here’s what I’ve already tried:

1. Swapped USB cables and confirmed the one I’m using supports data transfer.
2. Checked the Raspberry Pi’s USB ports with other devices—no issues there; they’re detected with `lsusb`. The only thing not showing up is the SKR3.
3. Confirmed that the CAN/USB switch is in the correct (released) position.

At this point, I gave up on USB and tried connecting the SKR3 to the Pi via UART:

- PA10 \> GPIO15
- PA9 \> GPIO14
- GND \> GND

Even with the `.bin` file from GitHub, it didn’t work.

Does anyone have any suggestions on what to try next? I’d appreciate any help!

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [October 7, 2024, 4:09pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/2 "2024-10-07T16:09:11Z")

</div>

> [@Seif\_Tama](#):
>
> SKR3 V3

Please check what kind of MCU is actually used on your board. It seems that BTT is silently shipping two different variants:

- STM32H7 **23**
- STM32H7 **43**

While both seem “pin compatible”, i.e. the settings in the printer.cfg are the same, they need different handling during `make menuconfig`.

---

<div class="post-metadata">

**Author:** ![Seif\_Tama](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@Seif\_Tama](https://klipper.discourse.group/u/Seif_Tama)\
**Post date:** [October 7, 2024, 6:02pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/3 "2024-10-07T18:02:59Z")

</div>

Hello friend ,  
yes that’s correct, mine is 723

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [October 7, 2024, 6:10pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/4 "2024-10-07T18:10:45Z")

</div>

Please be very precise with the board you have. There is:

- BTT SKR 3 → [GitHub - bigtreetech/SKR-3](https://github.com/bigtreetech/SKR-3)
- BTT SKR MINI E3 V3.0 → [BIGTREETECH-SKR-mini-E3/hardware/BTT SKR MINI E3 V3.0 at master · bigtreetech/BIGTREETECH-SKR-mini-E3 · GitHub](https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/tree/master/hardware/BTT%20SKR%20MINI%20E3%20V3.0)

---

<div class="post-metadata">

**Author:** ![Seif\_Tama](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@Seif\_Tama](https://klipper.discourse.group/u/Seif_Tama)\
**Post date:** [October 7, 2024, 6:14pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/5 "2024-10-07T18:14:33Z")

</div>

![aef7399a-6dd0-4626-8cd4-c880f0011cce](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/7/77dcf516c1f8f4a1bb909927ab4d6280037cf83d.jpeg)  
no, as mentioned it’s a BBT SKR 3

additional information :  
i tried what was mentioned here [Provide support/documentation for STM32H723 variant · Issue #48 · bigtreetech/SKR-3 (github.com)](https://github.com/bigtreetech/SKR-3/issues/48)  
but with no success

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [October 7, 2024, 6:22pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/6 "2024-10-07T18:22:24Z")

</div>

Try following settings:

 ![grafik](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/5/5982921210b8a06242f65a9b78967aae1c826012.png)

Copy the `firmware.bin` to a SD card and reboot the board.

---

<div class="post-metadata">

**Author:** ![Seif\_Tama](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@Seif\_Tama](https://klipper.discourse.group/u/Seif_Tama)\
**Post date:** [October 7, 2024, 7:13pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/7 "2024-10-07T19:13:40Z")

</div>

Great news—  
everything is working now! I’d like to share what I did in case it helps someone else.  
To summarize, I found myself stuck in **DFU mode** for reasons I still don’t understand, which caused the LED status to remain on.  
I generated the .bin file and successfully loaded it using the STM32 programmer, as shown in picture “a5.”

 ![a4](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/a/af5c161dcb14926f7e96ad4dee23f9c5114d7995.png)  
 ![a5](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/c/c0b336d787c490fe96af3d8a64a0d91e01796085.png)

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [October 8, 2024, 4:17pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/8 "2024-10-08T16:17:45Z")

</div>

Good job.  
So the above firmware config worked?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [December 7, 2024, 4:17pm UTC](https://klipper.discourse.group/t/skr3-v3-problem-ls-dev-serial-by-id/19257/9 "2024-12-07T16:17:54Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
