Hi,

I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
an independant little lcd screen with buttons, apparently it runs some
kind of OS because it can access the net (e.g. to retrieve RSS) even
when the computer is off - I guess they mean soft-off.

Well, all that is theory because it's under Vista, which I don't have.
Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
storage device, but I can't mount it (the kernel says it's bound to sdc,
but sdc doesn't exist).
I'd like to access it. Does anyone know how that thing works ?

Thanks,
	Xav

PS: please Cc: me on anwers

interesting dmesg part:

usb 7-4: new high speed USB device using ehci_hcd and address 3
usb 7-4: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access     ASUS     ScreenDUO             PQ: 0 ANSI: 2
sd 9:0:0:0: [sdc] Attached SCSI removable disk
usb 7-4: USB disconnect, address 3
usb 7-4: new high speed USB device using ehci_hcd and address 4
usb 7-4: configuration #1 chosen from 1 choice
scsi10 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 10:0:0:0: Direct-Access     ASUS     ScreenDUO             PQ: 0 ANSI: 2
sd 10:0:0:0: [sdc] Attached SCSI removable disk


[root@awak:~]$ fdisk /dev/sdc

Unable to open /dev/sdc



[root@awak:~]$ lsusb -v

Bus 007 Device 004: ID 1043:3100 iCreate Technologies Corp. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1043 iCreate Technologies Corp.
  idProduct          0x3100 
  ...
[ message continues ]

..

As root, try:   mknod /tmp/sdc b 8 32 ; fdisk /tmp/sdc

Any different?
--

[ message continues ]

Nope. But /dev/sdc has already been created, and looks right (b 8 32
too). Just there's nothing behind it.

	Xav


--

[ message continues ]

Turn on CONFIG_USB_STORAGE_DEBUG and see what logs it generates when you
try to access the device.

Matt

--=20
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.=
net=20
Maintainer, Linux USB Mass Storage Driver

NYET! The evil stops here!
					-- Pitr
User Friendly, 6/22/1998
[ message continues ]

What does usbmon show when you modprobe usb-storage?  (The instructions 
for usbmon are in the kernel source file Documentation/usb/usbmon.txt.)

Alan Stern

--

[ message continues ]

dfb8d3c0 4163439081 C Ii:7:001:1 0:2048 1 = 10
dfb8d3c0 4163439091 S Ii:7:001:1 -115:2048 4 <
e5d7aa40 4163439171 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163439176 C Ci:7:001:0 0 4 = 01050100
e5d7aa40 4163439179 S Co:7:001:0 s 23 01 0010 0004 0000 0
e5d7aa40 4163439182 C Co:7:001:0 0 0
e5d7aa40 4163439184 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163439186 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163470364 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163470368 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163502356 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163502360 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163534355 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163534358 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163566364 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163566367 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163566374 S Co:7:001:0 s 23 03 0004 0004 0000 0
e5d7aa40 4163566377 C Co:7:001:0 0 0
e5d7aa40 4163622353 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163622563 C Ci:7:001:0 0 4 = 03051000
e5d7aa40 4163678364 S Co:7:001:0 s 23 01 0014 0004 0000 0
e5d7aa40 4163678369 C Co:7:001:0 0 0
e5d7aa40 4163678392 S Ci:7:000:0 s 80 06 0100 0000 0040 64 <
e5d7aa40 4163678576 C Ci:7:000:0 0 18 = 12010002 00000040 43100031 01001020 6001
e5d7aa40 4163678602 S Co:7:001:0 s 23 03 0004 0004 0000 0
e5d7aa40 4163678607 C Co:7:001:0 0 0
e5d7aa40 4163734354 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163734568 C Ci:7:001:0 0 4 = 03051000
e5d7aa40 4163790363 S Co:7:001:0 s 23 01 0014 0004 0000 0
e5d7aa40 4163790370 C Co:7:001:0 0 0
e5d7aa40 4163790373 S Co:7:000:0 s 00 05 0005 0000 0000 0
e5d7aa40 4163790577 C Co:7:000:0 0 0
e5d7aa40 4163810360 S Ci:7:005:0 s 80 06 0100 0000 0012 18 <
e5d7aa40 4163810578 C Ci:7:005:0 0 18 = 12010002 00000040 43100031 01001020 6001
e5d7aa40 4163810603 S Ci:7:005:0 s 80 06 0200 0000 0009 9 <
e5d7aa40 4163810828 C Ci:7:005:0 0 9 = 09022300 010130c0 00
e5d7aa40 4163810847 S Ci:7:005:0 s 80 06 0200 0000 0023 35 <
e5d7aa40 ...
[ message continues ]

...

The ScreenDUO is reporting that no medium is present.  Maybe it needs 
you to insert some sort of flash memory card before it will work as a 
mass-storage device.

Alan Stern

--

[ message continues ]

Ah. Apparently it just waits for some driver from the Windows side (no
way to insert anything in there).
I guess it'll just be another useless piece of electronics at home.

Thanks,
	Xav


--

[ message continues ]

for future use, what was it that made everyone decide that this is going 
to show up as a storage device?

with a screen and buttons I would have guessed a HID of some sort.

David Lang
--

[ message continues ]

Maybe it waits for a firmware or something first.

	Xav


--

[ message continues ]

During enumeration it reports that it is a USB mass-storage-class 
device.  Look at Xavier's lsusb output in the original posting.

Alan Stern

--

[ message continues ]

If you have a friend with this device and windows, you might be able to
capture the initialization sequence using usbsnoopy or something similar.
Some devices just need a little proprietary poke before they become a normal
USB device.

-Bob
--

[ message continues ]

Well apparently vista expects the device to support running programs
written in .NET Micro Framework.  Maybe that is some JVM like thingy.  I
am not sure what Microsoft means by "Managed Code".  Since it seems to
be architecture independant I imagine it is similar to java byte code or
something similar.

Perhaps vista writes the firmware/OS to the mass storage device and they
talks to it after that.  Is there such a thing as a write only usb mass
storage device?

-- 
Len Sorensen
--

[ message continues ]

On Thu, Apr 3, 2008 at 5:24 PM, Lennart Sorensen

If it is supposed to implement the MS SideShow API, then that would be
the .NET VM (i.e. C#).  My 10 second googling turned up some info about
that but I couldn't find a definition of how the hardware interface
for such devices is supposed to work.  There's some XML-laden software
API but it seemed to be transport agnostic.

-Bob
--

[ message continues ]

Wouldn't there be at least 2 interfaces to the device ?

	Xav


--

[ message continues ]

Who knows, they could have a almost-mass-storage protocol layer that
recognizes proprietary stuff in the URBs.  It could be as simple as:

 - User clicks 'synchronize' in some windows app
 - Device driver on host does some magic to make Asus device pretend like
   removable media was inserted
 - Vista sees the new device, mounts it
 - App copies C# classes and XML files to special directories on the device
 - App ejects device

Does the screen turn on or is that software controlled too?

This is pure wild guessing since I have no clue about SideShow or this
device.  Anyway it would be hard to proceed without capturing a trace
or managing to find some docs somewhere.

-Bob
--

[ message continues ]

There's a power-on button, which lits the screen and makes the device

I certainly have no intention of installing vista on this host. I'll see
if I manage to borrow a windows laptop somewhere.

Thanks,
	Xav


--

[ message continues ]

You could also open the device up, snap a few pictures of it and start
googleing for chip datasheets.
Who knows what kind of fun chips might be hiding in there, Could be an
ARM for instance.

Regards,
Wander.
--

[ message continues ]