Hardware: Starling 2, M23000003C7
Software version: sdk-1.6.4, v1.9.21
What I am trying to do: Boot up the drone after a crash.
What actually happens: The drone does not finish booting. All leds turn on, but the drone is not accessable from adb. lsusb reports the drone as:
05c6:900e Qualcomm, Inc. QUSB_BULK_SN:2622B903
I used qdl to read the crash dump and after some digging I saw that the boot ended with the following lines:
...
fpm8150a_s3_mmcx_sup_level: regulator get failed, ret=-517
pm8150_s3_level: supplied by pm8150a_s3_level
pm8150_s3_level_ao: supplied by pm8150a_s3_level_ao
pm8150a_s3_mmcx_sup_level: supplied by pm8150_s3_mmcx_sup_level
oledb: Bringing 0uV into 4925000-4925000uV
ab: Bringing 0uV into 4600000-4600000uV
ibb: Bringing 0uV into 800000-800000uV
pm8150a_s4_level: supplied by pm8150a_s3_mmcx_sup_level
fspmi spmi-0: pmic_arb_wait_for_done: transaction failed (0x3)SUBSYSTEM=spmi
DEVICE=+spmi:spmi-0
pm8150a_s4_level_ao: supplied by pm8150a_s3_level_ao
B #!1!
B #!1!
|*eN,0
...
I'm not sure exactly what the problem is and if there is an easy fix. The board looks visibly unharmed.
Steps to reproduce: Probably caused by the crash, but unsure.