Can't start ESD CAN-USB/2

Hi guys!

I am running OpenSuse 12.2, kernel 3.4.63-2.44-desktop. I downloaded and installed libsocketcan v0.0.9 and canutils v4.0.6. I then compiled the esd_can2 module and modprobed it correctly. When i plug in my CAN-USB/2 device i get the following from dmesg:

   [186823.262021] usb 1-10: new high-speed USB device number 22 using
   ehci_hcd
   [186823.826031] usb 1-10: device not accepting address 22, error -71
   [186823.877025] hub 1-0:1.0: unable to enumerate USB device on port 10
   [186827.879018] usb 1-10: new high-speed USB device number 24 using
   ehci_hcd
   [186827.995429] usb 1-10: New USB device found, idVendor=0ab4,
   idProduct=0010
   [186827.995432] usb 1-10: New USB device strings: Mfr=1, Product=2,
   SerialNumber=3
   [186827.995435] usb 1-10: Product: USB2292
   [186827.995438] usb 1-10: Manufacturer: esd electronic system design
   gmbh (www.esd-electronics.com)
   [186827.995440] usb 1-10: SerialNumber: GM001950
   [186827.997824] esd_usb2 1-10:1.0: can0: device can0 registered

The device appears to be correctly recognised and the can0 interface is ready to be used. I then set the bitrate and several other paramters with:

   # canconfig can0 bittiming  prop-seg 2 phase-seg1 12 phase-seg2 5
   sjw 1 brp 3 tq 50

   can0 bittiming:
        tq: 50, prop-seq: 2 phase-seq1: 12 phase-seq2: 5 sjw: 1, brp: 3
   can0 bitrate: 1000000, sample-point: 0.750

Quoted 26 lines · Francesco Giovannini

Hi guys!

I am running OpenSuse 12.2, kernel 3.4.63-2.44-desktop. I downloaded and installed libsocketcan v0.0.9 and canutils v4.0.6. I then compiled the esd_can2 module and modprobed it correctly. When i plug in my CAN-USB/2 device i get the following from dmesg:

    [186823.262021] usb 1-10: new high-speed USB device number 22 using
    ehci_hcd
    [186823.826031] usb 1-10: device not accepting address 22, error -71
    [186823.877025] hub 1-0:1.0: unable to enumerate USB device on port 10
    [186827.879018] usb 1-10: new high-speed USB device number 24 using
    ehci_hcd
    [186827.995429] usb 1-10: New USB device found, idVendor=0ab4,
    idProduct=0010
    [186827.995432] usb 1-10: New USB device strings: Mfr=1, Product=2,
    SerialNumber=3
    [186827.995435] usb 1-10: Product: USB2292
    [186827.995438] usb 1-10: Manufacturer: esd electronic system design
    gmbh (www.esd-electronics.com)
    [186827.995440] usb 1-10: SerialNumber: GM001950
    [186827.997824] esd_usb2 1-10:1.0: can0: device can0 registered

The device appears to be correctly recognised and the can0 interface is ready to be used. I then set the bitrate and several other paramters with:

Quoted 6 lines

    # canconfig can0 bittiming  prop-seg 2 phase-seg1 12 phase-seg2 5
    sjw 1 brp 3 tq 50

    can0 bittiming:
         tq: 50, prop-seq: 2 phase-seq1: 12 phase-seq2: 5 sjw: 1, brp: 3
    can0 bitrate: 1000000, sample-point: 0.750

Try to set the bittiming with this command:

     canconfig can0 bitrate 1000000

Does this work?

Marc

I tried #canconfig can0 bitrate 1000000

   can0 bitrate: 1000000, sample-point: 0.750

I am however still unable to successfully start the can0 interface with

# ifconfig can0 up. Same error shows up.

Quoted 6 lines · Francesco Giovannini

I tried #canconfig can0 bitrate 1000000

   can0 bitrate: 1000000, sample-point: 0.750

I am however still unable to successfully start the can0 interface with

# ifconfig can0 up. Same error shows up.

What's the outout of "canconfig can0" after "canconfig can0 bitrate 1000000"

Quoted 6 lines · Francesco Giovannini

I tried #canconfig can0 bitrate 1000000

   can0 bitrate: 1000000, sample-point: 0.750

I am however still unable to successfully start the can0 interface with

# ifconfig can0 up. Same error shows up.

What's the outout of "canconfig can0" after "canconfig can0 bitrate 1000000"

Here is the output:

oSuseBox-IIT:/home/fgiovannini # dmesg -c > /dev/null

oSuseBox-IIT:/home/fgiovannini # canconfig can0 bitrate 1000000 can0 bitrate: 1000000, sample-point: 0.750

