Try with

jag flash esp32s3

Ok, jag flash esp32s3 works

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?

With Jaguar you need to

jag monitor

to watch the output of the chip.

Jaguar doesn't send output of the program through the wireless connection.

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, ...

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.

Yes. This was easier before. We still have plans to support this feature again, but it hasn't had high enough priority yet.

I was just curious to try S3, but it requires using jag.

Be aware that the old toit.io offering is deprecated and will soon shut down.

So all chips require Jaguar (or Artemis).

I realized this a long time ago, so I tried using JAG as a backup option.

Mostly curious: any plans to support raspberry pi pico?

No plans, but it should be possible.

Is there a C6 envelope with no Bluetooth stack, the way there's a regular ESP32-no-ble?

Not yet, but can be easily added

ok, Ive got a C6 with the onboard 512K of RAM. I want to drive a 320x320 TFT LCD display. I keep running into out-of-memory problems but I really am not taking very much care to figure out how to GC the bytes I am sending over SPI. I will be trying to implement

pixel-display-impl_.toit

and use the pixel-display library because I assume I am making some novice mistake that is causing me to run out of memory

Do you also have network connections open?

it won't be necessary, no. a different chip will handle WIFI and BLE. This chip is only responsible for driving the LCD. Possibly also some I2S but much lower frequency

Ok. One thing that could help: do you run out of memory early or over time? If it only happens after some time then it might be due to some memory leak or bad usage of the UI library.

no, right away. I get through the LCD setup commands, and then try to make a big for loop that writes a ton of pixels. It's clearly not the right way to do it:

// LCDWriteCommand(0x36); //Memory Data Access Control
  // LCDWriteData(0x00);
  command-spi 0x36 #[0x60]


  start:= Time.monotonic-us
  // // LCDWriteCommand(0x2C);//Write GRAM


  3.repeat: |i|
    bluary := #[0x85, 0xc0, 0x21, 0x70, 0x08, 0x5c, 0x02, 0x17, 0x00]
    if i % 2 == 0:
      bluary = #[0x80, 0xc0, 0xa0, 0x70, 0x48, 0x2c, 0x1a, 0x0f, 0x08]
      
    chomps := #[]

    times := 256
    times.repeat:
      chomps += bluary

    device.transfer --command=0 #[0x2C]
    device = bus.device --cs=cs --frequency=11_000_000
    (320 * 320 / 4   / times).repeat: //8 chomps in bluary, so divide by 4 since it's 2 bytes of color data per memory location
      device.transfer chomps 

    end := Time.monotonic-us
    print "Duration: $((end - start) / 1_000) ms"

  sleep --ms=10

^^here I am trying to preallocate this long

chomps

array and running out of memory

Ah. The pixel-display library isn't designed to emit pixels like that

We should add some support for bitmaps but it's not there yet

in the long run I don't intend to use bitmaps. I expect that there won't be enough RAM on the ESP32 to do that really

but if I can use the optimized things like text and polygons, then I think I'll be better off right? pixel-display is handling some of the lower-level rendering

It could work if the data was stored in flash. But without support from the UI library...

is the theory that you'd stream a small amount from flash into RAM, then pump it out to the display, then overwrite the allocated part of RAM from the flash, and repeat

The UI library paints the display block by block. The display library must provide the data as requested. If the data is in flash, it would just read it from there whenever needed.

esp32c6-no-ble is building.