Skip to content

Fix vector table bug when using bootloader on STM32WB55 #12958

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

Merged
merged 1 commit into from
May 13, 2020
Merged

Fix vector table bug when using bootloader on STM32WB55 #12958

merged 1 commit into from
May 13, 2020

Conversation

VeijoPesonen
Copy link
Contributor

Summary of changes

The address of the vector table is hardcoded to the start of flash in
many, if not all, ST targets. This causes a crash in applications that
are using a bootloader. This patch updates the board STM32WB55 so it
properly handle updating the VTOR with a bootloader.

Solution has been copied from the PR #3798.

Impact of changes

Migration actions required

Documentation


Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[X] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers

@ARMmbed/team-st-mcd
@SeppoTakalo
@TeroJaasko


The address of the vector table is hardcoded to the start of flash in
many, if not all, ST targets. This causes a crash in applications that
are using a bootloader.  This patch updates the board STM32WB55 so it
properly handle updating the VTOR with a bootloader.

Solution has been copied from the PR #3798.
Copy link
Contributor

@kjbracey kjbracey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how long @VeijoPesonen spent investigating this. Seems like it would be a good idea to finally update every ST target.

And/or stick some documentation somewhere in a bootloader HOWTO?

@jeromecoutant
Copy link
Collaborator

Seems like it would be a good idea to finally update every ST target.

Yes, it is now part of my "driver update" script!
Needs time to apply it for all STM32 sub families

@0xc0170
Copy link
Contributor

0xc0170 commented May 12, 2020

ci started

@mbed-ci
Copy link

mbed-ci commented May 12, 2020

Test run: SUCCESS

Summary: 6 of 6 test jobs passed
Build number : 1
Build artifacts

@0xc0170 0xc0170 merged commit cb4449a into ARMmbed:master May 13, 2020
@mergify mergify bot removed the ready for merge label May 13, 2020
@VeijoPesonen VeijoPesonen deleted the stm32wb_vtor_bootloader branch May 14, 2020 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants