[disssid]

I recently purchased a DIY frame kit from GearBest and this is my first drone build. I have quite some experience with electronics and computers, so wanted to assemble one myself.

I got the frame and wiring done and following the tutorial

when I had to connect my CC3D flight controller to my laptop(Ubuntu 16.04), it doesn't detect when I checked the dmesg log it says
 
[ 1967.650310] usb 2-1.3: new full-speed USB device number 9 using ehci-pci
[ 1967.722288] usb 2-1.3: device descriptor read/64, error -32
[ 1967.898234] usb 2-1.3: device descriptor read/64, error -32
[ 1968.074325] usb 2-1.3: new full-speed USB device number 10 using ehci-pci
[ 1968.146280] usb 2-1.3: device descriptor read/64, error -32
[ 1968.322310] usb 2-1.3: device descriptor read/64, error -32
[ 1968.498254] usb 2-1.3: new full-speed USB device number 11 using ehci-pci
[ 1968.906297] usb 2-1.3: device not accepting address 11, error -32
[ 1968.978392] usb 2-1.3: new full-speed USB device number 12 using ehci-pci

As anyone would do I googled and found this link, which is kind off similar https://paulphilippov.com/articles/how-to-fix-device-not-accepting-address-error
but even this didn't help.

I tried connecting it to a Windows 8 machine and I have the same issue "Unknown USB device (failed device descriptor)". I installed the driver that comes along Libre Pilot. I also tried troubleshooting techniques, reinstalling the driver and power management of USB on the windows machine.

Adding to this I also did try to connect the battery to the PDB and plugin the ESC pins to the CC3D, it powers on static blue light(PWR) and a slow blinking orange light(status). Even when I connect this setup via USB to my machine it gives me the same error.

I ran out of options so thought will ask the experts.

Thanks
Siddharth

[f5soh]

Hi,


You should get something similar to this:

[204641.738880] usb 3-2: new full-speed USB device number 33 using xhci_hcd
[204641.908104] usb 3-2: New USB device found, idVendor=20a0, idProduct=415b
[204641.908106] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[204641.908107] usb 3-2: Product: CopterControl
[204641.908108] usb 3-2: Manufacturer: openpilot.org
[204641.908108] usb 3-2: SerialNumber: 48FF74065180505517221987+FW
[204641.908605] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[204641.910709] input: openpilot.org CopterControl as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2/0003:20A0:415B.001D/input/input32
[204641.911126] hid-generic 0003:20A0:415B.001D: input,hiddev0,hidraw4: USB HID v1.10 Joystick [openpilot.org CopterControl] on usb-0000:00:14.0-2/input2

Try the manual update like described here : https://librepilot.atlassian.net/wiki/display/LPDOC/Firmware+Tab#FirmwareTab-Manualmethod

Is the CC3D blinking at some point when you apply power ?
If not, you should just ask for a replacement.

[disssid]

Thank you for the immediate reply.

I tried connecting it again to all the three USB 2.0 ports on my laptop I get the same message

Code: [Select]

[ 1195.451742] usb 2-1.1: new full-speed USB device number 9 using ehci-pci
[ 1195.523748] usb 2-1.1: device descriptor read/64, error -32
[ 1195.699661] usb 2-1.1: device descriptor read/64, error -32
[ 1195.875792] usb 2-1.1: new full-speed USB device number 10 using ehci-pci
[ 1195.947807] usb 2-1.1: device descriptor read/64, error -32
[ 1196.123810] usb 2-1.1: device descriptor read/64, error -32
[ 1196.299713] usb 2-1.1: new full-speed USB device number 11 using ehci-pci
[ 1196.707828] usb 2-1.1: device not accepting address 11, error -32
[ 1196.779870] usb 2-1.1: new full-speed USB device number 12 using ehci-pci
[ 1197.187881] usb 2-1.1: device not accepting address 12, error -32
[ 1197.188034] usb 2-1-port1: unable to enumerate USB device
PFA the image, I know its not the best of the pictures but yes I can see the orange LED blinking which is named as status and a static blue LED which is the power.

Please let me know if you need any further details.

Thanks
Siddharth

[f5soh]

Try the manual update like described here : https://librepilot.atlassian.net/wiki/display/LPDOC/Firmware+Tab#FirmwareTab-Manualmethod

[disssid]

I tried that Upgrade, Upgrade & Erase and also the Rescue options. They all time out after 20 seconds by saying board not connected.

I'll try the serial manual approach (http://www.southquay3d.com/index.php?route=news/article&news_id=9) and let you know if that works out.

