-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pi 4B with Cheetah 3.0 problem #1
Comments
Problem solved. |
@SzaryPB having same issue. What option do tou set for USB and BOOTloader in menuconfig for Cheetah V3 ? |
@Minims Hi! I create firmware without Bootloader and use STMCubeProgrammer to insert firmware into motherboard. |
Oh thanks @SzaryPB, I miss this thing. |
I have the same problem, I have the correct id in printer.cfg but klippy.log still tells me "mcu 'mcu': Unable to open serial port: [Errno 2] could not open port "[...] |
I finally make it work with on my side i will make a new sdcard with klipper once.i have finish my build |
I made it work now by using ls /dev/serial/by-path/ instead of /by-id/ and using that in the printer.cfg which for some reason works but the other way does not. Then I forgot to flash the voron display and setting the path in the config as well, just for anyone else who may have the same problem. (Also mind the connection picture for the display, black to the 5v marking on the pcb and red to the gnd marking, weird but that was also an issue) |
seems there is some issue with 64 bit os for pi. I can't see /dev/serial/by-id/ but there is a device inside /dev/serial/by-path/ after I reinstalled os to raspberry pi lite 32 bit I can see the board under /dev/serial/by-id |
Boards are connected via dupont and USB-c - microUSB-C, after typing lsusb in MobaXterm where is no motherboard showing.
5V, 12V 24V leds are ok.
USB cable is OK, I wrote firmware again via STM32CubeProgrammer but it doesn't help.
What I'm doing wrong?
The text was updated successfully, but these errors were encountered: