USB ( FT2232 ) not recognized

Projects iCEBreaker
1

Hello All,
thanks to @esden and the community for this wonderful project.

I have received my iCEBreaker v1.0e board, but so far I am unable to recognize it over the USB

I have tried on both Ubuntu 20.04 and Windows 10

Ubuntu 20.04
first I tried to check USB devices using the following command with plugin-ing in and out the iCEbreaker several times but no change in the list

$ sudo lsusb

Then checked by grepping FTDI but nothing was found [ i do not have anything else connected over USB ]

sudo dmesg | grep 'FTDI'

and finally checked the kernel log and found the USB failing to enumerate

image
image951×109 32.7 KB

Windows 10

when plugged in at windows it showed USB device was not recognized. and then I installed Zadig 2.7
Tried to install libusbK WinUSB libusb-win32 but all of them failed .

Hardware checking
fearing that A broken/faulty FT2232 chip got shipped I checked the 3.3V points of the PCB and found them to be okay. I do not have the apparatus to sample the FTDI_CLK pin

Help Wanted
I tried all the above with PMOD2 disconnected. I will very grateful for any help in this regard

1 Like
2

Also getting this error. sudo dmesg | tail -20 outputs the following:

[ 1910.415477] usb 3-2.4.4: new full-speed USB device number 51 using xhci_hcd
[ 1910.547580] usb 3-2.4.4: device descriptor read/64, error -32
[ 1910.791584] usb 3-2.4.4: device descriptor read/64, error -32
[ 1911.031466] usb 3-2.4.4: new full-speed USB device number 52 using xhci_hcd
[ 1911.163549] usb 3-2.4.4: device descriptor read/64, error -32
[ 1911.403564] usb 3-2.4.4: device descriptor read/64, error -32
[ 1911.512085] usb 3-2.4-port4: attempt power cycle
[ 1913.019335] usb 3-2.4.4: new full-speed USB device number 53 using xhci_hcd
[ 1913.019645] usb 3-2.4.4: Device not responding to setup address.
[ 1913.227721] usb 3-2.4.4: Device not responding to setup address.
[ 1913.435367] usb 3-2.4.4: device not accepting address 53, error -71
[ 1913.567327] usb 3-2.4.4: new full-speed USB device number 54 using xhci_hcd
[ 1913.567646] usb 3-2.4.4: Device not responding to setup address.
[ 1913.775678] usb 3-2.4.4: Device not responding to setup address.
[ 1913.983334] usb 3-2.4.4: device not accepting address 54, error -71
[ 1913.984028] usb 3-2.4-port4: unable to enumerate USB device
3

Hi @hassin, I was able to resolve this thanks to advice from @gatecat on the discord server. My problem was that I had unconstrained pins in my design (i.e. my pdc did not set the location of some outputs on my design), which led the Radiant tool to assign them randomly, likely to an important pin required by the FTDI chip (@gatecat believes it was pin 35, the FTDI sclk). Was able to test this by shorting the CRESET header and unplugging/replugging my usb cable in. Although it sounds like you had this issue from the very beginning / never programmed yours.

4

Hello, @slagernate thanks a lot for your kind reply

  1. my iCEBreaker v1.0e is freshly shipped, I never Programmed it before
  2. plugged it in at USB, the G R Leds are blinking
  3. Command $ lsusb did not find any FTDI device
  4. Then executed your command $sudo dmesg | tail -20 and has got similar output
    Selection_340
  5. shorted the CRESET header
  6. The G R Led blinking got stopped
  7. Plugged-out USB
  8. Plugged in USB again
  9. Like point 7 no blinking
  10. no FTDI device found by $ lsusb
  11. Command $sudo dmesg | tail -20 output is same as before
  12. if CRESET header is un-shorted like default , LEDs start blinking again

Am I missing anything out of the instructions given by you? or is my FTDI chip is faulty ?

Eagery waiting for your reply . thanks a lot for your kind patience

5

Hi @hassin. Sorry for not responding for a while. I found my solution by asking on the icebreaker discord chat room: 1BitSquared - Live Community Chat --you may be able to get help there as well (if you haven’t already asked).

6

@slagernate thanks for the heads-up
Let me create a Discord Account and join in there.