• State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 75 subscribers
  • Views 1246 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 275785
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

1.6.99 - nRF5340 - RPC_Host Sample execution, stuck in fault_s.S

MGSC

Hi, 

After many attempts I was unable to make RPC_Host sample work (link to the related nRF Connect SDK doc).

From SES in debugging mode, the network core gets stuck in an early initialization stage without ever reaching the __main call.
Idem when flashing (merged_domain.hex) the sample from nRF_ Connect_Programmer (Nothing on the network_core console / Beacon sample stuck waiting for the network core to register).

So far, other samples worked as expected.

Can someone try to guide me into where I could have missed a step with rpc_host sample ?


Please find below infos relative to my setup :

devKit : PCA10095 / 1.0.0 / 2021.10
Sdk : 1.6.99 (fresh install)
IDE : SES5.6

Network core (target : nrf5340-dk-nrf5340-cpunet) : 

- unmodified rpc_host sample.
--> exec state : stuck in fault_S.s
----> my guess : triggered by virtio (?)

There is one "error" shown in SES while programming the network core: 

Illegal value 0x210089D8 written to register 66 (MSP_NS) ignored

Application core (target : nrf5340-dk-nrf5340-cpuapp) :

- Tried with unmodified sample (via menuconfig from rpc_host in SES) nrf:empty_app_core
- Tried with unmodified sample (via CONFIG_BT_RPC option) zephir:beacon
--> exec. state : waiting for network core to register. In nrf_rpc_rpmsg.c l.136 (while (!rpmsg_service_endpoint_is_bound(endpoint_id)){...}  )



Best regards,

Maxime

Parents
  • 0

    Hi,

    Digging a little bit more in debugging mode (network core rpc_host, app core running empty_app_core via menuconfig).

    The fault seems to occur while executing "z_sys_init_run_level(_SYS_INIT_LEVEL_PRE_KERNEL_1);" line l.436 from init.c.
    The execution goes 2 times without success in for loop l.82 of device.c then at the 3rd attemp the CPU lock itself into fault_S.s.

    The flag SHCSR->BUSFAULTACT get to 1 which mean "BusFault exception active bit" (BUSFAULTENA been enabled).

    nRF DCNF doc extract : An attempt to access the blocked resources will trigger a BusFault or a HardFault exception, depending on the value of the BUSFAULTENA bit in the ARM Cortex-M33 SHCSR (system handler control and state register), described in the ARM Cortex-M33 Devices Generic User Guide.

    Link to The domain configuration (DCNF)

    Any idea of why and how to fix ? 



    Maxime

Reply
  • 0

    Hi,

    Digging a little bit more in debugging mode (network core rpc_host, app core running empty_app_core via menuconfig).

    The fault seems to occur while executing "z_sys_init_run_level(_SYS_INIT_LEVEL_PRE_KERNEL_1);" line l.436 from init.c.
    The execution goes 2 times without success in for loop l.82 of device.c then at the 3rd attemp the CPU lock itself into fault_S.s.

    The flag SHCSR->BUSFAULTACT get to 1 which mean "BusFault exception active bit" (BUSFAULTENA been enabled).

    nRF DCNF doc extract : An attempt to access the blocked resources will trigger a BusFault or a HardFault exception, depending on the value of the BUSFAULTENA bit in the ARM Cortex-M33 SHCSR (system handler control and state register), described in the ARM Cortex-M33 Devices Generic User Guide.

    Link to The domain configuration (DCNF)

    Any idea of why and how to fix ? 



    Maxime

Children
Related
Terms of service