Omap4430 ES1.0 boot init error

[Oblivious]

Hi to all,

I tried to boot Omap4430 ES1.0 from SD card ( kernel +file system).
I used the Android pre-built binary L27RC0.

I partitioned the SD and copy the binary in according to the guide:
http://omappedia.org/wiki/Android_SD_Configuration

The boot parameter from minicom are:
setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw
rootdelay=2 mem=463M init=/init
setenv bootcmd 'mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm
0x80000000'
boot


After the loading of image ... i have the following error:
Warning: unable to open an initial console.
Failed to execute /init. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init= option
to kernel.
CPU0: stopping
Backtrace:
[<c003d648>] (dump_backtrace+0x0/0x110) from [<c03c0fec>] (dump_stack
+0x18/0x1c)
r7:c17a4040 r6:00000010 r5:00000010 r4:ffffffff

everybody can hel me ?
Android pre-built binary L27RC0 i s the only release for Omap4430
ES1.0 ?
which are the correct setting S2(1:8) for Omap4430 in order to have SD
card boot ?

Thanks.

[Deva R]

bootargs are incomplete, but setenv command looks good.

can u share complete kernel bootlog?

somehow "init=/init" set during setenv in uboot is not effective.. probably newline character as shared here?

ps.

you will get immediate response for omap release queries at http://groups.google.com/group/omapdiscuss

-- 

Regards,

Deva

www.bittoggler.com

--
unsubscribe: android-porti...@googlegroups.com
website: http://groups.google.com/group/android-porting

[Deva R]

Can you share kernel bootlog? 

we can crosscheck if kernel command line is passed properly, for eg. see "Kernel command line" in below log..

Uncompressing Linux... done, booting the kernel.

Linux version 2.6.35-00158-g3957b62 (deva@deva-ubunt) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #50 SMP PREEMPT Wed Nov 10 22:26:15 IST 2010

CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7), cr=10c53c7f

CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

Machine: OMAP4430 4430SDP board

Memory policy: ECC disabled, Data cache writealloc

PERCPU: Embedded 7 pages/cpu @c18da000 s5504 r8192 d14976 u65536

pcpu-alloc: s5504 r8192 d14976 u65536 alloc=16*4096

pcpu-alloc: [0] 0 [0] 1

Kernel command line: console=ttyO2,115200n8 mem=458M@0x80000000 mem=512M@0xA0000000 root=/dev/mmcblk1p2 rw rootdelay=2 init=/init vram="10M" omapfb.vram="0:4M"

PID hash table entries: 4096 (order: 2, 16384 bytes)

Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

...

On Tue, Nov 9, 2010 at 1:40 PM, Md Oblivious <md.obl...@gmail.com> wrote:

Deva,
thanks for the reply
here below  complete bootargs:

setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem=463M init=/init
setenv bootcmd 'mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
boot

Please let me know.

Thanhs and Regards,
Oblivious

2010/11/8 Deva R <r.de...@gmail.com>

--

Regards,

Deva

www.bittoggler.com

[Md Oblivious]

Deva,
thanks for the reply
here below  complete bootargs:

setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem=463M init=/init
setenv bootcmd 'mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
boot

Please let me know.

Thanhs and Regards,
Oblivious

2010/11/8 Deva R <r.de...@gmail.com>

[Md Oblivious]

Hi

let me explain better:

I'm working on boot by sdcard,
so when i use sdcard I'm able to perform the boot,
whilst when I use a esternal emmc used as sdcard (with sdcard adapter) I have the problem showed below and I not able to perform the boot.
Of course the partition and the software are the same for sdcard and emmc.

Many thanks
Oblivious

2010/11/10 Deva R <r.de...@gmail.com>

Hi,

sorry, i occasionally check this personal inbox - you can mail to omapdiscuss googlegroups -> to get immediate response from multiple teams.,

>If I better understood  pre-build  L27.4 RC0 not work well with eMMC booting 
>could you suggest me the right release and configuration? 

L27.5.1 is the first release with eMMC boot supported -> prebuild binaries will have emmc boot support readily.

http://omappedia.org/wiki/L27.INC1.5.1_Froyo_ES2_Release_Notes

