Servers by jDrones

How to enter DFM mode on Pixhawk


(Felix) #1

I need help here. My pixhawk can’t boot and my PC can’t detect if after my first attempt to load arduplane firm into it.

The firmware installation fail after the process of live calibration of compass. After that my pixhawk cant boot, there is no sound and also the Main LED won’t light up anymore.

I have search the whole forum and found that the bootloader firmware might corrupted. How do i enter the DFM mode to install new good firmware. Hope someone can help.


(Greg Covey) #2

The information is in the APM Wiki. Good luck!

Loading a bootloader with DFU


(Felix) #3

Thanks GregCovey for prompt reply.

The first image is what i get from UAVOS. The second image is photo of my pixhawk FMU_V2. I am now having problem finding boot0 that i need to provide 3.3V+ in order to activate the DFU mode. My board seem a little different from the UAVOS reference photo. I have measure the point i circle in red. Its having +3.3V already. Any one can guide me which is the boot0 pin ? and where can i short it with 3.3V pin ?


(Greg Covey) #4

Felix,

If you look on the STM32 microprocessor on your Pixhawk, and guessing that you will see an “F4” as part of the number. If so, then the point you have marked in your photo is the correct Boot0 for F4.

Try connecting a pliers or tweezer from there to any 3.3v or 5v point while powering up the Pixhawk via the USB cable. If you have your drivers properly loaded on your PC, you can tell in the USB section of Device Manager that it can see the Pixhawk in DFU mode. Another easy way to do this is to use BetaFlight and it will automatically say “DFU Mode” in the upper right corner if it sees the Pixhawk. Then do a “Local Firmware” download.


(Felix) #5

Thanks GreCovey. I measure the voltage of the mark point by referencing the common point to the switch +3.3 pin ( as guided by the first image i attached in this thread ) , the measure result is 0v instead of 3.3V. Therefore I try to measure the voltage of the marked point in a way which i have shown in the picture below and the result is +3.3v. If this is the boot0 then it already have 3.3v which is weird. Any comment on this ?
measure%20point


(Oldgazer) #6

I have been working on this all morning and I cannot get BetaFlight to flash px4fmuv2_bl.bin. I have looked every where and I cannot find a .HEX version of this file. I NEED THIS ASAP… PLEASE


(Peter Hall) #7

http://firmware.ardupilot.org/Copter/stable/fmuv3/


(Oldgazer) #8

Thanks, but still no joy. BetaFlight sees the board in DFU mode but will not flash. Mission Planner times out trying to ID the board.

I’ll just buy a new one…


(Oldgazer) #9

I bought a new 2.4.8 to replace the 2.4.6, so that aircraft is back in service. Because the 2.4.6 was partially functional I didn’t toss it out. I messed with it off and on for a few days and I kept getting the same results. Then I had a brain flash… I had been using my new Acer laptop and my recently upgraded desktop, but I hadn’t used my old Toshiba laptop.

So I pulled the Toshiba out of the closet, fired it up, launched MP, plugged in the 2.4.6, went to Initial Setup > Install Firmware and BOOM… it worked.

All three machines are running Windows 10. The “new” machines are running MP 1.3.62 and the Pixhawk is detected as a PX4FMU. The old Toshiba is running MP 1.59.3 and Windows detects the Pixhawk as a LegacyFMU.