booting new image

booting new image

[Luís Vitório Cargnini]

Hi people,
After 2 days working with openembedded, thanks to Philip Balister and his
help in this 2 days, i have an image without warning or error on blocks of
erasure size etc.
But the system isn't bootin yet isn't opening the console.

this is my console loging:

OMAP5912 OSK # boot
## Booting image at 00040000 ...
   Image Name:   Linux-2.6.18-rc7-omap1-gf16bdc72
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1321708 Bytes =  1.3 MB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing
Linux.......................................................................................
done, booting the kernel.
Linux version 2.6.18-rc7-omap1-gf16bdc72-dirty (lvcargnini@enterprise) (gcc
version 4.0.0 (DENX ELDK 4.0 4.0.0)) #2 Fri Sep 22 00:02:25 BRT 2006
CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177
Machine: TI-OSK
Memory policy: ECC disabled, Data cache writeback
OMAP162123 revision 2 handled as 16xx id: e105940859901e19
SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x100000
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists.  Total pages: 8192
Kernel command line: console=ttyS0,115200n8 noinitrd rw rootfstype=jffs2
root=/dev/mtdblock3 mem=32M
Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2833 ARM_CKCTL: 0x2000
Clocking rate (xtal/DPLL1/MPU): 12.0/192.0/192.0 MHz
Total of 128 interrupts in 4 interrupt banks
OMAP GPIO hardware version 1.0
MUX: initialized M7_1610_GPIO62
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 29616KB available (2201K code, 477K data, 116K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
OMAP DMA hardware version 1
DMA capabilities: 000c0000:00000000:01ff:003f:007f
Initializing OMAP McBSP system
omap_dsp_init() done
USB: hmc 16, usb0 2 wires
i2c_omap i2c_omap.1: bus 0 rev2.2 at 100 kHz
tps65010: version 2 May 2005
No IRQF_TRIGGER set_type function for IRQ 353 (MPUIO)
MUX: initialized N14_1610_UWIRE_CS0
MUX: initialized P15_1610_UWIRE_CS3
NET: Registered protocol family 2
IP route cache hash table entries: 256 (order: -2, 1024 bytes)
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 1024 bind 512)
TCP reno registered
Power Management for TI OMAP.
MUX: initialized T20_1610_LOW_PWR
NetWinder Floating Point Emulator V0.97 (double precision)
OMAP OCPI interconnect driver loaded
OMAP DSP driver initialization
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>
eth0: SMC91C94 (rev 9) at c2850300 IRQ 160 [nowait]
eth0: Ethernet addr: 00:0e:99:02:0d:32
i2c /dev entries driver
Clock enabled to MCBSP1 & 3
TLV320AIC23 I2C version 1.8 (10-Feb-2006)
omapflash.0: Found 1 x16 devices at 0x0 in 16-bit bank
omapflash.0: Found 1 x16 devices at 0x1000000 in 16-bit bank
 Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
Creating 4 MTD partitions on "omapflash.0":
0x00000000-0x00020000 : "bootloader"
0x00020000-0x00040000 : "params"
0x00040000-0x00240000 : "kernel"
0x00240000-0x02000000 : "filesystem"
MUX: initialized W11_1610_CF_CD1
MUX: initialized P11_1610_CF_CD2
MUX: initialized R11_1610_CF_IOIS16
MUX: initialized V10_1610_CF_IREQ
MUX: initialized W10_1610_CF_RESET
omap_cf: cs2 on irq 222
mice: PS/2 mouse device common for all mice
OMAP Keypad Driver
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22
13:55:50 2006 UTC).
audio support initialized
ALSA device list:
  #0: OSK AIC23
TCP bic registered
NET: Registered protocol family 1
Disabling unused clock "usb_dc_ck"...  done
FIXME: Clock "tc2_ck" seems unused
Disabling unused clock "tc1_ck"...  done
Skipping reset check for DSP domain clock "dsptim_ck"
Skipping reset check for DSP domain clock "dspper_ck"
OMAP GPIO switch handler initializing
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 116K

my u-boot env:

