nrfConnect SDK 2.6.0

intelcomdk

Hi. I have written to Nordic about a problem in the latest NCS 2.6.0, don’t know if it is a toolkit problem or a problem with the files for the nrf9160 feather (or a bug in my app). A have an app that compiles and runs fine on ncs 2.5.2. On 2.6.0 the code compiles but enters a boot loop “ZEPHYR FATAL ERROR 25: Unknown error on CPU 0”. Disabling I2C with CONFIG_I2C=n allows it to run fine againg, but of course without the needed I2C interface. In my overlay I have added vl53l0x to i2c1. Modem firmware is 1.3.6. Has anybody experienced this problem?

AchimKraus

Using a Thingy:91 with NCS 2.6.0 doesn’t show an issue with the I2C. The environment sensor works well.
I’m not sure, maybe it’s more a vl53l0x issue, though the st-hal has been updated on my request.

intelcomdk

Thanks for your input AK. Maybe it is related to the settings in the feather files (DTS). Another user has reported the problem on a “Sparkfun nRF9160 Thing plus” with relative short instructions on how to reproduce (UDP sample and CONFIG_I2C=y added). If you have the time, please try and enable serial also on your thingy91 app. By the way, I just updated a Thingy91 with the latest asset tracker from Nordic, and it does run fine, and measurements are sent to nrfcloud.

AchimKraus

Using a nRF9160-feather with Zephyr coaps-client for a Mobile Bee-Hive-Scale using EEPROMs and ADC over I2C2 works.

please try and enable serial also on your thingy91 app

My Zephyr coaps-client if running on Thing:91 uses UART0 for logging and sh, UART1 for modem trace. Both enabled.

AchimKraus

Maybe you try, if you could use the lis2dh of the feather over I2C1?

AchimKraus

Using a nRF9160-feather with Zephyr coaps-client for a Mobile Bee-Hive-Scale using EEPROMs and ADC over I2C1 works.

I2C2 was a typo, I’m not allowed to edit that.

intelcomdk

thanks again. I cant’t test lis2dh in my current app, because CONFIG_I2C=y make the app crash rigth after boot. It is not productive to play around in a larger program, so I must make a small test program; but both lis2dh and vl53l0x have worked before. And just to be sure I will try to compile on another PC with a fresh NCS install.

intelcomdk

AK, I am not using the nxp,pcf85063a on the feather, and have not bothered to edit west.yaml, have you?

AchimKraus

I only use the pcf85063a node to disable it on startup ;-).

AchimKraus

I revived an old vl53l0x support for my app. Seems it requires now xshut-gpios if used with the power-manager.
beside of that:

Distance: 0. 1632 mm
Distance: 1. 1642 mm
Distance: 2. 1655 mm
Distance: 3. 1658 mm
Distance: 4. 1664 mm

AchimKraus

I pushed a vl53x with my overlays. Maybe that helps.

intelcomdk

I did reinstall 2.6.0 completely - no difference. Are you using windows or linux? my circuit dojo is version 0.2.4. I did also try a brand new feather v5 with no external connections - no difference. I then took a simple blinky app and testet it works on the feather - ok. I then added just CONFIG_I2C=y, and it dies immediatly. But now I have a good starting point for debugging. PS: I have overlay and xshut on my app also, but the program never even executes the first statement in main. It worked with 2.5.2

AchimKraus

Linux, Ubuntu 22.04

AchimKraus

added just CONFIG_I2C=y, and it dies immediatly

strange …

intelcomdk

could be a problem on windows alone, I don’t have time to compile under linux today. Are you using the latest circuit dojo zephyr SDK tools? (updated march 15)
PS: are you based in Berlin?

AchimKraus

Are you using the latest circuit dojo zephyr SDK tools? (updated march 15)

No, I use “zephyr-sdk-0.16.5-1” and the dependencies from NCS-2.6.0 to build the image.

PS: are you based in Berlin?

No, I’m based close to Stuttgart

intelcomdk

thanks again. I did compile my blinky with CONFIG_I2C=y for the Xiao ble (nrf52840 based), and everything worked. most likely the i2c problem is only with the nrf9160 feather (and the sparkfun edition). Possibly even only when compiled in the windows environment.

AchimKraus

My (re-)test with NCS-2.6.0 and the vl53l0x was done with the nRF9160 feather v5. Really irritating …

intelcomdk

just tested my blinky with I2C on a nrf9160dk and it worked. Is there a nxp,pcf85063a.yaml file on you linux installation?

AchimKraus

No.