• Hardware

  • FFC-3P (raspberry pi 4) semi-responsive but not recognized

I recent started using ffc-3p with a raspberry pi.  It had been working fine with code that I had written for my oak-1, but now appears to be mostly non-responsive. The oak-1 still functions as it had, so I think it is an ffc hardware problem, not a problem with the host.

I had been using the FFC-3P without the power adapter, just usb connection between the host and module and had no issues. Now when I plug in the module (USB only), none of the board or SoM LEDs light up.

I thought maybe it was a power issue, so I used the supplied power supply. The green lights on the SOM turned on as well as the two orange and one red light on the carrier board. However both with and without the external power supply, the myriad chip is not seen by the host usb. 

With the oak-1 module there is a myriad device listed when ‘’’lsusb’’’ is run, when the FFC-3P is plugged into power supply and host via USB, there is no myriad device listed. Anyone have any idea what could be wrong? The reset button on the carrier board seems to have no effect as well.

    Hi Chris_wei
    Looks like the device is not receiving enough power. Can you confirm: using the same usb, when connecting th 3p to the rpi, no LEDs light up, but when connecting to a charger, the lights turn on? Could you try connecting it to something more powerful (eg the PC)?

    Thanks,
    Jaka

        It's probably worth running dmesg in the console too, if there's a power error happening it should turn up in there. I'm using a 3P with a compute module 4 board which only has USB2 and it's pretty stable, if you're using a Pi 4 do you see a difference between the USB2 and USB3 ports on it?

        jakaskerl

        correct, with rpi host and usb only -> no lights. usb + power supply -> LEDs 5V:red, PG, RUN:.Orange, SoM:Green. same behavior on both rpi and full-size laptop. Additionally, same behavior observed on USB2 and USB3 ports.

        dmesg -w shows that plugging in the camera appears to disconnect the passive hub it is plugged into, which then reconnects after the camera is disconnected
        This is following the camera being plugged in
        [95422.503398] usb 1-3: USB disconnect, device number 18
        [95422.539408] usb 2-1: USB disconnect, device number 12
        This below is following the camera being unplugged
        [95425.783250] usb 1-3: new high-speed USB device number 19 using xhci_hcd
        [95425.933666] usb 1-3: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.56
        [95425.933671] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
        [95425.933673] usb 1-3: Product: USB2.1 Hub
        [95425.933675] usb 1-3: Manufacturer: GenesysLogic
        [95425.934348] hub 1-3:1.0: USB hub found
        [95425.934580] hub 1-3:1.0: 4 ports detected
        [95426.059346] usb 2-1: new SuperSpeed USB device number 13 using xhci_hcd
        [95426.081855] usb 2-1: New USB device found, idVendor=05e3, idProduct=0626, bcdDevice= 6.56
        [95426.081859] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
        [95426.081861] usb 2-1: Product: USB3.1 Hub
        [95426.081863] usb 2-1: Manufacturer: GenesysLogic
        [95426.083633] hub 2-1:1.0: USB hub found
        [95426.083928] hub 2-1:1.0: 4 ports detected
        [95426.219252] usb 1-3: USB disconnect, device number 19
        [95426.839253] usb 2-1: USB disconnect, device number 13
        [95426.839297] usb 2-1: Failed to suspend device, error -19
        [95427.295189] usb 1-3: new high-speed USB device number 20 using xhci_hcd
        [95427.445606] usb 1-3: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.56
        [95427.445611] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
        [95427.445614] usb 1-3: Product: USB2.1 Hub
        [95427.445615] usb 1-3: Manufacturer: GenesysLogic
        [95427.446297] hub 1-3:1.0: USB hub found
        [95427.446560] hub 1-3:1.0: 4 ports detected
        [95427.571286] usb 2-1: new SuperSpeed USB device number 14 using xhci_hcd
        [95427.593802] usb 2-1: New USB device found, idVendor=05e3, idProduct=0626, bcdDevice= 6.56
        [95427.593806] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
        [95427.593808] usb 2-1: Product: USB3.1 Hub
        [95427.593810] usb 2-1: Manufacturer: GenesysLogic
        [95427.595560] hub 2-1:1.0: USB hub found
        [95427.595857] hub 2-1:1.0: 4 ports detected
        For comparison, connecting and disconnecting an OAK-1 to the same machine yields below
        [96245.135879] usb 1-3.2: new high-speed USB device number 21 using xhci_hcd
        [96245.260678] usb 1-3.2: New USB device found, idVendor=03e7, idProduct=2485, bcdDevice= 0.01
        [96245.260683] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
        [96245.260684] usb 1-3.2: Product: Movidius MyriadX
        [96245.260685] usb 1-3.2: Manufacturer: Movidius Ltd.
        [96245.260686] usb 1-3.2: SerialNumber: 03e72485
        [96250.064550] usb 1-3.2: USB disconnect, device number 21

          I'm not sure if it's the case for Luxonis cameras but I know a lot of webcams and wireless adapters run in USB isochronous mode which isn't compatible with some USB hubs. I've seen issues where plugging one of those devices in will force all the other devices to be disconnected, I think they create a request for a low latency connection that forces the others in to an unsupported state. It's a really esoteric problem to hit so most folks don't come across it, it's stuck with me for the hassle it caused! 😅

          I ran lsusb -d 03e7:2485 -v which brings up extended info about the USB device, it's running in bulk transfer mode so shouldn't be the issue I mentioned above.

          For comparison, this is the output when I plug my FFC-3P in to my Pi. It's a Compute Module 4 board and using USB2, hence the "high speed" and dwc2 references:

          [   87.425249] usb 1-1.4: new high-speed USB device number 4 using dwc2
