unable to enumerate usb device

[Chris Bolton]

Hey guys, just tryin' to get started with the smoothieboard here, and I'm getting an 'unable to enumerate usb device' error when connecting the smoothieboard to any of my computers (osx and linux). Anyone seen this before?

[Arthur Wolf]

Hi !

Do you have a config file on the microsd card ?

Cheers !

2013/7/30 Chris Bolton <c...@chrisbolton.me>

Hey guys, just tryin' to get started with the smoothieboard here, and I'm getting an 'unable to enumerate usb device' error when connecting the smoothieboard to any of my computers (osx and linux). Anyone seen this before?

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Courage et bonne humeur.

[Federico Mazzini]

Yup. Copied it to the sd card and put it in the smoothieboard.

On Tuesday, July 30, 2013 1:25:03 AM UTC-7, Arthur Wolf wrote:

Hi !

Do you have a config file on the microsd card ?

Cheers !

2013/7/30 Chris Bolton <c...@chrisbolton.me>

Hey guys, just tryin' to get started with the smoothieboard here, and I'm getting an 'unable to enumerate usb device' error when connecting the smoothieboard to any of my computers (osx and linux). Anyone seen this before?

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-support+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Federico Mazzini]

Here's a quick rundown of where I am at (I'm running Linux Mint 64bit ):
-Started off by cloning the https://github.com/arthurwolf/Smoothie smoothie repo
-Copied the example config file to an 1gb sd card and put that in the smoothie
-Ran the linux_install file, all good no errors
-Ran Buildshell, and then "make clean all". Ran into some issue with the x64 not understanding an x32 command. Installed the ia32-libs package and got it to run all the way through (everything compiled, but did get some odd compiler warnings, not sure if that's normal).
-Ran "make flash", and got "
make[1]: Entering directory `/home/fed/Smoothie/src'
cp ../LPC1768/main.elf ../LPC1768/main_lastupload.elf
lpc21isp ../LPC1768/main.hex /dev/arduino_A900K10V 115200 12000
lpc21isp version 1.85
File ../LPC1768/main.hex:
    loaded...
Start Address = 0x0002404D
    converted to binary format...
    image size : 215572
Image size : 215572
Can't open COM-Port /dev/arduino_A900K10V ! (Error: 2d (0x2))
make[1]: *** [flash] Error 2
make[1]: Leaving directory `/home/fed/Smoothie/src'
make: *** [flash] Error 2"
as the output. Not sure yet what's going on there.

---
"dmesg" gives me this, in relation to the usb device
"[ 6956.712189] usb 3-1: new full-speed USB device number 30 using uhci_hcd
[ 6957.120112] usb 3-1: device not accepting address 30, error -71
[ 6957.120161] hub 3-0:1.0: unable to enumerate USB device on port 1
"

[Arthur Wolf]

2013/8/2 Federico Mazzini <feds...@gmail.com>

Here's a quick rundown of where I am at (I'm running Linux Mint 64bit ):
-Started off by cloning the https://github.com/arthurwolf/Smoothie smoothie repo
-Copied the example config file to an 1gb sd card and put that in the smoothie
-Ran the linux_install file, all good no errors
-Ran Buildshell, and then "make clean all". Ran into some issue with the x64 not understanding an x32 command. Installed the ia32-libs package and got it to run all the way through (everything compiled, but did get some odd compiler warnings, not sure if that's normal).
-Ran "make flash", and got "

you don't use make flash. you get a main.bin in /LPC1768/main.bin and copy that to the sd card as firmware.bin

 

make[1]: Entering directory `/home/fed/Smoothie/src'
cp ../LPC1768/main.elf ../LPC1768/main_lastupload.elf
lpc21isp ../LPC1768/main.hex /dev/arduino_A900K10V 115200 12000
lpc21isp version 1.85
File ../LPC1768/main.hex:
    loaded...
Start Address = 0x0002404D
    converted to binary format...
    image size : 215572
Image size : 215572
Can't open COM-Port /dev/arduino_A900K10V ! (Error: 2d (0x2))
make[1]: *** [flash] Error 2
make[1]: Leaving directory `/home/fed/Smoothie/src'
make: *** [flash] Error 2"
as the output. Not sure yet what's going on there.

---
"dmesg" gives me this, in relation to the usb device
"[ 6956.712189] usb 3-1: new full-speed USB device number 30 using uhci_hcd
[ 6957.120112] usb 3-1: device not accepting address 30, error -71
[ 6957.120161] hub 3-0:1.0: unable to enumerate USB device on port 1

"

--

You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Federico Mazzini]

