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
Lose Connection with Duet 2 WiFi after flashing #4933
Comments
After swapping USB cables and re-flashing this is what the output is. `/dev/serial/by-id/usb-03eb_6124-if00 pi@raspberrypi:~ $ ls /dev/serial/by-id/* Erase flash Done in 4.305 seconds It seems the USB isn't recognized after flashing the Duet and RPI MCU and reboot. |
It seems it's an issue with Klipper. I've tried cutting the 5v wire on the USB to ensure the Duet isn't being powered from the RPI. I've tried with 3 different Duet boards and 2 different RPIs along with trying to manually flash with my PC using Bossa. Every way I've tried I get the same result. The board cannot communicate once it's flashed. But if I erase the firmware it can communicate. |
I've already tried that |
I am having the same issue on a fresh install on a new pi4 with the latest on debian. I had a working install on a different pi that will not work now even after reflashing without rebuilding. The interesting part is the serial ID changed from: |
I am in the same boat as above. I tried erasing by jumper, and also flashing the firmware with bossa from windows. This did not help. Unfortunately I don't have the time nor tools to debug the issue right now. |
I'm not sure how to approach debugging this board. How do I easily debug the code without JTAG? I can't find anything in the klipper developer docs or Duet wiki that can help me along either. @KevinOConnor can you maybe give me some pointers? Stepping through klipper revisions to see where it breaks is a fallback, but that's a tedious job. |
I played with this issue a bit this weekend.
|
Hello, I also like to confirm this issue in a similar setup. Board reset to bootloader mode via Erase jumper is OK:
Flashing via make flash works without issues.
Lastest revision from git:
I Just tried to switch to Release 0.10.0 and 0.9.1 and they show exactly the same behavior. |
I just repeated everything with Ubuntu 20.10 on the same setup and everything is working as expected . |
Hello, It looks like there hasn't been any recent updates on this Best regards, ~ Your friendly GitIssueBot PS: I'm just an automated script, not a human being. |
I have the same problem with a Duet Wifi. Really dont know what to do now...Using Pi Os Lite with Kiauh - tried it 2 times with a clear installation. |
@Zodiak1993 see the reply just above by @danielschramm |
Sorry I am new to Linux and Raspberries - Ubuntu is an alternative to PI OS Lite? |
Yes, Ubuntu is another Linux OS and can replace PI OS. |
So for everybody - I could solve it with the "Mainsail OS" Thank you for your support. |
Topics seems concluded. Apparently some OS issue and not depending on Klipper. |
The problem still exists. |
Had this same issue. Could not get a working setup with the latest Bullseye version of Raspbian. Using MainsailOS , which uses Buster, works fine. |
Actual problem. |
@Sineos Can this issue please be re-opened? I can reliably reproduce this on a brand new installation of Debian 11, with only Klipper installed. This is the latest version of Raspberry Pi OS, so it's not a particularly unique setup. Yes, it does change based on OS, bu that isn't evidence that the OS itself is the issue. |
@Sineos |
I got same issue on Debian11 using bigtreetech CB1 and Duet2 wifi. |
Still a problem. |
Anyone know how to solve this problem? I just have the same issue. |
See https://klipper.discourse.group/t/duet-2-firmware-compilation-broken-on-debian-11/4762/ Only known fix is to use a different Linux version for compiling and flashing |
hmm tried mainsailOS 1.2.1; now also bullseye based and fails with same issue |
Sep 11 2023, I needed to use the ubuntu-server 20.04 image to be able to flash my duet2 wifi + duext5. Tried raspian buster-lite, mainsailos and neither would work. |
You need use raspberry Pi OS Lite (Legacy) on Debian 10 (buster), on this version firmware compile correctly and work fine. |
I was having issues with Moonraker so I decided to create a new Klipper USB(I like to use USB drives because their faster and more stable than SD cards). I have a RPI 4 8gb, 32gb USB 3.1 flash drive and Duet 2 WiFi. I used the kiauh.sh script to install Klipper, Fluid and Moonraker.
ls /dev/serial/by-id/* /dev/serial/by-id/usb-03eb_6124-if00
I'm able to flash the Duet but after flashing it seems like the board becomes locked. When I re-run
ls /dev/serial/by-id/
I get an error for "ls: cannot access '/dev/serial/by-id/*': No such file or directory". If I erase the flash on the Duet the RPI can communicate with it again. I've tried reflashing the Duet and the RPI many times but I'm not sure what else I can do to fix this.klippy (1).log
The text was updated successfully, but these errors were encountered: