One of the difficult things with a complete online interface is dealing with packages.

You can have a predefined set of them installed, but in theory you would want to be flexible and allow the user to choose which ones are installed.

Right, yes, again as you cant run

jag

the IDE integration itself would have to have some sort of package fetching stuff built into it etc i guess?

The package manager is part of

toit

, so

toit pkg

would work, but I'm not sure how much the filesystem is "workable". Maybe it's not really an issue. In other words: I don't know how much you can think of wasm-run programs to live in a small machine or not.

Fundamentally, you need: - start the LSP server somehow; maybe as a wasm plugin directly in vscode. The LSP server is a Toit program. - support starting (forking) the Toit compiler from in there. - have a way to install/delete packages. Note that the LSP server provides files to the compiler. Normally we only provide user files and not the SDK. However, it would be possible to let the LSP server provide all files. This might make things easier; or not.

Good progress on my lockfile package today. I think it's ready for a release as soon as the SDK and host package have been updated. This was the last blocker for a Toit-based package manager. In the past we have been reluctant to improve the package manager as it was written in Golang. Soon there will be a Toit version of it, which should make it more convenient to do changes in it.

Motorola 68000 assembly > Toit > Go

What supports cellular modul?

On toit cellular module only support for quectel bg96, can support another quectel type like ec800 or more?

And how do toit use, and does toit use esp modem to run cellular module?

The cellular support comes from this package: https://github.com/toitware/cellular I don't know how different the ec800 is from the bg96. It is probably unsupported at this time.

I ran into some extra ammount of effort using the envelope template with both the default TARGET and then a custom one One part of this wa the IDF setup. I managed to write ~10-40 line makefile changes to make all of this much nicer, so you can switch from

make IDF_TARGET=esp32c6

straight to

make IDF_TARGET=esp32

, basically reconfiguring the IDF, if it is configured in the wrong way Does this sound worth a PR? And also, should the idf setup thing actually be in the

toit

repo, or best to keep it in this evelope repo for now and see how ti goes?

Can you upload a PR for what you have? Doesn't need to be cleaned up. Just to get an idea of the changes.

something like https://github.com/toitlang/template-custom-envelope/pull/21

I see. In the toit repository we create different build directories for each variant. Would that work here too? (Feels a bit cleaner).

So currently in the envelopes one there still end up being different build dirs, I gues it would need to be multiple build-root dirs instead?

yes. Like in the toit repository. we have

build/esp32

,

build/esp32c3

, ... We could do the same in this repository.

yeah I think it could be well worth it Ignoroing the IDF configuration part, the main issue is if you clone the repo, and read the README ones thorugh, then realize you actually want to build for your seperate target, you have a lot of unpicking to do (deleting files etc) until

make

works with the new idf target 😄

Yes. This should be like in the Toit repository. Just a different build directory.

Hello, I was wondering whether Toit automatically supports memory expansion using the ESP32‑P4’s PSRAM?

SPIRAM is supported. For some variants (like the ESP32) we provide different envelopes ("firmwares") that have SPIRAM activated or not. (See, for example, https://github.com/toitlang/envelopes/releases/tag/v2.0.0-alpha.188). I think most of the other variants have SPIRAM active by default and detect it dynamically. All of this is quite flexible, so if we are missing a configuration, I can easily add one. That said: we don't support the ESP32-P4 yet. I just ordered a board, and will try to get it working once it arrives. Usually adding a new variant isn't too much work, but I don't want to promise any time frame. You can increase the priority of the port by asking from time to time about its status 🙂

Thank you, much appreciated.

Am I right in thinking that the

programs

partition in the default tables is used for the persistent flash buckets? (and possiblw some other stuff)

Hey y'all, has anyone flashed jag onto a Flipper Zero? Am I off base in assuming thats possible?

I'm not aware of any attempt, but since it's a normal esp32 (afaik) it should just work

More good progress this week(end). @z3ugma mentioned that the SPI device could be improved by allowing more flags, like 3-wire-mode, which I implemented. At the same time, I refactored the library so that data doesn't need to be bytes anymore (but can be used to send bits). Unfortunately, that made me look into the same for reading, and I'm hitting a bug, where the last (incomplete) byte isn't set. I'm currently suspecting a bug in the esp-idf library. More debugging needed... I continued work on the lockfile (file-system lock files) library, and started using it in the Toit-version of the package manager. With this, the package manager should be pretty much feature complete, and will likely replace the golang based package manager in the next (or the one ofter) release. I will travel next week, so not sure how much work I will be able to do.

Nice, this sounds like a fun time. sending 9-bit SPI arrays instead of bytes at 15MHz speeds is one thing I suspect I'll need to do and was considering having to drop into C++ with a little module that I compile in but that sounded like so much more toolchain work

if necessary, we can maybe add a flag to expand a byte-array to 9 bits in the transfer function.

Hi! I wasn't sure where to post this so here we go. I'm using Zed as my code editor and would like to have Toit language server integrated into it to be able to have syntax highlighting other features that LSP provides. I'm willing to give developing it a go myself. Is it something you (authors of Toit) want to have or are willing to support? Or should it be created as a community extension?

Looks like the issue I encountered is an esp-idf bug. I filed https://github.com/espressif/esp-idf/issues/17725.