* Booting a Xilinx board @ 2008-04-07 15:33 Guillaume Dargaud 2008-04-07 16:44 ` Stephen Neuendorffer 2008-04-08 3:55 ` Grant Likely 0 siblings, 2 replies; 7+ messages in thread From: Guillaume Dargaud @ 2008-04-07 15:33 UTC (permalink / raw) To: linuxppc-dev Hello all, sorry if this is an elementary question for most of you, but could you tell me where I'm going wrong in trying to boot a kernel 2.6.24 on a Xilinx ml405 board ? - I generate an ext2 partition with buildroot, cointaining busybox and uclibc. - I copy it to my CF card: sudo dd if=binaries/genepy/rootfs.test.ext2 of=/dev/sdc2 - I compile the git Xilinx kernel, with proper xparameters file from the BSP and proper .config options to match the design, using the cross compiler created by buildroot. - I generate a sysace file from that kernel and put it on the 1st partition: xmd -tcl genace.tcl -jprog -board ml405 -target ppc_hw -hw implementation/system.bit -elf ~/kernels/linux-2.6.24/arch/ppc/boot/images/zImage.elf -ace Kernel26.ace When I boot I get the following: loaded at: 00400000 0050719C board data at: 00505120 0050519C relocated to: 00404054 004040D0 zimage at: 00404E40 0050484E avail ram: 00508000 08000000 Linux/PPC load: console=ttyS0,9600 ip=on root=/dev/sysace/disc0/part2 rw Uncompressing Linux...done. Now booting the kernel And then it stops. I'm sure I've overlooked something obvious... Thanks -- Guillaume Dargaud http://www.gdargaud.net/ ^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: Booting a Xilinx board 2008-04-07 15:33 Booting a Xilinx board Guillaume Dargaud @ 2008-04-07 16:44 ` Stephen Neuendorffer 2008-04-07 16:59 ` John Linn 2008-04-08 3:55 ` Grant Likely 1 sibling, 1 reply; 7+ messages in thread From: Stephen Neuendorffer @ 2008-04-07 16:44 UTC (permalink / raw) To: Guillaume Dargaud, linuxppc-dev Generally, speaking the easiest way to debug such errors is to examine __log_buf using XMD. Steve > -----Original Message----- > From: = linuxppc-dev-bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org [mailto:linuxppc-dev- > bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org] On Behalf Of Guillaume Dargaud > Sent: Monday, April 07, 2008 8:34 AM > To: linuxppc-dev@ozlabs.org > Subject: Booting a Xilinx board >=20 > Hello all, > sorry if this is an elementary question for most of you, but could you tell > me where I'm going wrong in trying to boot a kernel 2.6.24 on a Xilinx ml405 > board ? >=20 > - I generate an ext2 partition with buildroot, cointaining busybox and > uclibc. >=20 > - I copy it to my CF card: > sudo dd if=3Dbinaries/genepy/rootfs.test.ext2 of=3D/dev/sdc2 >=20 > - I compile the git Xilinx kernel, with proper xparameters file from the BSP > and proper .config options to match the design, using the cross compiler > created by buildroot. >=20 > - I generate a sysace file from that kernel and put it on the 1st partition: > xmd -tcl genace.tcl -jprog -board ml405 -target ppc_hw -hw > implementation/system.bit -elf > ~/kernels/linux-2.6.24/arch/ppc/boot/images/zImage.elf -ace Kernel26.ace >=20 > When I boot I get the following: >=20 > loaded at: 00400000 0050719C > board data at: 00505120 0050519C > relocated to: 00404054 004040D0 > zimage at: 00404E40 0050484E > avail ram: 00508000 08000000 >=20 > Linux/PPC load: console=3DttyS0,9600 ip=3Don = root=3D/dev/sysace/disc0/part2 rw > Uncompressing Linux...done. > Now booting the kernel >=20 > And then it stops. > I'm sure I've overlooked something obvious... > Thanks > -- > Guillaume Dargaud > http://www.gdargaud.net/ >=20 >=20 > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev ^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: Booting a Xilinx board 2008-04-07 16:44 ` Stephen Neuendorffer @ 2008-04-07 16:59 ` John Linn 0 siblings, 0 replies; 7+ messages in thread From: John Linn @ 2008-04-07 16:59 UTC (permalink / raw) To: Stephen Neuendorffer, Guillaume Dargaud, linuxppc-dev You can also get our support file from the http git web site and then use the default ML405 kernel configuration just as a baseline to get the kernel running. The support file has a bit stream that supports the 405 def kernel configuration. Thanks, John -----Original Message----- From: linuxppc-dev-bounces+john.linn=3Dxilinx.com@ozlabs.org [mailto:linuxppc-dev-bounces+john.linn=3Dxilinx.com@ozlabs.org] On = Behalf Of Stephen Neuendorffer Sent: Monday, April 07, 2008 10:44 AM To: Guillaume Dargaud; linuxppc-dev@ozlabs.org Subject: RE: Booting a Xilinx board Generally, speaking the easiest way to debug such errors is to examine __log_buf using XMD. Steve > -----Original Message----- > From: = linuxppc-dev-bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org [mailto:linuxppc-dev- > bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org] On Behalf Of Guillaume Dargaud > Sent: Monday, April 07, 2008 8:34 AM > To: linuxppc-dev@ozlabs.org > Subject: Booting a Xilinx board >=20 > Hello all, > sorry if this is an elementary question for most of you, but could you tell > me where I'm going wrong in trying to boot a kernel 2.6.24 on a Xilinx ml405 > board ? >=20 > - I generate an ext2 partition with buildroot, cointaining busybox and > uclibc. >=20 > - I copy it to my CF card: > sudo dd if=3Dbinaries/genepy/rootfs.test.ext2 of=3D/dev/sdc2 >=20 > - I compile the git Xilinx kernel, with proper xparameters file from the BSP > and proper .config options to match the design, using the cross compiler > created by buildroot. >=20 > - I generate a sysace file from that kernel and put it on the 1st partition: > xmd -tcl genace.tcl -jprog -board ml405 -target ppc_hw -hw > implementation/system.bit -elf > ~/kernels/linux-2.6.24/arch/ppc/boot/images/zImage.elf -ace Kernel26.ace >=20 > When I boot I get the following: >=20 > loaded at: 00400000 0050719C > board data at: 00505120 0050519C > relocated to: 00404054 004040D0 > zimage at: 00404E40 0050484E > avail ram: 00508000 08000000 >=20 > Linux/PPC load: console=3DttyS0,9600 ip=3Don = root=3D/dev/sysace/disc0/part2 rw > Uncompressing Linux...done. > Now booting the kernel >=20 > And then it stops. > I'm sure I've overlooked something obvious... > Thanks > -- > Guillaume Dargaud > http://www.gdargaud.net/ >=20 >=20 > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Booting a Xilinx board 2008-04-07 15:33 Booting a Xilinx board Guillaume Dargaud 2008-04-07 16:44 ` Stephen Neuendorffer @ 2008-04-08 3:55 ` Grant Likely 2008-04-08 9:22 ` Guillaume Dargaud 1 sibling, 1 reply; 7+ messages in thread From: Grant Likely @ 2008-04-08 3:55 UTC (permalink / raw) To: Guillaume Dargaud; +Cc: linuxppc-dev On Mon, Apr 7, 2008 at 9:33 AM, Guillaume Dargaud <dargaud@lpsc.in2p3.fr> wrote: > > Linux/PPC load: console=ttyS0,9600 ip=on root=/dev/sysace/disc0/part2 rw > Uncompressing Linux...done. > Now booting the kernel > > And then it stops. > I'm sure I've overlooked something obvious... Are you using uartlite? Try console=ttyUL0. But Stephen is right, the first thing you should do is look at __log_buf. You can find its address in the System.map file. Cheers, g. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Booting a Xilinx board 2008-04-08 3:55 ` Grant Likely @ 2008-04-08 9:22 ` Guillaume Dargaud 2008-04-08 12:30 ` Guillaume Dargaud 0 siblings, 1 reply; 7+ messages in thread From: Guillaume Dargaud @ 2008-04-08 9:22 UTC (permalink / raw) To: linuxppc-dev > Are you using uartlite? Try console=ttyUL0. Thanks, I didn't know that. > But Stephen is right, the first thing you should do is look at > __log_buf. You can find its address in the System.map file. Unfortunately, the installation of the cable driver failed for some reason. I'll have to work on it... -- Guillaume Dargaud http://www.gdargaud.net/Antarctica/ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Booting a Xilinx board 2008-04-08 9:22 ` Guillaume Dargaud @ 2008-04-08 12:30 ` Guillaume Dargaud 2008-04-08 21:32 ` Grant Likely 0 siblings, 1 reply; 7+ messages in thread From: Guillaume Dargaud @ 2008-04-08 12:30 UTC (permalink / raw) To: linuxppc-dev I'm making progress, thanks in no small part to this list, but I still need coaching, if you don't mind. The current boot is currently going as such: loaded at: 00400000 005A819C board data at: 005A6120 005A619C relocated to: 00404054 004040D0 zimage at: 00404E40 00515AD1 initrd at: 00516000 005A5AF9 avail ram: 005A9000 08000000 Linux/PPC load: console=ttyUL0,9600 root=/dev/ram rw Uncompressing Linux...done. Now booting the kernel [ 0.000000] Linux version 2.6.24-rc8-xlnx (guinevere@lpsc6185x.in2p3.fr) (gcc version 4.1.2) #4 Tue Apr 8 13:41:02 CEST 2008 [ 0.000000] Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX) [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0 -> 32768 [ 0.000000] Normal 32768 -> 32768 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[1] active PFN ranges [ 0.000000] 0: 0 -> 32768 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: console=ttyUL0,9600 root=/dev/ram rw [ 0.000000] Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000 [ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes) [ 0.000224] Console: colour dummy device 80x25 [ 0.001417] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.003197] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.039286] Memory: 126804k available (1728k kernel code, 572k data, 104k init, 0k highmem) [ 0.132784] Mount-cache hash table entries: 512 [ 0.138698] net_namespace: 64 bytes [ 0.143763] NET: Registered protocol family 16 [ 0.147717] Registering device uartlite:0 [ 0.148883] Registering device xsysace:0 [ 0.149913] Registering device xilinx_emaclite:0 [ 0.191001] NET: Registered protocol family 2 [ 0.224934] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.228161] TCP established hash table entries: 4096 (order: 3, 32768 bytes) [ 0.228808] TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [ 0.229168] TCP: Hash tables configured (established 4096 bind 4096) [ 0.229201] TCP reno registered [ 0.241592] checking if image is initramfs...it isn't (no cpio magic); looks like an initrd [ 0.854687] Freeing initrd memory: 574k freed [ 0.855157] sysctl table check failed: /kernel/l2cr .1.31 Missing strategy [ 0.855208] Call Trace: [ 0.855227] [c7c17eb0] [c00081b8] show_stack+0x50/0x184 (unreliable) [ 0.855329] [c7c17ed0] [c0030514] set_fail+0x50/0x68 [ 0.855406] [c7c17ef0] [c0030b7c] sysctl_check_table+0x650/0x698 [ 0.855454] [c7c17f20] [c0030b8c] sysctl_check_table+0x660/0x698 [ 0.855501] [c7c17f50] [c001e874] register_sysctl_table+0x64/0xb4 [ 0.855567] [c7c17f70] [c0231c24] register_ppc_htab_sysctl+0x18/0x2c [ 0.855629] [c7c17f80] [c022b1e4] kernel_init+0xc8/0x284 [ 0.855667] [c7c17ff0] [c0004b18] kernel_thread+0x44/0x60 [ 0.864221] io scheduler noop registered [ 0.864277] io scheduler anticipatory registered (default) [ 0.864302] io scheduler deadline registered [ 0.864525] io scheduler cfq registered [ 0.939088] uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 2) is a uartlite [ 0.939174] console [ttyUL0] enabled [ 3.953024] RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize [ 4.036331] loop: module loaded [ 4.067349] xsysace xsa: Xilinx SystemACE revision 1.0.12 [ 4.131096] xsysace xsa: capacity: 1014048 sectors [ 4.186902] xsa: xsa1 xsa2 [ 4.222849] Xilinx SystemACE device driver, major=254 [ 4.280365] tun: Universal TUN/TAP device driver, 1.6 [ 4.340667] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 4.416748] xilinx_emaclite xilinx_emaclite.0: MAC address is now 2: 0: 0: 0: 0: 0 [ 4.506421] xilinx_emaclite xilinx_emaclite.0: using fifo mode. [ 4.580452] xilinx_emaclite xilinx_emaclite.0: Xilinx EMACLite at 0x81000000 mapped to 0xC9020000, irq=0 [ 4.691953] mice: PS/2 mouse device common for all mice [ 4.753483] TCP cubic registered [ 4.791772] NET: Registered protocol family 1 [ 4.843849] NET: Registered protocol family 17 [ 4.897987] RPC: Registered udp transport module. [ 4.953147] RPC: Registered tcp transport module. [ 5.011138] RAMDISK: Compressed image found at block 0 [ 5.905538] VFS: Mounted root (ext2 filesystem). [ 5.945703] Freeing unused kernel memormdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mdev: /etc/mdev.conf: No such file or directory mount: mounting configfs on /config failed: No such device Initializing random number generator... done. Starting network... ip: RTNETLINK answers: File exists And then it stops, although I still have echo when I type. Now there's no /etc/mdev.conf file in my root fylesystem and I understand I need to create the devices. I've been reading docs/mdev.txt and http://www.lfs-matrix.org/clfs/view/clfs-embedded/mips/bootscripts/mdev.html and I'm a bit confused. - do the devices need to be created in the FS before building the ramdisk and subsequent ACE file ? - are they created dynamically by /bin/mdev on boot based on a manually written /etc/mdev.conf table as the error messages seem to imply ? - can they be generated automagically by a MAKEDEV script ? In the second case, how do I know which devices and what names I'm supposed to define ? -- Guillaume Dargaud http://www.gdargaud.net/Climbing/ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Booting a Xilinx board 2008-04-08 12:30 ` Guillaume Dargaud @ 2008-04-08 21:32 ` Grant Likely 0 siblings, 0 replies; 7+ messages in thread From: Grant Likely @ 2008-04-08 21:32 UTC (permalink / raw) To: Guillaume Dargaud; +Cc: linuxppc-dev On Tue, Apr 8, 2008 at 6:30 AM, Guillaume Dargaud <dargaud@lpsc.in2p3.fr> wrote: > I'm making progress, thanks in no small part to this list, but I still need > coaching, if you don't mind. The current boot is currently going as such: > > > loaded at: 00400000 005A819C > board data at: 005A6120 005A619C <snip> > [ 4.897987] RPC: Registered udp transport module. > [ 4.953147] RPC: Registered tcp transport module. > [ 5.011138] RAMDISK: Compressed image found at block 0 > [ 5.905538] VFS: Mounted root (ext2 filesystem). > [ 5.945703] Freeing unused kernel memormdev: /etc/mdev.conf: No such > file > or directory > mdev: /etc/mdev.conf: No such file or directory <snip> > mdev: /etc/mdev.conf: No such file or directory > mdev: /etc/mdev.conf: No such file or directory > mount: mounting configfs on /config failed: No such device > Initializing random number generator... done. > Starting network... > ip: RTNETLINK answers: File exists > > > And then it stops, although I still have echo when I type. > Now there's no /etc/mdev.conf file in my root fylesystem and I understand I > need to create the devices. > I've been reading docs/mdev.txt and > http://www.lfs-matrix.org/clfs/view/clfs-embedded/mips/bootscripts/mdev.html > and I'm a bit confused. Congratulations, your kernel is in good shape. Now you're dealing with userspace issues. You can try bypassing most of the init process to see if you can get a prompt. Add init=/bin/sh to the kernel command line. > > - do the devices need to be created in the FS before building the ramdisk > and subsequent ACE file ? Yes, you can statically create the device files. MAKEDEV will do this for you. You can even just copy them from a working Linux system (any arch). > - are they created dynamically by /bin/mdev on boot based on a manually > written /etc/mdev.conf table as the error messages seem to imply ? That depends on your rootfs. Where did you get your rootfs image? > - can they be generated automagically by a MAKEDEV script ? > > In the second case, how do I know which devices and what names I'm supposed > to define ? Easiest way: copy from the /dev tree in a running Linux machine. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2008-04-08 21:32 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2008-04-07 15:33 Booting a Xilinx board Guillaume Dargaud 2008-04-07 16:44 ` Stephen Neuendorffer 2008-04-07 16:59 ` John Linn 2008-04-08 3:55 ` Grant Likely 2008-04-08 9:22 ` Guillaume Dargaud 2008-04-08 12:30 ` Guillaume Dargaud 2008-04-08 21:32 ` Grant Likely
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).