Alright, Copied the main.bin file to a 1gb SD card and named it firmware.bin and reset the smoothie as well tried the flashing the boot loader procedure. Got a FIRMWARE.BCK file to show up but no firmware.cur file. Still unable to read the device.

[Arthur Wolf]

Did you use the master branch or the edge branch ?

2013/8/5 Federico Mazzini <feds...@gmail.com>

Alright, Copied the main.bin file to a 1gb SD card and named it firmware.bin and reset the smoothie as well tried the flashing the boot loader procedure. Got a FIRMWARE.BCK file to show up but no firmware.cur file. Still unable to read the device.

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Federico Mazzini]

Master, I will try the edge branch tomorrow.

On Monday, August 5, 2013 1:07:43 AM UTC-7, Arthur Wolf wrote:

Did you use the master branch or the edge branch ?

2013/8/5 Federico Mazzini <feds...@gmail.com>

Alright, Copied the main.bin file to a 1gb SD card and named it firmware.bin and reset the smoothie as well tried the flashing the boot loader procedure. Got a FIRMWARE.BCK file to show up but no firmware.cur file. Still unable to read the device.

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-support+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Federico Mazzini]

alright same deal, still can't identify the device and FIRMWARE.BCK is all that shows up when reset, no .cur

[Mark Medrano]

With the current bootloader at least there is no .cur created.  once you've got the .bck file the flash should be finished.

[Federico Mazzini]

Ok well that's good then so it flashes successfully but then it still can't be identified. Any idea what can cause this? because that is currently the only hurdle.

[Arthur Wolf]

So, you are flashing edge, and it flashes correctly, but then over USB it's not recognized by the host computer ?

Using windows ?

2013/8/8 Federico Mazzini <feds...@gmail.com>

Ok well that's good then so it flashes successfully but then it still can't be identified. Any idea what can cause this? because that is currently the only hurdle.

On Wednesday, August 7, 2013 9:43:36 PM UTC-7, Mark Medrano wrote:

With the current bootloader at least there is no .cur created.  once you've got the .bck file the flash should be finished.

--

You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Federico Mazzini]

that's right, and no it's Linux, but ive tried it on all 3 os's and all the same thing.

On Thursday, August 8, 2013 2:05:29 AM UTC-7, Arthur Wolf wrote:

So, you are flashing edge, and it flashes correctly, but then over USB it's not recognized by the host computer ?

Using windows ?

2013/8/8 Federico Mazzini <feds...@gmail.com>

Ok well that's good then so it flashes successfully but then it still can't be identified. Any idea what can cause this? because that is currently the only hurdle.

On Wednesday, August 7, 2013 9:43:36 PM UTC-7, Mark Medrano wrote:

With the current bootloader at least there is no .cur created.  once you've got the .bck file the flash should be finished.

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-support+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Jim Morris]

Try plugging the smoothie directly into the computers USB port, or if it is already try plugging it into a USB2 hub instead. Also If you are plugging it into a USB 3 port try a USB2 port instead. I know that has made a difference with others.

[Daniel Dumitru]

On windows, could you see it on Device Manager ?  HAve you had a look with UsbDevview ?

Please , at the beginning use a short shielded  (thicker)  usb cable.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.

[Arthur Wolf]

Do you have a SD card in there with a config file ? That could be the problem if you don't.

2013/8/9 Federico Mazzini <feds...@gmail.com>

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Federico Mazzini]

yes, the default config file was copied to the sd card as well as the firmware.

[Arthur Wolf]

can I see dmesg just after you plug it in ?

2013/8/9 Federico Mazzini <feds...@gmail.com>

yes, the default config file was copied to the sd card as well as the firmware.

On Monday, July 29, 2013 7:40:35 PM UTC-7, Chris Bolton wrote:

Hey guys, just tryin' to get started with the smoothieboard here, and I'm getting an 'unable to enumerate usb device' error when connecting the smoothieboard to any of my computers (osx and linux). Anyone seen this before?

