The bootloader is not loading for FMU on Pixhawk 4

PX4 Autopilot
1

Hello,

I have a Holybro Pixhawk 4 board, and I attempted to flash the bootloader onto its IO and FMU chips. Here are the steps I followed:

  1. I downloaded the PX4-Bootloader GitHub repository.
  2. I navigated into the repository and ran the command:
    "make px4fmuv5_bl"
    This generated a .hex file, which I then tried to flash using an ST-Link through the FMU debug port.

The first flashing process was successful. However, I am unable to access the board via QGroundControl (QGC), and the FMU LEDs keep blinking red continuously.

When I attempted to reflash the bootloader, I encountered the errors shown in the images below.

Does anyone know how to resolve this issue?

image
image1829×1001 167 KB

image
image1829×1001 185 KB

How can I reflash the bootloader to the FMU side of this board?

Thank you in advance for your help!

2

I solved the problem. When I proceeded through the terminal as stated on this page, I was getting an error. The solution to the error is as follows.

Error: arm-none-eabi-gdb on stm32 warning: unrecognized item “timeout” in “qSupported” response

  • Ignoring packet error, continuing…
  • warning: unrecognized item “timeout” in “qSupported” response
  • Ignoring packet error, continuing…
  • Remote replied unexpectedly to ‘vMustReplyEmpty’: timeout
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Remote replied unexpectedly to 'vMustReplyEmpty': timeout

Solution:

  1. Open two terminals
  2. Start ST-Link GDB Server st-util -p 3333
  3. Inside the arm-none-eabi-gdb command, instead of “tar ext /dev/serial/by-id/” connect to the server, you can do this like this target extended-remote :3333
  4. The remaining steps are the same. The only thing different on this page is the linking done in step 6.
    `