This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF52833 i2s problem.

Hello. 

Is there any difference between i2s hardware in nRF52840 and nRF52833? I made WS2812B i2s driver and working very good on nRF52840. The same code (project is adjusted to nRF52833) doesn't work on nRF52833. I discovered that there is small oversight in SDK17.1.0. In nrfx_i2s_stop missing definition about nRF52833 which repair USE_WORKAROUND_FOR_I2S_STOP_ANOMALY (file nrfx_i2s.c). I try to find some differences in manuals, but I can't see.  

Best regards,

PiotrW

Parents
  • Hi there,

    I don't think there is any difference HW wise between the two in regards to the I2S peripheral. 

    discovered that there is small oversight in SDK17.1.0. In nrfx_i2s_stop missing definition about nRF52833 which repair USE_WORKAROUND_FOR_I2S_STOP_ANOMALY (file nrfx_i2s.c). I try to find some differences in manuals, but I can't see.  

    Can you elaborate a bit more on this? Maybe show me the difference in the driver? 

    Could you also describe how it doesn't work on the nRF52833? Does the project build successfully? Does it assert during runtime?

    regards

    Jared 

  • About SDK. I didn't express myself clearly. I wrote about definition which is in the beginning of file nrfx_i2s.c.

    Shouldn't there be extra definition for nRF52833? (I added it in my code and enabled workaround for i2s_stop anomaly)

    Project is built correctly. BLE, i2c master, i2c slave and SPI works good, exactly like in nRF52840 version. The problem is only i2s. After start i2s, signal isn't generated. Then after next start i2s, programm goes to "app_error_fault_handler". Between starts there is of cource "i2s_stop". I though there is some new issue with i2s in nRF52833, which can explain this kind of action :(

    Piotr

  • Hi,

    I agree that the workaround should be applied for the nRF52833 as the Errata has also been listed in the errata list for that IC. But I don't think that is causing your issue as the errata is related to the the current draw of the peripheral. Have you tried the I2S example in the SDK? I've attached the example folder from the SDK which contains a ported version that works on the nRF52833, see the PCA10100 folder.

    regards

    Jared

     i2s.7z

Reply
  • Hi,

    I agree that the workaround should be applied for the nRF52833 as the Errata has also been listed in the errata list for that IC. But I don't think that is causing your issue as the errata is related to the the current draw of the peripheral. Have you tried the I2S example in the SDK? I've attached the example folder from the SDK which contains a ported version that works on the nRF52833, see the PCA10100 folder.

    regards

    Jared

     i2s.7z

Children
No Data
Related