adb device problem

by Ramy » Wed, 25 Feb 2009 04:59:35 GMT


Sponsored Links
 Hi all,

I am very new to the android env. please bear with me if my question
is too fundamental.

I am using a peripheral driver with no host support for USB.
I am trying to use the adb driver to transfer a file. The adb driver
is compiled fine and two device are created in the kernel. android_adb
and android_adb_enable.
I understand that the android_adb_enable device must always be enabled
to use the android_adb device. I try to copy a file to device /dev/
android_adb using cp command.

cp ***.txt /dev/android_adb

but when i try to read the same using the cat command i get

rx c1cf4fa0 queue
rx c1cf4f60 queue
rx c1cf4f20 queue
rx c1cf4ee0 queue

and waits....

why am i not able to see the output using the cat command ? what is it
wiating for ??


Thanks in advance
Regards,
Ramalk






--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



adb device problem

by Mike Lockwood » Wed, 25 Feb 2009 15:23:40 GMT


 

Hi Ramy,

You can't just write arbitrary data to /dev/android_adb and expect it
show up on the host side.  adb (on the host) and adbd (on the device)
communicate with each other via a structured protocol.  The
/dev/android_adb driver file is intended to be used only by the adbd
daemon.  You can't write to it yourself unless you send data using the
adb protocol.

-- 
Mike Lockwood
Google android team

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


adb device problem

by Ramy » Thu, 26 Feb 2009 01:32:33 GMT


 You mean to say that the controller driver provided for msm 7200 will
only work with adb protocol. can it be changed or customized to meet
any specific protocol.






--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



adb device problem

by Mike Lockwood » Thu, 26 Feb 2009 13:08:22 GMT


 The adb kernel driver actually could support another protocol.  The
only limitation is that there is a maximum 4096 byte packet size.  Of
course you would need to write your own program on the PC that
understands the data you are sending from the device.  And you could
not use adb at all if you hijack the adb driver for another purpose.

You could use the adb sources as a starting point for whatever it is
you are trying to do.  But it sounds like it would be a non-trivial
effort and I don't think anyone on this mailing list will be able to
help you with it.

Mike









-- 
Mike Lockwood
Google android team

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



adb device problem

by Ramy » Fri, 06 Mar 2009 03:29:33 GMT


 can any one tell me why the below is coming .. I am trying to read
from the adb device (/dev/android-adb)

rx c1cf4f60 queue
rx c1cf4f20 queue
rx c1cf4ee0 queue
rx c1cf4ea0 queue

It keeps on waiting ...

and when i do cntrl +c i get

adb_read returning -512

Thanks for the help.









--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. does any one knows what is the difference between Surface Flinger and V4l2

HI Dave


Can you explain the difference between Surface Flinger and V4l2
driver, and in what usecases SurfaceFlinger will be useful and what
cases V4l2 useful.

Thanks
Sam
--~--~---------~--~----~------------~-------~--~----~

2. ADT0.9 plugin can't work

I have built a ADT0.9 plugin with the android release of 20090102,but
seems it still have error in recognizing resource files.
Does anyone have succeeded in using the 0.9 plugin?
--~--~---------~--~----~------------~-------~--~----~

3. keypad and Touchscreen Not working on IMX31 with Android SDK1.0

4. Google Earth Lite .. in android .

5. requestFocus failed

6. Optus to sell Google phone in Australia from Feb 16, 2009 - Please bump support for paid apps in the Android Market for the Asia Pacific region

7. How to call callActivityOnRestoreInstanceState of Instrumentation