Skip to content

Release v1.4 Tracking #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
3 of 4 tasks
firmwareguru opened this issue Dec 12, 2022 · 2 comments
Closed
3 of 4 tasks

Release v1.4 Tracking #7

firmwareguru opened this issue Dec 12, 2022 · 2 comments

Comments

@firmwareguru
Copy link
Contributor

firmwareguru commented Dec 12, 2022

Tracking release v1.4

New boards with Cube reference designs:

  • DISCO-F469I
  • NUCLEO-G0B1RE
  • NUCLEO-G491RE
  • NUCLEO-WLE5JC1
@firmwareguru
Copy link
Contributor Author

firmwareguru commented Dec 20, 2022

Added board support with libraries and test binaries for:

  • NUCLEO-G0B1RE
  • NUCLEO-WL55JC

The G0B1RE board expands the stm32-secure-patching-bootloader into the STM32G-series. These are very similar to their "STM32L" namesakes (e.g G0 <-> L0) but have been modernized a bit in terms of flash operation.

The NUCLEO-WL55JC board support functions similarly to the existing LORA-E5 board support with exception of different LED, button and UART GPIO assignments, and a slightly modified flash layout.

The 1.4.0-preview2 tag contains updates:

  • make_keys.bat replaced with make_keys_vXm.bat to ensure machine.txt is generated.
  • CRC clock is always enabled by patching engine when needed.
  • Added a new linker symbol STM32_SECURE_PATCHING_BOOTLOADER_RAM_TOP that can be used to define the device's stack limit and SRAM size instead of hard-coding it. It was possible for the bootloader and application to have different views of SRAM and this can be problematic. This ensures both have the same view. It is always set to the end of device SRAM. The application can set this lower for its own purposes if needed, but not higher.

@firmwareguru
Copy link
Contributor Author

v1.4.0 is released without G4 support; G4 support is pushed back to a later release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant