Voron 0.1 Display - no /dev/serial directory

[TitusADuxass]

Greetings all and best wishes for 2024,

So I am trying to get the display working on my v0.1,

It's a STM32....42F.

I flashed it, the flash has been successful but I cannot find the serial ID as there is no /dev/serial folder.

I had this problem on my V2.4 but I cannot remember how I fixed it. Googling it has led me down many rabbit holes.

Does anyone have a solution or can anyone point me in the right direction.

MfG 

TAD

[Dirk]

The flashing looks pretty straight forward Klipper flashing...

I also had the can-not-find / does not exist, with that command, and for me running these fixes worked.

 

 

 

[TitusADuxass]

1 hour ago, Dirk said:

The flashing looks pretty straight forward Klipper flashing...

I also had the can-not-find / does not exist, with that command, and for me running these fixes worked.

Thanks Dirk,

There was no buggy udev found but a parsing file was missing a description field.

[Repman]

Had the same issue after installing bullseye. It is a missing entry in the udev rules.

Take a look at this to find the solution: https://www.reddit.com/r/debian/comments/1331wlr/devserialbyid_suddenly_missing/

I fixed it with replacing my "/lib/udev/rules.d/60-serial.rules" with the current one from Github: https://github.com/systemd/systemd/blob/main/rules.d/60-serial.rules

Regards Repman

[TitusADuxass]

15 hours ago, Repman said:

Had the same issue after installing bullseye. It is a missing entry in the udev rules.

Take a look at this to find the solution: https://www.reddit.com/r/debian/comments/1331wlr/devserialbyid_suddenly_missing/

I fixed it with replacing my "/lib/udev/rules.d/60-serial.rules" with the current one from Github: https://github.com/systemd/systemd/blob/main/rules.d/60-serial.rules

Regards Repman

Thanks. I'll give it a try.

[BallisticTech]

Thing I see the most is the device didn't get reset and taken out of boot mode.

In addition to the command you ran you can run an `lsusb`. It'll show all currently attached USB devices.

If the device has been correctly flashed and reset it'll show up as something like `OpenMoko, Inc. stm32f042x6`

 

If it either isn't present on this list or still listed as `in DFU Mode` then there's something up with the device.



Removing the boot jumper, powering the system on off a few times, pressing the STM32 boards reset button, and/or restarting the pi can help.

[TitusADuxass]

11 hours ago, BallisticTech said:

Thing I see the most is the device didn't get reset and taken out of boot mode.

In addition to the command you ran you can run an `lsusb`. It'll show all currently attached USB devices.

If the device has been correctly flashed and reset it'll show up as something like `OpenMoko, Inc. stm32f042x6`

If it either isn't present on this list or still listed as `in DFU Mode` then there's something up with the device.



Removing the boot jumper, powering the system on off a few times, pressing the STM32 boards reset button, and/or restarting the pi can help.

I can get it to show up in DFU mode, if I then remove the jumper and do a reset it does not appear.

 

[BallisticTech]

@TitusADuxass Interesting. I had once when I flashed my display I accidently put the wrong communication settings in the menuconfig. I think I had it set to UART pins instead of USB.
https://github.com/VoronDesign/Voron-Hardware/raw/master/V0_Display/Images/Menuconfig_Base_Options.png

[TitusADuxass]

18 hours ago, BallisticTech said:

@TitusADuxass Interesting. I had once when I flashed my display I accidently put the wrong communication settings in the menuconfig. I think I had it set to UART pins instead of USB.
https://github.com/VoronDesign/Voron-Hardware/raw/master/V0_Display/Images/Menuconfig_Base_Options.png

Aaah! Thank you!

I have found one of my failures - I had the comm interface set to CAN.

It showed up (with lsusb) as  OpenMoko stm32f042x6 and the red LED was on, I rebooted and now it still shows up with lsub but there's nothing on the display.

I think I'll have start from the beginning and try again.

 

[Titus A Duxass]

Before anyone gets more confused that I am - I appear to have two accounts on here - when I login with my works laptop I am TitusADuxass, when I use my private laptop I am Titus A Duxass. I'll have to talk to the admins and get this sorted. Anyway back to the display problem.

I fixed it!! 

During one of the final flashing attempts I noted the errror that /dev/serail/by-id could not be found.

I manually created the missing directory serial (and it's sub-directory - by-id) and restarted the whole process - it worked.