# Pixhawk is not bootloading or found in lsusb search

**URL:** <https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841>\
**Category:** Blue Robotics Products\
**Created:** [December 3, 2018, 9:40pm UTC](https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841 "2018-12-03T21:40:03Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Scantron\_Robotics](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Scantron\_Robotics](https://discuss.bluerobotics.com/u/Scantron_Robotics)\
**Post date:** [December 3, 2018, 9:40pm UTC](https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841/1 "2018-12-03T21:40:03Z")

</div>

Hello,

I am trying to setup a blue Rov 2 system and have been having some difficulty getting the firmware to load on the pixhawk. I keep getting this error message.

> Flashing Pixhawk…  
> Loaded firmware for 9,0, size: 830044 bytes, waiting for the bootloader…  
> Timed out trying to catch bootloader!  
> Please try again.  
> Waiting to restart mavproxy…  
> Restarting mavproxy  
> Complete!

I have seen a similar issue from a post back in April of 2014 here:

> [@Companion computer not communicating](https://discuss.bluerobotics.com/t/companion-computer-not-communicating/2487):
>
> Hello, I am trying to use an RPi 3 as my companion computer. I’ve flashed the raspbian image onto the pi, loaded firmware onto the Pixhawk and set up the static IP on my surface computer. I am connected to the pi via ethernet and I have the pixhawk connected via USB, but when I start up QGroundControl, no vehicle connection is detected. I tried testing the MAVproxy as instructed on the troubleshooting page of the Ardusub gitbook, and i got the output shown below. pi@raspberrypi:~ screen -…

Where in that thread the user was told to run lsusb to see if the pixhawk is connected to the rasp pi. He is able to see the pixhawk, but I’ve still been unable to as seen in the picture here.

 ![Capture](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/2/21b3ec2c38e856610ceff5824392c1a28e44f018.png)

I’ve tried resetting the mavproxy, but it gave the same error as the other user. And I have tried several usb cables. This one has worked in the past for the Blue Rov as well.

Is my pixhawk busted or is there some sort of software mishap?

Thanks.

---

<div class="post-metadata">

**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\
**Post date:** [December 4, 2018, 11:00am UTC](https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841/2 "2018-12-04T11:00:38Z")

</div>

Hello Jeremy,

Try running `dmesg -w` and while it runs, unplug and plug the Pixhawk.  
If there is a usb communication error, it should show there.

---

<div class="post-metadata">

**Author:** ![Scantron\_Robotics](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Scantron\_Robotics](https://discuss.bluerobotics.com/u/Scantron_Robotics)\
**Post date:** [December 4, 2018, 2:31pm UTC](https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841/3 "2018-12-04T14:31:47Z")

</div>

It gave me this message.

 ![Capture3](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/3/35dcf2262a5001331d4dc722a91d676f7e00de80.png)

Does this mean that everything is fine?

---

<div class="post-metadata">

**Author:** ![Scantron\_Robotics](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Scantron\_Robotics](https://discuss.bluerobotics.com/u/Scantron_Robotics)\
**Post date:** [December 4, 2018, 2:39pm UTC](https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841/4 "2018-12-04T14:39:11Z")

</div>

When trying to flash pixhawk, it didn’t seem to work again.

 ![Capture4](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/f/f16391018f2e3687118af780871b4ce7a249072f.png)

When using lsusb again, it still hasn’t found the device that the troubleshooter says it should. Using the ls /dev/serial/by-id/\* function also turns up nothing as it says it cannot access this file/directory.

---

<div class="post-metadata">

**Author:** ![Scantron\_Robotics](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Scantron\_Robotics](https://discuss.bluerobotics.com/u/Scantron_Robotics)\
**Post date:** [December 4, 2018, 2:51pm UTC](https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841/5 "2018-12-04T14:51:35Z")

</div>

I don’t know if this helps narrow down the issue but I’ve also tried to update the firmware on the pixhawk directly through qgc with a usb cable to my computer and it starts the upload process then cancels around 10 seconds later saying that it failed.

---

<div class="post-metadata">

**Author:** ![patrickelectric](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/patrickelectric/32/2162_2.png) [@patrickelectric](https://discuss.bluerobotics.com/u/patrickelectric)\
**Post date:** [December 5, 2018, 10:29am UTC](https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841/6 "2018-12-05T10:29:59Z")

</div>

Hi Jeremy,

It appears to be a problem with your usb connection, try to replace the cable or to use another usb port in the raspberry.

---

<div class="post-metadata">

**Author:** ![jwalser](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jwalser/32/2234_2.png) [@jwalser](https://discuss.bluerobotics.com/u/jwalser)\
**Post date:** [December 5, 2018, 3:11pm UTC](https://discuss.bluerobotics.com/t/pixhawk-is-not-bootloading-or-found-in-lsusb-search/3841/7 "2018-12-05T15:11:57Z")

</div>

Please contact [support@bluerobotics.com](mailto:support@bluerobotics.com) with your order number and reference this thread.
