aboutsummaryrefslogtreecommitdiff
path: root/projects/bootloader
AgeCommit message (Collapse)Author
2016-07-10Check jumpers JP7 and JP8 before accepting new firmware or bootloader images.Paul Selkirk
Unfortunately, we can't read the jumper GPIOs directly, as that just gives us the last values written to them, so we see if we can read the FPGA configuration memory.
2016-06-28Fix the bootloader to accept firmware (with PIN login).Paul Selkirk
This involves entirely too much duplication of the CLI.
2016-06-13Only the HSM project needs the RTOS; most of the test projects can use the ↵Paul Selkirk
STM32 HAL code directly.
2016-06-08bootloader doesn't need stm-fmc eitherFredrik Thulin
2016-06-07Check the HARDWARE_EARLY_DFU_JUMP flag as soon as possible in the boot process.Paul Selkirk
This avoids the situation where the bootloader systick happens during firmware initialization, and freaks out. Also build the bootloader with the minimum resources needed (no RTOS, no SPI, no I2C).
2016-05-27DFU working - but no signature validation for now.Fredrik Thulin
2016-05-26Implement a bootloader.Fredrik Thulin
This bootloader is now the application at 0x08000000 (FLASH start), which the STM32 will execute upon reset. The other applications are now loaded at 0x08030000 (128 KB into the flash) and will never get started unless the bootloader has been programmed into flash too.