Hello,
This is not entirely clear to me from what I read on the internet.
Is the px4 firmware mainly build for the Pixhawk 4 (as the name says) or is the Pixhawk 2.4.8 fully supported too?
Thanks and regards
Hello,
This is not entirely clear to me from what I read on the internet.
Is the px4 firmware mainly build for the Pixhawk 4 (as the name says) or is the Pixhawk 2.4.8 fully supported too?
Thanks and regards
pixhawk 2.4.8 its fully supported by PX4.
there are two versions… px4fmuv2 and px4fmuv3.
If your board its equipped with the stm32f427vit6 rev3 your board will be flashes with px4fmuv3.
Pixhawk 4 released by holybro its px4fmuv5
i can’t able to install firmware on my Pixhawk 2.4.8 board. its fmuv2; i tried with stable and developers on QGC but uploading fmuv3. please guide me how to upload fmuv2 cause i am building a Pixhawk based rover which i need to integrate using jetson nano. if i can download custom firmware for fmuv2 , please sent me the link.
I also have a Pixhawk 2.4.8 and I’m experiencing similar issues. My board frequently shows sensor errors , and I believe I need to upload a different firmware version to fix these problems.
Currently, the firmware version shown in QGroundControl is 1.15.4 , and the board is detected as FMUv2 . However, when I attempt to update the firmware—similar to what is described in this discussion:
—it still installs FMUv3 , even though my hardware is FMUv2 . After flashing, the vehicle version still shows FMUv2 , not FMUv3, even though FMUv3 was supposedly uploaded.Like screenshoot below.
When I try to follow the suggestion from the link to update the bootloader using the SYS_BL_UPDATE parameter, I cannot find this parameter in my system. It simply doesn’t appear in QGroundControl.
So my questions are:
If there is a custom or legacy firmware specifically built for boards like Pixhawk 2.4.8, I’d appreciate it if someone could share a direct link or explain how to compile or download it manually.
Thanks in advance for your help!
Additionally, for reference, here is the log file from when I armed the vehicle (not during flight) , which might help in diagnosing the issue: