Replies: 3 comments 14 replies
-
What exactly are the errors you're getting when you try to build m5plusdemo? The CI on this project builds every project with every merge, so we know that the code as-is can build. Your repeated mention of COM8 makes me think the actual compile may complete, but the upload to the stick fails. Which still leaves you without it running the project you're trying to put onto it, but leans towards a different avenue of investigation. |
Beta Was this translation helpful? Give feedback.
-
Having let this simmer for a bit, I believe the "Can't open COM8" error can be caused by the COM port already being in use. Do you ever happen to use the "Upload and Monitor" or "Monitor" features within VSCode/PIO? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
My MCU is the M5StickC Plus. Setting the PlatformIO.ini's default_env = laserline works like a charm.
Setting default_env = demo fails with a "Can't open COM8; port doesn't exist" or some such error. It doesn't seem to know I'm using the M5StickC Plus.
However, if I modify the [env:demo] section to this:
[env:demo]
extends = dev_m5stick-c-plus ;originally dev_esp32
build_flags = -DDEMO=1
-Ofast
${dev_m5stick-c-plus.build_flags}
It compiles just fine.
I tried specifying the default_env = m5plusdemo in the .ini and leaving the [env:demo] section as originally written and this also does not compile.
Both project builds sometimes errors on not finding COM8 automatically and I have to manually equate it as upload_port = COM8
But then again, somethimes this manual equate results in the same "Can't open COM8" error.
Suggestion on this behavior are welcomed.
Beta Was this translation helpful? Give feedback.
All reactions