Reset CPU lockup error when using USB CDC ACM as backend on Matter Template example (SDK v1.9.99)

RE: Reset CPU lockup error when using USB CDC ACM as backend on Matter Template example (SDK v1.9.99)

Jørgen Holmefjord — Fri, 03 Jun 2022 08:40:06 GMT

nRF Connect SDK v2.0.0 was released yesterday. I would recommend that you switch to this and see if you are still seeing this issue.

RE: Reset CPU lockup error when using USB CDC ACM as backend on Matter Template example (SDK v1.9.99)

Carla31 — Tue, 10 May 2022 13:42:50 GMT

I'm using the version 1.9.99-dev because I know that it is compatible with the CHIP Tool controller. I read on Nordic website https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_matter_configuring_controller.html#configuring-matter-controller that CHIP Tool is the recommended Matter controller.

I didn't want to use the Python CHIP controller because I thought that later when the SDK version v1.9.99 will be released I should migrate from Python CHIP controller to CHIP Tool controller. That's why I decided to start working with the CHIP Tool controller and SDK v1.9.99-dev.

I tried to run the Matter example template (SDK v1.9.1) with CHIP Tool controller but it does not work.

I don't know if it is a good idea to work with Matter example template (SDK v1.9.1) and the Python CHIP controller.

I will try to read out the RESETREAS register. Thanks for your help

Do you know when the latest dev tag v1.9.99-dev will be released ?

RE: Reset CPU lockup error when using USB CDC ACM as backend on Matter Template example (SDK v1.9.99)

Jørgen Holmefjord — Tue, 10 May 2022 12:25:43 GMT

Hi,

Is there any specific reason you are running the latest dev tag and not the latest official release of nRF Connect SDK (v1.9.1)? Have you checked if you get the same error with v1.9.1?

Not sure what could cause a CPU lockup. This could be triggered by a hardfault in the hardfault handler, but that would indicate something very wrong in the application.

Can you read out the RESETREAS register directly from code (NRF_RESET->RESETREAS), or using a debugger, to verify that the bit on LOCKUP is set, or if LLOCKUP bit is set? Both can cause the RESET_CPU_LOCKUP return from hwinfo_get_reset_cause().

Best regards,
Jørgen