heltec esp32s3 wifi lora v3: new espressif board

[imnotjames]

adds the Heltec ESP32S3 WiFi LoRa V3 as a supported espressif ESP32-S3FN8 board

this board features a Semtec SP1261 LoRa chip (over SPI) and an 0.96-inch 128*64 screen (over I2C)

the board doesn't connect USB by default and instead supports interactions via a CP210x over USB

the USB VID/PID was pulled from the creator's repository but it's the standard espressif VID and a PID I don't recognize

Datasheet can be found here

[imnotjames]

Do I need to request a CIRCUITPY_CREATION_ID somewhere for this? Otherwise Bluetooth doesn't seem to build if I omit it.

[dhalbert]

Do I need to request a CIRCUITPY_CREATION_ID somewhere for this? Otherwise Bluetooth doesn't seem to build if I omit it.

https://github.com/creationid/creators

[imnotjames]

Do I need to request a CIRCUITPY_CREATION_ID somewhere for this? Otherwise Bluetooth doesn't seem to build if I omit it.

https://github.com/creationid/creators

Got it. Since this already has a USB VID and PID from espressif should I use the community documented VID & PID for espressif s3 boards?

I think the issue - as I understand it - is that even though the VID and PID are defined, because I don't have a physical USB connected & disable that USB by default, a VID/PID are unexpected, defaulting to the creator ID / creation ID. So using the espressif space would make sense?

[dhalbert]

The USB VID/PID are irrelevant since they will not be used. The creator ID should be based on the actual manufacturer, in this case, Heltec. When possible, we use the manufacturer's USB VID as part of the creator ID, but it sounds like they don't have their own VID? So just make up a creator ID -- anything that makes sense. Then for the creation ID, you could also see if there's a part number or something, or else just choose one. You might get some ideas from the other ones.

[imnotjames]

The USB VID/PID are irrelevant since they will not be used. The creator ID should be based on the actual manufacturer, in this case, Heltec. When possible, we use the manufacturer's USB VID as part of the creator ID, but it sounds like they don't have their own VID? So just make up a creator ID -- anything that makes sense. Then for the creation ID, you could also see if there's a part number or something, or else just choose one. You might get some ideas from the other ones.

Got it! I have updated this with the proposed creator ID & creation ID that I opened as a PR over in the creators repo

[tannewt]

One sdkconfig piece I don't think you need.