RTT Viewer doesn't show any debug messages of hci_rpmsg from nRF5340 NET core

Procedure to reproduce this issue.
1. cd D:\ncs\v2.3.0\zephyr\samples\bluetooth\hci_rpmsg
2. west build -b nrf5340dk_nrf5340_cpunet
3. west flash
4. Lauching RTT Viewer and selecting NRF5340_XXAA_NET target device
5. RTT Viewer doesn't show any debug messages

The following are log messages of RTT Viewer. Why does it shows "Security extension: not implemented"?

LOG: J-Link RTT Viewer V7.88k: Logging started.
LOG: Terminal 0 added.
LOG: Connecting to J-Link via USB...
LOG: Device "NRF5340_XXAA_NET" selected.
LOG: ConfigTargetSettings() start
LOG: ConfigTargetSettings() end - Took 13us
LOG: InitTarget() start
LOG: InitTarget() end - Took 4.11ms
LOG: Found SW-DP with ID 0x6BA02477
LOG: DPIDR: 0x6BA02477
LOG: CoreSight SoC-400 or earlier
LOG: AP map detection skipped. Manually configured AP map found.
LOG: AP[0]: AHB-AP (IDR: Not set)
LOG: AP[1]: AHB-AP (IDR: Not set)
LOG: AP[2]: MEM-AP (IDR: Not set)
LOG: AP[3]: MEM-AP (IDR: Not set)
LOG: AP[1]: Core found
LOG: AP[1]: AHB-AP ROM base: 0xE00FE000
LOG: CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
LOG: Feature set: Mainline
LOG: Cache: No cache

LOG: Found Cortex-M33 r0p4, Little endian.
LOG: FPUnit: 8 code (BP) slots and 0 literal slots
LOG: Security extension: not implemented
LOG: CoreSight components:
LOG: ROMTbl[0] @ E00FE000
LOG: [0][0]: E00FF000 CID B105100D PID 000BB4C9 ROM Table
LOG: ROMTbl[1] @ E00FF000
LOG: [1][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33
LOG: [1][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT
LOG: [1][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB
LOG: [1][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
LOG: RTT Viewer connected.

Parents Reply Children
  • Please try the sample attached below and let me know if you get the same result. Only change I made was to add the child_image->hci_rpmsg config overlay.

    2161.peripheral_lbs_rtt.zip

  • Thanks for your reply! I didn't get same result.

    00> *** Booting Zephyr OS build v3.2.99-ncs2 ***
    00> Start[[00:00:00.002,563] <inf> bt_hci_raw: Bluetooth enabled in RAW mode
    00> [00:00:00.002,868] <err> os: ***** BUS FAULT *****
    00> [00:00:00.002,899] <err> os: Precise data bus error
    00> [00:00:00.002,899] <err> os: BFAR Address: 0x20070000
    00> [00:00:00.002,929] <err> os: r0/a1: 0x210026c0 r1/a2: 0x00000001 r2/a3: 0x00000001
    00> [00:00:00.002,929] <err> os: r3/a4: 0x20070000 r12/ip: 0x01025d7d r14/lr: 0x0102a4c9
    00> [00:00:00.002,960] <err> os: xpsr: 0x69000000
    00> [00:00:00.002,960] <err> os: Faulting instruction address (r15/pc): 0x0102d392
    00> [00:00:00.002,990] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
    00> [00:00:00.003,021] <err> os: Current thread: 0x21008000 (unknown)
    00> [00:00:00.285,186] <err> fatal_error: Resetting system
    00> *** Booting Zephyr OS build v3.2.99-ncs2 ***
    00> Start[[00:00:00.002,593] <inf> bt_hci_raw: Bluetooth enabled in RAW mode
    00> [00:00:00.002,868] <err> os: ***** BUS FAULT *****
    00> [00:00:00.002,899] <err> os: Precise data bus error
    00> [00:00:00.002,899] <err> os: BFAR Address: 0x20070000[0m
    00> [00:00:00.002,929] <err> os: r0/a1: 0x210026c0 r1/a2: 0x00000001 r2/a3: 0x00000001
    00> [00:00:00.002,929] <err> os: r3/a4: 0x20070000 r12/ip: 0x01025d7d r14/lr: 0x0102a4c9
    00> [00:00:00.002,960] <err> os: xpsr: 0x69000000
    00> [00:00:00.002,960] <err> os: Faulting instruction address (r15/pc): 0x0102d392
    00> [00:00:00.003,021] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
    00> [00:00:00.003,051] <err> os: Current thread: 0x21008000 (unknown)
    00> [00:00:00.285,186] <err> fatal_error: Resetting system[0m

    Procedure to reproduce this issue is as follows.

    1. cd D:\ncs\v2.3.0\nrf\samples\peripheral_lbs_rtt

    2. west build -b nrf5340dk_nrf5340_cpuapp

    3. west flash --recover

    4. Launching RTT Viewer and rebooting nRF5340 board.

    5. RTT Viewer shows "BUS FAULT".

  • I don't understand why you get this MPU fault when you build the same project as I did. I did not get this error.

    Could you run the command below to see if you have any modified files in the SDK tree? 

    $ west forall -c "git status"

Related