Calling driver.initled with wrong pins causes crash

[ewowi]

Tested on Esp32-S3

This is the output

pins[, 26, 33, 32, 35, 34, 26] Start driveroffset initiationsemaphore initPins initiationESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x8 (TG1WDT_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT) Saved PC:0x403743c0 SPIWP:0xee mode:DIO, clock div:1 load:0x3fce3808,len:0x3ac load:0x403c9700,len:0x9a8 load:0x403cc700,len:0x2920 entry 0x403c98b8 COMMODORE BASIC V2

WARNING - possible crash: (code 5) Reset (software or hardware) due to interrupt watchdog. Core#0 (code 8) watchdog; Core#1 (code 8) watchdog.

Possible solution: test on valid pins before allocating

[ewowi]

List of valid pins in StarLight for S3:

Created using this code:

[ewowi]

Using virtual driver:

This is using a valid pin, but it is crashing with this error message:

But pin 2 is a valid pin isn't it?

Changing to pin 16:

No memory ... This is on a standard ESP32 (non psram, selecting a 64x64 pixels fixture) using https://github.com/ewowi/I2SClocklessVirtualLedDriver#c305662 (not latest) see https://github.com/ewowi/I2SClocklessVirtualLedDriver/commits/integration/

Using FastLED driver it works okay...

Loading a Live Fixture specific: WARNING - possible crash: (code 5) Reset (software or hardware) due to interrupt watchdog. Core#0 (code 8) watchdog; Core#1 (code 14) restart.

No actions required yet, investigation in progress...