[BUG] ESP32-s3 NR16... - Neopixel (p038) not working correct in 3004205 Release

[HarryHase4]

Describe the bug
The neopixel Basic plugin is configured but not working (quicktest with dev board, onboard ws2812 led GPIO48)
It is not possible to change or delete the Task, and the plugin/task is not working

To Reproduce
Donwgrade to Christmas edition, working, upgrade not working

Used platform (please complete the following information):

• ..ESP32s3_16M8M_LittleFS_OPI_PSRAM_CDC_E..max
• • ESP32-s3 NR16 Dev-board

Additional context
ESP32-c6 dev-board working with both releases

[tonhuisman]

Can you test using the current build from https://td-er.nl/ESPEasy/latest/ ?
This is based on a newer Arduino/IDF framework, and has many improvements since the last official release version.

Maybe even more important: The GPIO may not be connected to the WS2812 😲
This comment shows how to detect and fix that.

[tonhuisman]

OTOH, For ESP32-S3 there have been breaking changes in the RMT implementation since IDF 5.x, that may also cause this.
I'll see what I can do about that (it's an item on the TODO list, but hasn't got attention yet 🫣)

[HarryHase4]

latest also not working, but in the latest it is possible to delete the task.
donwgrade to the christmas version -> dircetly up and running. (so i "guess" the gpio is correct)

[TD-er]

You can work with NeoPixel on ESP32-S3 when using a build without PSRAM

[HarryHase4]

I will test (i can also work with the older Version), it is only a notification light for the camper ... (( ;) tim))

tested; without PSRAM Version are running, but also problem with deleting a doublicated neopixel basic task

[TD-er]

deleting should still work.
Can you also try to disable the task first and then try to delete it?
You can use the command taskdisable,N with N being the task index. (via the command line on the tools page, or via serial/USB terminal)

And if this doesn't work, please try with both/all of those tasks disabled.
N.B. the taskdisable and taskenable commands will not save that state, however if you then remove the task via the task setup page, the settings as they are in memory will get saved.

[woomiez]

just stumbled on this thread because i'm having the same problem with the current nightly build.
I can create a neopixel device, but writing data to it doesn't seem to do anything, and trying to edit or delete the device results in a crash and reboot. the only way to get rid of it again is a factory reset.

[tonhuisman]

the only way to get rid of it again is a factory reset.

Have you tried to use a non-PSRAM build, as suggested above?

[woomiez]

The non-PSRAM version of the 16M build seems to not have this problem, as far as I was able to test right now.

[TD-er]

Yep that's a known issue and to be honest I have no clue yet why...
I think the PSRAM does lock some cache lines so the CPU can't add new data using DMA to some block of data used by RMT (to create a very strict signal timing for the addressable LEDs)

I have tried to find a reliable work-around for this by telling the compiler/linker to load the RMT code into iRAM, but this doesn't seem to work reliable. As in it might work in one build and no longer work in another, or causes boot-loops.