Hello, I was trying to run the Matter template example on board nRF5340 DK.
- The nrf connect website example : https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/matter/template/README.html
- The github repo : https://github.com/nrfconnect/sdk-nrf/tree/v1.9.99-dev1/samples/matter/template
By default, console and shell outputs used for this example, come via UART0 of the board. I'm using the prj.conf file. The example works as expected. In fact, using the CHIP-TOOL as Matter controller on Raspberry PI, I'm able to add my device (running the Matter template) to my Thread network.
However, when I want to use USB CDC ACM as backend for console and shell, instead of UART0, after commissioning, my device resets in a loop. To use USB CDC ACM I added 2 overlay files to the original project Matter template :
- an overlay file containing extra Kconfig options to enable USB CDC ACM
- an overlay device tree file to active USB CDC ACM node and to link it to console and shell
Here, you can see the output of my Matter template example which uses USB CDC ACM as backend for console and shell. My program starts resetting at line 944 after getting Thread network credentials (PAN Id, channel, mesh prefix, etc)
I added as well to the main application the function called hwinfo_get_reset_cause(uint32_t *cause) to get the type of error that causes this reset. When I print the value 'cause', I got 256 which means that the error is a RESET_CPU_LOCKUP error https://docs.zephyrproject.org/apidoc/latest/group__hwinfo__interface.html#gad6721dc841941ccdca349999ce655e83.
Could you give some ideas to understand why I get this kind of behavior please? Why replacing UART0 by USB CDC ACM can lead to this kind of error?
