OzzieOrca
commented
2 years ago I flashed a build to use UART today and configured the Pi for UART (per https://github.com/FYSETC/FYSETC-SPIDER/blob/main/firmware/Klipper/Connect%20RPI%20uart.md). ls /dev/ttyAMA0 seems to work but Klipper still can't connect.
My Klipper printer.cfg has
[mcu]
serial: /dev/ttyAMA0
restart_method: commandklippy.log has:
mcu 'mcu': Starting serial connect
webhooks client 1967506616: New connection
webhooks client 1967506616: Client info {'program': 'Moonraker', 'version': 'v0.7.1-194-geda5623'}
mcu 'mcu': Timeout on connect
mcu 'mcu': Wait for identify_response
Traceback (most recent call last):
File "/home/pi/klipper/klippy/serialhdl.py", line 69, in _get_identify_data
params = self.send_with_response(msg, 'identify_response')
File "/home/pi/klipper/klippy/serialhdl.py", line 258, in send_with_response
return src.get_response([cmd], self.default_cmd_queue)
File "/home/pi/klipper/klippy/serialhdl.py", line 316, in get_response
cmd_queue)
File "/home/pi/klipper/klippy/serialhdl.py", line 250, in raw_send_wait_ack
self._error("Serial connection closed")
File "/home/pi/klipper/klippy/serialhdl.py", line 62, in _error
raise error(self.warn_prefix + (msg % params))
error: mcu 'mcu': Serial connection closed
mcu 'mcu': Timeout on connect
mcu 'mcu': Wait for identify_response
Traceback (most recent call last):
File "/home/pi/klipper/klippy/serialhdl.py", line 69, in _get_identify_data
params = self.send_with_response(msg, 'identify_response')
File "/home/pi/klipper/klippy/serialhdl.py", line 258, in send_with_response
return src.get_response([cmd], self.default_cmd_queue)
File "/home/pi/klipper/klippy/serialhdl.py", line 316, in get_response
cmd_queue)
File "/home/pi/klipper/klippy/serialhdl.py", line 250, in raw_send_wait_ack
self._error("Serial connection closed")
File "/home/pi/klipper/klippy/serialhdl.py", line 62, in _error
raise error(self.warn_prefix + (msg % params))
error: mcu 'mcu': Serial connection closed
GerogeFu
beikeland
I can't seem to get my Raspberry Pi 3 Model B+ to connect to the Spider v1.1 board. Here's a list of things I've tried so far:
ls -l /dev/serial/by-id/returnsls: cannot access '/dev/serial/by-id/': No such file or directory~/klipper/out/klipper.bintofirmware.binon the Raspberry Pi's SD Card, inserted that SD card in to the spider and powered the spider on. The Flash LED blinked quickly for 10s of seconds and then became solid. I've since tried that a couple times.When in DFU mode (jumper between
3.3VandBT0),dfu-util --listreturnsWhen in DFU mode,
dfu-util -R -a 0 -s 0x08008000:leave -D ~/klipper/out/klipper.binreturnsdmesg -wHreturns a few different thing depending on how the board is powered and DFU mode: a. Non-DFU mode powered by 24v, no messages b. DFU mode powered by 24v Googlingerror -110seems to often indicate a power issuec. DFU mode and powered by USB 5v (jumper moved to
U5V)d. Non-DFU mode powered by USB 5v
It seems like the board is responding correctly to USB connections. I've tried a couple different cables that work with my phone (I can get my phone to show up in
dmesg). All the appropriate power LED are on and it's able to power the Pi when it's hooked up that way. Do you guys have any other ideas of things to try? Is something wrong with my board?Thanks for your help! Hope I can figure this out :)