-
Notifications
You must be signed in to change notification settings - Fork 441
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
Raspberry Pi 400 "Could not find an attached device" #2312
Comments
I've realised that Raspberry Pi OS (Debian bullseye) has a fairly old version of Mu: 1.0.3, from January 2020: https://packages.debian.org/bullseye/mu-editor On Mac, I'm using Mu 1.1.1, which works well, but there is no more recent version of Mu than 1.0.3 available I can find that will run on 32-bit Debian Bullseye (Mu's downloads offers Linux AppImage Package (Experimental)), but that is 64bit & x86 (rather than ARM), so far as I can see). I also notice that PR #2263 may apply, because I've renamed my CircuitPython device from |
You are right, the main issue is that debian package is at v1.0.3, which is very old and predates the RP2040 devices, so Mu v1.03, which at the time used USB VID and PIDs, doesn't have the values for this devices in the source code. Unfortunately due to the current dependencies Mu uses it is not compatible with Python 3.8, so there is no simple way to install it in Raspbian Bullseye, which comes with Python 3.9. That being said, the main limiting factor for the Python 3.8 max version is PyQt, and to install Mu from source in PiOS you need to use the PyQt5 packages from apt, so you might be able to get it working by following the dev instructions but using the
|
Hello amigo, I tried this solution but it fails to run the run.py file. I Have collected the log file for the installation process as well as the error message which is the following thanks for your help |
Question : I'm encountering a similar problem on a regular raspberry pi 4. Latest OS, so past 3.8. But have Pyenv installed and was able to install Mu-editor via the Raspberry pi Preferences->Recommended Software. That installs a version of Mu-editor that runs and can load code from the device that shows up as a CircuitPy device. However, I get an error when trying to run serial. Could not find attached device. Is there a work around for this yet?And any ETA when Mu will get caught up with more recent Python versions? |
Hail Mary here, but I'm trying to get Mu to work with a Raspi4 and a PN532 breakout board and am facing a similar issue that OP had. Any fixes or updates on this yet? |
I encounter the same problem on a Raspberry Pi 5B-8GB. Raspberry PI OS: Linux raspi5B-8GB 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64. Mu editor version 1.0.3. Raspberry Pi OS Version: 12 (bookworm). Also installed via the Raspberry Pi Preferences->Recommended Software. The device I have connected via USB is an Espressif ESP-BOX S3. It's serial connection is via /dev/ttyACM0. |
What were you trying to do?
Use Mu on a Raspberry Pi 400 to read the Serial out of a rp2040 CircuitPython device, wanted to see the Serial output
What steps did you take to trigger the issue?
Press 'Serial' menu button
What did you expect to happen?
Expected Mu's built in serial monitor to operate
What actually happened?
Mu gave a "Could not find an attached device" error - the video below shows the issue being recreated. Note that
screen /dev/ttyACM0 115200
worked, and was able to display serial output - but Mu's in-built Serial view failed:MuCanNotFindCircuitpython.mov
Operating System Version
Raspberry Pi OS (raspbian) 11 (bullseye)
Mu Version
1.0.3
Other Info
Tested with 2 different CircuitPython devices:
Both devices are read ok with Mu running on my Ubuntu laptop and also on my Mac OS M1 Mac.
This issue seems similar/related to #1596 / #1543, though to be clear, I'm encountering the problem on a Raspberry Pi 400, rather than a M1 Mac
Editor Log
The text was updated successfully, but these errors were encountered: