the led isn't lighting up :'(

This commit is contained in:
benstrb 2026-04-06 19:52:48 +02:00
parent 242f218a62
commit 2854adeb13
7 changed files with 74 additions and 65 deletions

View file

@ -1,37 +1,12 @@
/* Memory layout of the STM32F469NI */
MEMORY
{
/* NOTE 1 K = 1 KiBi = 1024 bytes */
/* STM32F302R8T6 from STM32F302R8Tx_FLASH.ld in the STM32Cube archive */
/* or the reference doc at */
/* https://www.st.com/en/microcontrollers-microprocessors/stm32f302.html#resource */
FLASH : ORIGIN = 0x08000000, LENGTH = 2M
RAM : ORIGIN = 0x20000000, LENGTH = 320k
FLASH : ORIGIN = 0x08000000, LENGTH = 2048K
RAM : ORIGIN = 0x20000000, LENGTH = 256K
/* Core Coupled Memory (CCM) SRAM: 128KB at 0x10000000 */
CCMRAM : ORIGIN = 0x10000000, LENGTH = 128K
}
/* This is where the call stack will be allocated. */
/* The stack is of the full descending type. */
/* You may want to use this variable to locate the call stack and static
variables in different memory regions. Below is shown the default value */
/* _stack_start = ORIGIN(RAM) + LENGTH(RAM); */
/* You can use this symbol to customize the location of the .text section */
/* If omitted the .text section will be placed right after the .vector_table
section */
/* This is required only on microcontrollers that store some configuration right
after the vector table */
/* _stext = ORIGIN(FLASH) + 0x400; */
/* Example of putting non-initialized variables into custom RAM locations. */
/* This assumes you have defined a region RAM2 above, and in the Rust
sources added the attribute `#[link_section = ".ram2bss"]` to the data
you want to place there. */
/* Note that the section will not be zero-initialized by the runtime! */
/* SECTIONS {
.ram2bss (NOLOAD) : ALIGN(4) {
*(.ram2bss);
. = ALIGN(4);
} > RAM2
} INSERT AFTER .bss;
*/
/* The stack is of the full size of the RAM, minus the size of the .data section */
_stack_start = ORIGIN(RAM) + LENGTH(RAM);