Starling 2 doesn't detect camera after flashing new SDK

[Judoor 0]

Hi there,

I had some problems with libraries that I installed in double, so I decided to flash a new SDk that solves my problems. The installation was successful, but I have a problem.

I have the very latest version of the Starling 2 and when I run configure-sku and run configure-mpa after, the drone doesn't detect the cameras.

I have chosen all the parameters just like my other drone (I have 2 similar drones that I ordered at the same time) and it doesn't work.

Does anyone have a solution to my problem?

Thank you for your answers.

[tom]

@Judoor-0 With the newest SDKs we have been shipping multiple kernels to support various camera hardware configurations.

In your case, since you're using Starling 2 which contains the M0173 coax camera breakout board:
https://docs.modalai.com/voxl2-d0014/#new-kernel-configuration-for-m0173

you have to use the kernel that supports that configuration.

When going through the SDK install.sh script you'll reach a point where you're asking the following:

PLEASE SELECT WHICH KERNEL TO FLASH
1. M0054-1 -> QRB5165, Starling (D0005), FPV (D0008)
2. M0054-1 -> QRB5165, Starling 2 Max (D0012), Starling 2 (D0014)
Enter your choice (or press Enter to continue): 

In your case you will need to select 2, which will flash the correct kernel in order to support Starling 2's camera configuration.

If the wrong kernel is flashed then you won't see your camera config as an option in the camera selection step

[Judoor 0]

@tom I redid the install of the sdk and yes this time only this two option appeared :

1. M0054-1 -> QSM8250, Starling (D0005), FPV (D0008)
2. M0054-1 -> QSM8250, Starling 2 Max (D0012), Starling 2 (D0014)
   And it worked, thank you!

The weird things is that I did the exact same sdk install twice yesterday and was never serve with this two option only. There was like 6 option available, is it because I directly started the drone in FASBOOT Mode ?

[tom]

@Judoor-0 Yep exactly, if the drone is already in fastboot before running the flashing script it can't identify which board it is (M0054-1, M0054-2, M0104-1) so it has to give you all options. This time since it has ADB access it can be smarter and just ask you the possible options it knows are supported for your hardware