[nRF52833-DK][Zephyr]WS2812 example not work?

[Wols]

Hi Nordic,

I am using nRf52833-DK with zephry, an now I'm tring to drive ws2812 led strip.

I notice that there is no nRf52833-DK example in zephyr/samples/drivers/led_ws2812/boards.

So I copy y nrf52dk_nrf52832.conf and nrf52dk_nrf52832.overlay to same path , and rename to nrf52833dk_nrf52833.conf and nrf52833dk_nrf52833.overlay.

Here is the example build wilth "west build -b nrf52dk_nrf52832 samples/drivers/led_ws2812/ --pristine", and it work's well.

 

But if I build with " west build -b nrf52833dk_nrf52833 samples/drivers/led_ws2812/ --pristine", it not working like in video.

Is any way to fix it?

[JONATHAN LL]

Hi,

This is not neasasaerly a Nordic issue, more of a zephyr related, as the sample you are using is not one of ours. But your issue is that you have not made the correct overlay file.


Check out how the device tre works https://nrfconnect.github.io/vscode-nrf-connect/devicetree/install.html  here if you want to use our tools, or Zephyrs https://docs.zephyrproject.org/latest/build/dts/howtos.html here.

It is not clear exactly what is not wokring for the video and picture you share, do you get anny build errors?

I reccomed you ask in the Zephyr forum also.

Regards,
Jonathan

[Wols]

I accept this as an answer because is not neasasaerly a Nordic issue, more of a zephyr related.
The problem  still happens.

ws2812/52833.overlay and .conf should as same as 51822, because it just copy paste and renames.
 

The pic and video show when I build nrf52dk_nrf52832 it work well, keep red lighing.

But if I build nrf52833dk_nrf52833 option, the led keep blink, which mean the signal from 52833 to ws2812 is incorrect.

I use same hardware(nRF52833-DK), same dts overlay and  .conf, so I think the only different is zephyr bord config.
But I can't find out where has different.

[JONATHAN LL]

There is currently summer vacation for our Devzone engineers so low staffing. We will be back to full force in week 31.  

We can look more in to this but might take some time before we can look at it. So pleas be patient, and if you where to figure out the issue in the mean time then pleas update us. 

Regards,
Jonathan

[Wols]

Thanks  JONATHAN ,
I notice that the code for 52832 will run "transfer_next_chunk" 3 time in evey wa2812 blink cycle(whlie cycle).
But only run twice in 52833 version, still looking for reason.
`drivers/spi/spi_nrfx_spim.c`

static void transfer_next_chunk(const struct device *dev)

[Wols]

I just buy  another 52833 from https://www.raytac.com/tw/product/ins.php?index_id=121

Same error happend.

Zephyr-ws2812-52832 code, okay.
Zephyr-ws2812-52833 code, not work.

[JONATHAN LL]

I would check with the Zephyr comunity, ask in the Discord server https://zephyrproject.org/community/ maybe there is someone that has experianced the same issue.

I dont have the ws2812 to test so wont be able to do som testing any time soon.

Regards,
Jonathan

[Wols]

I already ask in Discord.
See : discord.com/.../996617182991618094

I had print out this two value in drivers/spi/spi_nrfx_spim.c at static void transfer_next_chunk

LOG_ERR(chunk_len);  
LOG_ERR(dev_config->max_chunk_len);

I notice there has a huge difference in 52833 and 52832 code.
I'll check and tack a picture at later maybe monday.