thanks. Let us hear what Jared has to say

That’s definitely strange. Probably need to see all your related .conf files to see what’s enabled/disabled.

What’s the error when you set this?

CONFIG_RESET_ON_FATAL_ERROR=n

Using addr2line is helpful in these situations if it spits out a valid address.

I would also probe the I2C SCK/SCL to make sure they’re not loaded down with the addition of that 3rd sensor. You may need to add more pull-ups depending on how much parasitic capacitance is on the lines. Though the peripherals are fairly robust, you never know.

Hi Jared. Thanks for the reply. Maybe you did not read all the posts. the error is easy to reproduce:
under windows with ncs 2.6.0 installed and circuit dojo SDK 0.2.4 in vscode
build the blinky app for feather, nordic nrf9160dk and xiao ble (nrf52840); it works on all three.
then add CONFIG_I2C=y to prj.conf so it has in total 3 lines
CONFIG_GPIO=y
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_I2C=y
It then fails on a feather with nothing externally connected (just the USB cable), and it works fine on 9160DK and Xiao ble (xiao of course with CONFIG_BOOTLOADER_MCUBOOT=n).
During build for the feather, it is unhappy about Unknown node type “nxp,pcf85063a” in circuitdojo_feather_nrf9160_common.dtsi.

adding the following overlay to the feather makes it run again

/delete-node/ &i2c1;
/ {
aliases {
/delete-property/ accel0;
};
};

That narrows it down

Nordic is not going to do more, as it is only a problem on the feathers. addr2line say
C:/ncs/v2.6.0/zephyr/drivers/pinctrl/pinctrl_nrf.c:193

@intelcomdk sorry I won’t be supporting NCS 2.6.x until the next release. I suggest you downgrade to 2.5.x.

next version of NCS or next version of circuit dojo SDK? Any idea about the timeframe, before I downgrade?
Is there supposed to be a file nxp_pcf85063a.yaml, I can’t find it in on my install (or is it included somewhere else).
Is this a problem on Windows alone?

    intelcomdk Is this a problem on Windows alone?

    No idea. Again I haven’t test 2.6.x and don’t plan for a month or two since it’s an effort to upgrade all the samples.

    intelcomdk Is there supposed to be a file nxp_pcf85063a.yam

    Unless they’ve changed how drivers work, there is no file that you mentioned above. The driver is included in the NFED manifest.

        a month later

        Today I have upgraded to SDK to 2.6.1, and it still did not work, but now i came across a similar problem on the nrf5340dk board. The feather works again after adding these two lines to the prj.conf file
        CONFIG_TFM_SECURE_UART=n
        CONFIG_TFM_LOG_LEVEL_SILENCE=y
        I has to do with a change in 2.6.0 whereby logging is enabled in TFM as default and collides with i2c1. For a more complete description look here https://devzone.nordicsemi.com/f/nordic-q-a/109959/i2c-problems-in-sdk-v2-6-0-on-nrf5340dk

        I’ve added:

        CONFIG_TFM_LOG_LEVEL_SILENCE=n
CONFIG_TFM_SPM_LOG_LEVEL_DEBUG=y
CONFIG_TFM_EXCEPTION_INFO_DUMP=y
CONFIG_TFM_SECURE_UART_SHARE_INSTANCE=y
CONFIG_TFM_SECURE_UART0=y

        to my prj.conf in order to get in some cases more infos about failures.
        I guess,

        CONFIG_TFM_LOG_LEVEL_SILENCE=n
        CONFIG_TFM_SECURE_UART_SHARE_INSTANCE=y
        CONFIG_TFM_SECURE_UART0=y

        helps to prevent the crash.

        Terms and Conditions | Privacy Policy