https://toitlang.org/ logo
Join Discord
Powered by
# porting
  • f

    floitsch

    10/18/2024, 7:51 AM
    esp32s3 is already supported.
  • f

    floitsch

    10/18/2024, 7:53 AM
    For the NRF: the VM itself is written in C++ and relatively portable. At some point we did a port to a different ARM chip, but unfortunately that was under NDA and we can't share more about it. It's definitely feasible, but requires a bit of work. Depending on the quality of SDK (of the chip) more or less.
  • f

    floitsch

    10/18/2024, 7:53 AM
    If you want to try the esp32s3:
    jag flash --chip=esp32s3
    and with Artemis
    envelope=esp32s3
    (for example, but I recommend an envelope with a different partition table with Artemis)
  • f

    floitsch

    10/18/2024, 7:54 AM
    Available envelopes (including some for hosts, like the raspberry pi) can be found here: https://github.com/toitlang/envelopes
  • a

    Andorian

    10/18/2024, 7:57 AM
    Wow! That changes alot. We're in a phase where we're evaluating wheather to go for NRF or ESP32 for our B2C project. And had already somewhat concluded with NRF until I found out about Toit. We'll give it a go! Seems brilliant
  • a

    Andorian

    10/18/2024, 7:58 AM
    Whats the status on C3 and C6? Not in the scope?
  • f

    floitsch

    10/18/2024, 8:40 AM
    C3 is also supported.
  • f

    floitsch

    10/18/2024, 8:41 AM
    For the C6 we would need to upgrade the ESP-IDF we are using, and last time I tried I ran into some issues.
  • f

    floitsch

    10/18/2024, 8:42 AM
    Upgrading the ESP-IDF is something we need to do anyway, so it will happen (hopefully sooner than later). After that we need to map the hardware. That shouldn't be too hard as we already have templates for the esp32, esp32s2, esp32s3 and esp32c3.
  • f

    floitsch

    10/18/2024, 8:42 AM
    That assumes that the C6 still supports the deprecated hw APIs. (Another task on my TODO list: migrate to the newer APIs).
  • a

    Andorian

    10/18/2024, 8:47 AM
    Yeah C6 is generally hard to find support for. So doesnt't have high expectations for that. But as long as S3 and C3 is supported we're covered on the ESP front
  • k

    kasperl

    12/09/2024, 2:29 PM
    We've made progress and just found and fixed a lock-related issue in the memory allocation subsystem (gotta love complex linker scripts). The ESP-IDF has been updated, so we expect that the next version of the SDK comes with support for the C6 - and we hope to have it out within a day or two.
  • z

    z3ugma

    12/13/2024, 4:34 PM
    Has anyone ported Toit to the
    Seeed Studio XIAO nRF52840 Sense
    ?
  • f

    floitsch

    12/13/2024, 4:37 PM
    So far Toit has only been ported to the ESP32 (+ variants) and desktop (macos, linux, windows). We made a port to an ARM-based chip, but that was under NDA. Since we got some experience from that port we would like to port to ARM chips in the future, but for now it hasn't reached the top of our priority lists yet.
  • z

    z3ugma

    12/13/2024, 4:42 PM
    ok! there are dev boards with a similar footprint like
    XIAO ESP32S3
    - 2.4GHz WiFi, BLE 5.0, 8MB PSRAM, 8MB FLASH that I can use instead of the nRF52840
  • m

    MichaelK

    01/09/2025, 11:18 AM
    Is it possible to use ESP32-S3?
  • k

    kasperl

    01/09/2025, 11:19 AM
    Yes 👍
  • m

    MichaelK

    01/09/2025, 11:24 AM
    Then what is the reason for this error: micrcx@micrcx-desktop:~/toit$ jag flash Enter WiFi network (SSID): MichaelK24 Enter WiFi password for 'MichaelK24': Flashing device over serial on port '/dev/ttyACM0' ... esptool.py v4.8.1 Serial port /dev/ttyACM0 Connecting.... A fatal error occurred: This chip is ESP32-S3 not ESP32. Wrong --chip argument? Error: exit status 1 micrcx@micrcx-desktop:~/toit$
  • f

    floitsch

    01/09/2025, 11:25 AM
    Try with
    jag flash esp32s3
  • m

    MichaelK

    01/09/2025, 11:44 AM
    Ok, jag flash esp32s3 works
  • m

    MichaelK

    01/09/2025, 11:45 AM
    Here is the hello.toit app: main: print "Hello, World!" micrcx@micrcx-desktop:~/toit$ jag run hello.toit Running 'hello.toit' on 'reversed-area' ... Success: Sent 37KB code to 'reversed-area' micrcx@micrcx-desktop:~/toit$ Why can't I see "Hello, World!" on the terminal?
  • f

    floitsch

    01/09/2025, 11:49 AM
    With Jaguar you need to
    jag monitor
    to watch the output of the chip.
  • f

    floitsch

    01/09/2025, 11:50 AM
    Jaguar doesn't send output of the program through the wireless connection.
  • f

    floitsch

    01/09/2025, 11:51 AM
    jag monitor
    connects to the chip vial the serial connection and prints the output of the chip. At the same time it automatically decodes stacktraces, ...
  • m

    MichaelK

    01/09/2025, 12:04 PM
    Yes, I see it now, but now need to use two terminals. It was simpler before with toit commands. [jaguar] INFO: program bd162137-39fc-f36d-97a0-d16b20cf83ed started Hello, World! [jaguar] INFO: program bd162137-39fc-f36d-97a0-d16b20cf83ed stopped Thanks anyway.
  • f

    floitsch

    01/09/2025, 12:05 PM
    Yes. This was easier before. We still have plans to support this feature again, but it hasn't had high enough priority yet.
  • m

    MichaelK

    01/09/2025, 12:09 PM
    I was just curious to try S3, but it requires using jag.
  • f

    floitsch

    01/09/2025, 12:10 PM
    Be aware that the old toit.io offering is deprecated and will soon shut down.
  • f

    floitsch

    01/09/2025, 12:10 PM
    So all chips require Jaguar (or Artemis).
  • m

    MichaelK

    01/09/2025, 12:14 PM
    I realized this a long time ago, so I tried using JAG as a backup option.