ANDROID PORTING TO IMX233

PatelBlog — Thu, 02 Dec 2010 05:37:17 GMT

hi everybody

I am very new to porting, this is my first porting i am doing, please forgive me for any silly questions or opinions.

I am trying to port android on to IMX233, i am using ltib to build the kernel,i am using U-boot as boot loader, the bootargs that i am passing while building the kernel are as below:

" console=ttyAM0,115200 init=/init root=/dev/mmcblk0p2 rw rootwait lcd_panel=lms430 ssp1=mmc "

i am burning the imx233_linux.sb image on to sdcard first partiotion which is of "OnTrack DM6 Aux3" format.

i am copying the "root" file system in to second partition of ty ext3.

after booting the board i am getting kernel panic. the log is like this .....

\0xffDec 2 201010:27:19
EVK board
EMI_CTRL 0x1C084040
FRAC 0x92926192
init_ddr_mt46v32m16_133Mhz
power 0x00820710
Frac 0x92926192
start change cpu freq
hbus 0x00000003
cpu 0x00010001
Uncompressing Linux...................................................................................................................................................... done, booting the kernel.
Linux version 2.6.31-203-gee1fdae (naveen@naveen-laptop) (gcc version 4.1.2) #1 PREEMPT Thu Dec 2 10:25:49 IST 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: STMP378X
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: -e console=ttyAM0,115200 init=/init root=/dev/mmcblk0p2 rw rootwait lcd_panel=lms430 ssp1=mmc
PID hash table entries: 512 (order: 9, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 125016KB available (4232K code, 295K data, 116K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:224
Console: colour dummy device 80x30
console [ttyAM0] enabled
Calibrating delay loop... 200.29 BogoMIPS (lpj=1001472)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
regulator: vddd: 800 <--> 1575 mV fast normal
regulator: vddd_bo: 800 <--> 1575 mV fast normal
regulator: vdda: 1500 <--> 2275 mV fast normal
regulator: vddio: 2800 <--> 3575 mV fast normal
regulator: overall_current: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-keyboard-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx_ts-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-appuart-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-dbguart-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx_wdt-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-rtc-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-fb-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-bl-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-rotdec-1: 0 <--> 2147483 mA fast normal
regulator: i2c_stmp3xxx-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-persistent-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-dcpboot-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-dcp-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-battery-1: 0 <--> 2147483 mA fast normal
regulator: stmp3xxx-pxp-1: 0 <--> 2147483 mA fast normal
regulator: mmc_ssp-1: 0 <--> 2147483 mA fast normal
regulator: mmc_ssp-2: 0 <--> 2147483 mA fast normal
regulator: charger-1: 0 <--> 2147483 mA fast normal
regulator: power-test-1: 0 <--> 2147483 mA fast normal
regulator: cpufreq-1: 0 <--> 2147483 mA fast normal
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
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
usb: DR gadget (utmi) registered
JFFS2 version 2.2. (NAND) \0xc2\0xa9 2001-2006 Red Hat, Inc.
msgmni has been set to 244
alg: No test for stdrng (krng)
cryptodev: driver loaded.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Console: switching to colour frame buffer device 60x34
stmp3xxx-dbguart: ttyAM0 at MMIO 0x80070000 (irq = 0) is a Debug UART
stmp3xxx-appuart.0: ttySP0 at MMIO 0x8006c000 (irq = 24) is a stmp3xxx-appuart.0
Found APPUART 3.0.0
loop: module loaded
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 11, io base 0x80080000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver usblp
usbcore: registered new interface driver cdc_wdm
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
mice: PS/2 mouse device common for all mice
input: stmp3xxx-keyboard as /class/input/input0
input: STMP3XXX touchscreen as /class/input/input1
input: stmp3xxx-rotdec as /class/input/input2
STMP3xxx RTC driver v1.0 hardware v2.0.0
stmp3xxx-rtc stmp3xxx-rtc: rtc core: registered stmp3xxx-rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
stmp3xxx-pxp stmp3xxx-pxp: initialized
IRQ 3/stmp3xxx-battery: IRQF_DISABLED is not guaranteed on shared IRQs
stmp3xxx-battery stmp3xxx-battery.0: 5v disconnection handled
stmp3xxx watchdog: initialized, heartbeat 19 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
Bluetooth: Broadcom Blutonium firmware driver ver 1.2
usbcore: registered new interface driver bcm203x
Bluetooth: Digianswer Bluetooth USB driver ver 0.10
usbcore: registered new interface driver bpa10x
Bluetooth: BlueFRITZ! USB driver ver 1.2
usbcore: registered new interface driver bfusb
Bluetooth: Generic Bluetooth USB driver ver 0.5
usbcore: registered new interface driver btusb
stmp3xxx-dcp stmp3xxx-dcp: DCP crypto enabled.!
Advanced Linux Sound Architecture Driver Version 1.0.20.
stmp378x-audio stmp378x-audio: STMP378X ADC/DAC Audio Codec 0.1
No device for DAI stmp378x adc/dac
stmp3xxx-spdif stmp3xxx-spdif: STMP3XXX SPDIF Audio Transmitter 0.1
No device for codec stmp3xxx spdif
No device for DAI stmp3xxx spdif
No device for DAI stmp3xxx adc/dac
No device for DAI stmp3xxx spdif
asoc: stmp378x adc/dac <-> stmp3xxx adc/dac mapping ok
asoc: stmp3xxx spdif <-> stmp3xxx spdif mapping ok
stmp3xxx_request_pin: CONFLICT DETECTED pin 2:7 caller spdif owner stmp3xxx-rotdec
ALSA device list:
#0: STMP3780 Devb (stmp378x adc/dac)
#1: STMP3780 Devb (stmp3xxx spdif)
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.13
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SU04G 3.69 GiB
mmcblk0:
stmp3xxx-rtc stmp3xxx-rtc: setting system clock to 1970-01-01 00:00:26 UTC (26)
p1 p2 p3
kjournald starting. Commit interval 5 seconds
EXT3 FS on mmcblk0p2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with writeback data mode.
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 116K
Warning: unable to open an initial console.
Kernel panic - not syncing: Attempted to kill init!

i am stuck in this error for two days please get me out of this

thanks in advance
S N Naveen patel

Re: ANDROID PORTING TO IMX233

munna — Thu, 02 Dec 2010 14:50:57 GMT

even me too searching for that patel

Re: ANDROID PORTING TO IMX233

Alexey_ng — Mon, 24 Jan 2011 15:26:47 GMT

Hi,

Your kernel not have a "ashmem" driver module. Ashmem is a new android shared memory allocator.

"init" attempts to use this allocator and fails (kernel panic).

Make sure that option CONFIG_ASHMEM is enabled when you build the kernel.

WBR,

Alex-y

Re: ANDROID PORTING TO IMX233

PatelBlog — Mon, 24 Jan 2011 16:28:58 GMT

Thanks Alex

Alexey said:

Hi,
Your kernel not have a "ashmem" driver module. Ashmem is a new android shared memory allocator.
"init" attempts to use this allocator and fails (kernel panic).
Make sure that option CONFIG_ASHMEM is enabled when you build the kernel.
WBR,
Alex-y

Re: ANDROID PORTING TO IMX233

swetha1z — Mon, 31 Jan 2011 07:03:58 GMT

how to apply android patches to imx233 bsp and how to get it? or the filesystem of android, will it directly work with the existing ltib image.

Re: ANDROID PORTING TO IMX233

bharathi_onchip — Tue, 01 May 2012 05:34:25 GMT

Hi Naveen patel,

I am also started "porting android on i.mx233".

I didn't got any BSP for this.

Can you help me in how to do this?

Like, from where to get android BSP for i.mx233 ?

How to build them ?

As of now I took Freescale i.mx233 Linux BSP and trying to build with android tool chain.

I am not sure it is correct or not?

Thanks in advance.

Regards,

Bharathi.

i.MX ProcessorsのトピックRe: ANDROID PORTING TO IMX233

ANDROID PORTING TO IMX233

Re: ANDROID PORTING TO IMX233

Re: ANDROID PORTING TO IMX233

Re: ANDROID PORTING TO IMX233

Re: ANDROID PORTING TO IMX233

Re: ANDROID PORTING TO IMX233