This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(275.2, 2%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH9%3C/text%3E%3C/svg%3E)
Hello
The module requirements (see https://learn.microsoft.com/en-us/azure/rtos/threadx-modules/chapter2) state that modules need to be built with position independent code and data. I understand that this is required when the module needs to be loaded/executed from a memory area that is not known at link time.
IAR documents in https://www.iar.com/knowledge/support/technical-notes/compiler/ewarm-position-independent-code-and-data-ropi-and-rwpi-ewarm-5.50/ some limitations to position independent code and data.
I wonder if building with position independent code and data is only required to be free where the module gets placed within deployment and RAM used during runtime. In other words: Can modules also be build without position independent code and data. The only difference is that the module needs to be deployed to memory where it is linked to. Additionally, the RAM area needs to be fixed at link time. This both is a matter of linker configuration.
Are there more to change other than IAR compiler code generation settings and IAR linker command file (remove 'movable' command from block definition)?
Are there other notable changes or limitation when not using position independent code and data.
Thanks for support
Peter
![](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(214.4, 74%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
@HugPeter-9392 The doc has been updated as per the feedback. Please have a look and let us know if you have any further queries.
See: Module Manager APIs
![](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(25.6, 6%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
Our documentation hasn't been updated with this newer API, but function txm_module_manager_absolute_load is exactly what you are looking for. The module doesn't need to be built with any position independence. See example of its use in the A35 example.
Hello
Great, this function looks pretty for what I am looking for.
I tried it. Now I observe a memory fault exception. I could not yet find the reason for it. Is there any special configuration required to use txm_module_manager_absolute_load? I'm working with a Cortex-M7 (STM32H7x)
Thanks, Peter
There is no special configuration, other than making sure that your linker files are not overlapping each other. If you can't figure it out, please contact azure-rtos-support@microsoft.com.
I'm not used to gnu/ac6 tool chain, but I could fix it for IAR. When a module should be loaded by use of txm_module_manager_in_place_load.c instead of txm_module_manager_in_place_load.c the following changes are required.
Module preamble
Remove the subtraction of the 'program location counter' (-> the dot operator) from function address. Generic example:
// Original:
DC32 my_function_name - . - 0 // Comment
// Changed (-> remove '- . - 0'):
DC32 my_function_name // Comment
Linker configuration file
Remove from the block definition the movable keyword.
IAR project file
Clear in Options -> C/C++ Compiler -> Code -> Position-independence all options.
Ah, yes, all of the relative positioning syntax and options need to be removed. Thanks for the additional information!