From: Matthias Fuchs <matthias.fuchs@esd.eu>
To: Francesco Giovannini <francesco.giovannini@iit.it>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
esd - Support <support@esd.eu>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Can't start ESD CAN-USB/2
Date: Mon, 17 Feb 2014 14:14:34 +0100 [thread overview]
Message-ID: <53020B3A.1090906@esd.eu> (raw)
In-Reply-To: <5301FF62.4090800@iit.it>
Hi Francesco,
I forwarded this issue to our support. We will try to reproduce
the issue here with your setup (Suse 12.2) and will come back to you
later.
We will keep the list on cc as far this has to do with linux-can.
Matthias
On 02/17/2014 01:24 PM, Francesco Giovannini wrote:
>
> On 02/17/2014 08:29 AM, Matthias Fuchs wrote:
>> Hi Francesco,
>>
>> I just saw your posting to the linux-can list about our CAN-USB/2.
>>
>> Did you solve your problems?
>>
>> Matthias
>>
>
> On 02/01/2014 03:27 PM, Marc Kleine-Budde wrote:
>>>>> 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 :)
>>
>>> 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.
>>
>>> 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<matthias.fuchs@esd.eu>, 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
>
--
------------------------------------------------------------------------
Dipl.-Ing. Matthias Fuchs
Head of System Design
esd electronic system design gmbh
Vahrenwalder Str. 207 - 30165 Hannover - GERMANY
Phone: +49-511-37298-0 - Fax: +49-511-37298-68
Please visit our homepage http://www.esd.eu
Quality Products - Made in Germany
-------------------------------------------------------------------------
Geschäftsführer: Klaus Detering
Amtsgericht Hannover HRB 51373 - VAT-ID DE 115672832
-------------------------------------------------------------------------
next prev parent reply other threads:[~2014-02-17 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 16:09 Can't start ESD CAN-USB/2 Francesco Giovannini
2014-01-31 16:14 ` Marc Kleine-Budde
2014-01-31 17:04 ` Francesco Giovannini
2014-01-31 17:26 ` Marc Kleine-Budde
2014-01-31 17:27 ` Marc Kleine-Budde
2014-01-31 17:38 ` Francesco Giovannini
2014-01-31 17:43 ` Marc Kleine-Budde
[not found] ` <52EBE25E.40707@iit.it>
2014-01-31 17:56 ` Marc Kleine-Budde
[not found] ` <52EBF7C5.9050309@iit.it>
2014-02-01 12:21 ` Marc Kleine-Budde
[not found] ` <52ECEE3D.4000701@iit.it>
2014-02-01 14:27 ` Marc Kleine-Budde
[not found] ` <5301FF2B.4020701@iit.it>
2014-02-17 12:24 ` Francesco Giovannini
2014-02-17 13:14 ` Matthias Fuchs [this message]
2014-02-17 13:30 ` Matthias Fuchs
2014-02-17 13:37 ` Matthias Fuchs
2014-02-17 16:13 ` Francesco Giovannini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53020B3A.1090906@esd.eu \
--to=matthias.fuchs@esd.eu \
--cc=francesco.giovannini@iit.it \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=support@esd.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).