>I'm using pre-build RLS25.inc2.5 but I don't have problem with sd card
>whilst with eMMc I have the following error:
>                  VFS: Unable to mount root fs via NFS, trying floppy.
>                  VFS: Cannot open root device "mmcblk0p2" or unknown-block(2,0)

did u meant Nand boot?? can you cross check the bootargs (we dont specify root for nand boot)?

nand bootargs for l25x link - http://git.omapzoom.org/?p=device/ti/zoom2.git;a=blob;f=env.txt;hb=froyo

bootdelay 5
bootargs androidboot.console=ttyO3 console=ttyO3,115200n8 rootdelay=1 init=/init omap_vout_mod.video1_numbuffers=6 omap_vout_mod.vid1_static_vrfb_alloc=y omapfb.vram=0:4M
bootcmd nand unlock; nand read.i 81c00000 ${kernel_nand_offset} ${kernel_nand_size}; bootm 81c00000

On Wed, Nov 10, 2010 at 7:16 PM, Md Oblivious <md.obl...@gmail.com> wrote:

Hello,
 sorry for the pushing ....  any geedback for me ?
thanks

2010/11/9 Md Oblivious <md.obl...@gmail.com>

Deva,

first to all thanks for your precious support.

in emmc Blaze  (internal) there is a release build from binaries.
I'm working with pre-build L27.4 RC0.
I already use the  partition procedure showed in you link.

If I better understood  pre-build  L27.4 RC0 not work well with eMMC booting
could you suggest me the right release and configuration?
It 's ok also if I need to built the binaries.

The same think (boot by Emmc) is also valid for Omap 3630 -GP rev 1?

Less or more I have the same problem with Omap 3630,

I'm using pre-build RLS25.inc2.5 but I don't have problem with sd card
 whilst with eMMc I have the following error:
                  VFS: Unable to mount root fs via NFS, trying floppy.
                  VFS: Cannot open root device "mmcblk0p2" or unknown-block(2,0)

I hope that  I have clarify the scenario.

Regards,
Oblivious

2010/11/9 Deva R <r.de...@gmail.com>

all looks good till filesystem partition mount..

one more question: did u tested first with prebuilt binaries or you built binaries locally?

because 'Failed to execute /init.  Attempting defaults...' might also result result if we use non ARM binaries (say if build went wrong, like when we built for generic platform (x86) instead of blaze (arm) )

>Do you know if there are some differences to boot the platform by Sd card and  eMMc card ?

>Let me explain the pre-build android work well also with eMMC card ?

booting procedure differs a bit for eMMC, the way we partition eMMC 

its officially supported from L27.INC1.5 release (but was functional with earlier releases)

Detailed steps are available at http://omappedia.org/wiki/L27.INC1.5.1_Froyo_ES2_Release_Notes#Booting_Kernel_and_Android_File_System_from_eMMC 

On Tue, Nov 9, 2010 at 4:59 PM, Md Oblivious <md.obl...@gmail.com> wrote:

Deva,
here below the full kernel bootlog.
I kindly ask you a new question:
Do you know if there are some differences to boot the platform by Sd card and  eMMc card ?
Let me explain the pre-build android work well also with eMMC card ?

Thanks a lot
Oblivious



