regarding ANALOGICS GPRS MODEM interface with BeagleBoard

by gayatri devi » Fri, 04 Jun 2010 15:37:05 GMT

Sponsored Links
 Hi all, I Gayatri we are using BeagleBoard REV C3 Board. We ported
ANDROID Operating Systems on BeagleBoard. In ANDROID there is no
access for serial port to interface ANALOGICS GPRS MODEM to the
BeagleBoard. Instead of using serial port I used USB-Serial converter
(pl2303) by using that i interfaced the Modem still Modem is not
responding. PLZ help me in interfacing plz tell me your valuable


regarding ANALOGICS GPRS MODEM interface with BeagleBoard

by ms12 » Mon, 07 Jun 2010 21:33:59 GMT

 Which port does the converter show up on?  Typically something like /
dev/ttyUSB0.  Then put something like this in the init.rc

service ril-daemon /system/bin/rild -l /system/lib/
-- -d {your serial port}
    socket rild stream 660 root radio
    socket rild-debug stream 660 radio system
    user root
    group radio cache inet misc

In my case, {your serial port} was /dev/ttyUSB1.



Sponsored Links

Other Threads

1. Problem with INTERNET permission


I'm making socket connection to my localhost i.e. http://localhost/fetch.php
is the URL.
Now I have added in permission for internet in manifest. Still it
Connection refused to http://localhost

I even tried  Still it gives the same error.

I'm using emulator; not android device.

Please help me out, as I'm not able to continue to my app development.


2. Background apps (Instant Messaging) being killed without user notification

Hello everyone!

Aftera few months of living with the problem, I'd like to try to
understand what's going on here. In the mean time, I've switched to
the HTC Desire, and even though I constantly have 200MB+ of RAM free,
IM apps are still crashing and burning in the background, with the
exact same symptons (except for the low memory warnings - haven't
spotted any of those on the Desire yet). Guess it's not just a lack of
free memory?

I have, in the mean time, discovered an app that manages to work
around the problem by restarting itself each time it's closed: IM+
2.x. However, the developers seem to have removed this feature in
their latest release, 3.0.11, which exhibits the same symptoms as all
the other apps. The new Nimbuzz 2.x release also displays the same
unfortunate behaviour.

Is it really possible that the devs of _all_ these applications are
doing something wrong? Is there no possibility that there is an error
of some sort in the frameworks and APIs used for building background

How can I gather more information about this problem? I'd love to see
it solved, as the only functioning messaging program (IM+ 2.x) has
other problems of its own and lacks support for Skype.

Thanks everyone!


3. Why i cann't login my account of android market?

4. Android - Large Application size (Memory) issue

5. Is there a way to request permissions from auser as you need them?

6. stretch_copybit::run_render fail causing noticeable pauses in my display

7. Bes resource to get started with Android development.