oSuseBox-IIT:/home/fgiovannini # canconfig can0
can0 bitrate: 0, sample-point: 0.000
can0 bittiming:

	tq: 0, prop-seq: 0 phase-seq1: 0 phase-seq2: 0 sjw: 0, brp: 0

can0 state: STOPPED
can0 restart-ms: 0
can0 ctrlmode: loopback[OFF], listen-only[OFF], tripple-sampling[OFF],one-shot[OFF], berr-reporting[OFF] can0 clock freq: 60000000
can0 bittiming-constants: name esd_usb2,

	tseg1-min: 1, tseg1-max: 16, tseg2-min: 1, tseg2-max: 8,
	sjw-max 4, brp-min: 1, brp-max: 1024, brp-inc: 1,

oSuseBox-IIT:/home/fgiovannini # dmesg

[ 1189.194292] esd_usb2 1-10:1.0: can0: setting BTR=0x804d0002
[ 1189.195338] usb 1-10: USB disconnect, device number 7
[ 1189.432021] usb 1-10: new high-speed USB device number 8 using ehci_hcd
[ 1189.547438] usb 1-10: New USB device found, idVendor=0ab4, idProduct=0010
[ 1189.547442] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1189.547445] usb 1-10: Product: USB2292
[ 1189.547447] usb 1-10: Manufacturer: esd electronic system design gmbh (www.esd-electronics.com)
[ 1189.547450] usb 1-10: SerialNumber: GM001950
[ 1189.549832] esd_usb2 1-10:1.0: can0: device can0 registered

Weird. Looks like canconfig bitrate acts like it is unplugging and plugging the device. Is this normal?

I am running OpenSuse 12.2, kernel 3.4.63-2.44-desktop. I downloaded and installed libsocketcan v0.0.9 and canutils v4.0.6. I then compiled the esd_can2 module and modprobed it correctly. When i plug in my CAN-USB/2 device i get the following from dmesg:

Yes I had to compile it myself because OpenSuse does not include it. I first added it to the kernel config as a module and then ran make M=./drivers/net/can/usb in the kernel source tree.

Sorry my email client does that automatically.

I just re-build the kernel module without luck. I am getting the same weird behaviour. I also tried changing CAN-USB/2 device, cable and port. This too did not solve the problem.

Unfortunately I cannot try a different machine. I am bound to this OpenSuse machine because of hardware requirements.

Any chance you might have a last minute inspiration? ;)

Quoted 3 lines

Quoted 1 line

Any chance you might have a last minute inspiration? ;)

Can you make a firmware update of the USB adapter? Does the adapter work under windows?

So yesterday I tried the same esd device on my Debian machine running Wheezy and kernel 3.2.0 (so an older kernel than the OpenSuse one) and everything worked fine. I was able to set the bitrate and dump data from the device. And yes the device works flawlessly under windows.

With Suse I also tried switching esd devices and cables without any luck.

Do you think this behaviour might be due caused by problems on the driver side or on the canutils side? As in: should I raise this issue with the ESD driver developers?

Hi Francesco,

I just saw your posting to the linux-can list about our CAN-USB/2.

Did you solve your problems?

Matthias

Quoted 7 lines

Quoted 3 lines

Quoted 1 line

Any chance you might have a last minute inspiration? ;)

Can you make a firmware update of the USB adapter? Does the adapter work under windows?

So yesterday I tried the same esd device on my Debian machine running Wheezy and kernel 3.2.0 (so an older kernel than the OpenSuse one) and everything worked fine. I was able to set the bitrate and dump data from the device. And yes the device works flawlessly under windows.

Okay, the device is working. Even under Linux :)

Quoted 1 line

With Suse I also tried switching esd devices and cables without any luck.

But the Suse is a different machine, so different USB controller/hardware and different USB driver.

Quoted 3 lines

Do you think this behaviour might be due caused by problems on the driver side or on the canutils side? As in: should I raise this issue with the ESD driver developers?

It's not the canutils, they just send the parameters into the kernel. The kernel driver hasn't changed much. Feel free to contact the driver developer Matthias Fuchs<[email protected]>, keep the mailinglist on Cc, if possible.

regards,
Marc

Quoted 3 lines · Francesco Giovannini

Yes I had to compile it myself because OpenSuse does not include it. I first added it to the kernel config as a module and then ran make M=./drivers/net/can/usb in the kernel source tree.

Please don't top post.

Have you used the kernel sources provided by suse? If not, try these. Try a different USB port on the machine, if the CAN adapter has a USB cable that is removable, swap it too. If it's still failing try a different machine.

Quoted 8 lines · Matthias Fuchs

Hi Francesco,

