No RTT output when enabling mcuboot

RE: No RTT output when enabling mcuboot

Einar Thorsrud — Mon, 03 Mar 2025 15:47:20 GMT

Hi,

I am sorry for the delay. Have you made any progess on this on your end?

I do not see anything missing you your custom board build folder related to RTT logging, it all seems to be in place.

I am also wondering about this strange RTT og with duplicated letters you are getting without bootloader, which I have not seen before. Just out of curiosity, would that look the asme if you set CONFIG_RTT_TX_RETRY_CNT=3 (instad of 2 which is default)?

RE: No RTT output when enabling mcuboot

mackz — Fri, 21 Feb 2025 14:36:10 GMT

devzone.nordicsemi.com/.../combined_5F00_archive.tar.gzHere are the build folders for the custom board and thingy91

RE: No RTT output when enabling mcuboot

mackz — Fri, 21 Feb 2025 14:06:09 GMT

RE: Building a custom board in VS Code for nRF9160, and getting an error
I added the suggested mcuboot.conf to the hello_world project and tried again but got no output on rttViewer when i built for the custom board.
But when i tried building for thingy91_9160_ns and flashing the file to the custom board i get output.

RE: No RTT output when enabling mcuboot

mackz — Fri, 21 Feb 2025 12:48:52 GMT

****** BBoooottiinngg nnRRFF CCoonnnneecctt SSDDKK vv33..55..9999--nnccss11--11 ******

II:: SSttaarrttiinngg bboooottllooaaddeerr

II:: PPrriimmaarryy iimmaaggee:: mmaaggiicc==uunnsseett,, sswwaapp__ttyyppee==00xx11,, ccooppyy__ddoonnee==00xx33,, iimmaaggee__ookk==00xx33

II:: SSeeccoonnddaarryy iimmaaggee:: mmaaggiicc==uunnsseett,, sswwaapp__ttyyppee==00xx11,, ccooppyy__ddoonnee==00xx33,, iimmaaggee__ookk==00xx33

II:: BBoooott ssoouurrccee:: nnoonnee

II:: IImmaaggee iinnddeexx:: 00,, SSwwaapp ttyyppee:: nnoonnee

II:: BBoooottllooaaddeerr cchhaaiinnllooaadd aaddddrreessss ooffffsseett:: 00xxcc000000

II:: JJuummppiinngg ttoo tthhee ffiirrsstt iimmaaggee sslloott

EE:: PPrrootteecctt mmccuubboooott ffllaasshh ffaaiilleedd,, ccaanncceell ssttaarrttuupp..

I also get this sometimes when i run the build for the custom board on the DK

RE: No RTT output when enabling mcuboot

mackz — Fri, 21 Feb 2025 12:38:13 GMT

It seems like the application is never loaded after mcuboot. I sent you the board files in a private message. I have tried to change them to follow the thingy91 and also tried to make them more like nrf9160dk, but i cant get it to work.

RE: No RTT output when enabling mcuboot

mackz — Fri, 21 Feb 2025 12:18:37 GMT

When i use the partition conf from thingy91 i get that weird output and when i use the one from the DK i get nothing

RE: No RTT output when enabling mcuboot

mackz — Fri, 21 Feb 2025 11:47:20 GMT

When using a custom nrf9160 board is it better to use the partition_conf from thingy91 or the DK?

RE: No RTT output when enabling mcuboot

mackz — Fri, 21 Feb 2025 10:07:24 GMT

I have noticed that when i remove CONFIG_BOOTLOADER_MCUBOOT=y from the custom boards _ns_defconfig but enable it in prj.conf i get this output in the RTTViewer, when i add CONFIG_BOOTLOADER_MCUBOOT=y back to the _ns_defconfig i get no output.

******  BBoooottiinngg  nnRRFF  CCoonnnneecctt  SSDDKK  vv33..55..9999--nnccss11--11  ******

II::  SSttaarrttiinngg  bboooottllooaaddeerr

II::  PPrriimmaarryy  iimmaaggee::  mmaaggiicc==uunnsseett,,  sswwaapp__ttyyppee==00xx11,,  ccooppyy__ddoonnee==00xx33,,  iimmaaggee__ookk==00xx33

II::  SSeeccoonnddaarryy  iimmaaggee::  mmaaggiicc==uunnsseett,,  sswwaapp__ttyyppee==00xx11,,  ccooppyy__ddoonnee==00xx33,,  iimmaaggee__ookk==00xx33

II::  BBoooott  ssoouurrccee::  nnoonnee

II::  IImmaaggee  iinnddeexx::  00,,  SSwwaapp  ttyyppee::  nnoonnee

II::  BBoooottllooaaddeerr  cchhaaiinnllooaadd  aaddddrreessss  ooffffsseett::  00xx1100000000

II::  JJuummppiinngg  ttoo  tthhee  ffiirrsstt  iimmaaggee  sslloott

