There's probably a better way to do this (and @dhylands would know how)

I'm sure you know it too - just write suitable linker script (don't rely on vendor mess).

Yeah - we actually already do something like this for the stmhal linker script file.

Look at: https://github.com/micropython/micropython/blob/master/stmhal/stm32f405.ld#L44-L45
where we grab some specific files and put their .text* stuff into the .isr_vector section.

You could change up the pattern to be something like this:

*/py/*.o(.text)

and place that inside the .irom0.text section of the linked elf file.

Think of the linker script as being a mapper which can take sections (.text, .data, whatever) from the various .o files which are passed to it and assemble them together into the .elf which the linker outputs.

In extreme cases you could even generate portions of the linker script from the Makefile or other files.

Here's the linker documentation on how the wildcards work (and the order things appear in the script file is important):
https://sourceware.org/binutils/docs-2.24/ld/Input-Section-Wildcards.html#Input-Section-Wildcards

Uh oh!

ESP8266 support? #986

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions