Divya,

The lines which i have typed should be typed thru ur hyperterminal when
android kernel boots . you can add these lines in init.rc file.  what Sean
suggested is for emulating ethernet over USB like RNDIS.  I have not tried
on windows.


intrc scriptloglevel 3
loglevel 3

# setup the global environment
    export PATH /sbin:/system/sbin:/system/bin:/system/xbin
    export LD_LIBRARY_PATH /system/lib
    export ANDROID_BOOTLOGO 1
    export ANDROID_ROOT /system
    export ANDROID_ASSETS /system/app
    export ANDROID_DATA /data
    export EXTERNAL_STORAGE /sdcard
    export BOOTCLASSPATH
/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar

# Backward compatibility
    symlink /system/etc /etc

# create mountpoints and mount tmpfs on sqlite_stmt_journals
    mkdir /sdcard 0000 system system
    mkdir /system
    mkdir /data 0771 system system
    mkdir /cache 0770 system cache
    mkdir /sqlite_stmt_journals 01777 root root
    mount tmpfs tmpfs /sqlite_stmt_journals size=4m

#    mount rootfs rootfs / ro remount

    write /proc/sys/kernel/panic_on_oops 1
    write /proc/sys/kernel/hung_task_timeout_secs 0
    write /proc/cpu/alignment 4
    write /proc/sys/kernel/sched_latency_ns 10000000
    write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000

# mount mtd partitions
    # Mount /system rw first to give the filesystem a chance to save a
checkpoint
#    mount yaffs2 m...@system /system
#    mount yaffs2 m...@system /system ro remount

    # We chown/chmod /data again so because mount is run as root + defaults
#    mount yaffs2 m...@userdata /data nosuid nodev
    chown system system /data
    chmod 0771 /data

    # Same reason as /data above
#    mount yaffs2 m...@cache /cache nosuid nodev
    chown system cache /cache
    chmod 0770 /cache

    # This may have been created by the recovery system with odd permissions
    chown system system /cache/recovery
    chmod 0770 /cache/recovery

# create basic filesystem structure
    mkdir /data/misc 01771 system misc
    mkdir /data/misc/hcid 0770 bluetooth bluetooth
    mkdir /data/local 0771 shell shell
    mkdir /data/local/tmp 0771 shell shell
    mkdir /data/data 0771 system system
    mkdir /data/app-private 0771 system system
    mkdir /data/app 0771 system system
    mkdir /data/property 0700 root root

    # create dalvik-cache and double-check the perms
    mkdir /data/dalvik-cache 0771 system system
    chown system system /data/dalvik-cache
    chmod 0771 /data/dalvik-cache

    # create the lost+found directories, so as to enforce our permissions
    mkdir /data/lost+found 0770
    mkdir /cache/lost+found 0770

    # double check the perms, in case lost+found already exists, and set
owner
    chown root root /data/lost+found
    chmod 0770 /data/lost+found
    chown root root /cache/lost+found
    chmod 0770 /cache/lost+found

on boot
# basic network init
    ifup lo
    hostname localhost
    domainname localdomain

# set RLIMIT_NICE to allow priorities from 19 to -20
    setrlimit 13 40 40

# Define the oom_adj values for the classes of processes that can be
# killed by the kernel.  These are used in ActivityManagerService.
    setprop ro.FOREGROUND_APP_ADJ 0
    setprop ro.VISIBLE_APP_ADJ 1
    setprop ro.SECONDARY_SERVER_ADJ 2
    setprop ro.HIDDEN_APP_MIN_ADJ 7
    setprop ro.CONTENT_PROVIDER_ADJ 14
    setprop ro.EMPTY_APP_ADJ 15

# Define the memory thresholds at which the above process classes will
# be killed.  These numbers are in pages (4k).
    setprop ro.FOREGROUND_APP_MEM 1536
    setprop ro.VISIBLE_APP_MEM 2048
    setprop ro.SECONDARY_SERVER_MEM 4096
    setprop ro.HIDDEN_APP_MEM 5120
    setprop ro.CONTENT_PROVIDER_MEM 5632
    setprop ro.EMPTY_APP_MEM 6144

# Write value must be consistent with the above properties.
    write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15

    write /proc/sys/vm/overcommit_memory 1
    write /sys/module/lowmemorykiller/parameters/minfree
1536,2048,4096,5120,5632,6144

    # Set init its forked children's oom_adj.
    write /proc/1/oom_adj -16

    # Permissions for System Server and daemons.
    chown radio system /sys/android_power/state
    chown radio system /sys/android_power/request_state
    chown radio system /sys/android_power/acquire_full_wake_lock
    chown radio system /sys/android_power/acquire_partial_wake_lock
    chown radio system /sys/android_power/release_wake_lock
    chown radio system /sys/power/state
    chown radio system /sys/power/wake_lock
    chown radio system /sys/power/wake_unlock
    chmod 0660 /sys/power/state
    chmod 0660 /sys/power/wake_lock
    chmod 0660 /sys/power/wake_unlock
    chown system system /sys/class/timed_output/vibrator/enable
    chown system system /sys/class/leds/keyboard-backlight/brightness
    chown system system /sys/class/leds/lcd-backlight/brightness
    chown system system /sys/class/leds/button-backlight/brightness
    chown system system /sys/class/leds/red/brightness
    chown system system /sys/class/leds/green/brightness
    chown system system /sys/class/leds/blue/brightness
    chown system system /sys/class/leds/red/device/grpfreq
    chown system system /sys/class/leds/red/device/grppwm
    chown system system /sys/class/leds/red/device/blink
    chown system system /sys/class/leds/red/brightness
    chown system system /sys/class/leds/green/brightness
    chown system system /sys/class/leds/blue/brightness
    chown system system /sys/class/leds/red/device/grpfreq
    chown system system /sys/class/leds/red/device/grppwm
    chown system system /sys/class/leds/red/device/blink
    chown system system /sys/class/timed_output/vibrator/enable
    chown system system /sys/module/sco/parameters/disable_esco
    chown system system /sys/kernel/ipv4/tcp_wmem_min
    chown system system /sys/kernel/ipv4/tcp_wmem_def
    chown system system /sys/kernel/ipv4/tcp_wmem_max
    chown system system /sys/kernel/ipv4/tcp_rmem_min
    chown system system /sys/kernel/ipv4/tcp_rmem_def
    chown system system /sys/kernel/ipv4/tcp_rmem_max
    chown root radio /proc/cmdline

# Define TCP buffer sizes for various networks
#   ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
    setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
    setprop net.tcp.buffersize.wifi    4095,87380,110208,4096,16384,110208
    setprop net.tcp.buffersize.umts    4094,87380,110208,4096,16384,110208
    setprop net.tcp.buffersize.edge    4093,26280,35040,4096,16384,35040
    setprop net.tcp.buffersize.gprs    4092,8760,11680,4096,8760,11680
    setprop net.dns1 192.168.1.1
    class_start default

## Daemon processes to be run by init.
##
service console /system/bin/sh
    console

# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
    disabled

# adbd on at boot in emulator
on property:ro.kernel.qemu=1
    start adbd

on property:persist.service.adb.enable=1
    start adbd

on property:persist.service.adb.enable=0
    stop adbd

service servicemanager /system/bin/servicemanager
    user system
    critical
    onrestart restart zygote
    onrestart restart media

service mountd /system/bin/mountd
    socket mountd stream 0660 root mount

service debuggerd /system/bin/debuggerd

service ril-daemon /system/bin/rild
    socket rild stream 660 root radio
    socket rild-debug stream 660 radio system
    user root
    group radio cache inet misc

service zygote /system/bin/app_process -Xzygote /system/bin --zygote
--start-system-server
    socket zygote stream 666
    onrestart write /sys/android_power/request_state wake
    onrestart write /sys/power/state on

service media /system/bin/mediaserver
    user media
    group system audio camera graphics inet net_bt net_bt_admin

service bootsound /system/bin/playmp3
    user media
    group audio
    oneshot

service dbus /system/bin/dbus-daemon --system --nofork
    socket dbus stream 660 bluetooth bluetooth
    user bluetooth
    group bluetooth net_bt_admin

#STOPSHIP: disable the verbose logging
service hcid /system/bin/logwrapper /system/bin/hcid -d -s -n -f
/etc/bluez/hcid.conf
    socket bluetooth stream 660 bluetooth bluetooth
    socket dbus_bluetooth stream 660 bluetooth bluetooth
    # init.rc does not yet support applying capabilities, so run as root and
    # let hcid drop uid to bluetooth with the right linux capabilities
    group bluetooth net_bt_admin misc
    disabled

service hfag /system/bin/sdptool add --channel=10 HFAG
    user bluetooth
    group bluetooth net_bt_admin
    disabled
    oneshot

service hsag /system/bin/sdptool add --channel=11 HSAG
    user bluetooth
    group bluetooth net_bt_admin
    disabled
    oneshot

service installd /system/bin/installd
    socket installd stream 600 system system

#service flash_recovery /system/bin/flash_image recovery
/system/recovery.img
#    oneshot

