Skip to content
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

Open
SzaryPB opened this issue May 9, 2023 · 8 comments
Open

Pi 4B with Cheetah 3.0 problem #1

SzaryPB opened this issue May 9, 2023 · 8 comments

Comments

@SzaryPB
Copy link

SzaryPB commented May 9, 2023

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?

@SzaryPB
Copy link
Author

SzaryPB commented May 10, 2023

Problem solved.
I've reinstall mainsailos, make new firmware and now I see motherboard

@Minims
Copy link

Minims commented May 15, 2023

@SzaryPB having same issue. What option do tou set for USB and BOOTloader in menuconfig for Cheetah V3 ?

@SzaryPB
Copy link
Author

SzaryPB commented May 16, 2023

@Minims Hi! I create firmware without Bootloader and use STMCubeProgrammer to insert firmware into motherboard.
the same settings as here: https://github.com/FYSETC/FYSETC-Voron-0.2-Pro/blob/main/Firmware&OS/makemenuconfig.jpg?raw=true

@Minims
Copy link

Minims commented May 16, 2023

Oh thanks @SzaryPB, I miss this thing.
So now I can see my serial-id, I have updated in klipper config, but klipper still saying it can't connect to MCU, digging...

@RansomScientist
Copy link

Oh thanks @SzaryPB, I miss this thing. So now I can see my serial-id, I have updated in klipper config, but klipper still saying it can't connect to MCU, digging...

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 "[...]
Did you find any solution?

@Minims
Copy link

Minims commented May 21, 2023

I finally make it work with
make flash FLASH_DEVICE=xxxx:xxxx
Which the lsusb device id ,
You may have it in the bash history.

on my side i will make a new sdcard with klipper once.i have finish my build

@RansomScientist
Copy link

RansomScientist commented May 21, 2023

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)

@yzheka
Copy link

yzheka commented May 22, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants