2024-01-07 02:18 AM
Hi There,
I am using a SWV ITM to print the messages but it always stoped printing after 221 counter number as below image. Could any tell us what needs to be set to see continues printing.
2024-01-10 03:53 PM - edited 2024-01-10 03:54 PM
If the clocking rate on the core and the clocking rate on the debugger are not the same it can potentially desynchronize over time. Because if you tell the baud rate for the manchester encoder is one thing, and the core's doing another thing they are going to diverge at some point.
If this is using an ST-LINK/V3 the HSE_VALUE is closer to 8333333 than 8000000
Would suggest reading the SWV baud rate divider value and back computing that the actual rate is. And printing out the Core speed based on the clock sources, and PLL settings.
Did you check with STM32 Cube Programmer, and it's SWV Viewer?
2024-01-10 03:56 PM
Here we do this so we can quick establish wtf a particular board is doing
void SystemDiagnostic(void)
{
printf("\n\nCore=%d, %d MHz\n", SystemCoreClock, SystemCoreClock / 1000000);
CORECheck();
IDCODECheck();
FPUCheck();
printf("APB1=%d\n", HAL_RCC_GetPCLK1Freq());
printf("APB2=%d\n", HAL_RCC_GetPCLK2Freq());
}
2024-01-11 06:25 AM
Hi Tesla,
Thanks i used above code and PCLK1 and PCLK2 frequency are same 170MHz.
I think this is the issue in STM cube ID software.
I tested the same code in STM cube programmer, I did not find any issue at all.
2024-01-11 06:58 AM - edited 2024-01-11 06:59 AM
I tested just prinf ... in IDE (1.13.1) :
26242 lines text ..then error.
this might be the problem:
(But my buffer is already at 2000000; try to increase yours.)
2024-01-11 07:41 AM
Hi AScha,
I am using FreeRTOS and I am using UBUNTU and STM cube ID is 1.14.0.
Im my case i have not seen above messages as my trace buffer size is 2000000.
2024-01-11 08:05 AM - edited 2024-01-11 08:11 AM
Hi @Tesla DeLorean ,
btw
HSE_VALUE on (new) H563-nucleo is 8M , from ST-LINK/V3 onboard,
i tested mco , makes 10,000xx Mhz on DSO counter.
"NEW" : stlink has 24M clk on H563-nucleo 144 here ... :)
NOT the (older) 25M oszillator , giving 25/3 = 8,3333 M ; (silly idea) on H7B3-disco here:
ps : But somewhere in the big company the guy with the "25MHz" reference idea still working,
because there is a crystal onbord the new H563-nucleo 144 , and guess which frequ.:
2024-01-11 10:21 AM
https://community.st.com/t5/stm32cubeide-mcus/swv-itm-data-console-is-empty/m-p/599578
Need to determine the SWO->CODR address for the G4, and the wire rate of the SWCLK
https://developer.arm.com/documentation/ddi0314/h/Chdgfafd
Probably 0xE0003010