https://toitlang.org/ logo
Powered by
Newbie problem: Error: open COM16: The system cann...
# help
e
I'm failing at one of the first hurdles trying to flash the firmware to an ESP32 WROOM dev module, I'm getting the error: Error: open COM16: The system cannot find the file specified. Any thoughts, apologies if this is covered elsewhere, I did search the forum first and didn't find any reference to this error. https://cdn.discordapp.com/attachments/1164859883905110077/1164861047610556427/image.png?ex=6544c063&is=65324b63&hm=d6d5a47738a57e081583ca3212ae95eac6750b216b552067daa5e95efd8e90cb&
f
@endomonkey_93231 it looks like we had a regression with Jaguar 1.13. We are working on a fix. You can try to downgrade to an earlier version for now.
e
Yep, I'll give that a go right now. @floitsch I'm totally new to Jaguar, how do I go about rolling back to a previous version? Is there a post you can point me to with instructions perhaps?
f
winget install --id=Toit.Jaguar -e -v 1.12.0
Assuming you are using winget.
I don't really have an easy way to test this, though. (No Windows machine right now).
If it doesn't work, don't hesitate to come back.
After downgrading, you will need 
jag setup
again.
e
I presume I need to uninstall the previous version first or will the new install overwrite the newer version without the need to uninstall?
f
I think it should uninstall the old one first.
But 
jag
is really just one executable.
So there isn't a lot of things that can go wrong.
The majority of it is downloaded dynamically into the 
.cache
directory, which will get updated with a call to 
jag setup
.
e
f
ok. so looks like you need to uninstall first...
e
winget remove --id=Toit.Jaguar worked to uninstall the newer version fine.
f
winget uninstall -e --id=Toit.Jaguar
(I think)
Apparently 
remove
and 
rm
are aliases.
So yes.
And the 
-e
is just for "exact match".
e
Okay, that worked a treat and the flash command fetched and installed the firmware first time.👍
f
Great!
Sorry about that. We hope to have this fixed within the next few hours.
e
Now all I need to do is learn Toit! 😆
f
Have fun. (And I mean it). Don't hesitate to ask questions.
I think the tutorials are the best place to start: https://docs.toit.io/tutorials
e
I'm looking into the COM port thing. Even with the newest Jaguar it works for me, so I'm wondering how to reproduce the issue.
Here's what my Device Manager looks like.
I'd be interested to see other people's device manager who see the issue.
e
i
mine is a CH340 as well
f
Looks like it's the CH340 that stopped working.
i
the Olimex boards usually using them
e
OK good I have a device here with the CH340
Unfortunately that also works fine for me on my virtual WIndows box....
I'll try on the physical box.
i
what could the message "file not found" mean? what file?
f
According to the issue, adding backslashes to the port fixes it.
Something like 
\\.\COM16
https://support.microsoft.com/en-us/topic/howto-specify-serial-ports-larger-than-com9-db9078a5-b7b6-bf00-240f-f749ebfd913e Maybe the upgrade of the 
serial
module in Jaguar removed support for this? (We did upgrade it when going to Jaguar 1.13)
We found it... And it's our fault. Should be easy to fix.
e
f
Probably would need to be 
\\\\.\\COM16
but we are already fixing it.
But it's not unlikely that the 
\\
approach won't work either.
i
I can remember that we did this once in the past because I had this issue
e
Thanks, everyone, for the help and the bug reports.
New Jaguar release coming up.
https://github.com/toitlang/jaguar/releases 1.16 available now. Takes a bit of time before it hits winget, if that's what you use.
f
If you don't want to wait, just grab it from the releases page: https://github.com/toitlang/jaguar/releases/tag/v1.16.0
i
sorry to ruin the show, but doesnt seem to help
f
There is Jaguar v1.16.1 out, but unfortunately I doubt it will fix the issue.
However, you should be able to write 
jag flash --skip-port-check
now.
i
:/
neup
f
I guess it doesn't help if you select the port with an argument 
--port COM17
.
i
nope, same story
should i try 1.16.1?
f
It shouldn't really make a difference, but it wouldn't hurt.
However.
If you could test older versions to see if they work, that would help us.
And COM17 is the port the device is connected to?
i
well yes
1161 doesnt help
is that really because of port above 9?
f
just to be sure: 
jag version
shows the correct version?
i
f
It's likely, but I don't see any 
os.OpenFile
in our sources anymore. At least none that should be executed.
Give me a few seconds, and I will prepare a 
jag executable
that prints a bit more debug information.
i
this worked fine
f
So it is Jaguar itself that has issues.
ok. It's a stupid 
!=
vs 
==
. I think.
Give me a second and I will prepare an executable.
i
ok, happens:)
some 
jag --verbose
would be nice
f
Could you try with this?
i
one sec
f
Agreed, but unfortunately not high priority. Also, the Jaguar desktop version was written in Golang, and there is a bit of a preference to work in tools now that have been written in Toit. So typically Toit tools see a bit more love than the Golang ones. Not really an excuse, but explanation
i
f
yeah. It's because it isn't signed.
I just built it on my Linux machine using cross-compilation.
i
yeah
wait a moment
bravo, it works
🥳
f
Great. Thanks for testing. I will TBR (to be reviewed) the change and release a new Jaguar version.
i
brilliant
thanks for your help - this ESP was almost on its way to trashbin as I thought its damaged
f
hehe. It's really us who are grateful here. We are not using Windows ourselves, and without our user's help these kind of bugs would linger for a long time (and potentially scare new users). So big thanks.
i
🤝
im still unshure why im on windows, but here I am:D moving from development to management does crazy stuff with people - like turning them to Win, Sharepoint and PowerBI 😄
f
🙂 I fully understand. Once a system is set up correctly, it's annoying to change.
Hmm. Winget has about 2 PRs/hour. I wonder if we could hit PR 123456 🙂
i
😄
k
winget install --id=Toit.Jaguar -e -v 1.17.0 ==> Es wurde bereits ein vorhandenes Paket gefunden. Es wird versucht, das installierte Paket zu aktualisieren... Es wurde keine übereinstimmende Version gefunden: 1.17.0
f
Isn't that 
winget update
?
Let me check
winget upgrade
(but 
winget update
is an alias)
aaah.
I see. So it is trying to upgrade, but can't find the version?
So winget of Jaguar is now broken?
Could you try 
winget upgrade
to see if that works/
k
winget upgrade : shows list of updatable apps, but jaguar 1.17.0 is not included
i
I always just run: 
winget install --id=Toit.Jaguar -e
but it installed 1.16.0
f
It's pending a review
Sometimes takes a while before packages are available on winget
i
but more like hours, not days, right?
f
24h is not uncommon
1.17 is now merged on Winget
2 Views
PreviousNext
Powered by