nRF5340 peripheral selection w/Engineering A silicon - comments please

Question

Hi everyone, 
 Currently I am routing hardware for an upcoming project using the nRF5340 and it's time for a sanity check. 
 The goal is that the HW works well enough w/Engineering A samples for initial development. I reviewed the errata for Engineering A samples (included on nRF5340-PDK reference board). 
 I am interested the concurrent resource availability and functionality of the following nRF5340 peripherals. Any comments are welcome regarding issues that I might encounter. 
 I am planning to run both cores at 64 MHz. 
 UARTE0 and UARTE1 both running at ~460 kbaud w/DMA QSPI running at 64MHz w/DMA SPIM0 running at 4MHz, no DMA SPIM4 running at 8MHz w/DMA TWIM0 (I2C) running at 1000 kHz, no DMA TWIM1 (I2C) running at 390 kHz, no DMA 
 Any problems I should know about in Nordic Connect SDK 1.2.0 targeting these peripherals? 
 Thanks for your help!

Einar Thorsrud · Accepted Answer

Hi, 
 The Device Tree approach used in Zephyr does not work with having the same pins for several peripherals, so you need to use the nrfx drivers directly. Then, you basically follow this approach: 
 
 Initialize the peripheral when you need it. 
 Use it 
 Uninitialized peripheral when done. 
 Now you can do the same with the other peripheral of the same ID, since the first peripheral is no longer in use. And so on... 
 
 Taking SPIM as an example, this means that for step 1 you initialize it with nrfx_spim_init(), use it as described in the API doc and uninitialized it with nrfx_spim_uninit(). 
 You can refer to nRF91 nrfx example to see an example of how to use nrfx drivers directly (there is no example specifically for nRF5340, but the principles are the same).

nRF5340 peripheral selection w/Engineering A silicon - comments please

Top Replies