https://toitlang.org/ logo
Join Discord
Powered by
Chrome under MacOSX cannot seem to find the device...
# help
m
I can provision the esp32 with the jag cli and everything seems to work fine. I'm now trying to add it to the portal to get an idea how everything hooks up etc. Chrome is asking for my serial port, but no matter if i choose the older driver (usbserial-0001) or the new driver the interface tells me to go an install (SLAB_USBtoUART) it just never seems to connect. I've tried the provisioning wizard as well as the serial section but no dice. Not sure what other information will be useful other than I've tried a few different ESP32 dev boards and they all seem to work using CLI but not the web browser. Thanks.
f
Jaguar and the portal are two different Toit versions and don't work together. The older, v1, version is used by the portal, whereas Jaguar uses Toit v2. We generally recommend to stick with Jaguar nowadays, as the code is significantly more up to date.
That said: if you want to experiment with the portal, then that's still possible.
Normally, provisioning via Chrome should just work. I googled your issue, but haven't really found a good answer yet. That said: you can also provision your device with the command-line tool. It's a bit hidden nowadays, but you can download it here: https://archive.toit.io/cli/latest/darwin
m
Cools. Thanks for the information. A followup question if you dont mind, but if the portal isn't recommended any more, than is there an alternate for running all the devices in a central place? Plan is to have multiple devices across various locations and wanting a central place to monitor/manage (i.e. all the things promised by the toit.io webpage). Perhaps I am missing something obvious. Whenever I click the 'start now' button on the page it sends me to github, and I believe I only found the console by a google search.
FYI the toit command you sent me a link to doesn't seem to want to connect to my esp either. But i've only just started trying to work with it, so I will persist with it for the moment!
f
We are working on a tool (codename "Jaguar") for fleet management.
It will be a command line tool without the web site (console).
The biggest change will be under the hood as we will encourage our users to run/own their own servers. We are planning support for MQTT brokers and Supabase.
For minor usage we will probably also allow to use our Supabase instance.
m
actually, that sounds really awesome!
f
Another big change is that we won't provide any pubsub mechanism anymore. Same reasoning and solution: we shouldn't see your data, and the solution is to send it to an MQTT broker or to Supabase.
m
Amazing. And the 10 million dollar question.... Do you have a timeline for that? is it open source? Can I help? 🙂
f
We hoped to have an alpha by the end of this year, but didn't manage to. Hopefully early next year.
It's not open source. This is where we would like to make some money 🙂
We are generally fans of open source, so maybe we will eventually manage to open source this one too, but for now we will keep it closed.
m
I will look forward to the release - I'm just starting to get back into embedded and looking around for a iot platform, and toit jumped out as a particularly nice offering, and now its sounding like you guys are on a good path 🙂
thanks for your help!
f
Glad to hear.
m
one really quick (possibly unrelated) question - how do i get the hardware-id from a connected device - I need that to be able to 'claim' into the portal
f
Wrt the 
toit
not connecting. Give me a few seconds to reread your issue and to see if I have more advice.
If you flash using the 
toit
tool it will automatically claim the device. While flashing the tool also prints out the ID.
m
i have gotten toit command to do serial monitor, so its connecting, i just need more understanding on how it works 🙂
f
Ok. Good. 
toit
and 
jag
use (mostly) the same flashing tool underneath (esptool) so if one can flash then the other should be able too.
I'm trying to find the old documentation...
We had some instructions on our docs.toit.io but removed most of it recently. It's still in the commits, but I'm on my phone so have a hard time finding it. https://github.com/toitware/web-docs/tree/master/docs
m
all good, you've been amazinly helpful thankyou. I'm getting stuck at "erasing device flash" (i've tried in flash boot mode and normal mode). I will check out the documentation and see where i can get 🙂
f
Hmm interesting. Try with 
--verbose
(iirc). Also. If things fail the tool should ask you whether you want to write a log. That can also help with debugging.
m
oh, there is a log file generated - yes, its looking for boot mode - let me play with that for a bit
Copy code
29 A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
 30 Running "/Users/matt/.cache/toit/tools/esptool_darwin_v3.0 --chip esp32 --port /dev/cu.SLAB_USBtoUART --baud 921600 --before default_reset --after hard_reset erase_flash"
 31 esptool.py v3.0
 32 Serial port /dev/cu.SLAB_USBtoUART
 33 Connecting........_____....._____....._____....._____....._____....._____....._____
 34
 35 A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
f
Classic...
Just need to press the button at the right time.
(I hope)
m
yes, i think so - i've been putting into boot mode before i click "y" - looks like i might need to wait for a second or two
f
We shouldn't have hidden the "connecting ..."
m
bingo
f
We were lucky to never need it on our boards and machines. And then later we never got around fixing it.
m
Copy code
erasing device flash
successfully erased device flash
writing device partitions
successfully written device partitions
reading hardware chip information
successfully read hardware chip information
+--------------------------+-----------+
|         SETTING          |   VALUE   |
+--------------------------+-----------+
| factory device model     | esp32-4mb |
| factory firmware version | v1.6.25   |
+--------------------------+-----------+
hardware was successfully provisioned
f
Next step is to install apps with specifications...
Again. You might need to go back in the history of the repository.
m
thankyou very much - i'm just evaluating at the moment, so i'll probably be able to work out the rest from here - but I'm very much looking forward to seeing the new tools early next year 🙂
f
I'm signing off now, but don't hesitate to ask here. We know that our docs aren't always perfect, but we are very active here.
m
If we can connect devices to our own servers all using mqtt then that is an option I am really excited out!
For sure. Thank you for your time!
PreviousNext
Powered by