Skip to main content
Associate
December 16, 2024
Question

No source available for "uwTickPrio0 at 0x20000004

When compiling and debugging with STM32CubeIDE, it shows: uwTickprio0 at 0x200000004 has no available source and the burner is using stlink v2. What is the cause of this problem?

sy556_0-1734343104154.jpeg

sy556_1-1734343182158.jpeg

 

 

This topic has been closed for replies.

7 replies

ST Technical Moderator
December 16, 2024

Hello @sy556 ,

I edited your post to translate it from Chinese to comply with the ST Community guidelines.

If possible, please share more details that can help us to understand and reproduce your issue (which device used? which Cube package and tools version, what do you expect exactly? Are you using a particular Cube example? ....)

Please follow this post on how to write your question to maximize your chances to find a solution:

https://community.st.com/t5/community-guidelines/how-to-write-your-question-to-maximize-your-chances-to-find-a/ta-p/57522

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
sy556Author
Associate
December 16, 2024

What I want to ask is, why is this problem: No Source Available for "uwTickprio0 at 0x20000004, how to solve it? The compiler is STM32CubeIDE 1.12.1, and the programming device is ST-LINK.

ST Technical Moderator
December 16, 2024

Please share more details about your hardware and software used.

But first, please make sure to use the latest release of Cube firmware package. CubeMx and CubeIDE.

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
Tesla DeLorean
Guru
December 16, 2024

So no details about your board the connections, or the code..

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
Pavel A.
December 16, 2024

Likely the program jumped to data (corrupted stack?)