• OAK-FFC 6P in boot loop

Our 6P appears to be in a boot loop, as the USB device number is changing every few seconds, and I can no longer ssh in, or see it with ip a or ifconfig.

I started with a fresh device and was able to ssh in, after changing the static IP on usb0 to 192.168.197.10/24.

However, I then tried to update the firmware to the latest version by running:

mender -install luxonisos-1.8.dm-verity.mender ; reboot

After this, I am no longer able to see the device as described above. I have tried flashing various versions (1.2, 1.4) using the recovery SW, e.g:

flashtool flashall fip-oak-ffc-6p-rvc3-1.2.0.bin boot.img data.img system.img syshash.img

This goes through successfully:

(tmp) user@host:~/Downloads/14$ flashtool flashall fip-oak-ffc-6p-rvc3-1.2.0.bin boot.img data.img system.img syshash.img
/home/user/Downloads/14/fip-oak-ffc-6p-rvc3-1.2.0.bin is a valid FIP
/home/user/Downloads/14/boot.img is a valid boot image
/home/user/Downloads/14/data.img is a valid data image
/home/user/Downloads/14/system.img is a valid system image
/home/user/Downloads/14/syshash.img is a valid verity image
FIP flashed to device: 5272C816838860C6
Waiting 30s before reenumarating
FIP flashed successfully for device 1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6
1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6 created GPT in 0.0150s
1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6 flashed boot_a in 13.2160s
1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6 flashed boot_b in 13.0090s
1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6 flashed data in 20.6630s
|  Downloading..
1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6 flashed system_a in 295.9090s
1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6 flashed system_b in 381.1670s
1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6 flashed syshash_a in 5.3360s
1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6 flashed syshash_b in 5.3080s
OS flashing done for device 1-6 Intel Keembay USB(in OS recovery mode): 5272C816838860C6. Please shutdown the system, set the boot switch to normal and reboot the system
Unable to find or flash PCIe devices due to missing drivers. If you intend to flash a PCIe device, please install the drivers and rerun the tool

But still is in bootloop. I have tried unplugging and replugging many times.

Any ideas on how to recover?

    21 days later

    No luck, now just using a different device. I did notice that some firewall settings were preventing me from SSH'ing in, but not sure if that's at all related to the bootloop.

    4 days later

    I am also having this issue.

    I ended up trying to update the OS using flashtool since I thought the mender instructions did not work as I was no longer able to ping the device and I still can not ping it.

    The device shows up in dmesg like so:

    [ 5386.088616] usb 2-1.4: new SuperSpeed USB device number 9 using tegra-xusb

    [ 5386.111403] usb 2-1.4: New USB device found, idVendor=1d6b, idProduct=0103

    [ 5386.111475] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

    [ 5386.111523] usb 2-1.4: Product: USB Ethernet

    [ 5386.111565] usb 2-1.4: Manufacturer: Luxonis

    [ 5386.111606] usb 2-1.4: SerialNumber: t00000002

    [ 5386.138498] cdc_ncm 2-1.4:1.0: MAC-Address: 8a:d8:3f:ad:b2:ac

    [ 5386.141172] cdc_ncm 2-1.4:1.0 usb0: register 'cdc_ncm' at usb-70090000.xusb-1.4, CDC NCM, 8a:d8:3f:ad:b2:ac

    [ 5386.460480] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready

    [ 5386.490781] cdc_ncm 2-1.4:1.0 usb0: 3750 mbit/s downlink 3750 mbit/s uplink

    [ 5386.522772] cdc_ncm 2-1.4:1.0 usb0: 3750 mbit/s downlink 3750 mbit/s uplink

    [ 5386.938777] cdc_ncm 2-1.4:1.0 usb0: 3750 mbit/s downlink 3750 mbit/s uplink

    [ 5386.970839] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready

    Any updates would be appreciated on this matter if someone finds out what causes this.

    • erik replied to this.

      Hi Synergyst ,
      How are you powering the device? It seems like the device brownouts on bootup

          Hello erik,

          I am using the supplied power adapter and USB3 cable plugged into a USB3 port.

          I'm not sure if it's brownouts given that's how I am powering it.

            I also found someone else with a similar issue (when I also posted on the GitHub).

            See here: luxonis/depthai-core802

            For further context it seems to be when you update to v1.9 as well (not just v1.8 like mentioned in that GitHub issue), and flashing 1.2 like you suggested in an old post on the Discord (see attachment) does not resolve the issue unfortunately.

            Any ideas?

            Solution:

            Use DHCP to fetch an IP from the RVC3 device rather than using a static IP (`169.254.0.10` netmask `255.255.0.0` or `192.168.197.10` netmask `255.255.255.0`) after upgrading the OS as the subnet changes to `255.255.255.240`

            CC: @abroekhof @hjpark erik