#EjectDriveToMakeCodeRun
1 messages · Page 1 of 1 (latest)
it's not supposed to eject, it should just work as is
and serial should just work
there's no error when opening the serial panel ? does it have a menu in the bottom corner to select different ports ?
that popup menu ?
what version of Mu by the way ?
1 choses between CP boards and ESP Micropyton. 2 does nothing. 3 brings up logs.
oh you have another board connected ?
Nope. Not that I am aware of
what version of Mu ?
Log, for what it;s worth
Mu 1.2.0
The board seems to change it's com port number as it is rebooting when I hit reset. So it sees it as a Micropython board for a short time on Com10 or something, then it sees it as a CPython board on Com29
OK so it actually seems to run, but REPL doesn't work.
try adding an error in the code, like 1/0 or raise "Error"
or just add prints in the code if it has none
From the latest log, I print out Hello World 7. Then modify code to Hello World8 and save it.
It shows up in log. But REPL is a no go.
oh yeah but more than one
like a loop
import time
while True:
print("hi")
time.sleep(1)
there is an issue with Mu where it can make the REPL unresponsive because it tries to move the cursor when you click in the serial panel and that fills up the output buffer, so it blocks ctrl-C but it doesn't block prints
one way to reset the buffer is to reset the board or cause an error
and then not use the Mu serial panel
there should be a fix in the next update
same issue when using Putty
did you try the loop and see the prints ?
Tried the loop. No print'
ok so it's something else
what if you eject and reset the board ?
otherwise I'd see hello world over and over
that works, but now no drive
and i didn;t reset. just eject
I've also tried with VSCode and Putty. Same thing
And notepad, and notepad++ and...
did you abandon me?
😩
I don't understand why it connects to COM29
CP board on port 10, but connect to port 29 ???
what happens if you change the selection in the menu at the bottom ?
COM29 is an FTDI cable hooked to something else. When I eject the drive, COM10 goes away and Mu then sees COM29 and thinks it's a micropython thing, which I assure your it's not. I have since removed pretty much everything non-adafruit. Now i'm also trying it on another computer with absolutely no USB devices other than internal. Installing mu now
it's weird, I would expect that selecting Circuitpython in the bottom menu would get the CP and not COM29, that might be a bug to report
still installing Mu... 8(
and to whom would i report such a thing? Same person I would report this issue to?
that would be here: https://github.com/mu-editor/mu/issues
actually, is Mu in Circuitpython mode ?
Yes, when connected to CircuitPlayground. When it connects to port 29 it trys to be Micropython mode. But I switch it back. Now no com29 since I unplugged it. Still, same issue (except for switching com ports). I can make video. Put in dropbox. Share linkShowing screen. Would that help?
well hey there. Do the same thing on my laptop, same board and everything, and it works exactly as expected.
modify code, hit save, off it goes.
Is that a Mu thing? Circuit Python thing? Circuit Playground thing? Obviously something on my computer, but what and who of the three do I talk to?
good question
if Mu is confused with the FTDI port, that's one thing, but I would still expect the print loop to appear in putty or other when connected to COM9 or whichever it is that day
So, who might I start with? Adafruit?
Seems more of a Mu thing.
Mu doesn't like something about my Filesystem or something on my PC
Or USB? Or...?
dunno, I don't know how ejecting the drive would change anything about connecting to the COM port
like, if it doesn't work with putty when the drive is mounted, it's not the same issue as Mu getting the wrong port
It does not work with Putty and Notepad with out eject. Per the website:
If you don't or can't use Mu, there are a number of other editors that work quite well. The Recommended Editors page has more details. Otherwise, make sure you do "Eject" or "Safe Remove" on Windows or "sync" on Linux after writing a file if you aren't using Mu. (This is not a problem on MacOS.)
no that's about editors that don't write files immediately
it's saying: don't reset or unplug the board without ejecting
OK.
like a USB drive
That makes more sense.
Seems like driver issue. Brought it all up on my laptop and no issue. Laptop and desktop are almost identical. Desktop has Acronis 2016 (backup and recovery software). Removed it. Now everything works fine. Kind of nuts. Thanks for the assist!