RTT log output issue(sdk, toolchain v3.0.2)

RTT log output issue

Hello,
I am using SDK v3.0.2 and toolchain v3.0.2.
After building and flashing my firmware, no logs are being output to RTT Viewer.
What should I do to resolve this issue?

Additionally, the build completes successfully, but after flashing the firmware to the board, it is not functioning at all—not only is there no log output, but the application itself does not operate.

The application worked properly with toolchain v2.8.0, but after switching to version 3.0.2, this problem started to occur.

LOG: Executing default behavior previously saved in the registry.
LOG: Device will be unsecured now.
LOG: InitTarget() end - Took 386ms
LOG: Failed to attach to CPU. Trying connect under reset.
LOG: Found SW-DP with ID 0x6BA02477
LOG: SWD speed too high. Reduced from 12000 kHz to 8100 kHz for stability
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, ADDR: 0x00000000)
LOG: AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
LOG: AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
LOG: AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
LOG: AP[0]: Core found
LOG: AP[0]: 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: Cortex-M (ARMv8-M and later): The connected J-Link (S/N 20600506) uses an old firmware module that does not handle I/D-cache correctly. Proper debugging functionality cannot be guaranteed if cache is enabled
LOG: FPUnit: 8 code (BP) slots and 0 literal slots
LOG: Security extension: implemented
LOG: Secure debug: enabled
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][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM
LOG: [1][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM
LOG: [1][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
LOG: [0][1]: E0040000 CID B105900D PID 000BBD21 DEVARCH 00000000 DEVTYPE 11 TPIU
LOG: RTT Viewer connected.

 ...

Parents
  • Hi, 

    Are you able to test the NCS v3.0.2  zephyr\samples\hello_world or nrf\samples\bluetooth\peripheral_lbs sample with the following configs? Can you obtain the RTT log?

    CONFIG_LOG=y
    CONFIG_USE_SEGGER_RTT=y
    CONFIG_LOG_BACKEND_RTT=y
    CONFIG_UART_CONSOLE=n
    CONFIG_RTT_CONSOLE=y
    CONFIG_PRINTK=y
    
    CONFIG_LOG_BUFFER_SIZE=2948

    If you still cannot get the RTT log, could you test with nRF5340DK?

    Regards,
    Amanda H.

Reply
  • Hi, 

    Are you able to test the NCS v3.0.2  zephyr\samples\hello_world or nrf\samples\bluetooth\peripheral_lbs sample with the following configs? Can you obtain the RTT log?

    CONFIG_LOG=y
    CONFIG_USE_SEGGER_RTT=y
    CONFIG_LOG_BACKEND_RTT=y
    CONFIG_UART_CONSOLE=n
    CONFIG_RTT_CONSOLE=y
    CONFIG_PRINTK=y
    
    CONFIG_LOG_BUFFER_SIZE=2948

    If you still cannot get the RTT log, could you test with nRF5340DK?

    Regards,
    Amanda H.

Children
Related