Thank you for the help

[f5soh]

Can you post a picture of the board ?

Blinking led mean a working board and do not need bootloader flashing, you should also try another USB cable.

[disssid]

PFA a 5 second clip of the LED blinking as well as the board.

I tried 3 different USB cables. I use these to connect raspberry pi and beaglebone blacks, they all work fine. I can guarentee you that.

Please let me know if you need any further information

Thanks
Siddharth

[f5soh]

The fading blinking show a board in bootloader mode.
Just tried and i have the exact same errors while in bootloader mode.

With a good cable the manual method should work, this mean connect the board after you hit the Upgrade&Erase button.

[disssid]

I'm not sure if my guess is correct but I guess my controller is already in bootloader mode and Librepilot or for that case even the USB driver is unable to detect it.

I tried your suggestion of hitting Upgrade & Erase and then connect the board, it just times out. The same happens with Upgrade and Rescue as well. The board is not even detected by Librepilot.

Please correct me if I'm wrong

Thanks
Siddharth

[f5soh]

Try the flash through the MainPort you mentioned a few posts before.
http://www.southquay3d.com/index.php?route=news/article&news_id=9

Flash demonstrator : http://cdn2.starkled.com/content/uploads/2012/11/Flash_Loader_Demonstrator_v2.5.0_Setup.exe

and bootloader attached.

[disssid]

Hello,

Sorry for the delay, was trying everything possible

1. followed the instructions at
http://www.southquay3d.com/index.php?route=news/article&news_id=9

attached are the screenshots. After this tried connecting same issue and tried connecting it to a Windows machine same issue again. Librepilot doesn't even detect the board with upgrade, upgrade & erase and rescue after clicking and connecting the board or before clicking connecting and clicking and then re-connecting

2. tried another cable from an old external HD cable, same issue.

3. Finally raised a ticket with GearBest and waiting for their technical team to review it

@f5soh Thank you for all the immediate responses and help.

Let me know if you want me to try anything else.

Thanks
Siddharth

[AerialPerPlexity]

Are you 100% sure the cable you are using to try to hook up the flight controller is a otg (on the go) mini b usb cable. Because that would explain nothing recognizing it. If you used that cable to charge cell phones than it would provide power and show you that its in boot loader mode but once you tried anything else it would fail because it doesn't have the data wires in it to send the information back and forth. Maybe going out and buying a new otg mini b USB would eliminate any  doubt about that being an issue.  Because all the responses from everyone else would have got a workable flight controller working as long as you followed the manual steps maticulusly. One of those cables is like five bucks what's the worst that could happen your in the same position your in now

[disssid]

Thank you for the reply wayne.

As I mentioned in my earlier comment, I used a cable that I used to connect my external HD and it works fine I can still connect my hard disk and see all the data, so my guess is the cable isn't faulty.

But yes as you suggested, there's nothing wrong in getting a new one and trying it out. Will try that tomorrow and update you guys

Thanks
Siddharth

[Mateusz]

Hi Siddarth,

First of all your screenshots indicate that you are using Windows. Sometimes Windows does some wired stuff by using device by another process. That may cause troubles.
If you are using Linux, then I remember modemanager was taking over all uart devices and after removing it, all worked for me. It could also be permissions (try from root maybe).
If you use some virtualisation platform to run Linux under Windows like Virtualbox, it's even more complicated, as Windows may still disconnect device or do some strange things to it.

I would suggest to boot pure Linux and check dmesg. Also be sure to desolder SBL pads, once you flash your firmware. Soldered SBL pads mean that it will always come up into bootloader mode.
With CC3D you have to use SBL method and Uart2USB serial adapter 3.3V afaik like explain in the southquay link you posted yourself.

[disssid]

Thank You for the reply, apologies for the late reply, was busy working on something else.

1. The thing is I use Ubuntu 16.04, but due to the issue and all the resolutions or most of the resources out there being for Windows, I installed Virtual Box and I'm running Windows on it. As the host OS doesn't detect the device it doesn't even get to the guest OS.

2. As you suggested I removed modemmanager and tried but I still get the issue, attached is the screenshot of the dmesg

3. When I flashed the firmware, I joined the SBL and 3.3V using a screw driver and so I don't have any soldered pads.

4. I did follow the method as mentioned in the southquay link, the firmware flashes successfully but the board isn't detected by either linux or windows(checked it on another windows laptop not on virtual box).

I used a FTDI USB TTL Serial cable for flashing the firmware.

Please let me know if you need any further information

Thanks
Siddharth