On Thu, Feb 5, 2009 at 8:25 AM, divya <[email protected]> wrote:

>
> Vishal,
>
>  I am able to ping to my board ..But the lines with is suggested by
> Sean and you is not present in my init.rc file.
>
>  Can you just share ur init.rc file.
>
> Actually my requirement is to use both the linux and windows system.
> Just trying with the windows system first.
>
> Do you use minicom as hyperterminal in linux.. or something else?
>
> Regards,
> Divya
>
> On Feb 5, 5:17 pm, vishal bhoj <[email protected]> wrote:
> > Divya,
> >
> > I am using a linux host machine, That ip is for network over USB (not
> sure
> > ).I din't modify my initrc file. I hope 3430sdp has a ethernet port . Can
> > you ping to ur board ? I mean is your network up ? if not try this
> >
> > setprop net.dns1 <primary-dns-server-ip>
> > $netcfg eth0 up
> > $netcfg eth0 dhcp
> >
> > After this try to ping and then follow Sean's procedure .
> >
> >
> >
> >
> >
> > On Thu, Feb 5, 2009 at 6:48 AM, divya <[email protected]> wrote:
> >
> > > Hi vishal,
> >
> > >  I am still having some problem with this.I checked my init.rc but
> > > the above line isnt present in it.And what is this ip "192.168.0.202
> > > ".
> >
> > > Can you share ur init.rc script file.
> >
> > > And this you are able to work on windows system....right?
> >
> > > Regards,
> > > Divya
> >
> > > On Jan 22, 10:47 am, vishal bhoj <[email protected]> wrote:
> > > > Thanks Sean,
> >
> > > > It works now :)
> >
> > > > On Thu, Jan 22, 2009 at 12:02 AM, Sean McNeil <[email protected]
> >
> > > wrote:
> >
> > > > > It is very simple:
> >
> > > > > First, make sure you have connectivity to the zoom. Ping the ip
> > > address.
> > > > > Next, type the command as follows (with appropriate changes):
> >
> > > > > ADBHOST=ip_address adb kill-server
> > > > > ADBHOST=ip_address adb shell
> >
> > > > > If using ethernet over usb, the zoom/OMAP USB gadget driver has an
> odd
> > > > > requirement. When you use ifconfig to setup the ip address on the
> zoom,
> > > > > you have to specify "up" on the ifconfig command. So in init.rc
> you'd
> > > > > have something like:
> >
> > > > > ## Configure the USB interface
> > > > > ##
> > > > > service usb-ether /system/bin/ifconfig usb0 192.168.0.202 up
> > > > >    oneshot
> >
> > > > > If you are using the ethernet port, then you'll have to set it up
> > > > > appropriately. Again, if you can ping you should be OK.
> >
> > > > > Cheers,
> > > > > Sean
> >
> > > > > vishal bhoj wrote:
> > > > > > Hi Divya ,
> >
> > > > > > Even I tried to connect through adb but I could not. When i do a
> adb
> > > > > > devices it doesn't list anything. The adbd demon is running on
> the
> > > > > > traget device . If you are able to connect on zoom please update
> me .
> >
> > > > > > thanks in advance
> >
> > > > > > On Wed, Jan 21, 2009 at 11:20 PM, Nimit Manglick
> > > > > > <[email protected] <mailto:[email protected]>> wrote:
> >
> > > > > >     Hi Divya,
> >
> > > > > >     No i haven't tried anything using adb..
> >
> > > > > >     Bye t way why r u looking for adb..?? After booting android
> >
> > > > > >     u will get the console itself na...
> >
> > > > > >     Anyways sorry no idea :(
> >
> > > > > >     Regards
> > > > > >     Nimit
> >
> > > > > >     On Wed, Jan 21, 2009 at 8:33 PM, divya <[email protected]
> > > > > >     <mailto:[email protected]>> wrote:
> >
> > > > > >         Hi Nimit,
> >
> > > > > >          Have you tried adb with ur OMAP Board.If yes can you
> update
> > > me.
> > > > > >         I am using a tcp ip connection using a windows host and
> OMAP
> > > > > >         3430 SDP.
> >
> > > > > >         Waiting for ur reply...
> >
> > > > > >         Regards,
> > > > > >         Divya
> >
> > > > > > --
> > > > > > with regards vishal
> >
> > > > --
> > > > with regards vishal- Hide quoted text -
> >
> > > > - Show quoted text -
> >
> > --
> > with regards vishal- Hide quoted text -
> >
> > - Show quoted text -
> >
>


-- 
with regards vishal

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to