Uploading Firmware

Vrinda · October 16, 2018, 2:53pm

Hello !
I have a query regarding firmware upload. I get the Erase, Program and Verify lines mentioned below. However I do not get the Rebooting line. Apologize for this silly question. I just want to receive a thumbs up from someone regarding this.
Thank you for your time !

Dave84 · October 16, 2018, 5:34pm

Good day, In which way did you upload the firmware? is this for flight controller or a peripheric?

Vrinda · October 17, 2018, 9:16pm

This is for pixhawk. When I implemented the command,
_“make px4fmu-v4_default upload”

Dave84 · October 17, 2018, 9:43pm

ok… which version of Pixhawk do you have,

Vrinda · October 17, 2018, 9:48pm

It is 1.8 @Dave84. I did “make px4fmu-v2default upload”

Dave84 · October 17, 2018, 10:02pm

ok, before you upload the firmware you must check first the version of your flight controller.
Pixhawk v1 work with px4fmu v2, pixfalcon with px4fmu-v3,pixracer with px4fmu-v4default, pixhawk v4 by holybro with px4fmu-v5

Vrinda · October 17, 2018, 10:06pm

Yes ! I did -v2 since my pixhawk is of version 1. Am I doing anything wrong ?

Dave84 · October 18, 2018, 3:41pm

You are uploading the firmware with usb… jtag or dfu?

Vrinda · October 18, 2018, 4:59pm

I am using USB @Dave84.

Dave84 · October 18, 2018, 5:23pm

ok…after you have done the update you can hear the music tone

Vrinda · October 18, 2018, 6:47pm

No, I cannot. However I see the “ACT BUZZER” light blinking.

Dave84 · October 18, 2018, 7:02pm

can you send me pls a small video of the procedure you are doing

Vrinda · October 19, 2018, 5:31pm

Hello ! So weird, now am getting the rebooted line. All good now. Thank you very much for helping me @Dave84.

Dave84 · October 19, 2018, 6:10pm

Good to hear… happy fly

Vrinda · October 19, 2018, 7:27pm

Thank you @Dave84 ! Just started working on this. Adventure awaits…

elserpiente · February 11, 2020, 1:12pm

I flashed FW on my Pixhawk Lite 2.4.6. After reboot I’m unable to connect to it via MAV.
Before this it’s used to work, but after I upgraded bootloader from FMU2 to FMU3 I ended up in this.

$ ./px_uploader.py --port /dev/ttyACM0 --force ./px4_fmu-v2_default.px4 
Loaded firmware for board id: 9,0 size: 1028712 bytes (99.66%), waiting for the bootloader...


Found board id: 9,0 bootloader version: 5 on /dev/ttyACM0
sn: 002300313335510933373538
chip: 20016419
family: STM32F42x
revision: 3
flash: 2080768 bytes
Windowed mode: False

Erase  : [====================] 100.0%
Program: [====================] 100.0%
Verify : [====================] 100.0%
Rebooting. Elapsed Time 16.387

My dmesg

[427929.298063] usb 1-2: New USB device found, idVendor=26ac, idProduct=0011
[427929.298066] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[427929.298067] usb 1-2: Product: PX4 BL FMU v3.x
[427929.298068] usb 1-2: Manufacturer: 3D Robotics
[427929.298069] usb 1-2: SerialNumber: 0
[427929.298657] cdc_acm 1-2:1.0: ttyACM1: USB ACM device
[427933.828320] usb 1-2: USB disconnect, device number 84
[427935.245090] usb 1-2: new full-speed USB device number 85 using xhci_hcd
[427935.394474] usb 1-2: New USB device found, idVendor=26ac, idProduct=0011
[427935.394479] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[427935.394481] usb 1-2: Product: PX4 FMU v2.x
[427935.394484] usb 1-2: Manufacturer: 3D Robotics
[427935.394486] usb 1-2: SerialNumber: 0
[427935.395628] cdc_acm 1-2:1.0: ttyACM1: USB ACM device

TechNaturalist · February 24, 2020, 10:26pm

@elserpiente

according to your dmesg you are connected to your pixhawk. When you say “connect to it via MAV” are you using qgroundcontrol or custom software? Either way, try to see if you change your serial to read in /dev/ttyACM1 instead of /dev/ttyACM0 (which is usually the default).

I am no expert, but I have run into similar issues before.

I hope this helps!