Hi!
Setup:
I am using Ozone 3.10b and a STM32H743 @ 480MHz.
I've set up ETF trace according to wiki.segger.com/STM32H7#Tracing_on_ST_STM32H743
In the trace settings dialog, I set the source to Trace Buffer, and CPU Frequency to 480000000.
I'm using the .pex file from
wiki.segger.com/images/b/b8/ST…43_400MHz_TraceBuffer.zip
Problem:
After the OnTraceStart() hook of the pex-File is run, the DBGMCU->IDCODE register at 0x5C001000 reads 0x00000000 instead of the expected 0x20036450.
This can also be seen in Ozone's memory view. OK without trace, 0 after OnTraceStart.
The problem is only resolved by a power cycle. A reset is not sufficient.
This is problematic, because the IDCODE register is used by ST's HAL code to enable errata workarounds:
github.com/STMicroelectronics/…s/system_stm32h7xx.c#L229
github.com/STMicroelectronics/…m32h7xx_hal_adc_ex.h#L579
github.com/STMicroelectronics/…/stm32h7xx_ll_adc.h#L2572
best regards,
Thomas
Setup:
I am using Ozone 3.10b and a STM32H743 @ 480MHz.
I've set up ETF trace according to wiki.segger.com/STM32H7#Tracing_on_ST_STM32H743
In the trace settings dialog, I set the source to Trace Buffer, and CPU Frequency to 480000000.
I'm using the .pex file from
wiki.segger.com/images/b/b8/ST…43_400MHz_TraceBuffer.zip
Problem:
After the OnTraceStart() hook of the pex-File is run, the DBGMCU->IDCODE register at 0x5C001000 reads 0x00000000 instead of the expected 0x20036450.
This can also be seen in Ozone's memory view. OK without trace, 0 after OnTraceStart.
The problem is only resolved by a power cycle. A reset is not sufficient.
This is problematic, because the IDCODE register is used by ST's HAL code to enable errata workarounds:
github.com/STMicroelectronics/…s/system_stm32h7xx.c#L229
github.com/STMicroelectronics/…m32h7xx_hal_adc_ex.h#L579
github.com/STMicroelectronics/…/stm32h7xx_ll_adc.h#L2572
best regards,
Thomas