Skip to content
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

What is the "bug" that was corrected for 2MB flash on the FMUv3? #119

Open
Zipdox2 opened this issue Dec 8, 2023 · 3 comments
Open

What is the "bug" that was corrected for 2MB flash on the FMUv3? #119

Zipdox2 opened this issue Dec 8, 2023 · 3 comments

Comments

@Zipdox2
Copy link

Zipdox2 commented Dec 8, 2023

The PX4 docs read:

FMUv3 open hardware design, which corrects a bug that limited the original Pixhawk 1 to 1MB of flash.

What is this bug? Is it just replacing the MCU, which I assume was the STM32F427VG (can't find a barebones picture), with a STM32F427VI, which has 2MB flash? Or is there something else?

@Zipdox2 Zipdox2 changed the title What is the "bug" that was corrected for 2MB flash on teh FMUv3? What is the "bug" that was corrected for 2MB flash on the FMUv3? Dec 8, 2023
@hamishwillee
Copy link
Contributor

@proficnc
Copy link

proficnc commented Dec 8, 2023

A bug with FMUv2 wasn't fixed. The chip used on FMUv3 was a newer version where the hardware issues had been resolved.

When I designed FMUv3, it was specifically for Pixhawk 2.0 (which became the cube)

FMUv3 later got modified to accommodate fmuv2 PCBs with the updated chip.

I would be very surprised if there are still 1M issue stm32F427 out there. Even on Pixhawk 1 clones.

@Zipdox2
Copy link
Author

Zipdox2 commented Dec 8, 2023

So if I were to build the FMUv2 PCB with new STM32F427 chips I would be able to use the full 2MB?

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

3 participants