bfd-register-capture

To capture STM32 register values over time, you can sample peripheral registers via J-Link and export time-stamped snapshots to CSV. This allows you to track hardware state changes for debugging and fault analysis.

Yes, you can export USART and FDCAN peripheral registers to CSV. The tool reads selected register sets during a J-Link debugging session and saves the captured data with timestamps for offline analysis.

Yes, a J-Link debugger is required to snapshot STM32F4 and STM32H7 registers. The tool relies on J-Link workflows to read peripheral addresses and extract register field values for capture.

The best way to track STM32 peripheral register changes is to run a bootstrap profile, select your target peripheral and registers, then perform a repeated capture. This exports a time-stamped CSV snapshot of the hardware state for trend detection.

The bootstrap profile setup aligns your toolchains and configures the environment before capture. By running this setup first, you ensure reproducible register sampling and CSV exports across different STM32 debugging sessions.

Yes, STM32 register capture supports decoding register fields where they are defined. Alongside raw address reads, this allows you to analyze specific peripheral bit-field changes and export them to a CSV file.