Menu

Topic-icon SDC2130 (without P5 pad) lost USB after upgrading firmware to v.1.2, May 25, 2013 version

More
6 years 5 months ago #29528397 by sd1074
I've just updated my SDC2130 firmware from FID="Roboteq v1.2 RCB100 08/24/2011" to v.1.2, May 25, 2013 version. DFULoader reported "Verified successfully". After that I lost USB connection to the device. The USB LED on the board is off.

My motor controller board does not have an 8-pin pad labelled as "P5" which was mentioned here . It has an 8-pin pad labelled as "P3" though.

I was able to connect it in the DFU mode by shortening pins 2 and 6 as described here . This allowed me to update the firmware again, which, however, did not bring my USB back to life. Also I was unable to find older firmware version on the web-site to resurrect my motor controller.

Please, help.

Please Log in or Create an account to join the conversation.

  • Griffin Baker
  • Griffin Baker's Avatar
6 years 5 months ago #29528398 by Griffin Baker
So it appears you have a newer pcb rev. After the update is done in dfu mode, you have to cycle the power to the controller again before it becomes active again. When you cycle the power to the controller, does your computer give you an error saying usb malfunctioned, or does it computer making a beep sound like it detected hardware?

Please Log in or Create an account to join the conversation.

  • Griffin Baker
  • Griffin Baker's Avatar
6 years 5 months ago #29528399 by Griffin Baker
So I did the following. Mine already had a newer version of firmware installed. Using the usb and connecting to Roborun+, I went into console tab and did a firmware update via usb. I had the STM dfu drivers installed, and then flashed back to 8/25/11 firmware. I did the update, closed the dfu loader, and then cycled power to controller. Connected to roborun+ again, and the firmware reported back the 8/25/11 firmware, just 1 day after your version.

I then did the update via usb again, and selected the 5/25/13 version, and did the update. Verified successfully came up. I closed the dfu loader, and cycled power. Upon power up, I got a usb not recognized; so I cycled power again. This time the error did not come up, and I was able to connect to roborun+ again.

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #29528400 by sd1074

When you cycle the power to the controller, does your computer give you an error saying usb malfunctioned, or does it computer making a beep sound like it detected hardware?

Computer makes a beep sound like a new USB device is connected.

I checked Device manager (Windows 7 Enterprise). Motor controller appears as "Unknown Device" with an exclamation mark. Device status in the properties says: "Windows has stopped this device because it has reported problems. (Code 43)".

I did cycle power several times after update. It didn't help.

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #29528401 by sd1074
Not sure if this will help, but I also tried it on a Linux machine. No tty device appears in /dev when plugging the motor controller USB cable, and here is what dmesg reports when I do this:
[554715.908653] usb 3-1: new full-speed USB device number 45 using xhci_hcd
[554715.911505] usb 3-1: Device not responding to set address.
[554716.115476] usb 3-1: Device not responding to set address.
[554716.316587] usb 3-1: device not accepting address 45, error -71
[554716.428600] usb 3-1: new full-speed USB device number 46 using xhci_hcd
[554716.431325] usb 3-1: Device not responding to set address.
[554716.635338] usb 3-1: Device not responding to set address.
[554716.836534] usb 3-1: device not accepting address 46, error -71
[554716.948535] usb 3-1: new full-speed USB device number 47 using xhci_hcd
[554716.951372] usb 3-1: Device not responding to set address.
[554717.155341] usb 3-1: Device not responding to set address.
[554717.356464] usb 3-1: device not accepting address 47, error -71
[554717.468450] usb 3-1: new full-speed USB device number 48 using xhci_hcd
[554717.471300] usb 3-1: Device not responding to set address.
[554717.675184] usb 3-1: Device not responding to set address.
[554717.876381] usb 3-1: device not accepting address 48, error -71
[554717.876433] hub 3-0:1.0: unable to enumerate USB device on port 1

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #29528402 by sd1074
Where can I download previous versions of the firmware?

Please Log in or Create an account to join the conversation.

  • roboteq
  • roboteq's Avatar
6 years 5 months ago #29528403 by roboteq
To make an old SDC2130/2150 work with new firmware, you would need to solder a wire across two pad of the 8-pad empty spot.

Alternatively, you can install this old firmware.
Attachments:

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago - 6 years 5 months ago #29528404 by sd1074
All right. Maybe because it was kind of late yesterday, I did not notice the P5 pad. I was looking for an 8-pin SIP connector similar to this one . And I found the P3 pins, so I thought I don't have P5.
Nevertheless, I actually have it.

Based on [ dev.roboteq.com/dev1/index.php/forum/10-...2-usb-not-recognised ], I figured I need to solder pin 1 and 2 on P5. I do not see a clear mark for the first pin on the board.

Here is how my board looks like: (You can see there is no pins in P5 just pads). Should I solder pads labelled A or pads labelled B on the image to make the new firmware work?

Please Log in or Create an account to join the conversation.

  • Griffin Baker
  • Griffin Baker's Avatar
6 years 5 months ago #29528405 by Griffin Baker
I can't see your board. I don't have any older pcb boards that have the P5 location. Perhaps take a close up pic.

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #29528406 by sd1074
I am not sure why you can't see my pic. I opened it from another location, and on three other computers. Let me clarify: there is no connector, there is no pins on P5. There are just 8 pads similar tow what you find for a SOIC-8 component. It's labelled as P5 though.

Here is a pic from Roboteq web-site: dev.roboteq.com/dev1/press/sdc2130-1850x1387.jpg
If you open this pic in MS Paint, the top left corner of P5 pad will be at the following pixel coordinates: 810px,790px, and the bottom right corner will be at: 890px, 855px.

Please Log in or Create an account to join the conversation.

Moderators: tonysantoni
Time to create page: 0.117 seconds
Go to top