My time base is wrong about stmviewer HOT 8 CLOSED

Could you verify the timing with systick? Could you attach the full clock setup? Which MCU are you using?

from stmviewer.

"Could you verify the timing with systick?" How can i do this, can you explain further?

STM32F103C8

from stmviewer.

Sure, you could write a value to the CH0 in the SysTick 1kHz interrupt so that we are sure the problem is on STMViewer's side. You can write any value, just make sure it changes every interrupt so that the steps indicate the time period we want to examine.

from stmviewer.

I also tried to increase systick freq. I was able to increase it 10 times and it seems ok. But when ı tried 100 times it broke again. Am i stuck at speed limit? I tried prescaler between 36 to 72 this means a period of 1-2 microseconds .
Why does the problem occur when the systick period is 10 microseconds?

normal settings: HAL_SYSTICK_Config(HAL_RCC_GetHCLKFreq()/1000); //1000

HAL_SYSTICK_Config(HAL_RCC_GetHCLKFreq()/10000); //10000

HAL_SYSTICK_Config(HAL_RCC_GetHCLKFreq()/100000); //100000

This is the oscilloscope view of the real signal. The values i get from the adc seems correct.

from stmviewer.

Which STMViewer version are you on? Are you monitoring the error frames indicators on the left? You're most probably saturating the SWO output.

from stmviewer.

I think you are right about saturation. I am using STMViewer 0.4.0. Maybe ı need better STLİNK.

from stmviewer.

Yes this is possible. I can recommend the ST-Link V3 minie.

Why did you have to check the frames in Cube IDE? Is there a problem with the trace indicators on the left panel in STMViewer? A full screen screenshot would be helpful in the case you're suspecting a saturation.

from stmviewer.

Closing due to inactivity. If you see a similar issue please reopen.

from stmviewer.