Memory specifications via options #2

New Issue

Closed

opened 2023-01-11 04:34:15 +00:00 by alexisvl · 0 comments

alexisvl commented

2023-01-11 04:34:15 +00:00

Owner

Currently, there is just a single fixed linker script (in either ch32v10x-meson or ch32v30x-meson). It's often desirable to specify a location and size offset (for making bootloaders, or bootloaded apps). Also, this series (at least the CH32V30x) allows customizing the amount of SRAM by dedicating different amounts to the flash backing, so we should support this too. This can be done by removing the MEMORY section from the linker scripts and generating a full linker script at build time (in the ch32v libs). We'll also have to figure out how to set the user row for the custom SRAM/flash sizes.

Currently, there is just a single fixed linker script (in either [ch32v10x-meson](https://gitea.alexisvl.rocks/alexisvl/ch32v10x-meson) or [ch32v30x-meson](https://gitea.alexisvl.rocks/alexisvl/ch32v30x-meson)). It's often desirable to specify a location and size offset (for making bootloaders, or bootloaded apps). Also, this series (at least the CH32V30x) allows customizing the amount of SRAM by dedicating different amounts to the flash backing, so we should support this too. This can be done by removing the MEMORY section from the linker scripts and generating a full linker script at build time (in the ch32v libs). We'll also have to figure out how to set the user row for the custom SRAM/flash sizes.