Fixed the invalid module data pointers in the absolute module load (#699)

Browse Source

An absolutely located module has its code and its data placed at two
independent fixed addresses by the module's linker script. The module
preamble carries the code and data sizes but not the data address, so
_txm_module_manager_absolute_load() could not determine where the
module's data area was. It computed txm_module_instance_data_start
from the code size and the preamble size, which yields a size rather
than an address, and it set txm_module_instance_module_data_base_address
one past the end of the byte pool allocation.

Added _txm_module_manager_absolute_load_extended(), which accepts the
module's data area address from the caller. Deprecated
_txm_module_manager_absolute_load(), which now forwards to the extended
service with an unknown data area location and rejects modules that
request memory protection, since the memory protection hardware cannot
be programmed to cover an unknown data area.

Fixes #450

Assisted-by: Copilot (Opus 5) <noreply@github.com>

...

This commit is contained in:

Frédéric Desbiens

2026-09-08 10:03:45 -04:00

committed by GitHub

parent d7789f0b12

commit b0ec8bfbb9

7 changed files with 578 additions and 377 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

common_modules/module_manager/src/txm_module_manager_absolute_load.c

+48 -369

File diff suppressed because it is too large Load Diff

common_modules/module_manager/src/txm_module_manager_absolute_load_extended.c

+486

File diff suppressed because it is too large Load Diff