Android

Forum Post: RE: Error when installing ADT Plugins on CCSv5

Manuel Contreras — Fri, 17 May 2013 22:56:00 GMT

Try to set the proxy value for both Eclipse and Android SDK. for Android SDK proxy setup run from a terminal /Android_sdk/tools/android and select the network tab, for eclipse select Window/preferences menu, follow General/Network Connections.

If you are not behind a proxy then I had similar issue when Installing Android ADT, I used to download the Android ADT zip file and install it directly to Eclipse using archive button when installing it. I just checked and

http://developer.android.com/sdk/installing/bundle.html

is not providing a zip file alone, it is a bundle but it is still there the previous link, check the trouble shoot section, it should help because it is not using network access to install Android ADT.

http://developer.android.com/sdk/installing/installing-adt.html#Troubleshooting

What version of Ubuntu 13.04 are you using? 64bits or 32bits?

Forum Post: RE: Android i2c drivers, where to start?

Andrew Miller1 — Fri, 17 May 2013 15:51:00 GMT

Hello greenja,

Thank you for your response, that link to another thread is very helpful. I am rather familiar with the protocol itself, its just the i2c subsystem that confuses me. I can't seem to find the right files to implement to make a driver.

In this forum (http://e2e.ti.com/support/interface/etc_interface/f/390/p/202938/729372.aspx#729372) they said that a particular i2c line is programmed in <kernel>/arch/arm/mach-omap2, and there appear to be 3 different i2c.h and .c files. Its not immediately obvious to me what structs i need to use and how I need to implement these. Can you help me at all or point me in a direction?

I appreciate your help. I'm a student and intern and I'm still trying to figure this stuff out.

cheers,

Andrew

Forum Post: RE: How to flash the ANDROID OS into NAND.

SANGILI KUMAR — Fri, 17 May 2013 10:48:00 GMT

Hello sir

I've changed the u-boot arg and cmd but still can't boot from NAND.

Here i've attached the log. surely yo can guess the problem from this log kindly check it.

(Please visit the site to view this file)

Forum Post: RE: am335 EVM Boot Problem

Richard Stewart82593 — Fri, 17 May 2013 08:21:00 GMT

Hi Pankaj,

I manually installed the SGX driver and I think this has worked, I now see from lsmod: omaplfb and pvrsrvkm

However boot still fails. Below is a paste of the debug output, and logcat. It seems to fail each time at

I/ethernet( 387): Loading ethernet jni class
E/JNIHelp ( 387): Native registration unable to find class 'com/android/server/Watchdog', aborting
F/libc ( 387): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

http://pastebin.com/964YpnMT

Many thanks

Richard

Forum Post: RE: where can i download the CCSV5_ADT_dependencies

Manuel Contreras — Thu, 16 May 2013 16:42:00 GMT

The link in Post was a mistake, maybe I moved/dragged the post button inside the post text and that caused the Post text.

By following the link number 788817 and considering it to be in this same forum, the correct link should be next one, and it is this same post.

http://e2e.ti.com/support/embedded/android/f/509/p/197149/788817.aspx

The information to follow from this post was in the link

http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_DeveloperGuide#Using_TI.27s_Code_Composer_Studio_V5_.28Eclipse_based.29

the error that was happening was that when installing CCSv5 it shows a window with some options to install CCSV5_ADT_dependencies, the procedure was to cancel this window to install it at this time and continue the CCSv5 installation, one time finished it was time to continue the instructions to install Android SDK.

Remember to check the Proxy values for both Eclipse and Android SDK, they are different locations.

Forum Post: RE: am335x porting problem

Vishveshwar Bhat — Thu, 16 May 2013 10:48:00 GMT

[quote user="chia te chu"]

We make a custom AM335x board , it reference AM335x EVM.

what difference between TI AM335x EVM and our custom AM335x board.

TI AM335x EVM custom AM335x board

ETH may be grmii MII

WIFI wl127x No wifi No BT NO CAN

other is same.

And We have run it in the custom board ,follow TI-Android-ICS-4.0.3-DevKit-3.0.1 DeveloperGuide.

download TI-Android-ICS-4.0.3_AM335x_3.0.1.bin,and make TARGET_PRODUCT=am335xevm OMAPES=2.x -j.

[/quote]

The am335xevm build product includes support for WLAN/BT in the kernel and filesystem build. Please ensure that these are modified/removed as per your device.

http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide can provide you some pointers.

Forum Post: WL1271: sdioDrv_InitHw() - request_irq FAILED

shangzhi zhu — Thu, 16 May 2013 02:56:00 GMT

Hi, everyone!

When enable wifi from android UI, I'm having this trouble;

TIWLAN: driver init
------------hPlatform_Wlan_Hardware_Init-omap3530
val = 0x1180118,read_pad = 0x1180118 // CONTROL_PADCONF_MMC2_CLK pad_config
val = 0x1180118,read_pad = 0x1180118   // CONTROL_PADCONF_MMC2_DAT0 pad_config
val = 0x1180118,read_pad = 0x1180118   // CONTROL_PADCONF_MMC2_DAT2 pad_config
val = 0x1040000,read_pad = 0x1040000   // CONTROL_PADCONF_MMC2_DAT4 pad_config for gpio_137 for WLAN_IRQ
val = 0x1180004,read_pad = 0x1180004   // CONTROL_PADCONF_MMC2_DAT6 pad_config for gpio_138 for WLAN_ENABLE
WLAN_ENABLE = 138
WLAN_IRQ = 137
TIWLAN: 101.725931: wlanDrvIf_Open()
TIWLAN: 101.798959: pInitParams->RoamingScanning_2_4G_enable 0
SDIO clock Configuration is now set to 24Mhz
sdioDrv_InitHw() - request_irq FAILED!!
TIWLAN: 102.082681: Try to SDBus Connect again...
SDIO clock Configuration is now set to 24Mhz
sdioDrv_InitHw() - request_irq FAILED!!
TIWLAN: 102.397684: Try to SDBus Connect again...
SDIO clock Configuration is now set to 24Mhz
sdioDrv_InitHw() - request_irq FAILED!!
TIWLAN: 102.710245: Try to SDBus Connect again...
SDIO clock Configuration is now set to 24Mhz
sdioDrv_InitHw() - request_irq FAILED!!
TIWLAN: 103.122507: Try to SDBus Connect again...
SDIO clock Configuration is now set to 24Mhz
sdioDrv_InitHw() - request_irq FAILED!!
TIWLAN: 103.534921: Try to SDBus Connect again...
SDIO clock Configuration is now set to 24Mhz
sdioDrv_InitHw() - request_irq FAILED!!
TIWLAN: 103.947488: Try to SDBus Connect again...
SDIO clock Configuration is now set to 24Mhz
sdioDrv_InitHw() - request_irq FAILED!!
TIWLAN: 104.360055: Try to SDBus Connect again...
SDIO clock Configuration is now set to 24Mhz
sdioDrv_InitHw() - request_irq FAILED!!
TIWLAN: 104.772836: SDBus Connect Failed, Set Object Event !!

----------------------------------------------------------------------------------------

What I had done was following this porting guide:

http://processors.wiki.ti.com/index.php/Android_wireless_build_and_porting_guide#Porting_guide

kernel version: 2.6.32

android version: 2.3

CPU: AM3715

and the debug as following:

Linux version 2.6.32 (root@zhusz) (gcc version 4.4.3 (GCC) ) #1 Wed May 15 19:21:12 CST 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 DEVKIT8500/SED_MT2 Board
Memory policy: ECC disabled, Data cache writeback
OMAP3630/DM3730 ES1.0 (l2cache iva sgx neon isp 192mhz_clk )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 8388608 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: console=ttyS2,115200n8 androidboot.console=ttyS2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=1000 omapfb.rotate=3 omapfb.rotate_type=1 vram=8M omapfb.vram=0:8M
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 246016KB available (4360K code, 829K data, 160K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:402
$$$$$$$$$$$$$$omap2_clk_init
$$$$$$$$$$$$$$ cpu_is_omap34xx
$$$$$$$$$$$$$$ cpu_is_omap3630
Clocking rate (Crystal/Core/MPU): 26.0/200/600 MHz
Reprogramming SDRC clock to 200000000 Hz
dpll3_m2_clk rate change failed: -22
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
------------ads7846_dev_init: OMAP3_DEVKIT8500_TS_GPIO = 27
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 473.71 BogoMIPS (lpj=1851392)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16

Found NAND on CS0
Registering NAND on CS0
Target VDD1 OPP = 4, VDD2 OPP = 2
OMAP DMA hardware revision 5.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev4.0 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VPLL2: 1800 mV normal standby
regulator: VMMC2: 1850 <--> 3150 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz
i2c_omap i2c_omap.3: bus 3 rev4.0 at 100 kHz
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
omap-iommu omap-iommu.0: isp registered
NetWinder Floating Point Emulator V0.97 (double precision)
ashmem: initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 480
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2

Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0xad, Chip ID: 0xbc (Hynix NAND 512MiB 1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand":
0x000000000000-0x000000080000 : "X-Loader"
0x000000080000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x000000a80000 : "Kernel"
0x000000a80000-0x000020000000 : "File System"
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V1.0
dm9000 Ethernet Driver, V1.31
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver cdc_eem
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver gl620a
usbcore: registered new interface driver net1080
usbcore: registered new interface driver plusb
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver MOSCHIP usb-ethernet driver
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
android init
android_probe pdata: c04a36bc
android_bind
android_usb gadget: android_usb ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
f_adb init
android_register_function adb
f_mass_storage init
android_register_function usb_mass_storage
adb_bind_config
mass_storage_bind_config
android_usb gadget: Number of LUNs=1
mice: PS/2 mouse device common for all mice
gpio-keys gpio-keys: failed to request GPIO 29, error -16
gpio-keys: probe of gpio-keys failed with error -16
input: TWL4030 Keypad as /devices/platform/i2c_omap.1/i2c-1/1-004a/twl4030_keypad/input/input0
ads7846 spi2.0: touchscreen, irq 187
ads7846 spi2.0: ads7846_read12_ser return 417
input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.2/spi2.0/input/input1
using rtc device, twl_rtc, for alarms
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
omap-iommu omap-iommu.0: isp: version 1.1
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Registered led device: sys_led
Registered led device: user_ledb
Registered led device: user_led1
Registered led device: user_led2
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
Advanced Linux Sound Architecture Driver Version 1.0.21.
No device for DAI omap-mcbsp-dai-0
No device for DAI omap-mcbsp-dai-1
No device for DAI omap-mcbsp-dai-2
No device for DAI omap-mcbsp-dai-3
No device for DAI omap-mcbsp-dai-4
OMAP3 Devkit8500 SoC init
asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
ALSA device list:
#0: omap3devkit8500 (twl4030)
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Power Management for TI OMAP3.
Unable to set L3 frequency (400000000)
Switched to new clocking rate (Crystal/Core/MPU): 26.0/200/1000 MHz
IVA2 clocking rate: 800 MHz
SmartReflex driver initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
Console: switching to colour frame buffer device 30x40

regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:53:38 UTC (946688018)
omapdss DPI error: display already enabled
omap_vout omap_vout: 'lcd' Display already enabled
omapdss DPI error: display already enabled
omap_vout omap_vout: 'lcd' Display already enabled
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 0
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 1
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SD card at address e624
mmcblk0: mmc0:e624 SU02G 1.84 GiB
mmcblk0: p1 p2 p3
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 160K
Warning: unable to open an initial console.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
# enabling adb
adb_open
warning: `zygote' uses 32-bit capabilities (legacy support in use)
request_suspend_state: wakeup (3->0) at 13750793460 (2000-01-01 00:53:48.988555908 UTC)

could anyone give me some advise?

Thanks advanced!

Forum Post: RE: how to make android usb-modeswitch tools

Fabio Fumi — Tue, 14 May 2013 15:39:00 GMT

Hi, thanks for answering.

the following is waht I get from the radio log, as soon as I power the 3G module up. It's not easy for me to understand what's going wrong... For example, what is the repeated "ATE0Q0V1" command about? Could you help please? Thanks.

I/RIL     (   79): Setting speed
D/RILC    (   79): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED  {RADIO_OFF}
D/AT      (   79): AT> ATE0Q0V1
D/RILJ    (  384): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED RADIO_OFF
D/RILB    (  384): Notifying: radio available
D/RILJ    (  384): [0006]> SCREEN_STATE: true
D/RILJ    (  384): [0007]> RADIO_POWER on
D/GSM     (  384): [GsmSST] Poll ServiceState done:  oldSS=[1 home null null null  Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[3 home null null null  Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldGprs=1 newData=1 oldMaxDataCalls=1 mNewMaxDataCalls=1 oldReasonDataDenied=-1 mNewReasonDataDenied=-1 oldType=Unknown newType=Unknown
D/GSM     (  384): [GsmSST] operatorNumeric is null
D/GSM     (  384): [GsmDCT] handleMessage msg={ what=270337 when=-8ms obj=android.os.AsyncResult@41096e68 }
D/GSM     (  384): [GsmDCT] onRadioAvailable
D/GSM     (  384): [GsmDCT] overall state is IDLE
D/RILJ    (  384): [0008]> BASEBAND_VERSION
D/RILJ    (  384): [0009]> GET_IMEI
D/RILJ    (  384): [0010]> GET_IMEISV
D/AT      (   79): AT> ATE0Q0V1
D/AT      (   79): AT> ATE0Q0V1
D/AT      (   79): AT> ATE0Q0V1
D/AT      (   79): AT> ATE0Q0V1
D/AT      (   79): AT> ATE0Q0V1
D/AT      (   79): AT> ATE0Q0V1
D/AT      (   79): AT> ATE0Q0V1
D/AT      (   79): AT> ATE0Q0V1

Forum Post: RE: AM3715/Android 2.3.4 display problem

shangzhi zhu — Tue, 14 May 2013 11:11:00 GMT

It was the DSS interface CONTROL_PADCONF problem.

Forum Post: RE: omap3 (powerSGX 530 ) Android (4.x) Hwcomposer support

mike soso — Tue, 14 May 2013 09:55:00 GMT

Hi Aditya,

Thank you for this clear explanation.

Regards,

Mike

Forum Post: Android JellyBean am37x on NFS Trouble

mike soso — Tue, 14 May 2013 09:39:00 GMT

Hi all,

My case :
1) SDCard with 3 partitions (Boot/rootfs/data) my device boots like a charm and apps like gallery are functionnal.
2) I change bootargs to boot on NFS (with the same tarball untar the same way for the rootfs SDcard partition & NFS) to boot on the rootfs on my host and not on my sdcard. In /mnt/sdcard i can see the data partition and the vold.fstab is unchanged.
(dev_mount sdcard /mnt/sdcard 3 /devices/platform/mmci-omap-

hs.0/mmc_host/mmc0)

In case 1) all apps work fine and 2) system works finebut apps (like gallery or file manager) have permission error...

Can somebody put me in the way to solve this (if it cans be solved) ?

What is the good way to have the same behavior when booting the rootfs on NFS and SDcard ?

With rowboat-ics rootfs i don't have this behavior (on NFS all work fine)

Mike

Forum Post: RE: Data corruptions problem in AM3505/17 Android system

Pekon Gupta — Tue, 14 May 2013 09:04:00 GMT

Yakir,

[quote user="Yakir Matusovsky"]

I am using linux 2.6.37 with minimal ecc mode adjustment changes. Debugging the decode_bch method showed many errors found, some of them fixed (<=4) and some not. I saw the fact of correcting the errors was actually damaging the system even more (means, these are not real errors probably). I reckon the kernel isn't using the gpmc to correctly write stuff to the system or altenatively the nand disk (inside nand_base.c) is doing something wrong whereas the ubifs is using it to access memory pages.

[/quote]

I'm not much knowledgeable about AM35x, so can't help you with the details. But what it seems is there is mis-match in way ECC is used in U-boot and kernel

(1) either ECC scheme is different BCH4_SW and BCH4_HW

(2) Or the way ECC algorithm is implemented.

I would suggest to look for following:

(1) ECC layout is same in both kernel and U-boot. (by seeing at OOB area dump)

(2) ecc.calculate is implemented in similar way in both U-boot and kernel. (by reviewing the code).

(3) GPMC registers are used in ecc.calculate in both U-boot and kernel.

Above pointers may help you to dig more deeper.

And we too recommend using BCH8 over BCH4, but for that you need to upgrade to latest kernel and u-boot present on

http://arago-project.org/git/projects/linux-omap3.git

with regards, pekon

Forum Post: Flashing generated Android Image into AM335xEVM

Hafedh Haouala — Tue, 14 May 2013 08:59:00 GMT

Hi,

I've followed these steps in order to generate an Android Image for the AM335x EVM http://processors.wiki.ti.com/index.php/TI-Android-ICS-4.0.3-DevKit-3.0.1_DevelopersGuide, however, I couldn't find any useful link for flashing this Image into the EVM.

All the links I've checked wheither required windows and I'm working on Ubuntu, or required some files like boot.scr and ubi.img that I couldn't find in my

AM335x EVM environment nor in the generated Image, and other talking about MTD utilities etc..

I'm really lost in the documentation and I'll appreciate your guidance.

Thanks in advance.

B.R

Forum Post: RE: Source code for galloc.omap3.so

febin george — Tue, 14 May 2013 08:57:00 GMT

Hi Aditya,

Any update on this? Please share your thoughts.

Regards,

Febin

Forum Post: RE: AM335x EVM and Network Devloppement Kit (NDK)

Pankaj Bharadiya — Mon, 13 May 2013 10:46:00 GMT

HI,

You shold be able to use poll API. Please have a look at "system/core/toolbox/getevent.c" as a reference for poll api usage.

Thanks and Regards,

Pankaj Bharadiya

Forum Post: RE: JellyBean support for AM3715?

Pankaj Bharadiya — Mon, 13 May 2013 05:53:00 GMT

HI SI,

There is no plan to to release Android JellyBean 4.2.2 on AM37x platform.

JellyBean 4.1.2 for AM37x is not officially released. It is available on rowboat. You can refer to below link for getting sources

http://processors.wiki.ti.com/index.php/TI-Android-JB-4.1.2-DevKit-4.0.0_DeveloperGuide#Getting_Source_.26_Toolchain

Thanks and Regards,

Pankaj Bharadiya

Forum Post: Enable ethernet support for Java framework services on rowboat Android JellyBean 4.1.2

Massimo Bifaro — Sun, 12 May 2013 13:09:00 GMT

Hi to all,

I' ve a BeagleBone on which I've installed Android Jelly Bean 4.1.2.

I'm trying SIP application demo from android samples. When I debug the application I get the error "No Data connection" also if the beaglebone has an ethernet connection.

From http://elinux.org/images/9/98/Dive_Into_Android_Networking-_Adding_Ethernet_Connectivity.pdf I' ve read :

Java framework services and apps rely on ConnectivityManager and have no clue what Ethernet route/connection actually means.
Except for some apps (e.g. Browser, which relies on native implementation).

I've tried to apply the patch, but at compiling time I get some error on EthernetNative.java, EthernetStateMachine and so on.

Where can I get a patch for rowbat jelly bean 4.1.2 in order to adding ethernet support at framework level?

Thanks in advance.

Forum Post: RE: Suspend problem in custom AM3359 board with Android 4.0.3

Leonardo Prates — Fri, 10 May 2013 21:14:00 GMT

The problem occur inside of omap_i2c_isr, most specifically in this line of i2c-omap.c:

if (stat & (OMAP_I2C_STAT_RRDY | OMAP_I2C_STAT_RDR)) {
           u8 num_bytes = 1;
           if (dev->errata & I2C_OMAP_ERRATA_I207)
               i2c_omap_errata_i207(dev, stat);
           if (dev->fifo_size) {
               if (stat & OMAP_I2C_STAT_RRDY)
                   num_bytes = dev->fifo_size;
               else    /* read RXSTAT on RDR interrupt */
                   num_bytes = (omap_i2c_read_reg(dev,
                           OMAP_I2C_BUFSTAT_REG)
                           >> 8) & 0x3F;
           }
           while (num_bytes) {
               num_bytes--;
               w = omap_i2c_read_reg(dev, OMAP_I2C_DATA_REG);
               if (dev->buf_len) {
                   *dev->buf++ = w;
                   dev->buf_len--;

.....

Just before the crash to occur dev->buf points to address 0x0004 that crash the system when the code try to write in that address. I have seen that dev->buf gets that address 0x0004 from omap_i2c_xfer_msg function. The i2c address of device at this point is 0x2D (PMIC general purpose control). Please, can anyone help me with this issue?

Forum Post: RE: Beaglebone LCD3 Cape Rev.A patch for android

SANGILI KUMAR — Fri, 10 May 2013 12:12:00 GMT

Hello Vishveshwar

I've another question when i try to connect my device via adb its showing 0123456789ABCDE. i need to change according to my customer name. how can i change it and also i need to change root@android # also

Thanks

Forum Post: RE: something wrong with Resolution or not

shangzhi zhu — Fri, 10 May 2013 02:27:00 GMT

[quote user="Jianhua Zhao"]

Hi, Vaibhav and everyone posted here.

The LCD issue is OK now----it caused by hardware link.Thank you!

By the way, Vaibhav. when I used gcc compiled the saFbdevDisplay.c as follow :

gcc -o saFbdevDisplay.o saFbdevDisplay.c

and then I copied saFbdevDisplay.o to SD, after android booted up, I execute saFbdevDisplay.o with shell by Tera Term as follow :

/mnt/sdcard
./saFbdevDisplay.o

I was reminded of "./saFbdevDisplay.o: permission denied", so the question is how can I get root privileges in Android?

Thank you!

[/quote]

你好！我遇到和你一样的问题，一直没有解决。

你这里说的是因为hardware link问题，能不能说具体一点，谢谢！