Hi
what should I put in the menuconfig for BIGTREETECH-GTR V1.0, if I use it with the Raspberry pi GPIO
The processor is STM32f407 but I don’t know what to put in the bootloader offset section, or what option to choose in the communication interface
when connecting the board with uart1 it tells me
ls: cannot access ‘/ dev / serial / by-id / *’: No such file or directory
If I connect it with usb, it does leave me but it should be possible to connect the board with uart
Sure you can but it is way more complicated:
- Depending on the used features of your board (TFT, I2C etc), chose which pins to use on your GTR
- Compile your firmware accordingly
- Prepare the RPi to release the serial pins, e.g. turn off BT overlay, turn off serial console, enable UART
- Connect to the RPI pins, for a RPI3 most commonly GPIO14/15
- Connect Klipper’s mcu via
ttyS0orttyAMA0(depending on your RPi version and RPi config settings)
after doing all octoprint it gives me the following error
Changing monitoring state from “Offline” to “Detecting serial connection”
Performing autodetection with 7 port/baudrate candidates: /tmp/printer@115200, /tmp/printer@250000, /tmp/printer@230400, /tmp/printer@57600, /tmp/printer@38400, /tmp/printer@19200, /tmp/printer@9600
Trying port /tmp/printer, baudrate 115200
Connecting to port /tmp/printer, baudrate 115200
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0x67fb0330, open=True>(port=’/tmp/printer’, baudrate=115200, bytesize=8, parity=‘N’, stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0125
Recv: // Shutdown due to M112 command
Recv: // Once the underlying issue is corrected, use the
Recv: // “FIRMWARE_RESTART” command to reset the firmware, reload the
Recv: // config, and restart the host software.
Changing monitoring state from “Detecting serial connection” to “Operational”
Recv: // Printer is shutdown
Recv: !! Shutdown due to M112 command
Send: N0 M110 N0125
Changing monitoring state from “Operational” to “Error”
Send: M112
Send: N1 M11232
Send: N2 M104 T0 S035
Send: N3 M140 S0*102
Changing monitoring state from “Error” to “Offline after error”
Connection closed, closing down monitor
Strange combination of (error) messages. Please attach your klippy.log
klippy.log (9.8 KB)
The log is hsowing your problem more clearly:
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/ttAMA0: [Errno 2] No such file or directory: '/dev/ttAMA0'
Apparently connecting the board directly to the RPi did not work. One of the steps as outlined above did not work. If you successfully activated and freed the serial ports on your RPi either ttyS0 or ttyAMA0 has to exists.
You can check on the RPi console with
ls -al /dev/ttyAMA0
ls -al /dev/ttyS0
In addition you have a typo in your config: The serial port is /dev/ttyAMA0 and not /dev/ttAMA0
I have already corrected that part, but it still gives me an error:
Connected to: Serial<id=0x69880830, open=True>(port=’/tmp/printer’, baudrate=115200, bytesize=8, parity=‘N’, stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
that’s the part that changed from the last mistake
klippy.log (21.2 KB)
Your errors from Octoprint are completely unrelated and at best a consequence of the underlying problem. You always have to check your klippy.log:
mcu 'mcu': Starting serial connect
mcu 'mcu': Timeout on connect
In your chosen configuration the Klipper Host on the RPi can’t get a connection to your board. Reasons could be:
- Wrong cabling → Have you connected RX to TX and vice versa?
- Wrong firmware build
- Wrong pins on the board
- Correct pins but wrong UART bus, i.e. clash with other periphery of the board
- Wrong configuration of the RPi Linux, i.e. serial console not deactivated etc. (Needs RPi restart, btw.)
See, e.g. pi 3 - How do I make serial work on the Raspberry Pi3 (PiZeroW, Pi4 or later models) - Raspberry Pi Stack Exchange or dozens of other resources for more detailed information.
I’ve gotten to this point in the documentation
sudo service klipper stop
make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
sudo service klipper start
but according to the GTR example file this does not work:
The “make flash” command does not work on the GTR. Instead,
after running “make”, copy the generated “klipper/out/klipper.bin” file to a
file named “firmware.bin” on an SD card and then restart the GTR
with that SD card.
so I copied the .bin file to a SD card and rebooted.
To configure I added /tmp/printer to serial connections in octoprint, set the Behavior to Cancel any ongoing prints but stay connected to the printer , tried to connect to the board with the /tmp/printer serial port…no connection. I’m also getting ls: cannot access ‘/dev/serial/by-id/*’: No such file or directory when running ls /dev/serial/by-id/* after loading the klipper.bin. I’ve tried both Communication interface (USB (on PA11/PA12)) and Communication interface (Serial (on USART1 PA10/PA9)) in make menuconfig both with the same result.
I’m stuck at the point where I can start to configure Octoprint to use Klipper because I cannot connect to the BTT GTR board after loading the klipper firmware. Any insight as to why this is happening? klippy.log (39.1 KB)