OMAP5912 OSK # printenv
baudrate=115200
etheraddr=00:0e:99:02:0d:32
ethaddr=00:0E:99:02:0D:32
bootdelay=4
bootfile=uImage
bootargs=console=ttyS0,115200n8 noinitrd rw rootfstype=jffs2
root=/dev/mtdblock3 mem=32M
filesize=142b2c
fileaddr=10000000
netmask=255.255.255.0
ipaddr=192.168.1.1
serverip=192.168.1.6
bootcmd=bootm 0x00040000
stdin=serial
stdout=serial
stderr=serial


someone knows what is faulting to the system finally boots and open the
console ???
What i have missing ?
I'm asking here because I'm interrupting a lot Balister and he had to finish
his papers, so any help is always welcome.


-- 
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Mastering Degree student @ PUC-RS Electrical Engineer Faculty

Re: booting new image

[Luís Vitório Cargnini]

answers on message body as follow:

On 9/22/06, Nishanth Menon <menon.nishanth@gmail.com> wrote:
>
> Luís Vitório Cargnini stated on 9/21/2006 11:08 PM:
>
> do let us know how you solved the issue too. :)


the openembedded did all the job but when it tried to use the mkfs it fail,
the nice thing is OE do not clean all work done until the point you stop and
restart again, so the directory with image almost ready was there i only
need to copy the directory add my own kernel modules and voilá it was
ready.

>
> This is ur first boot right? please wait for 1 hr and see. One usual
> area of problem is that a first time mount is seen to consume time.. at
> least it used too.. dunno abt it now.. but give it a shot.. as long as u
> do not get a kernel panic, ur good..


1 hr ???
ok I'm doing this now 1 minute and counting.......

Regards,
> Nishanth Menon
>



-- 
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Mastering Degree student @ PUC-RS Electrical Engineer Faculty

Re: booting new image

[Luís Vitório Cargnini]

Gentlemen after booted my board using the image available in:
http://oskfordummies.hp.infoseek.co.jp/downloads/rootfs2.6.11_0612.tar.bz2

it booted using my kernel and my u-boot, it's an busybox version 1.0.0 so i
think the problem colud be with busy box.
any opinion ?

On 9/22/06, Philip Balister <philip@balister.org> wrote:
>
> yeah, let me put them on a web server. The only SW is all open source.
>
> Philip
>
> > On 9/22/06, * Philip Balister* <philip@balister.org
> > <mailto:philip@balister.org>> wrote:
> >
> >     I just took a look at my boot log and right after yours hangs I see
> >
> >     INIT: version 2.86 booting
> >
> >     Then it trys to start udev. With the fstab on your image that may
> not go
> >     smoothly. I have some changes I ahven't been able to check back in
> yet.
> >     RP in #oe mentioned there might be some trouble with busybox, but I
> do
> >     not know if it is related to this problem.
> >
> >     I would like to try and rebuild my OE stuff and test again to see if
> I
> >     can narrow this down better, but I won't have time until next week,
> and
> >     even then it will be a background task for me. October I do need to
> make
> >     this work well though. Try asking gently in the #oe channel.
> >
> >     Thanks for the kind words :)
> >
> >     Philip
>
>


-- 
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Mastering Degree student @ PUC-RS Electrical Engineer Faculty

Re: booting new image

[Nishanth Menon]

Luís Vitório Cargnini stated on 9/22/2006 1:14 PM:
> Gentlemen after booted my board using the image available in:
> http://oskfordummies.hp.infoseek.co.jp/downloads/rootfs2.6.11_0612.tar.bz2
> 
> it booted using my kernel and my u-boot, it's an busybox version 1.0.0 so i
> think the problem colud be with busy box.
> any opinion ?
yes, like OE, udev here too? that is a usual tricky place too.. I just
googled and saw some stuff like this:
http://bugs.busybox.net/view.php?id=1041
I suppose you can move to 1.2.1. give that too a shot :) or maybe ping
the buxybox folks on this. http://www.busybox.net/lists.html

Regards,
Nishanth Menon