Skip to main content
Associate II
June 10, 2024
Question

Segger RTT doesn't work when the touchgfx is initiated.

  • June 10, 2024
  • 3 replies
  • 1834 views

Hello,

I am using the touchgfx designer generated project as template to develop my project.  The DK I am using is the STM32U5G9J-DK1. 

I tried to bring up the Segger RTT viewer feature.  The RTT works well before the ToughGFX initialization.  If I comment out the ToughGFX initiation functions and its tasks [ MX_TouchGFX_Init() & MX_TouchGFX_PreOSInit() ], the RTT print can work in the FreeRTOS tasks.  But once I leave the TouchGFX initialization as it is, the RTT stops working after it. 

It seems the RTT and touchgfx have some conflict, but I cannot figure out the root cause. 

Thank you very much,

Thanks, 

 

3 replies

Andrew Neil
Super User
June 10, 2024
A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
lhz412Author
Associate II
June 10, 2024

Thank you, Andrew,  I will try to reach Segger, too. 

Graduate II
June 10, 2024

Hello

Im not familiar with RTT but could it be conflict in CRC module. 

Here is some workaround suggestion in another context though:

https://community.st.com/t5/stm32-mcus-touchgfx-and-gui/what-are-the-crc-dependencies-that-touchgfx-expect/m-p/645625

Br JTP

lhz412Author
Associate II
June 10, 2024

Thank you for the information.  I just tried your clue and verified that the CRC is not the root cause. But good to know the CRC in the touchgfx could cause some issue.  Thank you.     

ST Employee
June 11, 2024

Hello @lhz412 and @JTP1 ,

 

CRC is used by TouchGFX but only at startup so it should not be the root cause of the problem.

 

Regards,

Pavel A.
Super User
June 10, 2024

It seems the RTT and touchgfx have some conflict

Over the RAM buffer allocated to the RTT?