--

You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Brian Dickman]

If you can download USB Prober for OS X and post a dump from that, it would be helpful as well. You may also get messages in the Console app during plug-in, but you may not.

[Federico Mazzini]

[  229.012247] usb 3-1: new full-speed USB device number 4 using uhci_hcd
[  229.420220] usb 3-1: device not accepting address 4, error -71
[  229.532288] usb 3-1: new full-speed USB device number 5 using uhci_hcd
[  229.948197] usb 3-1: device not accepting address 5, error -71
[  229.948248] hub 3-0:1.0: unable to enumerate USB device on port 1

there are a lot more of those error -71 messages I just cut it off, but basically that ^
I've tried different usb ports, different cable, disabling and re-enabling ndiswrapper/restarting with the device plugged in, irqpoll as a boot option, and installing usbmount (I don't know why it wasn't installed in the first place, but it always mounted other sd readers fine and made no difference with the smoothie).

[Federico Mazzini]

Nothin?

[Chris Bolton]

get a beagleboard

On Mon, Aug 12, 2013 at 5:07 PM, Federico Mazzini <feds...@gmail.com> wrote:

Nothin?

--
You received this message because you are subscribed to a topic in the Google Groups "Smoothieware Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/smoothieware-support/qWkQHPUO6ao/unsubscribe.
To unsubscribe from this group and all its topics, send an email to smoothieware-sup...@googlegroups.com.

[Federico Mazzini]

Lol beagleboards sounding appealing but I'm leaning printrboard. Still would really like this to work. Anyone have anything left? heres the full dmesg if anyone's interested:
[  142.820241] usb 2-1: new full-speed USB device number 6 using uhci_hcd
[  142.944172] usb 2-1: device descriptor read/64, error -71
[  143.172226] usb 2-1: device descriptor read/64, error -71
[  143.388184] usb 2-1: new full-speed USB device number 7 using uhci_hcd
[  143.716258] usb 2-1: device descriptor read/64, error -71
[  143.940261] usb 2-1: device descriptor read/64, error -71
[  144.156282] usb 2-1: new full-speed USB device number 8 using uhci_hcd
[  144.568188] usb 2-1: device not accepting address 8, error -71
[  144.680266] usb 2-1: new full-speed USB device number 9 using uhci_hcd
[  145.092243] usb 2-1: device not accepting address 9, error -71
[  145.092299] hub 2-0:1.0: unable to enumerate USB device on port 1

screencap of whats on the sd card after a flash (via a usb reader since the device can't be enumerated ofc):
http://ge.tt/214Cbko/v/0

On Monday, August 12, 2013 5:09:30 PM UTC-7, Chris Bolton wrote:

get a beagleboard

On Mon, Aug 12, 2013 at 5:07 PM, Federico Mazzini <feds...@gmail.com> wrote:

Nothin?

--
You received this message because you are subscribed to a topic in the Google Groups "Smoothieware Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/smoothieware-support/qWkQHPUO6ao/unsubscribe.

To unsubscribe from this group and all its topics, send an email to smoothieware-support+unsub...@googlegroups.com.

[Arthur Wolf]

Hi !

This is very strange. Did you try on another completely different computer ?

2013/8/13 Federico Mazzini <feds...@gmail.com>

--

You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Brian Dickman]

Obviously there is some bad communication happening with the target board. A few things off the top of my head that would cause this:

