Ardupilot firmware can not running on a fmuv5 board

Hardware Pixhawk family
,
1

Hi there!
I have a self-made fmuv5 board and try to use Ardupilot firmware.

I found the bootloader file from the following URL.

Then I transferred it to the board using the STM32 ST-Link. Everything looks good up to this step.

Then I used Mission Planner to flash the official firmware to board and the process went fine. But after that I couldn’t connect the flight controller to the computer and the flight controller didn’t seem to work properly.

And there are the following evens:
a) After the board was connected to the computer (which means it was powered), the FMU LED on the board would flash for a few seconds and then stop flashing. The tri-color LED on the board never turned on;
b) Also after the board was connected to the computer, the MP would detect a serial port (shown as COM13, MAVLink on my computer and Ardupilot in the device manager). This serial port disappeared after the FMU LED stopped flashing. It was immediately replaced by COM15 MAVLink and COM14 SLCAN. I could not connect the board to the MP through the COM15 MAVLink port at any baud rate.
c) Using QGC to burn the firmware and connect the board has the same phenomenon;
d) Using QGC to burn the PX4 firmware is OK. The board works fine.
e) I tried to read the data on COM15 MAVLink. At 115200 baud rate, COM15 steadily sends a set of text “Unable to init RAMTRON storage”

I can’t tell if this is a hardware problem or if there is something I missed when burning the firmware or bootloader.

So what should I do on next？Thx:)

2

CUAV V5 Nano is a STM32F427 board…

Search for another “maybe compatible” firmware or bootloader.

3

Have you read and followed the hardware porting instructions?

5

My board is based on the following design：

The difference is some modification of the LDO chips and some IO ports such as PWM. Unchanged on porting and design of the SD card and storage chip.

6

You did not answer the question.

7

OK. If you mean the official Pixhawk fmuv5 standard document, I haven’t read it. I chose to trust CUAV’s design document at the time. I will go through the Pixhawk document.

However, I have made a different boards based on the same design before and at less there are no this error at that time. The difference between two designs only be a re-layout and a few insignificant connectors. :frowning:

8

No, I mean: Porting to a new flight controller board — Dev documentation

9

Thx,I have read it and do some work,and it fianlly worked.

The problem is on size of the storage.The current code set HAL_STORAGE_SIZE for fmuv5 with 32768.But on this board it should set to 16384.I can not use the exist fmuv5 hwdef file and i write a newone and it worked.It can also running on a original CUAVv5 boards.

But on my old experence on fmuv3,if the design,selection on MCU and chips,pingout and function with MCU not change with the published schematic,then the firmware and bootloader should work directly. I am checking if the supplier gave me a chip with the wrong capacity or if there was a problem with the storage chip selection on the ancient schematic. And I will re-compare the differences in the relevant codes in the past and now.

Thx for your help:)

1 Like