i2c_nrfx_twi: Error 0x0BAE0001 occurred for message 0

[CeDeROM]

Hello world :-)

I am writing I2C temperature sensor driver over `i2c0` working in `twi` mode in Zephyr with my custom `dts` board configuration and this pops up on the console:

`i2c_nrfx_twi: Error 0x0BAE0001 occurred for message 0`

Any hints welcome on the error details and possible causes/fixes :-)

[Håkon Alseth]

Hi,

 

That error is a address NACK on the TWI bus:

https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/drivers/nrfx_errors.h#L70

 

Are you sure the address of your slave is correct?

Have you tried scoping the SCL/SDA lines to see how they behave?

 

Kind regards,

Håkon

[CeDeROM]

Turns out to be hardware problem with the prototype board. With and without some parts problem was exactly the same, that lead me to the solution :-)

First steps in Zephyr + DTS + NRFX/NCS + Custom Board + Custom Driver so I wanted to ask here too. After hardware fixes all works fine now :-)

It would be really nice if error messages contained some sort of str_error() human readable hint or reference.. but now I know where to search for the codes thanks :-)

Thank you for your time Håkon Alseth! :-)

[Håkon Alseth]

I am glad to hear that you found the source of the issue!

CeDeROM said:

It would be really nice if error messages contained some sort of str_error() human readable hint or reference.. but now I know where to search for the codes thanks :-)

strerror is usually set aside for errno's, unfortunately; and also given in the standard lib (newlib c in this case). We had a nrf_strerror implementation in nRF5 sdk, but this is towards that SDK's specific return codes. Translating nrfx errors over to errno gives "loss" of traceability in my opinion (ie: where did this error originate). Its a good idea, but I'm not sure if we can add this in a easy-to-use way.

 

Kind regards,

Håkon