RE: No RTT output when enabling mcuboot

Einar Thorsrud — Fri, 21 Feb 2025 09:05:21 GMT

I see. Then this should really work on the custom board as well. At least from an RTT perspective, as that does not depend on anything on the board (just the SoC itself and the debugger). Can you debug a bit further to verify that the application runs properly and that the code that should log to RTT runs successfully? Perhaps stepping down and verifying if things actually gets written to the RTT Buffer, or if not, why?

RE: No RTT output when enabling mcuboot

mackz — Thu, 20 Feb 2025 06:34:47 GMT

If i program the DK with the project built for the custom board i get

 "[Sec Thread] Secure image initializing!
TF-M isolation level is: 0x00000001
Booting TF-M v2.0.0"

in the serial terminal and then i get the "hello world" application output in the JLinkRTTViewer.

RE: No RTT output when enabling mcuboot

Einar Thorsrud — Wed, 19 Feb 2025 13:08:57 GMT

Thanks. Looking at these files, in both cases the map files look good and same with regards to RTT, and also the configs. I do not see anything that explains this. What happens if you build and run the project built for the custom board on the DK (I assuem somethings will fail, but perhaps not until after something has been written to the RTT buffer). Do you get output then?

RE: No RTT output when enabling mcuboot

mackz — Mon, 17 Feb 2025 09:01:05 GMT

devzone.nordicsemi.com/.../build_5F00_folders.tar.gz

"build" is the build folder for the custom board and "build_1" is for the devkit.

RE: No RTT output when enabling mcuboot

Einar Thorsrud — Mon, 17 Feb 2025 08:53:46 GMT