- Bad cable (you said you've tried other cables)

- Target CPU brownout (You could put a meter on the 3.3v line and make sure it's stable)

- Firmware is causing the target to reset on USB activity

If you can connect an FTDI cable (USB->TTL UART) to the UART pins, then you could see if the controller is being reset, or staying up but not responding properly to USB. I think that's the most important debug step to start; establishing whether it's a communication issue or a microcontroller hang/reset issue.

[Federico Mazzini]

Sorry, it has been quite a while since I responded. I ordered another board as our project was getting delayed and I needed it running. I'm pretty disappointed since this seems to be a dud board, but I'm going to keep playing with it and seeing if I can get it to work. going to take the FTDI cable suggestion, only question I suppose I have is; when I've narrowed down the issue, what are my options on an actual repair?

2013/8/13 Federico Mazzini <feds...@gmail.com>

get a beagleboard

Nothin?

To unsubscribe from this group and all its topics, send an email to smoothieware-support+unsubscrib...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-support+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Courage et bonne humeur.

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-support+unsub...@googlegroups.com.

[Brian Dickman]

It really depends on what component is the culprit in the end. About the only component I wouldn't replace myself is the uController, as that will take hot air and a very practiced hand, preferably with a stereoscope. Other areas like power supply or the USB lines could be replaced easily enough with a good iron and some patience. If it does turn out to be simply a firmware issue, that is the easiest to fix.

To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.

[Federico Mazzini]

So, after a long time and a different controller, I have finally gotten back to playing with the smoothieboard. I soldered on the FTDI connection but it appears that the board is still not responding. Is there anything more I can do about this troubleshooting-wise? Any possible way to get a replacement after this long seeing as it appears to have been DOA and smoothie is going into production now?

[Chris Harvie-Smith]

There's always hope :-)

I don't know what you can &/or are willing to do so I'll start with the basic as they are most likely.

Do you have any of the following:

Soldering iron Tick

Magnifying lens with good lighting ?

DMM (Amps, Volts, Resistance measurement) ?

Power supply  with V & A meter or connectable through DMM ?

Eagle to view schematics ?

Oscilloscope ? MHz ?

Start:

Power on & this is supplied to the board at 5V ? this is regulated down to 3.3 V.

Using the DMM on Volts range 20 or auto.

Is 3.3 V reaching the CPU  ?

Connect DMM between Gnd on a header to COMmon on DMM & probe the Power in + & - on the pads nearby then on the regulator.

DON'T SHORT ANYTHING OUT WITH THE PROBE TIP, They are sharp to grip but still easily slip off if you turn your head to read the meter.

Should see 5V at input to board & regulator & 3.3V on output of regulator.

Next test the decoupling capacitors near the CPU (biggest chip) AVOID the crowded side with clock crystal & other components.

There are six easy to get at caps to check. One side 0V the other 3.26V on mine.

The CPU pins are too fine a pitch to get a standard probe onto without shorting to next door pins or bending them so don't try you'll just fry it.

Is current being drawn ? My 5 axis smoothie is ~150 mA idle but running firmware attached to a PSU not USB powered.

Connect DMM inline in 10 A mode. PSU + DMM 10A then COMmon to + input to board.

As soon as you are happy with the current disconnect this 10A connection & move back to volts so the next time you probe you don't short out the signal.

So no regulator input &/or output.

+ & - the right way round ?! This happens a lot & is easily overlooked. The markings next to the pads are just for that connector. If you are using a power connection nearby is might be the other way round. Not for 5 V but check what you think is right is. Barrel connector power supplies are not all positive centre (round with hole in centre for pin at plug end).

Beta 4 driver board pic http://smoothieware.org/smoothieboard-beta-guide

Newer 5 driver capable board http://smoothieware.org/smoothieboard

So it might also be a dry joint at one end or the other (looks like a crack around the soldered leg where it should smoothly join to the pad on the PCB.

Probing along the path will show you where to look.

http://en.wikipedia.org/wiki/Soldering

These are through hole examples but the tell-tale gap can be seen.

http://upload.wikimedia.org/wikipedia/commons/thumb/2/20/Cold_solder_joint2.jpg/220px-Cold_solder_joint2.jpg

http://upload.wikimedia.org/wikipedia/commons/thumb/7/72/Gebrochene_loetstellen.jpg/220px-Gebrochene_loetstellen.jpg

Low no current drawn but 3.3 V present ?

Chip may be being held in reset, clock not ticking, bootstrap DFU code empty.

Reset has a pullup resistor to hold it off at 3.3V & a reset button to turn it on pulling it to 0V.

Resistor missing/dry input will float low & be active.

Switch stuck holding low & be active.

Clock not ticking will need a scope to see the 12 MHz cycle on one of the tuning capacitor pins.

Not easy without a scope. Can still look for dry joints or missing tuning caps.

Wit no bootstrap it might be sat there waiting without any way of making it do something you can see.

If power has pulsed a bit high at some point the first thing that seems to happen is wiping of flash memory particularly inside a chip.

If that's all OK the the serial TTL ISP port is next. Did I say check the ground is connected ?!...

Chris
~~~~~