I am currently working on the first flight procedure. I have the RC transmitter and receiver connected for the transmitter (remote) displays TX and RX. All other settings have been replicated on the transmitter. I then used J-link to upload the bootloader. I made connection with the device, and then I believe I uploaded the correct bootloader: fmuk66v3_bl.bin. I then downloaded QGroundControl to set up the FMU and upload the PX4 firmware. However, my QGroundControl does not connect to the drone, preventing me from moving forward. Do I need to redownload the bootloader or could I have done something wrong in another step?
Here’s a couple of things to check
When you plug in the FMU using a USB cable, it should start flashing yellow to show it is in bootloader mode. You can then try the QGroundControl update method. It may re-enter this state if you press reset button on the side when plugged in to USB. You don’t need the external battery power at this point.
Iain,
I used the fmuk66v3_bl.bin bootloader from the “Downloads” page on the gitbook. I then proceeded to follow all the program directions on the gitbook page “Program software using debugger” which directed me to use J-link to properly upload the bootloader using the memory address 0x0000.
Then instead of using J-link to upload a PX4 firmware file to a memory address of 0x6000 I was going to use the QGroundControl to update the PX4 firmware as directed. Should I be downloading another file to write to the 0x6000 memory address using J-link before using QGroundControl?
Thank you,
Mitchell H Neal
Hi nxf45918 did you see the px4 binary file that i sent in the last email? I'll send it again.. That PX4 software should be programmed at 0x6000
Q:
A: