Add CircuitPyhton for ESP32-S3 Devkit-C-1.1 N32r16

[CoolDom]

Hi,
Adafruit sell on their shop esp32-S3 n32r16 devkit-C-1.1. But currently there is no CP that support this board but there is one for the older version n32r8.
Also the UF2 bootloader has the same "issue" one for the older version n32r8 exists but not for the new one.

Thanks,
Dom

[mikeysklar]

Fair point that it's not discoverable if you search circuitpython.org for N32R16 and get nothing.

In the meantime the n32r8 build runs on it as-is. Flash config is identical 32MB, and PSRAM size is auto-detected at runtime. You get the full 16MB. Flash the .BIN with esptool.

[grgrant]

One other difference between the boards is the neopixel is on GPIO38 rather than GPIO48. So when using the R8V version of CircuitPython on a R16V board you need to ignore board.NEOPIXEL and instead use board.IO38 as in:

np = neopixel.NeoPixel(board.IO38, 1)

[mikeysklar]

@grgrant good point about the NeoPixel move. The N32R8V is also EOL, so the new board def @CoolDom asked for is worth adding, even though the n32r8 build already runs on the R16V today as long as you use board.IO38 instead of board.NEOPIXEL.

I only have an N32R8V on hand, which is what I tested with, so I'll open the PR as a draft until someone can confirm on real R16V hardware. @grgrant sounds like you already have one, can you verify the board boots and reports 16MB?

[grgrant]

@mikeysklar I have a couple of the boards. Back in Feb I tested the board with the N32R8V build and it sees and can address all the memory. I agree that their should be a new build to reduce the confusion and to properly address the NeoPixel as well as properly name the board.

https://discord.com/channels/327254708534116352/537365702651150357/1476092210922520761

As soon as there is a new CI build with the correct definitions I will gladly test. I'll also test later today the current alpha.4 but I don't expect it to work any better/worse that 10.2.1 did.

[CoolDom]

@mikeysklar @grgrant, thanks for chiming in (I was outside watching the eclipse...). Yes, I knew already the LED was on GPIO38 instead of GPIO48. I have also a board and be happy to test also when the new build is available.

[mikeysklar]

@CoolDom I'm jelly about you catching the eclipse. You must be pretty far North. Maybe I'll get to see some meteor shower / planet alignment tonight.

You can test the build (CircuitPython and bootloader) from the PR artifacts.

CircuitPython #11192:

Bootloader adafruit/tinyuf2#482, adds the 32MB partition table

Two ways to load it:

1. Flash the tinyuf2 combined.bin at 0x0 with esptool, then drop the CircuitPython .uf2 on the N32R16BOOT drive.
2. Skip the bootloader and flash the CircuitPython .bin at 0x0 with esptool.

Either way CIRCUITPY should come back around 29MB or more, versus the 5.9MB the stock 8MB bootloader gives.

>>> import os, gc, board
>>> print(os.uname().machine)
>>> s = os.statvfs("/"); print(s[0]*s[2])
>>> gc.collect(); print(gc.mem_free())      # ~16.5MB with the 16MB PSRAM
>>> print(board.NEOPIXEL)                   # board.IO38

[CoolDom]

@mikeysklar LOL I am in MA so just ~16% for the eclipse but still some great pics.

I just wrote on the other PR (TinyUF2) that I just did the test with the CP .bin and get the following results:

ESP32-S3-DevKitC-1-N32R16 with ESP32S3
31080448
16522240
board.IO38

Thanks again for all your works!

[mikeysklar]

@CoolDom - Nice. Thank you for testing. Glad it worked for you too.