Hi everyone,
We found that the LIS2MDL_INT interrupt from the compass on P1.06 affects communication between the app core and the network core.
About 3 seconds after bootup, if we perform a Bluetooth function such as scanning or advertising, it results in a timeout and causes the system to reset, as shown below.
We tried postponing bt_enable(), but it failed because the app core couldn't communicate with the network core.
However, if we select a different compass interrupt, the LSM6DSV_INT1 on P1.04, the Bluetooth function works well.
We use an external clock and added the configuration to prj.conf
in both the app core and the network core.
Has anyone encountered a similar issue? Could there be any specific cause I should check?
Any suggestions would be greatly appreciated. Thanks!