I just saw your posting to the linux-can list about our CAN-USB/2.

Did you solve your problems?

Matthias

Quoted 16 lines · Marc Kleine-Budde

Quoted 7 lines

Quoted 3 lines

Quoted 1 line

Any chance you might have a last minute inspiration? ;)

Can you make a firmware update of the USB adapter? Does the adapter work under windows?

So yesterday I tried the same esd device on my Debian machine running Wheezy and kernel 3.2.0 (so an older kernel than the OpenSuse one) and everything worked fine. I was able to set the bitrate and dump data from the device. And yes the device works flawlessly under windows.

Okay, the device is working. Even under Linux :)

Quoted 1 line

With Suse I also tried switching esd devices and cables without any luck.

But the Suse is a different machine, so different USB controller/hardware and different USB driver.

Quoted 3 lines

Do you think this behaviour might be due caused by problems on the driver side or on the canutils side? As in: should I raise this issue with the ESD driver developers?

Quoted 8 lines

It's not the canutils, they just send the parameters into the kernel. The kernel driver hasn't changed much. Feel free to contact the driver developer Matthias Fuchs<[email protected]>, keep the mailinglist on Cc, if possible.

regards,
Marc

Hi Matthias,

I was told to keep the linux-can mailing list in the loop.

I did not solve the problem. I believe it might be due to a USB controller problem as Marc suggested. For information sake here are the output of dmesg, lsusb and lspci as I plug in the device:

oSuseBox-IIT:/home/fgiovannini # dmesg | tail
[ 1126.850018] usb 1-10: new high-speed USB device number 8 using ehci_hcd
[ 1126.965630] usb 1-10: New USB device found, idVendor=0ab4, idProduct=0010
[ 1126.965634] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1126.965637] usb 1-10: Product: USB2292
[ 1126.965640] usb 1-10: Manufacturer: esd electronic system design gmbh (www.esd-electronics.com)
[ 1126.965642] usb 1-10: SerialNumber: GM001950
[ 1126.968027] esd_usb2 1-10:1.0: can0: device can0 registered

oSuseBox-IIT:/home/fgiovannini # lsusb
Bus 002 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 001 Device 008: ID 0ab4:0010
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

oSuseBox-IIT:/home/fgiovannini # lspci
00:00.0 Host bridge: NVIDIA Corporation MCP73 Host Bridge (rev a2) 00:00.1 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a2)
00:01.0 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.1 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.2 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.3 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.4 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.5 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.6 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:02.0 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:03.0 ISA bridge: NVIDIA Corporation MCP73 LPC Bridge (rev a2) 00:03.1 SMBus: NVIDIA Corporation MCP73 SMBus (rev a1) 00:03.2 RAM memory: NVIDIA Corporation MCP73 Memory Controller (rev a1) 00:03.3 Co-processor: NVIDIA Corporation MCP73 Co-processor (rev a2) 00:03.4 RAM memory: NVIDIA Corporation MCP73 Memory Controller (rev a1) 00:04.0 USB controller: NVIDIA Corporation GeForce 7100/nForce 630i USB (rev a1)
00:04.1 USB controller: NVIDIA Corporation MCP73 [nForce 630i] USB 2.0 Controller (EHCI) (rev a1)
00:08.0 IDE interface: NVIDIA Corporation MCP73 IDE (rev a1) 00:09.0 Audio device: NVIDIA Corporation MCP73 High Definition Audio (rev a1)
00:0a.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1) 00:0b.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1) 00:0c.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1) 00:0d.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1) 00:0e.0 SATA controller: NVIDIA Corporation GeForce 7100/nForce 630i SATA (rev a2)
00:0f.0 Ethernet controller: NVIDIA Corporation MCP73 Ethernet (rev a2) 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350]
02:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI RV710/730 HDMI Audio [Radeon HD 4000 series]

Francesco

Quoted 3 lines · Francesco Giovannini

Yes I had to compile it myself because OpenSuse does not include it. I first added it to the kernel config as a module and then ran make M=./drivers/net/can/usb in the kernel source tree.

Please don't top post.

Have you used the kernel sources provided by suse? If not, try these. Try a different USB port on the machine, if the CAN adapter has a USB cable that is removable, swap it too. If it's still failing try a different machine.

Marc

Quoted 3 lines · Francesco Giovannini

Yes I had to compile it myself because OpenSuse does not include it. I first added it to the kernel config as a module and then ran make M=./drivers/net/can/usb in the kernel source tree.

Please don't top post.

Have you used the kernel sources provided by suse? If not, try these. Try a different USB port on the machine, if the CAN adapter has a USB cable that is removable, swap it too. If it's still failing try a different machine.

Marc