I see. There must be something though, and I am not able to see what that oculd be.. Can you share your custom board files as well as the map file (or full build folder again) you bild for the DK (where you confirmed RTT works and the map file for your custom board (where it does not)? (same exact project, just built for the working and non-working board)

RE: No RTT output when enabling mcuboot

mackz — Fri, 14 Feb 2025 06:27:15 GMT

The defconfigs are exactly the same as thingy 91 except that i have removed:

CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

from both secure and non secure.

RE: No RTT output when enabling mcuboot

Einar Thorsrud — Thu, 13 Feb 2025 15:16:50 GMT

I see. There should not be a fundamental difference between a DK and a custom board when it comes to RTT, as it is just a RAM buffer that is accessed by the degbugger, so I suspect a configuration issue of some sort. Can you share your board files for your custom board?

RE: No RTT output when enabling mcuboot

mackz — Thu, 13 Feb 2025 14:44:31 GMT

I managed to fix the secure fault by adding some missing configurations in my boards defconfig files. But the main issue still remains, i cant see any logs on my custom board when mcuboot is enabled.

this is my build folder now:
devzone.nordicsemi.com/.../2630.build.tar.gz

RE: No RTT output when enabling mcuboot

mackz — Thu, 13 Feb 2025 14:24:06 GMT

I tried to use your config but still got no output on my custom nrf9160 board. I got when i built and ran it for nrf9160 devkit like before. I also tried to run the build for the custom board on the devkit and then i got:

[Sec Thread] Secure image initializing!
TF-M isolation level is: 0x00000001
Booting TF-M v2.0.0
FATAL ERROR: SecureFault
Here is some context for the exception:
    EXC_RETURN (LR): 0xFFFFFFBD
    Exception came from non-secure FW in thread mode.
    xPSR:    0x60000007
    MSP:     0x20000BF8
    PSP:     0x200018B8
    MSP_NS:  0x2000E770
    PSP_NS:  0x2000E590
    Exception frame at: 0x2000E590
        R0:   0x40000105
        R1:   0x020103F5
        R2:   0x2000E660
        R3:   0x2000E688
        R12:  0x00019850
        LR:   0x0001B78F
        PC:   0x00007C20
        xPSR: 0x61000000
    Callee saved register state:        R4:   0x00007C21
        R5:   0x40000105
        R6:   0x020103F5
        R7:   0x2000E660
        R8:   0x00000000
        R9:   0x00019850
        R10:  0x00019850
        R11:  0x00019850
    CFSR:  0x00000000
    BFSR:  0x00000000
    BFAR:  Not Valid
    MMFSR: 0x00000000
    MMFAR: Not Valid
    UFSR:  0x00000000
    HFSR:  0x00000000
    SFSR:  0x00000001
    SFAR: Not Valid

addr2line -e zephyr.elf 0x0001B78F
/home/ncs/v2.6.1/zephyr/modules/trusted-firmware-m/interface/interface.c:60

shows that it is coming from

tfm_ns_interface_dispatch()
and the line:
result = fn(arg0, arg1, arg2, arg3);



here is the build folder: 
devzone.nordicsemi.com/.../0361.build.tar.gz

RE: No RTT output when enabling mcuboot

mackz — Thu, 13 Feb 2025 14:10:49 GMT

It works for me aswell if i run it on nrf9160 devkit. It is on the custom board it is not working. I tried to copy your conf but still could not get any output. devzone.nordicsemi.com/.../build.tar.gz

I have included my build folder that is not working.

If i try to run the build for the custom board on the devkit i can see in serial terminal that i get:

[Sec Thread] Secure image initializing!
TF-M isolation level is: 0x00000001
Booting TF-M v2.0.0
FATAL ERROR: SecureFault
Here is some context for the exception:
    EXC_RETURN (LR): 0xFFFFFFBD
    Exception came from non-secure FW in thread mode.
    xPSR:    0x60000007
    MSP:     0x20000BF8
    PSP:     0x200018B8
    MSP_NS:  0x2000E770
    PSP_NS:  0x2000E590
    Exception frame at: 0x2000E590
        R0:   0x40000105
        R1:   0x020103F5
        R2:   0x2000E660
        R3:   0x2000E688
        R12:  0x00019850
        LR:   0x0001B78F
        PC:   0x00007C20
        xPSR: 0x61000000
    Callee saved register state:        R4:   0x00007C21
        R5:   0x40000105
        R6:   0x020103F5
        R7:   0x2000E660
        R8:   0x00000000
        R9:   0x00019850
        R10:  0x00019850
        R11:  0x00019850
    CFSR:  0x00000000
    BFSR:  0x00000000
    BFAR:  Not Valid
    MMFSR: 0x00000000
    MMFAR: Not Valid
    UFSR:  0x00000000
    HFSR:  0x00000000
    SFSR:  0x00000001
    SFAR: Not Valid

repeatedly.

RE: No RTT output when enabling mcuboot

Einar Thorsrud — Thu, 13 Feb 2025 14:03:45 GMT

I see. Can you share the exact project you are using with your changes? I ask because I am not able to reproduce. If I use the unmodified hello_world sample from SDK 2.6, and add this to prj.conf:

CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_SEGGER_RTT_BUFFER_SIZE_UP=4096
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_PRINTK=y
CONFIG_UART_CONSOLE=n
CONFIG_CONSOLE=y
CONFIG_RTT_CONSOLE=y

CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUBOOT_BOOTUTIL_LIB=y

I get this RTT output:

SEGGER J-Link V8.12c - Real time terminal output
SEGGER J-Link (unknown) V1.0, SN=960061150
Process: JLinkExe
Hello World! nrf9160dk_nrf9160
*** Booting nRF Connect SDK v3.5.99-ncs1-2 ***

Note that there is a difference in the config here, as with your config, the printf is not forwarded ot RTT (but you should stil see the bot banner ("*** Booting nRF Connect SDK v3.5.99-ncs1-2 ***"), and I do that if I test your exact configuration).

RE: No RTT output when enabling mcuboot

mackz — Thu, 13 Feb 2025 10:30:23 GMT

nrfjprog --memrd 0x20000000 --n 0x40000 > full_ram_dump.txt i ran this

and then used ctrl + F with "SE" and "RT" but could not find the magic string.

RE: No RTT output when enabling mcuboot

Einar Thorsrud — Thu, 13 Feb 2025 10:04:36 GMT

I see. Can you dump the RAM of the device and search for the RTT buffer in it (see this post)? Do you find the magic string marking the start of the RTT buffer? Do you find only one instance or multiple? And does it work if you explicitly configure the RTT viewer to look in that address?

RE: No RTT output when enabling mcuboot

mackz — Thu, 13 Feb 2025 09:37:09 GMT

This is what i get when i connect via JLinkRTTViewer:
LOG: Cortex-M: The connected J-Link (S/N 1050014356) uses an old firmware module: V1 (current is 2)
LOG: Cortex-M (ARMv8-M and later): The connected J-Link (S/N 1050014356) 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] @ E00FF000
LOG: [0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33
LOG: [0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT
LOG: [0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB
LOG: [0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM
LOG: [0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM
LOG: [0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
LOG: RTT Viewer connected.

But i get no output.

I am using a nrf5340dk to communicate with the nrf9160.

RE: No RTT output when enabling mcuboot

mackz — Wed, 12 Feb 2025 12:23:01 GMT

I have confirmed that the application actually is started, i am reopening and reconnecting each time after flashing the device but I still get no output I even tried to set the adress manually from the output that I got from the objdump.

RE: No RTT output when enabling mcuboot

Einar Thorsrud — Wed, 12 Feb 2025 12:11:31 GMT

Hi,

Can you start by verifying that the application is actually started? For instance by toggling a GPIO, or checking something else that is observable from the outside?

Other than that, RTT is tricky because it uses a buffer in RAM that is allocated build time, so it will typically move when you re-build the application. Therefore, you normally always need to open the RTT viewer again after flashign new firmware. (The RTT viewer seraches for a magic pattern, and decides on where the buffer is. It will not serch again automatically unless you re-open it).