Uncompressing Linux...
Linux version 2.6.32.9 (a0272553local@dta0272553-ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 SMP PREEMPT 0
CPU: ARMv7 Processor [410fc091] revision 1 (ARMv7), cr=10c53c7f

CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP4430 4430SDP board
Memory policy: ECC disabled, Data cache writealloc

OMAP4430 ES1.0
SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0x100000
Reserving 14745600 bytes SDRAM for VRAM
PERCPU: Embedded 8 pages/cpu @c17a4000 s10080 r8192 d14496 u65536
pcpu-alloc: s10080 r8192 d14496 u65536 alloc=16*4096

pcpu-alloc: [0] 0 [0] 1

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 117602
Kernel command line: console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem=463M init=/init
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 463MB = 463MB total
Memory: 449280KB available (4712K code, 1105K data, 192K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:388
omap_hwmod: tesla: cannot be enabled (3)
omap_hwmod: sdma: cannot be enabled (3)
omap_hwmod: cust_efuse: cannot be enabled (3)
omap_hwmod: pdm: cannot be enabled (3)
omap_hwmod: sl2: cannot be enabled (3)
omap_hwmod: sr_core: cannot be enabled (3)
omap_hwmod: sr_iva: cannot be enabled (3)
omap_hwmod: sr_mpu: cannot be enabled (3)
omap_hwmod: iss: cannot be enabled (3)
omap_hwmod: ivahd: cannot be enabled (3)
omap_hwmod: sad2d: cannot be enabled (3)
omap_hwmod: ducati: cannot be enabled (3)
GPMC revision 6.0
OMAP GPIO hardware version 0.1
OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 1195.29 BogoMIPS (lpj=4669440)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
L2x0 cache controller enabled
CPU1: Booted secondary processor
Brought up 2 CPUs
SMP: Total of 2 processors activated (2395.78 BogoMIPS).
regulator: core version 0.5
NET: Registered protocol family 16
(wl12xx):  Connectivity board init
(wl12xx):  Adding Connectivity platform device
(wl12xx):  Configuring Connectivity GPIOs
omap_hsmmc_reset: Unable to enable clocks for MMC0, cannot reset.
pm_dbg_init: only OMAP3 supported
OMAP DMA hardware revision 0.0
bio: create slab <bio-0> at 0
i2c_omap i2c_omap.1: bus 1 rev4.0 at 400 kHz
Skipping twl internal clock init and using bootloader value (unknown osc rate)
twl6030: PIH (irq 39) chaining IRQs 368..387
regulator: VMMC: 1200 <--> 3000 mV at 3000 mV normal standby
omap_device: i2c_omap.1: new worst case deactivate latency 0: 30517
regulator: VPP: 1800 <--> 2500 mV at 1900 mV normal standby
regulator: VUSIM: 1200 <--> 2900 mV at 1800 mV normal standby
regulator: VANA: 2100 mV normal standby
regulator: VCXIO: 1800 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VUSB: 3300 mV normal standby
regulator: VAUX1_6030: 1000 <--> 3000 mV at 2800 mV normal standby
omap_device: i2c_omap.1: new worst case activate latency 0: 30517
regulator: VAUX2_6030: 1200 <--> 2800 mV at 1800 mV normal standby
regulator: VAUX3_6030: 1000 <--> 3000 mV at 1200 mV normal standby
i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz
i2c_omap i2c_omap.4: bus 4 rev4.0 at 400 kHz
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Switching to clocksource 32k_counter
Clockevents: could not switch to one-shot mode:
Clockevents: could not switch to one-shot mode: dummy_timer is not functional.
Could not switch to high resolution mode on CPU 1
 dummy_timer is not functional.
Could not switch to high resolution mode on CPU 0
musb_hdrc: version 6.0, musb-dma, peripheral, debug=0
musb_hdrc: USB Peripheral mode controller at fc0ab000 using DMA, IRQ 124
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 5, 196608 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
sdp4430_wifi_init: start
omap-iommu omap-iommu.0: ducati registered
ashmem: initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 877
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
CM_DSS_CLKSTCTRL 0xf02 0xfc009100
CM_DSS_DSS_CLKCTRL 0x40f02 0xfc009120
PM DSS wrst 0x37 0xfc307104
OMAP DSS rev 4.0
OMAP DISPC rev 4.0
dsi_init calling
OMAP DSI rev 3.0
dsi2_init calling
OMAP DSI2 rev 3.0
OMAP HDMI W1 rev 1.0

 omap_dss_register_driver DONE pico probe called
omap-hsuart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0
omap-hsuart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1
omap-hsuart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2
console [ttyO2] enabled
omap-hsuart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3
brd: module loaded
loop: module loaded
ks8851 spi1.0: message enable is 0
ks8851 spi1.0: revision 0, MAC 08:00:28:01:50:d1, IRQ 194, has EEPROM
android init
android_probe pdata: c04f0aa8
android_bind
android_usb gadget: android_usb ready
f_acm init
android_register_function acm
f_adb init
android_register_function adb
f_mass_storage init
android_register_function usb_mass_storage
f_rndis init
android_register_function rndis
mass_storage_bind_config
android_usb gadget: Number of LUNs=1
adb_bind_config
rndis_function_bind_config MAC: 02:32:4B:78:02:75
android_usb gadget: using random self ethernet address
android_usb gadget: using random host ethernet address
usb0: MAC 5a:51:77:c4:1c:17
usb0: HOST MAC f2:7e:b0:30:9f:14
OMAP Keypad Driver
input: omap_keypad as /devices/platform/omap-keypad/input/input0
tm12xx_ts: Synaptic TM12xx Touchscreen Driver found man id 1 (1)
tm12xx_ts 2-004b: resetting device (reg 0x62)
using rtc device, twl_rtc, for alarms
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
twl_rtc twl_rtc: Power up reset detected.
twl_rtc twl_rtc: Enabling TWL-RTC.
i2c /dev entries driver
Linux video capture interface: v2.00
tm12xx_ts 2-004b: no button capabilities found
tm12xx_ts: product ID: TM1217 family:1 fw:9
input: Synaptic TM12XX TouchPoint 1 as /devices/platform/i2c_omap.2/i2c-2/2-004b/input/input1
tm12xx_ts 2-004b: device status: 0x0, no error
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCILL protocol initialized
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
proc4430_drv_initializeModule
Advanced Linux Sound Architecture Driver Version 1.0.21.
twl: i2c_write failed to transfer all messages
mmc1: new high speed MMC card at address 0001
mmcblk0: mmc1:0001 MMC32G 29.8 GiB
 mmcblk0: p1 p2 p3 p4
i2c_omap i2c_omap.1: controller timed out
twl: i2c_write failed to transfer all messages
twl: i2c_write failed to transfer all messages
i2c_omap i2c_omap.1: controller timed out
twl: i2c_write failed to transfer all messages
No device for DAI Multimedia
No device for DAI Tones DL
No device for DAI Voice
No device for DAI Digital Uplink
No device for DAI Vibrator
No device for DAI omap-abe-mm
No device for DAI omap-abe-tone-dl
No device for DAI omap-abe-voice
No device for DAI omap-abe-dig-ul
No device for DAI omap-abe-vib
OMAP HDMI W1 rev 1.0
No device for DAI omap-hdmi-dai
SDP4430 SoC init
No device for DAI null
asoc: Multimedia <-> omap-abe-mm mapping ok
asoc: Tones DL <-> omap-abe-tone-dl mapping ok
asoc: Voice <-> omap-abe-voice mapping ok
asoc: Digital Uplink <-> omap-abe-dig-ul mapping ok
asoc: Vibrator <-> omap-abe-vib mapping ok
asoc: null <-> omap-hdmi-dai mapping ok
SDP4430 SoC init
ALSA device list:
  #0: SDP4430 (twl6040)
oprofile: using timer interrupt.
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.14
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: HIDP (Human Interface Emulation) ver 1.2
 Enabling AXI2OCP errata Fix
Power Management for TI OMAP4.
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0
rotation = 0, var->rotate = 0
rotation = 0, var->rotate = 0
Console: switching to colour frame buffer device 108x30
OMAP DISPCONTROL read (stallmode)0
OMAP DISPCONTROL read (gpout)0
OMAP DISPCONTROL read (stallmode)0
panel-taal display0: revision e3.84.00
regulator_init_complete: incomplete constraints, leaving VAUX3_6030 on
regulator_init_complete: incomplete constraints, leaving VAUX2_6030 on
regulator_init_complete: incomplete constraints, leaving VAUX1_6030 on
regulator_init_complete: incomplete constraints, leaving VUSB on
regulator_init_complete: incomplete constraints, leaving VDAC on
regulator_init_complete: incomplete constraints, leaving VCXIO on
regulator_init_complete: incomplete constraints, leaving VANA on
regulator_init_complete: incomplete constraints, leaving VUSIM on
regulator_init_complete: incomplete constraints, leaving VPP on
DEBUG omaplfb (OMAPLFBInit 1527): Initializing 3rd party display driver
DEBUG omaplfb (OMAPLFBInit 1528): Found 1 framebuffers
DEBUG omaplfb (OMAPLFBInit 1572): -> Initializing display device 0
DEBUG omaplfb (InitDev 1441): Framebuffer index 0 information:
DEBUG omaplfb (InitDev 1443): *Physical address: 0x80990000
DEBUG omaplfb (InitDev 1445): *Virtual address: 0xdd400000
DEBUG omaplfb (InitDev 1446): *Size (bytes): 1658880
DEBUG omaplfb (InitDev 1448): *Width, height: 864,480
DEBUG omaplfb (InitDev 1450): *Virtual width, height: 864,480
DEBUG omaplfb (InitDev 1451): *Rotation: 0
DEBUG omaplfb (InitDev 1453): *Stride (bytes): 3456
DEBUG omaplfb (InitDev 1474): *Bits per pixel: 32
DEBUG omaplfb (InitDev 1504): *Format: ARGB8888
DEBUG omaplfb (OMAPLFBInit 1589): -> Populating display device 0
DEBUG omaplfb (OMAPLFBInit 1623): Flipping not supported, no swap chain will be created
DEBUG omaplfb (OMAPLFBInit 1657): Buffers available: 1 (1658880 bytes per buffer)
DEBUG omaplfb (OMAPLFBInit 1692): Display device 0 registered with id 1
DEBUG omaplfb (OMAPLFB_Init 381): Registering platform driver
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:06 UTC (946684806)
omap_vout: registered and initialized video device 0 [v4l2]
omap_vout: registered and initialized video device 1 [v4l2]
Waiting 2sec before mounting root device...
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: mounting fs wHi to all,

ith errors, running e2fsck is recommended
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: 192K

Warning: unable to open an initial console.
Failed to execute /init.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
CPU0: stopping
Backtrace:
[<c003d648>] (dump_backtrace+0x0/0x110) from [<c03c0fec>] (dump_stack+0x18/0x1c)
 r7:c17a4040 r6:00000010 r5:00000010 r4:ffffffff

[<c03c0fd4>] (dump_stack+0x0/0x1c) from [<c00382ec>] (do_IPI+0xf4/0x16c)
[<c00381f8>] (do_IPI+0x0/0x16c) from [<c0038c84>] (__irq_svc+0x44/0xbc)
Exception stack(0xc04d3f40 to 0xc04d3f88)
3f40: c0536f1c 00000000 c04d3f88 00000000 c04d2000 c0530d1c c04d2000 c04e2514
3f60: 8002c8e4 410fc091 00000000 c04d3f94 c04d3f98 c04d3f88 c003a430 c003a434
3f80: 60000013 ffffffff
[<c003a408>] (default_idle+0x0/0x30) from [<c003ac50>] (cpu_idle+0x84/0xe0)
[<c003abcc>] (cpu_idle+0x0/0xe0) from [<c03bae10>] (rest_init+0x78/0x8c)
 r5:c0530d1c r4:c04d2000
[<c03bad98>] (rest_init+0x0/0x8c) from [<c0008ce0>] (start_kernel+0x284/0x2e4)
 r5:c0530d1c r4:c055e05c
[<c0008a5c>] (start_kernel+0x0/0x2e4) from [<80008080>] (0x80008080)
 r6:c002f014 r5:c0530e64 r4:10c53c7d

2010/11/9 Deva R <r.de...@gmail.com>

--

Regards,

Deva

www.bittoggler.com

--

Regards,

Deva

www.bittoggler.com

[Deva R]

Sorry, its my bad - i mistook external emmc booting with onboard emmc booting.

provided your kernel has booted, no problem with card interface.,

only filesystem start have issue, and it could be

 - wrongly formatted partition ext3

 - error in filesystem preparation

 - wrong partition number (seems u got 32GB card with 4 partitions. where is file system copied?)

    >mmcblk0: mmc1:0001 MMC32G 29.8 GiB 
    >mmcblk0: p1 p2 p3 p4

   you can cross check if root=/dev/mmcblk0p<> is properly pointing to a partition with android init.

--

Regards,

Deva

www.bittoggler.com