https://toitlang.org/ logo
Powered by
# help
  • Early exit from a lambda
    a
    I tried 
    return
    to exit early in one condition from a lambda, But of course 
    Can't explicitly return from within a lambda
    Is there a way to stop execution of a lambda part way through?
    f
    • 2
    • 1
  • PWM generator start seems to cause LED to flicker once?
    a
    We have some code such as this
    Copy code
    for i := 0; i < 3; i++:
      leds[i] = gpio.Pin pins[i] --output=true --value=1
      sleep --ms=1000
    for i := 0; i < 3; i++:
      channels[i] = generator.start leds[i] --duty-factor=1
      sleep --ms=1000
    sleep --ms=10000
    Where we control an RGB LED. First looping to setup the pins, with value 1 which in this case is LED OFF We then look through to start the generators, and calling .start seems to cause a small flicker once for each color. Is there a way to avoid this / a bug that can be fixed?
    f
    • 2
    • 16
  • check network state without net.open?
    a
    I currently check for a device IP with
    Copy code
    network := net.open
network.address
    or sometihng similar. But this has the side affect of actually opening the network, even if it were nt previously opened. What is the recommended way to check if the device is connected via WiFi, without calling 
    open
    ? I also tried 
    network.name
    but this also requires you to get the network first? Do I need to do something at a lower level? 
    NetworkServiceClient
    ? etc?
    f
    • 2
    • 2
  • Command line firmware size calculation
    a
    Every now and again I make firmware that is too big 
    Error: Firmware is too big to fit in designated partition (1844624 > 1835008)
    for example Is there a command line tool / way that I can get the size of an envelope file? without having to try and flash it? I thought perhaps 
    jag toit tool firmware -e apps.envelope show | yq '.Containers | .[] as $item ireduce (0; . + $item.Size)'
    , but that returns only 
    396868
    (far below the limit)?
    f
    • 2
    • 3
  • automatic light sleep
    a
    Hey all, I'm planning to build a battery powered device, but it needs to stay connected to wifi and have low latency reconnects. I saw there is a light sleep which is availabe under power management. Any plan to support that [automatic light sleep](https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/system/power_management.html) ?
    Copy code
    c
#include "esp_pm.h"

// ... other includes and setup

void app_main(void) {
    esp_pm_config_esp32_t config = {
        .max_freq_mhz = 80, // or 160, depending on your needs
        .min_freq_mhz = 10, // minimum frequency for the clock
        .light_sleep_enable = true
    };
    esp_err_t result = esp_pm_configure(&config);

    if (result == ESP_OK) {
        // Configuration successful
    } else {
        // Handle error
    }
}
    f
    • 2
    • 5
  • Issues with simple Neopixel code
    a
    Using the following code, I get this when using 
    jag monitor
    . Any ideas?
    Copy code
    import gpio
import pixel_strip show PixelStrip

