Okay a bit of a play - and a version running on an 8MHz MCU. There is an issue - the pin used is hardcoded here as D7. If you want to change it then you'll need to change the output at the start of main (this sets the pin to be an output and should really be done by setting DDRx etc). And the occurr...

I've tested using an ATMega8 - running at 16MHz (with external crystal) - LED lights all good and at 8MHz (internal)- not good. Checking on a scope - the timings look 'out' when running at 8MHz - and in fact altering the clock speed - seems to generate the same number of nops (for example setting it...

Can you try the attached - just outputs a colour (255) to each of RG and B then repeats - note that if you don't have the RGBW variant (I don't) then setting W to 0 is okay... (Note I use D7 as the output pin - you'll need to change this to suit)
Martin

Just got an SK6812 running with an Arduino - admittedly 16MHz - using the library. The solution seems to be simpler than expected - add a small delay after the initialise (it seems that the LED takes a moment to become 'ready' after power on')

I have some sk6812 chips - I'll see if I can get it working in hardware for you....

Again - just to check - your board is running at 8MHz.

The alternative is a ws2812?

Martin

The timing might be a bit 'tight' on an 8MHz chip and hardware? A while ago I posted some code for the ATTiny85 - at85_rainbow.fcfx Where you can try 'tweaking' the timings. Note that this can be sped up by removing the 32 bit variable in Refresh and using 3 single byte 'shifts' (the AVR MCUs are 8 ...

Something is wrong.... I downloaded Testsk6812 from above - the MCU is set as ATMEGA328PTQFP (is this intended?) Changing the target to ATMEGA328p gives -> Pin0 of component ESP_RMT1 is connected to bit 2 of Port A but this port/bit does not exist on the new microcontroller Flowcode then closes (cra...

You also need to call Refresh after doing the setall - to upload the data to the leds

C:\ProgramData\MatrixTSL\FlowcodeV9\CAL\ESP\ESP_CAL_RMT.c:112:19: error: conflicting types for 'FC_CAL_RMT_TX_1'
CALFUNCTION(void, FC_CAL_RMT_TX_, (void))

Definitely trying to include the esp code?

If the target is a 328p then there is an issue with the component?

Martin

This is an issue with ESP32 and later versions of the RMT interface.

See the post at viewtopic.php?p=14339#p14339

For a working version - the RMT interface and to have changed dramatically...

Martin