RE: NRF_ERROR_BUSY at TWI embedded code

tyro01 — Fri, 03 Jun 2022 12:46:34 GMT

Hi Jørgen,

Thanks for your advice, I have verified that the program works correctly with the following modifications.

/* TWI instance ID. */
#define TWI_INSTANCE_ID     1

As a beginner, I had read warnings on the blogs of my great predecessors to beware of duplicate instance IDs.

However, I had let my guard down, thinking that it would not matter to me, as I do not set up complex programs.

<info> app: LoRaWan Class A example started.
<info> app: TWI TX Done.
<info> app: TWI TX Done.
<info> lmh: DevEui=70-B3-D5-7E-xx-xx-xx-xx
<info> lmh: JoinEui=00-00-00-00-00-00-00-00
<info> lmh: Send OTAA Join Request, status: OK
<info> app: TWI RX Done.
<info> app: Temperature: 29 Celsius degrees.
<info> lmh: Send OTAA Join Request, status: OK
<info> app: TWI RX Done.
<info> app: Temperature: 29 Celsius degrees.
<info> lmh: Send OTAA Join Request, status: Busy
<info> app: TWI RX Done.
<info> app: Temperature: 29 Celsius degrees.
<info> lmh: Send OTAA Join Request, status: OK

The more complex the program, the greater the opportunity to copy-paste sample code, but I would consider the possibility that the sample program reserves the ID.

Thank you for your kind advice.

Best regards,

tyro

RE: NRF_ERROR_BUSY at TWI embedded code

Jørgen Holmefjord — Fri, 03 Jun 2022 11:48:22 GMT

Hi,

One serial instance can only be used either as SPI or TWI peripheral at the same time. The GitHub library you linked are using SPI_INSTANCE 0 in the SPI init functions, while you are using the same instance 0 for your TWI_INSTANCE in above code:

#define TWI_INSTANCE_ID     0

...

/* TWI instance. */
static const nrf_drv_twi_t m_twi = NRF_DRV_TWI_INSTANCE(TWI_INSTANCE_ID);

You need to select a different instance in one of the codes, or make sure that SPI and TWI are not initialized at the same time.

Best regards,
Jørgen