# Timed out trying to catch bootloader **URL:** \ **Category:** QGroundControl\ **Created:** [September 8, 2020, 1:52am UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133 "2020-09-08T01:52:47Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![fish\_ecology](https://avatars.discourse-cdn.com/v4/letter/f/838e76/32.png) [@fish\_ecology](https://discuss.bluerobotics.com/u/fish_ecology)\ **Post date:** [September 8, 2020, 1:52am UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/1 "2020-09-08T01:52:47Z")
Hey Everyone, After some time off the water, I went back to use the ROV and tried connecting but was getting no telemetry. I have: - Updated companion computer to 0.0.22 - Tried updating Pixhawk firmware via 192.168.2.2:2770/system and it is saying ArduSub Version not found. I go to update stable version but, I get the message “Timed out trying to catch bootloader”. - I do see “PX4\_FMU\_v2.x (Pixhawk AutoPilot)” in the detected devices. - Then I tried connecting the pixhawk directly to a computer to update the firmware. This worked but I don’t see the same option as mentioned in this thread ([ArduSub Updating Firmware through browser - no internet - #12 by Jimmi77](https://discuss.bluerobotics.com/t/ardusub-updating-firmware-through-browser-no-internet/5042/12)). So instead I select “ArduSub” “Nutx” “Sub” and then whatever firmware option that was provided. This work and I get telelemtry. However as soon as I plug the USB cable back into the Companion Computer nothing, no telemetry. - Turned everything on and off several times. - Tried different USB cables. - Formatted SD cards It appears I can not get a connection between the companion computer and the Pixhawk? Any suggestions I am out of option! Thanks in advance. ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [September 8, 2020, 1:01pm UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/2 "2020-09-08T13:01:12Z")
Hi, Are you receiving video? Have you checked your IP address? both the IP 192.168.2.1 and netmask 255.255.255.0 are very important. ---
**Author:** ![sudheeshk](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@sudheeshk](https://discuss.bluerobotics.com/u/sudheeshk)\ **Post date:** [September 8, 2020, 5:34pm UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/3 "2020-09-08T17:34:00Z")
hi, try disconnect USB cable from ( Raspberry pi-Pixhawk USB cable ) pixhawk and reconnect at a point where firmware updation got stucked. The process is to load the bootloader by power recycling the Pixhawk. -thank you ---
**Author:** ![fish\_ecology](https://avatars.discourse-cdn.com/v4/letter/f/838e76/32.png) [@fish\_ecology](https://discuss.bluerobotics.com/u/fish_ecology)\ **Post date:** [September 8, 2020, 11:03pm UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/4 "2020-09-08T23:03:30Z")
Hi Willian, Yes I am receiving video and the IP address is correct. Any other ideas? ---
**Author:** ![fish\_ecology](https://avatars.discourse-cdn.com/v4/letter/f/838e76/32.png) [@fish\_ecology](https://discuss.bluerobotics.com/u/fish_ecology)\ **Post date:** [September 8, 2020, 11:04pm UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/5 "2020-09-08T23:04:22Z")
Hi Sudheeshk, Thanks, I am pretty sure I have tried this but I am a bit unsure how to power cycle the pixhawk? I have read a few people mention this? Cheers Joel ---
**Author:** ![fish\_ecology](https://avatars.discourse-cdn.com/v4/letter/f/838e76/32.png) [@fish\_ecology](https://discuss.bluerobotics.com/u/fish_ecology)\ **Post date:** [September 9, 2020, 1:26am UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/6 "2020-09-09T01:26:25Z")
Ok, I have some progress… - I established that there was no mavproxy? - I re-flashed the raspberry pi SD card. This worked and I can now see mavproxy and I can establish a vehicle connection, i.e. video and telemetry. - However, ArduSub version is 3.5.4. Now, when I attempt to update, the ROV lights flash on, lots of beeps and repeated messages of “attempting to reboot on /dev/autopilot” followed by the “timed out trying to catch bootloader” Any ideas? ---
**Author:** ![sudheeshk](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@sudheeshk](https://discuss.bluerobotics.com/u/sudheeshk)\ **Post date:** [September 9, 2020, 7:09am UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/7 "2020-09-09T07:09:41Z")
Hi Joel, i had the same issue. I can help you to solve this problem. first you need to find your Pixhawk Bootloader version connect pixhawk with your linux computer by using a USB cable, and run the following command on linux termianl. _ls /dev/serial/by-id/_ you have to run this command with in 2-3 seconds after connecting your computer’s usb port. other wise the you will not get the bootloader information. so you need to open a terminal in advance and execute the commands immediately after connecting the pixhawk. Kindly share the boot loader version. Thans you ---
**Author:** ![fish\_ecology](https://avatars.discourse-cdn.com/v4/letter/f/838e76/32.png) [@fish\_ecology](https://discuss.bluerobotics.com/u/fish_ecology)\ **Post date:** [September 9, 2020, 11:28pm UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/8 "2020-09-09T23:28:42Z")
Thanks for your offer to help Sudheeshk. I am running a windows computer and not sure what the windows command prompt version of your command is? However, in QC Groundcontrol when I go to update the firmware via USB I can see it see connected to Bootloader V5 BoardID 255 ---
**Author:** ![fish\_ecology](https://avatars.discourse-cdn.com/v4/letter/f/838e76/32.png) [@fish\_ecology](https://discuss.bluerobotics.com/u/fish_ecology)\ **Post date:** [September 9, 2020, 11:45pm UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/9 "2020-09-09T23:45:21Z")
I have also tried following these instruction: [https://docs.px4.io/v1.9.0/en/advanced\_config/bootloader\_update.html](https://docs.px4.io/v1.9.0/en/advanced_config/bootloader_update.html) How do you enable [SYS\_BL\_UPDATE] in the parameters if default is 0? ---
**Author:** ![fish\_ecology](https://avatars.discourse-cdn.com/v4/letter/f/838e76/32.png) [@fish\_ecology](https://discuss.bluerobotics.com/u/fish_ecology)\ **Post date:** [September 13, 2020, 11:02pm UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/10 "2020-09-13T23:02:01Z")
Ping! So every time I try to update the Ardusub firmware the lights flash and the ROV beeps etc but it still comes up with “timed out trying to catch bootloader”. I have tried following the github book on updating the bootloader but no success? Could this be due to the pixhawk being older? Is it easier to replace the pixhawk? ---
**Author:** ![L3Y1Q2](https://avatars.discourse-cdn.com/v4/letter/l/a8b319/32.png) [@L3Y1Q2](https://discuss.bluerobotics.com/u/L3Y1Q2)\ **Post date:** [December 30, 2020, 2:30am UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/11 "2020-12-30T02:30:16Z")
Hi Joel, I have the same issue ,'“timed out trying to catch bootloader”. Did you solve this problem? ---
**Author:** ![gcelec](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/gcelec/32/2038_2.png) [@gcelec](https://discuss.bluerobotics.com/u/gcelec)\ **Post date:** [May 19, 2021, 2:12pm UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/12 "2021-05-19T14:12:35Z")
I’m having the same problem after replacing a Pixhawk - It has ArduSub 3.5.4 but when I try to update I get the message “Timed out trying to catch bootloader!” I’ve tried manually uploading ardusub.apj that I download from [Downloads · GitBook](https://www.ardusub.com/resources/downloads.html) ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [May 20, 2021, 1:26am UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/13 "2021-05-20T01:26:18Z")
Hi @gcelec 🙂 @williangalvani provided several things to try in [this thread](https://discuss.bluerobotics.com/t/ardusub-updating-firmware-through-browser-no-internet/5042). Could you take a look and see if any of those help? In the meantime I’ll ask internally and see if I can collect together a common set of approaches to fix the issue. ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [May 20, 2021, 1:46am UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/14 "2021-05-20T01:46:36Z")
v0.0.26 of companion switched to using a different uploader that’s expected to work more reliably (PR [here](https://github.com/bluerobotics/companion/pull/398)), so if you update companion first that should hopefully solve this issue. Would be great if you can confirm once you’ve tried it 🙂 ---
**Author:** ![gcelec](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/gcelec/32/2038_2.png) [@gcelec](https://discuss.bluerobotics.com/u/gcelec)\ **Post date:** [May 20, 2021, 1:51am UTC](https://discuss.bluerobotics.com/t/timed-out-trying-to-catch-bootloader/8133/15 "2021-05-20T01:51:12Z")
I solved the issue by connecting the Pixhawk directly to my laptop via USB, then updating the Ardusub through the firmware update tab in QGroundControl.