Skip to main content
Associate
August 17, 2026
Question

Missing message IDs in STM32N6 BootROM trace parser

  • August 17, 2026
  • 2 replies
  • 63 views

Hello,

I am currently working with the STM32N6 and debugging the boot sequence using the BootROM traces. I am dumping the secure and non-secure RAM ring buffers via STM32CubeProgrammer while the chip is in the Open state (using hotplug).

To decode the traces, I am referring to the “official” ST template: Template_BootRom_traces/FSBL/Src/rom_trace_parser.c.

However, I have noticed that the BootROM outputs several message IDs that are entirely missing from the switch statement in the romTrace_ParseRecord() function. Because these IDs are omitted from the table, they just get skipped by the C API, making it difficult to fully understand the boot execution flow.

My questions are:

  1. Is there an updated version of rom_trace_parser.c available that includes a more complete table of these message IDs?
  2. Alternatively, is there a reference manual or document that lists all possible BootROM trace message codes and their meanings?

 

Any pointers would be greatly appreciated.

Thank you!

2 replies

ST Technical Moderator
August 18, 2026

Hello ​@Jimmy7 

Please refer to the UM3234  

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Saket_Om
Jimmy7Author
Associate
August 18, 2026

Hello Saket_Om,

To decode the traces, I am using the official ST template: rom_trace_parser.c https://github.com/stm32-hotspot/STM32N6-Boot-ROM-Traces/blob/main/Template_BootRom_traces/FSBL/Src/rom_trace_parser.c.

However, the BootROM outputs several message IDs that are entirely missing from the infMSG_ID2String() switch statement. This results in unresolved traces like UNKNOWN_0x2A000001, UNKNOWN_0x00002909, and UNKNOWN_0x0000003B, making it hard to follow the execution flow.

I have searched through all official ST documentation (including UM3234 and RM0486), and these 32-bit trace message codes are completely undocumented in any ST manual. (Note: UM3234 Section 3.10 only documents the high-level 64-bit status word, not the detailed 32-bit hex codes found in the parser https://github.com/stm32-hotspot/STM32N6-Boot-ROM-Traces/blob/main/Template_BootRom_traces/FSBL/Src/rom_trace_parser.c).

Thank you!