PIXELS ::= 1
main:
  pin := gpio.Pin 08
  pixels := PixelStrip.uart PIXELS --pin=pin

  r := ByteArray PIXELS
  g := ByteArray PIXELS
  b := ByteArray PIXELS

  r.fill 0x44
  g.fill 0x80
  b.fill 0xff

  pixels.output r g b

  sleep --ms=1
    https://cdn.discordapp.com/attachments/1432094642517704946/1432094642761109615/message.txt?ex=6901c7d1&is=69007651&hm=9bee49a60b551b46298f8298e2d562c69afc3af74da7665ee36c1ef66576a1f4&
    f
    z
    • 3
    • 56
  • 💥 ESP32-C3 mini crashes when using 2 uarts
    k
    In a test application, two UARTs are used for a LD2450 and a Pixelstrip. As soon as the second UART is opened, the system crashes. https://cdn.discordapp.com/attachments/1432771183681474620/1432771184369336430/message.txt?ex=6902ec65&is=69019ae5&hm=3b0840206fdd37db6f963a728887f9dcada39cf2ff951161f3b8d0dacea7464c&
    f
    z
    • 3
    • 5
  • jag flash refusing to use correct esptool file
    e
    Copy code
    Error: failed to probe chip type: failed to probe chip type: exec: "esptool.py": cannot run executable found relative to current directory:
    f
    k
    • 3
    • 6
  • Trouble Monitoring: Unexpected EOF
    c
    Hi All, I'm attempting to monitor my esp32 from my desktop. I have flashed the device and see it on my wifi network, so the flash process worked. I can run "jag monitor" on my laptop and monitor my device's output without issue. On my desktop, however, I receive the following error: C:\Users\robin>jag monitor v COM5 Starting serial monitor of port 'COM5' ... =?a� Error: unexpected EOF I have tried unistalling jag, reinstalling, redoing the SDK setup, monitoring at different baud rates, changing ports - I still get the EOF error on my desktop. Any direction would be appreciated.
    m
    f
    • 3
    • 4
  • surviving a power outage
    r
    After a power outage the ESP32 comes up faster than the WiFi router, so jaguar tends to fail. What is the easiest way to overcome this problem? Using a watchdog? And if so, which of the two, the built-in or the package?
    m
    f
    • 3
    • 3
  • Building a single binary .bin to flash to a device
    a
    In order to get a single binary easily for flashing on a device, we have flashed it to a device and read it back. Something like... - 
    jag toit tool firmware --envelope=.\ble.envelope flash -pCOM70
    - 
    esptool.exe -p COM70 -b 460800 read_flash 0 ALL ble_adv_500.bin
    Is there an easy way to get and or reconstruct such as binary using the toit firmware commands that I am missing?
    k
    • 2
    • 31
  • mDNS alternatives
    g
    Last post I found was 2024 stating mDNS not implemented yet. What is the best way for toit to find its server on a local network?
    f
    • 2
    • 1
  • Profiling code (time / cycles)
    a
    Are there any profiling capabilities hidden away anywhere?
    k
    • 2
    • 3
  • ble hci uart init error! panic :(
    a
    It seems im abusing my BLE?
    Copy code
    ble hci uart init error!
E (295585) BLE_INIT: controller init failed

Guru Meditation Error: Core  0 panic'ed (Load access fault). Exception was unhandled.

Core  0 register dump:
MEPC    : 0x4080ba84  RA      : 0x4201cdba  SP      : 0x50002f90  GP      : 0x40824824
TP      : 0x50002fe0  T0      : 0x00000000  T1      : 0x4080bb6a  T2      : 0x00000000
S0/FP   : 0x4085ada4  S1      : 0x4082e000  A0      : 0x4085ada4  A1      : 0x00000054
A2      : 0xffffffa7  A3      : 0x00000001  A4      : 0x00000000  A5      : 0x00000000
A6      : 0x00000000  A7      : 0x00000000  S2      : 0x4082e000  S3      : 0x4082e000
S4      : 0x00000000  S5      : 0x00000000  S6      : 0x00000000  S7      : 0x00000000
S8      : 0x00000000  S9      : 0x00000000  S10     : 0x00000000  S11     : 0x00000000
T3      : 0x00000000  T4      : 0x00000000  T5      : 0x00000000  T6      : 0x00000000
MSTATUS : 0x00001881  MTVEC   : 0x40800001  MCAUSE  : 0x00000005  MTVAL   : 0x000000a8
MHARTID : 0x00000000
    f
    • 2
    • 9
  • Pixel-Display
    k
    I am currently using a 3.5-inch SPI-based TFT touch display. Is it possible to create UI elements such as drop-down menus and left or vertical scrolling? Are there any examples available for these behaviors? Also, does it support animations similar to LVGL when using the Arduino IDE?
    f
    • 2
    • 1
  • Best recommendation for recording / tracking a container version
    a
    I'm getting to the point of having CI build 1) a container from an example app 2) combining that with a custom envelope and 3) spitting out a final .bin file for flashing to the ESP Are there already any best practices I should be following in terms of versioning and having output in logs the version of the container code and or envelope code and or final bin? I see toit outputs something along the lines of 
    [toit] INFO: starting <v2.0.0-alpha.189>
    and I think that is from https://github.com/toitlang/toit/blob/0a240593d64c18508fce04a86dae235e191dfef5/src/rtc_memory_esp32.cc#L135 And I think that just comes from 
    -DVM_GIT_VERSION=\"\\\"
    and Is that the best pattern probably?
    f
    • 2
    • 6
  • Setting system time from a GNSS device.
    m
    Tying to find the smartest/most accurate way to set system time using GNSS. Most GNSS devices I've seen so far can emit 'time' type messages, and some* GNSS devices have a PPS pin - so I am thinking of implementing two methods. Looking for feedback/better ideas in case anyone has any! #1 (supports devices that don't have a pps pin): Take the exact time when a time message comes in. To account for system time not set - if difference is > 1 day, set the time immediately to the time in the packet. Take a moving average of the difference of GPS time to System time, for the next 3 (5? more?) messages. Adjust the system time by that difference. Assuming this will be less exact than #2, so we could add a fixed (configurable) +/- x ms/us to account for processing delay. #2 (for devices with a pps pin): When configured, PPS pin can pulse exactly 1 time (usually 1x/sec, depending on device/config). Do the same as #1, but instead, take the moving average from the pin rising edge instead. Other things: - perhaps some holddowns, eg, set the time only when time difference is > threshold, do only once/day, etc. (maybe look at the NTP method and use the same from there) - maybe adjust the 'time' message constructor to record the system time when the packet is received. (Or leave that to the driver - at the cost of an increase in the time difference. Any thoughts appreciated!
  • Does anyone know of a Toit package for LCD menus with encoder support?
    k
  • Trying to initialize uart on esp32c6
    a
    Running
    Copy code
    import gpio
