alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
71cf821659
esp-idf/tools/test_apps/build_system/ldalign_test
History
Omar Chebib 974b8dd4c4 build: (Custom) App version info is now on a dedicated section, independent of the rodata alignment 
It is now possible to have any alignment restriction on rodata in the user
applicaiton. It will not affect the first section which must be aligned
on a 16-byte bound.

Closes https://github.com/espressif/esp-idf/issues/6719
Closes https://github.com/espressif/esp-idf/issues/6976
2021-05-10 11:17:58 +08:00
..
main build: (Custom) App version info is now on a dedicated section, independent of the rodata alignment 2021-05-10 11:17:58 +08:00
check_alignment.py build: (Custom) App version info is now on a dedicated section, independent of the rodata alignment 2021-05-10 11:17:58 +08:00
CMakeLists.txt build: (Custom) App version info is now on a dedicated section, independent of the rodata alignment 2021-05-10 11:17:58 +08:00
README.txt build: (Custom) App version info is now on a dedicated section, independent of the rodata alignment 2021-05-10 11:17:58 +08:00

README.txt 

Runs a build test to check alignment and position of `.flash.appdesc` and
`.flash.rodata` sections. Indeed, `.flash.appdesc` shall ALWAYS be aligned on
a 16-byte bounds, whereas `.flash.rodata` can have any alignment. In any case,
the end address of first one shall match the start address of the second one.
This will let both of them be merged when generating the final bin image.
The Python script that performs the checks, `check_alignment.py`, automatically
runs after the app is built.