I used the envelop esp32s3 to install and flash my own code using the tutorial in the toit repo (I did not build my own toit, I used one from envelopes) I receive a crash but it can not be decoded:

$ jag decode WyNVBVVYU1UQdjIuMC4wLWFscGhhLjE0NVNVAFskVSNVEMo6M7I26VnnsQydl1gfQixbI1UEVUVTVQlFWENFUFRJT05TVQRbNzRdWyNVAlVTWyNVC1sjbAAAAANVRlUASR5/WyNsAAAAA1VGVQFJHmtbI2wAAAADVUZVAkkErlsjbAAAAANVRlUDSRKLWyNsAAAAA1VGVQRJFD9bI2wAAAADVUZVBUkUVlsjbAAAAANVRlUGSWbdWyNsAAAAA1VGVQdJZvVbI2wAAAADVUZVCElmGVsjbAAAAANVRlUJSWahWyNsAAAAA1VGVQpJEqI=
EXCEPTION error. 
[74]
No such file: C:\...\.cache\jaguar\snapshots\ca3a33b2-36e9-59e7-b10c-9d97581f422c.snapshot
Error: cannot decode stacktrace without snapshot for program: ca3a33b2-36e9-59e7-b10c-9d97581f422c

How can I change this path or tell toit to use it? And where can I even find this snapshot? Is it the one I created (but with a different name?)

There is currently no better way to do this. Our tools automatically copy snapshots they create into that directory so

jag monitor

works.

Maybe

jag decode

could take a path to a snapshot as an optional argument?

Probably a good idea.

I think I can pass an envelope but that was not decoding

Yes. The envelope is currently only used for the C-based stack traces. When the underlying system crashes.

how can I determine the uuid which the snapshot is named after? then I could copy the snapshop into the .cache folder

The latest SDK has

toit tool snapshot uuid

@floitsch is there a docker image where toit is already installed? I want to build that ne firmware in my GitHub repo and release it there so I can download the file from GitHub as the server for my firmware

If you want to run Toit on GitHub runners use the GitHub action: https://github.com/toitlang/action-setup

ah nice! thanks

Use

toit.pkg

instead.

hm.. something does not work here:

/home/runner/work/trap-a-rep-trigger/trap-a-rep-trigger/src/toit/package.lock:5:10: error: Package 'github.com/informaticore/toit-ringbuffer-1.0.3' not found

the link is not right at least

you can always use

toit.pkg --project-root=...

yes I was running it in the root working directory, its fine now. But now I can not run the firmware part where I install the container into the envelope? because firmware does not exist where is this actually coming from? jaguar I guess?

- name: Build toit firmware
  working-directory: src/toit
  run: |
    toit.pkg install
    toit.compile -w komodo.snapshot src/komodo.toit
    firmware -e firmware-esp32s2.envelope container install komodo komodo.snapshot

firmware

is also part of the SDK. It might not be automatically in the PATH. But the GitHub action also sets an environment variable where it has put the SDK. It's then in

sdk/tools

you might add this to the GitHub action to maybe also put this as an env. Btw: the file which is generated by that build process and which is flashed onto the device - is this the one I can download and "install" via BLE? as a firmware update? or do I actually only need the snapshot? I am a bit confused because the size of this firmware is quite big

The envelope and snapshot usually contain all the debug info... (You can remove those with the

--strip

flag). The binary you get from the

firmware extract

command, on the other hand, is just what needs to be shipped

that looks corrrect - the extracted bin file is only 1.3mb. nice! Now my GitHub repo generates the firmware which can be downloaded by an app and shipped to the ESP