RE: serial: usb: cdc-acm: OMRON B5L ToF, device probe failed

From: "michael.lee@omron.com" <michael.lee@omron.com>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>,
	Lars Melin <larsm17@gmail.com>,
	USB list <linux-usb@vger.kernel.org>
Cc: Oliver Neukum <oneukum@suse.com>
Subject: RE: serial: usb: cdc-acm: OMRON B5L ToF, device probe failed
Date: Tue, 21 Jun 2022 00:38:22 +0000	[thread overview]
Message-ID: <OSZP286MB1776CCBCBFE38B25C7DB9978E1B39@OSZP286MB1776.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <cbcc2071-5b56-025e-cae6-5af0210e2363@gtsys.com.hk>

Dear Chris,

The below is the reply from Japan.

Dose they do the below commnad after connect B5L to USB?

sudo modprobe usbserial vendor=0x0590 product=0x00ca
sudo chmod o+wr /dev/ttyUSB0

For linux environment ,this commnad is needed to connect B5L to USB.
We preapre the below sh file with c++ sample codes.
connect_tof.sh
https://github.com/omron-devhub/b5l_TOFsensor_Sample_cpp
----------------
ReadMe_E.txt
1. File description & How to build
The following files are included in the Sample Code package.
  build.sh             [   Linux   ] Shell script for compilation
 connect_tof.sh       [   Linux   ] Shell script for connection B5L (Use when ToF_Sample execution does not work)
 DetectionCuboid.pdf  [ Win/Linux ] Explanatory drawing of Detection Cuboid setting
 init_gpio7.sh        [RaspberryPi] Shell script for setting GPIO #7 pin as output
 ToF_Sample.cpp       [ Win/Linux ] Sample Code Main
..........

Best Regards

Michael Lee

-----Original Message-----
From: Chris Ruehl <chris.ruehl@gtsys.com.hk> 
Sent: Monday, June 20, 2022 2:21 PM
To: Lars Melin <larsm17@gmail.com>; USB list <linux-usb@vger.kernel.org>
Cc: Oliver Neukum <oneukum@suse.com>
Subject: Re: serial: usb: cdc-acm: OMRON B5L ToF, device probe failed

On 20/6/2022 11:35 am, Lars Melin wrote:
> On 6/20/2022 09:44, Chris Ruehl wrote:
>> Enabled the debugfs and checked /sys/kernel/debug/usb/devices for the 
>> B5L
>>
>> T:  Bus=02 Lev=03 Prnt=04 Port=01 Cnt=01 Dev#= 17 Spd=480  MxCh= 0
>> D:  Ver= 2.00 Cls=02(comm.) Sub=02 Prot=00 MxPS=64 #Cfgs=  1
>> P:  Vendor=0590 ProdID=00ca Rev= 2.00
>> S:  Manufacturer=OMRON Corporation
>> S:  Product=OMRON B5L-001011
>> S:  SerialNumber=010000319A1
>> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=  4mA
>> I:* If#= 0 Alt= 0 #EPs= 4 Cls=02(comm.) Sub=02 Prot=00 Driver=(none)
>> E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>> E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>> E:  Ad=03(O) Atr=03(Int.) MxPS=  64 Ivl=4096ms
>> E:  Ad=84(I) Atr=03(Int.) MxPS=  64 Ivl=4096ms
>>
>> Driver is not assigned.
>
>
> There is nothing CDC-ACM in that interface except for the interface 
> attributes, the interface lacks everything else needed for it to be CDC-ACM.
> Check if Omron has an updated firmware fixing the problems or if they 
> have their own proprietary driver for the device.
>
>
> /Lars

Hi Lars,

that's what I hold the Hk headquarter, they forward the request back to the developers in Japan.

Thanks
Chris