New product - Asus detachable CM3 with CP210x device not supported

[Lee T. Davy]

I have the new CM3000 Chromebook known as "Asus detachable CM3 Chromebook"

in developer mode now.

Before I enabled developer mode I saw "hammer" which is the detachable keyboard

and touch pad implemented as a USB device.

It appeared in the managed USB alone when I turned on Linux

 in Chrome OS Version 96.0.4664.111 (Official Build) (32-bit).

After enabling developer mode it no longer appears.

In crosh shell it is

 Bus 001 Device 003: ID 18d1:5044 Google Inc. Hammer

Additionally I wanted to use an NCE USB model train interface with JMRI.

It incorrectly appears in crosh as

Bus 001 Device 006: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light

Beyond that I fail to see how to add it to the list of supported devices either oin my own system or publicly here.

What is the correct way to test locally and pass on the USB device enabling ?

[ggg]

On Wednesday, December 29, 2021 at 3:14:35 PM UTC-8 leetdavy....@gmail.com wrote:

I have the new CM3000 Chromebook known as "Asus detachable CM3 Chromebook"

in developer mode now.

Before I enabled developer mode I saw "hammer" which is the detachable keyboard

and touch pad implemented as a USB device.

It appeared in the managed USB alone when I turned on Linux

 in Chrome OS Version 96.0.4664.111 (Official Build) (32-bit).

After enabling developer mode it no longer appears.

In crosh shell it is

 Bus 001 Device 003: ID 18d1:5044 Google Inc. Hammer

 

Again, as with previous USB thread, if you are using console (with root login) and not signed in via the GUI,  most external USB peripherals aren't allowed to bind until someone signs in.

Additionally I wanted to use an NCE USB model train interface with JMRI.

It incorrectly appears in crosh as

Bus 001 Device 006: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light

Is the "10c4:ea60" incorrect or the descriptive string?

If it's the latter, my guess is the /etc/udev/hwdb.bin might be out of date. In the past, we made no effort to update it since developers are the only ones looking at the output and the file is only growing in size.

 

Beyond that I fail to see how to add it to the list of supported devices either oin my own system or publicly here.

What is the correct way to test locally and pass on the USB device enabling ?

Does this device need a special USB driver?

And note that "supported" is not the same as "enabled". Historically we've enabled more drivers than are supported.

If the driver is in the upstream linux kernel, you can follow these instructions:

    https://groups.google.com/a/chromium.org/g/chromium-os-dev/c/qFEYjT0WFf4

and in particular read up on kernel configuration:

   https://chromium.googlesource.com/chromiumos/docs/+/master/kernel_development.md#Kernel-configuration

cheers,

grant

[Lee T. Davy]

The device may be correct driver but developers are not the only ones looking at the validity of the VID/PID.
I use this link for valid vendor id.
https://usb-ids.gowdy.us/read/UD/10c4

There is an official response to PID gives me confidence in having the right driver.

https://usb-ids.gowdy.us/read/UD/10c4/ea60

"Name: myAVR mySmartUSB light

The following product actually uses this USB-UART chip: mySmartUSB light
http://shop.myavr.com/index.php?sp=article.sp.php&artID=200006
It's a cheap AVR ISP programmer
pmjdebruijn
2012-03-28 21:59:02"

This is my view from an official response from the VID owner suggesting the preferred PID name.

"Name: CP210x UART Bridge

I work at Silicon Labs. There are several compatible parts that use this PID. It would be awkward to list all in the description and we prefer CP210x UART Bridge. Also, this should not be overloaded with other product names that happen to use the CP210x and don't bother to change the PID. If custom branding is desired then those vendors should use a different PID.
kroesche
2017-09-27 21:05:29"

I have POWERWASHED back to non-developer and await correct permissions or I could not use Crostini with NCE USB and JMRI.

It is a disappointment but only to a very small group of hobbyists using JMRI with NCE interface with crostini.