[   87.626105] usb 1-1.4: New USB device found, idVendor=03e7, idProduct=2485, bcdDevice= 0.01
[   87.626125] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   87.626144] usb 1-1.4: Product: Movidius MyriadX
[   87.626155] usb 1-1.4: Manufacturer: Movidius Ltd.
[   87.626166] usb 1-1.4: SerialNumber: [REMOVED]

          The vendor and product IDs are the same at least so we can take udev rules out of the equation.

          Are you able to plug directly in to the Pi without going via a USB hub? If you plug another device in using the same cable do you see dmesg update? I've lost count of the times I've used a USB-C cable and it turns out it's charge only, sadly I'll do it again too!

            kneave

            had to find a C-to-C data cable, but still same respective behavior for both units when plugging directly into the USB ports on the laptop. What really puzzles me is that it was previously working with just the provided USB cable and no power supply. I've tested that particular cable with the OAK-1 module as well as other unrelated devices and they all function properly, so I don't think there's anything wrong with the cable. I'm not much of a hardware person, so beyond trying any possible permutation of hardware config I'm pretty stumped

              Hmm, an odd one! I have to say I've had some odd behaviour with C to C cables, I have to use a C to A adapter, then plug an A to C.

              Does the 3p work normally, powered by usb, from the laptop? I can't remember if you mentioned that or if the same behavior you mentioned is needing the psu while plugged in to either.

              For the Pi, you're not plugging in to the Pis usb c power socket are you? Sorry if it's a stupid question, always best to confirm!

                kneave

                Nope, using the block of usb-A ports and the A-to-C cables that shipped with my OAK-1 and 3P. OAK-1 functions normally in all scenarios, so there’s a functional baseline. The 3P does not work in any configuration(pi or laptop, hub or no hub, w/ or w/o power supply in addition to USB), it previously did work on the Pi w/o the power supply, but no longer does. All of this is using the same code on both units

                  Ah, yeah it sounds like there may be an issue with the USB-C port on 3P in that case that's somehow disconnected the power lines from the USB port. Apologies, I thought that the 3P was working fine over USB-only on the laptop but just wasn't showing up on the Pi. I didn't realise the 3P wasn't working on the laptop when attempting to power by USB-C.

                  If you have access to a camera with a macro lens, most phones have one now, it could be worth taking a close up photo with good light of the top and bottom of the 3P from a few angles and sharing them.

                    kneave
                    Here are some photos, let me know if they are not close enough I can try something else




                      jaka, kneave - do you see anything obviously wrong in these pictures? do you think I should request a replacement? (For some reason the forum is not letting me respond to posts or tag right now, hopefully you will see this)

                      We are processing the RMA request, will get back to you shortly. Regarding tagging, hopefully it will get resolved soon.