import uart
UART_RX_GPIO ::= 20
UART_TX_GPIO ::= 19
main:
  port := uart.Port
    --rx=gpio.Pin UART_RX_GPIO
    --tx=gpio.Pin UART_TX_GPIO
    --baud_rate=115200
    Getting
    Copy code
    Potential deadlock detected:
  Process: 2
  Program: a42ef4b4-b892-6588-9883-ce3d1e1e3b30
  BCI: 0x5c6
  Primitive: 10:1
fatal: Potential dead-lock

abort() was called at PC 0x4202f7fd on core 0
Core  0 register dump:
MEPC    : 0x40806b76  RA      : 0x4081546e  SP      : 0x40831da0  GP      : 0x40824824
TP      : 0x40831fe0  T0      : 0x37363534  T1      : 0x7271706f  T2      : 0x33323130
S0/FP   : 0x40831ddc  S1      : 0x40831ddc  A0      : 0x40831ddc  A1      : 0x40831dbe
A2      : 0x00000000  A3      : 0x40831e09  A4      : 0x00000001  A5      : 0x4082d000
A6      : 0x00000000  A7      : 0x76757473  S2      : 0x40831dc0  S3      : 0x00000001
S4      : 0x004c4b40  S5      : 0x00000005  S6      : 0x028e885f  S7      : 0x408332c0
S8      : 0x00000000  S9      : 0x00000000  S10     : 0x00000000  S11     : 0x00000000
T3      : 0x6e6d6c6b  T4      : 0x6a696867  T5      : 0x66656463  T6      : 0x62613938
MSTATUS : 0x00001881  MTVEC   : 0x40800001  MCAUSE  : 0x00000002  MTVAL   : 0x00000000
MHARTID : 0x00000000
    not sure what the Primitive is, and seemignly i can only reproduce it on this hardeware setup. Got any pointers?
    f
    • 2
    • 32
  • Envelopes for ESP32 S3
    g
    Are there sample envelopes for the ESP32 S3? My code is just about 2MB and won't fit with Artemis in a 4MB VROOM. Thank you.
    f
    • 2
    • 1
  • ESP32 S3 Touch Support
    g
    Does toit support the new touch system on the ESP32 S3? I get an Exception error with touch.threshold that Gemini claims is an incompatibility.
    f
    • 2
    • 9
  • Wi-Fi with EAP
    b
    Hello, is there any method to setup Jaguar / Toit in order to use [EAP Methods](https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/wifi-security.html#supported-eap-methods) ?
    f
    • 2
    • 2
  • Zygote and Artemis
    g
    Zygote is a terrific starting point for field-provisioning and SSID and password but assumes you only need to do so when your existing credentials are invalid. To support pre-loading credentials setup.toit must be able to start an AP even when Jaguar or Artemis has wi-fi running. Jaguar can get around this with -D jag.wifi=false but how can I turn off Artemis' wifi temporarily? Temporary turn-off of Artemis' wifi would also be beneficial for when I need to run a sensor for an hour but don't need wifi or it's current draw in the meantime. Thank you.
    f
    • 2
    • 3
  • Cause of PREVIOUS_READER_NOT_FINISHED?
    g
    Copy code
    [network] INFO: closing {connection: wifi-0}
[network] INFO: closed {connection: wifi-0}
[artemis.scheduler] INFO: job stopped {job: synchronize}
NETWORK: Listener exception: 'PREVIOUS_READER_NOT_FINISHED' for msg:'null'
    Is this due to Artemis contention or something else? Thank you. Happens here:``` msg := null error := catch: msg = ws.receive // wait for web socket traffic if error: catch: ws.close // Force cleanup of the potentially "corrupted" object logger.error "NETWORK: Listener exception: '$error' for msg:'$msg'" ```
    f
    • 2
    • 3
  • Storage Bucket Retreival
    g
    I could not find a method to retreive items from bucket key-value storage if you do not know the key. Just want to make sure that is true before trying to solve that another way. Thank you.
    f
    • 2
    • 1
  • jag list missing options
    g
    The json and yaml output options do not appear to work for jag list. This would be handy but is not urgent for me. Mostly just so you know.
    Copy code
    PS D:\projects> jag scan --list --output=yaml
devices:
- devicebase: {}
- devicebase: {}

PS D:\projects> jag scan --list --output=short  <--default works
original-college
rough-location

PS D:\projects> jag scan --list --output=json 
{"Devices":[{},{}]}
PS D:\projects\Liquifi\flowi>
    f
    • 2
    • 1
  • Reading and Writing eFuses
    z
    I'm working on an ESP32-C6 project with Jaguar and I need to read (and possibly write) ESP32 eFuse values from my Toit application code (e.g., reading the MAC, checking chip revision, or burning custom fields for device identity). I searched the toitlang/toit and toitlang/jaguar repos and found: - The Toit firmware internally calls esp_efuse_mac_get_default() to read the MAC, and links against the IDF efuse component. - But there's no Toit-level API — no efuse.toit library, no primitives like efuse_read or efuse_write. Is there an efuse API I'm missing somewhere in the SDK, a package, or an undocumented primitive? Specifically EFUSE_BLK3 - I want to set some serial numbers into the device I think what I see is that the firmware already links against the IDF efuse component, but there are no Toit primitives or library functions exposed for reading or writing eFuses from Toit code. I expect I would need to add C++ primitives and a Toit library to surface esp_efuse_read_field_blob(), esp_efuse_write_field_blob(), etc.
    f
    • 2
    • 1
  • AdvertisementData parameters
    m
    I found an inaccuracy in the ble.RemoteScannedDevice parameters when retrieving AdvertisementData., as shown below:
    Copy code
    micrcx@micrcx-desktop:~/toit/ruuvi_ble$ jag run -d basic ruuvi_ble.toit
Scanning for device with name: 'basic'
Running 'ruuvi_ble.toit' on 'basic' ...
ruuvi_ble.toit:31:35: warning: Deprecated 'AdvertisementData.manufacturer-data'. Use 'Advertisement.manufacturer-specific' instead
      md/ByteArray := device.data.manufacturer-data
                                  ^~~~~~~~~~~~~~~~~
Success: Sent 78KB code to 'basic' in 2.92s
    manufacturer-data was replaced with manufacturer-specific, but now a compilation error occurs:
    Copy code
    micrcx@micrcx-desktop:~/toit/ruuvi_ble$ jag run -d basic ruuvi_ble.toit
Scanning for device with name: 'basic'
Running 'ruuvi_ble.toit' on 'basic' ...
ruuvi_ble.toit:31:35: error: Argument mismatch for 'AdvertisementData.manufacturer-specific'
Block argument not provided
      md/ByteArray := device.data.manufacturer-specific
                                  ^~~~~~~~~~~~~~~~~~~~~
Compilation failed
    I've use Jaguar v1.69.0 with Toit SDK v2.0.0-alpha.196.
    f
    • 2
    • 6
  • How can I make my toit jaguar NOT advertise on UDP? :)
    a
    Basically got too many devices running, and its clogging up the wifi. Can I stop it from advertising? 🙂 I'm pretty sure the answer is yes, but I now think I'm being blind.
    f
    • 2
    • 6
  • Update certificate-roots pkg
    r
    Hello, I am requesting an update to certificate-roots pkg. I am specifically interested in 
    ISRG Root YR
    because our current certificate is running out in 2030. No rush 🙂
    f
    • 2
    • 2