flashing starling 1.1.4 with the latest 1.4.5
-
i have an older starling (v1) with a preinstalled 1.1.4 voxl2 sdk. i'm trying to flash it with the latest 1.4.5 version and i'm having problems as the device does not go into fastboot mode, note i've tried power cycling and switching the fastboot dip switch to on. I've attached the logs.
additional info: doing the same (without actually needing to do the fastboot switch turning on) i've successfully flashed the 1.4.5 on a starling v2!
-
i have an older starling (v1) with a preinstalled 1.1.4 voxl2 sdk. i'm trying to flash it with the latest 1.4.5 version and i'm having problems as the device does not go into fastboot mode, note i've tried power cycling and switching the fastboot dip switch to on. I've attached the logs.
additional info: doing the same (without actually needing to do the fastboot switch turning on) i've successfully flashed the 1.4.5 on a starling v2!
@Viktor-Gal , it is possible that your OS is not correctly recognizing the fastboot USB device or there are insufficient permissions.
While the board is in the fastboot mode (either using the dip switch or using
adb reboot bootloader, which is called by the sdk install script), do you see a QCOM device when runninglsusb?Alex
-
@Viktor-Gal , it is possible that your OS is not correctly recognizing the fastboot USB device or there are insufficient permissions.
While the board is in the fastboot mode (either using the dip switch or using
adb reboot bootloader, which is called by the sdk install script), do you see a QCOM device when runninglsusb?Alex
@Alex-Kushleyev as said above with the very same machine i successfully updated a starling v2 drone. but i'll try to check what you've just suggested.
-
@Alex-Kushleyev as said above with the very same machine i successfully updated a starling v2 drone. but i'll try to check what you've just suggested.
@Viktor-Gal , yes please try to put the device into bootloader mode via a switch or using the
adb reboot bootloadercommand and then checking if it's actually in bootloader mode:
fastboot devices
or
sudo fastboot devicesand also checking output of
lsusbAlex
-
@Viktor-Gal , yes please try to put the device into bootloader mode via a switch or using the
adb reboot bootloadercommand and then checking if it's actually in bootloader mode:
fastboot devices
or
sudo fastboot devicesand also checking output of
lsusbAlex
using the dip switch and powercycling there's no devices showing up with
sudo fastboot devices.unfortunately no
lsbusbas i'm under macos, but sysprofiler's output is:Host Controller Driver: AppleT6000USBXHCI QUSB_BULK_CID:0412_SN:008A1847: Product ID: 0x9008 Vendor ID: 0x05c6 (Qualcomm, Inc) Version: 0.00 Speed: Up to 480 Mb/s Manufacturer: Qualcomm CDMA Technologies MSM Location ID: 0x01100000 / 1 Current Available (mA): 500 Current Required (mA): 2 Extra Operating Current (mA): 0if you really think there's some extra info with lsusb that you are looking for i can hook it up to my raspberry pi.
-
using the dip switch and powercycling there's no devices showing up with
sudo fastboot devices.unfortunately no
lsbusbas i'm under macos, but sysprofiler's output is:Host Controller Driver: AppleT6000USBXHCI QUSB_BULK_CID:0412_SN:008A1847: Product ID: 0x9008 Vendor ID: 0x05c6 (Qualcomm, Inc) Version: 0.00 Speed: Up to 480 Mb/s Manufacturer: Qualcomm CDMA Technologies MSM Location ID: 0x01100000 / 1 Current Available (mA): 500 Current Required (mA): 2 Extra Operating Current (mA): 0if you really think there's some extra info with lsusb that you are looking for i can hook it up to my raspberry pi.
@Viktor-Gal , I think we need some help form @tom

My guess is that OSX is not supporting fastboot for some reason, so you may want to try using native Linux, as that usually fixes most issues like this. QUSB_BULK device seems the correct one for the VOXL2 board that is in fastboot mode.
Alex
-
@Viktor-Gal , I think we need some help form @tom

My guess is that OSX is not supporting fastboot for some reason, so you may want to try using native Linux, as that usually fixes most issues like this. QUSB_BULK device seems the correct one for the VOXL2 board that is in fastboot mode.
Alex
@Alex-Kushleyev you reckon? i mean the starling v2 just went to fastboot mode very nicely and i could flash it easily on the same macos. or is there so much of a difference between the starling v1 and v2 chips? i'll give it a go on the raspberry pi.
-
@Alex-Kushleyev you reckon? i mean the starling v2 just went to fastboot mode very nicely and i could flash it easily on the same macos. or is there so much of a difference between the starling v1 and v2 chips? i'll give it a go on the raspberry pi.
@Viktor-Gal , yes I understand what you are saying.
Just to double check, the older Starling boots fine when not in fastboot mode, right?
Please try on Linux OS just to double check anyway..
Alex
-
@Viktor-Gal , yes I understand what you are saying.
Just to double check, the older Starling boots fine when not in fastboot mode, right?
Please try on Linux OS just to double check anyway..
Alex
@Alex-Kushleyev yes yes, it boots up fine in normal mode
-
@Alex-Kushleyev yes yes, it boots up fine in normal mode
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login