Azure RTOS
An Azure embedded development suite including a small but powerful operating system for resource-constrained devices.
331 questions
Link problem when linking libthreadx.a
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 54%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Sai
45
Reputation points
Hi all
I am quite new to Azure RTOS and I have a question when using cortex-m33.
I followed the steps of https://video2.skills-academy.com/en-us/azure/rtos/threadx/chapter2#:~:text=application%20development%20area.-,Using%20ThreadX,-To%20use%20ThreadX to link my bsp port and libthreadx.a, the error is as followed:
.text._tx_initialize_kernel_enter+0x50): undefined reference to `_tx_thread_secure_stack_initialize'
Besides, I removed the "_tx_initialize_low_level()" in _tx_initialize_kernel_enter() because the vector table has been set in the bsp port. Are there any other implements required？
Thank you!
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 22%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
shaunnorris 5 Reputation points2023-07-25T10:20:33.77+00:00 The error message you encountered,
undefined reference to _tx_thread_secure_stack_initialize, indicates that the linker is unable to find the definition for the_tx_thread_secure_stack_initializefunction. This function is provided by Azure RTOS ThreadX and is necessary for proper initialization of the kernel.Based on the information you provided, it seems like you might have removed the
_tx_initialize_low_level()function call, but that function is not responsible for the missing symbol error you're facing. Removing_tx_initialize_low_level()should not be causing this particular problem.To resolve this issue, make sure you have properly linked the ThreadX library (
libthreadx.a) and that you haven't accidentally excluded any necessary files from your build.Here are some steps you can follow to troubleshoot and fix the issue:
Verify ThreadX Library: Double-check that you have correctly linked the
libthreadx.alibrary in your build. Ensure that the library file is present in the correct location and that the linker is set up to include it during the linking phase.- BSP Configuration: Ensure that the BSP (Board Support Package) configuration is correct and includes all the necessary components for Azure RTOS ThreadX. Check if there are any specific configuration options related to ThreadX initialization that you might have missed.
Check Includes and Paths: Ensure that you have included the necessary header files and that the paths to these header files are set correctly. This includes the header files related to ThreadX and any other dependencies.
Verify BSP Port Changes: Double-check the modifications you made to the BSP port to ensure that they are correctly implemented. If you made any changes related to ThreadX initialization or stack setup, review them carefully.
Check for Missing Symbols: Verify that there are no other missing symbols or unresolved references in your code or libraries.
Build Clean: Sometimes, build systems can cache old object files, leading to strange errors. Try cleaning your build and then rebuilding the project.
If you've carefully checked the above points,
Sign in to comment
Sign in to answer