Re: u-boot for ML403
In message [EMAIL PROTECTED] you wrote: I am new to virtex 4 platform and i am trying to bringup u-boot on ML403 You are off topic on this list. Please post U-Boot related questions o the U-Boot mailing list. But - be warned: DISCLAIMER: Such disclaimers are taken seriously there, and incidents of unauthorized disclosure will be reported to your management. Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Also note that HTML is strictly forbidden on the U-Boot mailing list. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] panic: kernel trap (ignored) ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
u-boot for ML403
Hi, I am new to virtex 4 platform and i am trying to bringup u-boot on ML403 board. I download u-boot.zip ftrom ML410 site and am trying to compile it for ML403 using the following command make ml403_config make and i am getting the following error. ../xilinx_iic/iic_adapter.c: In function 'receive': .../xilinx_iic/iic_adapter.c:91: error: 'XIIC_STOP' undeclared (first use in this function) .../xilinx_iic/iic_adapter.c:91: error: too many arguments to function 'XIic_Send' .../xilinx_iic/iic_adapter.c:96: error: too many arguments to function 'XIic_Recv' make[1]: *** [../xilinx_iic/iic_adapter.o] Error 1 Am i missing some files or patch here? Does someone have a ready made code for u-boot on ML403? If so can you please share it with me. Thanks Rgds Anand DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ---___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Load Kernel 2.6 using U-boot on ML403
If you're starting a new design, I *highly* recommend using EDK9.2 with MPMC3 and LL_TEMAC. Using the Wizard in EDK9.2 and using the kernel from git.xilinx.com everything will work fine out-of-the-box. Including the ethernet. I've had troubles with the older (EDK9.1) TEMAC and GigE switches not syncing correctly. The LL_TEMAC in EDK9.2 solved this issue. RJW. On Sun, 2008-01-27 at 20:25 -0800, Yedu Jathavedan wrote: Looking at your bootlog, it doesn't look like you've got the systemace driver built into the kernel. Grant, Yes, the systemace was not built into the kernel. It is successfully booting the kernel now. Trying to bring up the Ethernet interface. Any pointers? Thank you, Yedu ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Load Kernel 2.6 using U-boot on ML403
Do you really need u-boot?? I'm using an ML403 without u-boot. I've generated my .ace file with the zImage.elf directly and it works fine. If there is a choice of u-boot or not, why choose u-boot? RJW. On Sat, 2008-01-26 at 23:10 -0800, Yedu Jathavedan wrote: Hi, I have downloaded the 2.6 kernel from http://git.secretlab.ca/git/linux-2.6-virtex.git , installed compiled it. I used make ARCH=ppc CROSS_COMPILE=ppc_4xx- ml403_defconfig to build the .config file. (As explained in http://wiki.secretlab.ca/index.php/Linux_on_Xilinx_Virtex) Problem - 1)Downloaded(sourceforge.net) compiled the U-boot 1.1.6 files to get u-boot, u-boot.srec u-boot.bin (I didn't find ml403 board config for the uboot. So used ml300_config). After this, I tried to convert the u-boot (README says that this is an ELF file) into an ace file. But, it gave me the error saying unable to read elf file. Is it because ML403 board is not supported or is it possible that the u-boot image that I created is corrupted? $ xmd -tcl genace.tcl -jprog -board ml403 -hw download.bit -elf u-boot -ace uboot.ace Xilinx EDK 9.1 Build EDK_J.19 Executing xmd script : $HOME/EDK/data/xmd/genace.tcl ### XMD GenACE utility. Generate SystemACE File from bit/elf/data Files ### Target Type not defined for Processor 1, Using default Target Type ppc_hw GenACE Options: Board : ml403 Jtag Devs : xcf32p xc4vfx12 xc95144xl FPGA pos : 2 JPROG : true HW File: download.bit ACE File : uboot.ace nCPUs : 1 Processor ppc_hw_1 Information Debug opt : -debugdevice devicenr 2 cpunr 1 ELF files : u-boot Start PC Address : 0xfff8 Converting Bitstream 'download.bit' to SVF file 'download.svf' Executing 'impact -batch bit2svf.scr' Copying download.svf File to uboot.svf File Converting ELF file 'u-boot' to SVF file 'u-boot.svf' Error: E02 Failed to download ELF file ERROR(1053): UNABLE to Read Elf File. The Elf File Maybe Corrupted : u-boot #$ __ Problem - 2) Since generating ace files failed, I tried to search the net for an u-boot ace file that could run on ML403 found it at http://88.191.24.164/docenligne/projets/samba/2006/linux-embarque-sur-ml-403/u-boot-ml403.ace/view I copied this ace file (u-boot-ml403.ace) along with the kernel 2.6 image (uImage) onto my CF card booted the board. After loading the kernel, it fails to read the correct root device. I tried changing the bootargs env variable root = /dev/xsysace/disc0/part2 rw to root = /dev/xsysace2 rw root = /dev/xsda2 rw. But, it failed in both cases. (There was a previous post on Problem2 a year ago he solved it by giving root =/dev/xsysace2) Environment size: 246/1020 bytes #u-boot setenv bootargs console=ttyS0,9600 root=/dev/xsysace2 rw #u-boot fatload ace 0 0x40 uImage reading uImage 952237 bytes read #u-boot bootm 0x40 ## Booting image at 0040 ... Image Name: Linux-2.6.24-rc3 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:952173 Bytes = 929.9 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK [0.00] Linux version 2.6.24-rc3 ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.0 4.0.0)) #1 Fri Jan 25 21:23:54 PST 2008 [0.00] Xilinx ML403 Reference System (Virtex-4 FX) [0.00] Zone PFN ranges: [0.00] DMA 0 -16384 [0.00] Normal 16384 -16384 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 -16384 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: console=ttyS0,9600 ip=off root=/dev/xsysace root=/dev/xsysace2 rw [0.00] Xilinx INTC #0 at 0xD1000FC0 mapped to 0xFDFFEFC0 [0.00] PID hash table entries: 256 (order: 8, 1024 bytes) [0.000179] Console: colour dummy device 80x25 [0.000669] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.001431] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.015197] Memory: 62860k available (1452k kernel code, 496k data, 96k init, 0k highmem) [0.204614] Mount-cache hash table entries: 512 [0.209345] net_namespace: 64 bytes [0.213840] NET: Registered protocol family 16 [0.252576] NET: Registered protocol family 2 [0.288713] IP route cache hash table entries: 1024
Re: Load Kernel 2.6 using U-boot on ML403
On 1/27/08, Yedu Jathavedan [EMAIL PROTECTED] wrote: 1)Downloaded(sourceforge.net) compiled the U-boot 1.1.6 files to get u-boot, u-boot.srec u-boot.bin (I didn't find ml403 board config for the uboot. So used ml300_config). U-boot 1.1.6 is ancient. The u-boot project has moved off of sourceforge to denx.de After this, I tried to convert the u-boot (README says that this is an ELF file) into an ace file. But, it gave me the error saying unable to read elf file. Is it because ML403 board is not supported or is it possible that the u-boot image that I created is corrupted? I don't know; but personally I don't weld u-boot into an ace file. I use a 1st stage bootloader to load the u-boot image off the cf card (but unfortunately I'm not able to post that loader at this time). Try again with a recent u-boot version. 2) Since generating ace files failed, I tried to search the net for an u-boot ace file that could run on ML403 found it at http://88.191.24.164/docenligne/projets/samba/2006/linux-embarque-sur-ml-403/u-boot-ml403.ace/view I copied this ace file (u-boot-ml403.ace) along with the kernel 2.6 image (uImage) onto my CF card booted the board. After loading the kernel, it fails to read the correct root device. I tried changing the bootargs env variable root = /dev/xsysace/disc0/part2 rw to root = /dev/xsysace2 rw root = /dev/xsda2 rw. But, it failed in both cases. (There was a previous post on Problem2 a year ago he solved it by giving root =/dev/xsysace2) Looking at your bootlog, it doesn't look like you've got the systemace driver built into the kernel. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Load Kernel 2.6 using U-boot on ML403
Looking at your bootlog, it doesn't look like you've got the systemace driver built into the kernel. Grant, Yes, the systemace was not built into the kernel. It is successfully booting the kernel now. Trying to bring up the Ethernet interface. Any pointers? Thank you, Yedu ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Load Kernel 2.6 using U-boot on ML403
Hi, /I have downloaded the 2.6 kernel from /http://git.secretlab.ca/git/linux-2.6-virtex.git , installed compiled it. I used make ARCH=ppc CROSS_COMPILE=ppc_4xx- ml403_defconfig to build the .config file. (As explained in http://wiki.secretlab.ca/index.php/Linux_on_Xilinx_Virtex)PROBLEM - 1)Downloaded(sourceforge.net) compiled the U-boot 1.1.6 files to get u-boot, u-boot.srec u-boot.bin (I didn't find ml403 board config for the uboot. So used ml300_config). After this, I tried to convert the u-boot (README says that this is an ELF file) into an ace file. But, it gave me the error saying unable to read elf file. Is it because ML403 board is not supported or is it possible that the u-boot image that I created is corrupted? $ xmd -tcl genace.tcl -jprog -board ml403 -hw download.bit -elf u-boot -ace uboot.ace Xilinx EDK 9.1 Build EDK_J.19 Executing xmd script : $HOME/EDK/data/xmd/genace.tcl ### XMD GenACE utility. Generate SystemACE File from bit/elf/data Files ### Target Type not defined for Processor 1, Using default Target Type ppc_hw GenACE Options: Board : ml403 Jtag Devs : xcf32p xc4vfx12 xc95144xl FPGA pos : 2 JPROG : true HW File : download.bit ACE File : uboot.ace nCPUs : 1 Processor ppc_hw_1 Information Debug opt : -debugdevice devicenr 2 cpunr 1 ELF files : u-boot Start PC Address : 0xfff8 Converting Bitstream 'download.bit' to SVF file 'download.svf' Executing 'impact -batch bit2svf.scr' Copying download.svf File to uboot.svf File Converting ELF file 'u-boot' to SVF file 'u-boot.svf' Error: E02 Failed to download ELF file ERROR(1053): UNABLE to Read Elf File. The Elf File Maybe Corrupted : u-boot #$ - PROBLEM - 2) Since generating ace files failed, I tried to search the net for an u-boot ace file that could run on ML403 found it at http://88.191.24.164/docenligne/projets/samba/2006/linux-embarque-sur-ml-403/u-boot-ml403.ace/view I copied this ace file (u-boot-ml403.ace) along with the kernel 2.6 image (uImage) onto my CF card booted the board. After loading the kernel, it fails to read the correct root device. I tried changing the bootargs env variable root = /dev/xsysace/disc0/part2 rw to root = /dev/xsysace2 rw root = /dev/xsda2 rw. But, it failed in both cases. (There was a previous post on Problem2 a year ago he solved it by giving root =/dev/xsysace2) Environment size: 246/1020 bytes #u-boot setenv bootargs console=ttyS0,9600 root=/dev/xsysace2 rw #u-boot fatload ace 0 0x40 uImage reading uImage 952237 bytes read #u-boot bootm 0x40 ## Booting image at 0040 ... Image Name: Linux-2.6.24-rc3 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 952173 Bytes = 929.9 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK [ 0.00] Linux version 2.6.24-rc3 ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.0 4.0.0)) #1 Fri Jan 25 21:23:54 PST 2008 [ 0.00] Xilinx ML403 Reference System (Virtex-4 FX) [ 0.00] Zone PFN ranges: [ 0.00] DMA 0 - 16384 [ 0.00] Normal 16384 - 16384 [ 0.00] Movable zone start PFN for each node [ 0.00] early_node_map[1] active PFN ranges [ 0.00] 0: 0 - 16384 [ 0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [ 0.00] Kernel command line: console=ttyS0,9600 ip=off root=/dev/xsysace root=/dev/xsysace2 rw [ 0.00] Xilinx INTC #0 at 0xD1000FC0 mapped to 0xFDFFEFC0 [ 0.00] PID hash table entries: 256 (order: 8, 1024 bytes) [ 0.000179] Console: colour dummy device 80x25 [ 0.000669] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.001431] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [ 0.015197] Memory: 62860k available (1452k kernel code, 496k data, 96k init, 0k highmem) [ 0.204614] Mount-cache hash table entries: 512 [ 0.209345] net_namespace: 64 bytes [ 0.213840] NET: Registered protocol family 16 [ 0.252576] NET: Registered protocol family 2 [ 0.288713] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.291229] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 0.291535] TCP bind hash table entries: 2048 (order: 1, 8192 bytes) [ 0.291709] TCP: Hash tables configured (established 2048 bind 2048) [ 0.291737] TCP reno registered [ 0.301433] sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
Re: Linux doesn not boot from u-boot on ML403
Hi Grant, Thank you very much for your response. actually I was wrong when saying: My observation is that the linux 2.6.23 rc-2 is not that stable as 2.6.21. In most cases It boots successfully (ie. zImage.elf) but occasionally it fails during booting. It has never occurred with 2.6.21 which I also copied from your side. Both version of linux 2.6.21 and 2.6.23 run very well and always boot properly. To deal with u-boot and linux kernel I use jtag and load the software straight to RAM. I have difficulties to boot uImage (kernel v2.6.23) from u-boot 1.2.0. uImage boots sometimes from u-boot but zImage.elf boots always (when loaded to RAM via jtag). It seems to be that I have the general problem with u-boot which I have described on u-boot users forum: http://www.nabble.com/u-boot-init-problem-on-ml403-%28virtex-4%29-board-tf4514050.html Best Regards Mirek -- View this message in context: http://www.nabble.com/Re%3A-Linux-doesn-not-boot-from-u-boot-on-ML403-tf4504418.html#a12875133 Sent from the linuxppc-embedded mailing list archive at Nabble.com. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
Hi Grant, Thank you very much for your advices which were very valuable for me. Recently I have followed your advice to move from kernel 2.6.21 to the higher one in order to have the possibility to boot the kernel from u-boot. I have copied across from you git tree the latest version of linux kernel 2.6.23 rc-2. It compiles successfully with some warnings like below: MODPOST vmlinux.o WARNING: vmlinux.o(.text+0x223c): Section mismatch: reference to .init.text:early_init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x2254): Section mismatch: reference to .init.text:machine_init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x2258): Section mismatch: reference to .init.text:MMU_init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x22b2): Section mismatch: reference to .init.text:start_kernel (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x22b6): Section mismatch: reference to .init.text:start_kernel (between 'start_here' and 'initial_mmu') LD vmlinux My observation is that the linux 2.6.23 rc-2 is not that stable as 2.6.21. In most cases It boots successfully (ie. zImage.elf) but occasionally it fails during booting. It has never occurred with 2.6.21 which I also copied from your side. For both kernels I use the same xparamerets_ml403.h file and very similar .config file Do you have some idea if it is known problem with booting in 2.6.23 rc-2? It of course could be something wrong with my ml403 board but I just wanted to get your opinion about the stability issue. Maybe it is better to use 2.6.22? Second question: In addition I wanted to ask you about u-boot tree which you have mentioned in the post on u-boot mailing list. This post was about uart lite for ml403 in u-boot. I was not able to find the project which you have mentioned there: git://git.secretlab.ca/git/u-boot.git This what interests me in particular concerning u-boot is the uart lite and temac interfaces from ml403. Thank you very much in advance for any hint Best Regards Mirek ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
On 9/23/07, Miroslaw Dach [EMAIL PROTECTED] wrote: Hi Grant, Thank you very much for your advices which were very valuable for me. Recently I have followed your advice to move from kernel 2.6.21 to the higher one in order to have the possibility to boot the kernel from u-boot. I have copied across from you git tree the latest version of linux kernel 2.6.23 rc-2. It compiles successfully with some warnings like below: MODPOST vmlinux.o WARNING: vmlinux.o(.text+0x223c): Section mismatch: reference to .init.text:early_init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x2254): Section mismatch: reference to .init.text:machine_init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x2258): Section mismatch: reference to .init.text:MMU_init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x22b2): Section mismatch: reference to .init.text:start_kernel (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x22b6): Section mismatch: reference to .init.text:start_kernel (between 'start_here' and 'initial_mmu') LD vmlinux Yes, I see this warning too. I haven't had a chance to debug it. My observation is that the linux 2.6.23 rc-2 is not that stable as 2.6.21. In most cases It boots successfully (ie. zImage.elf) but occasionally it fails during booting. It has never occurred with 2.6.21 which I also copied from your side. Hmm, what failure mode are you seeing? I haven't experienced that problem. However, -rc7 is now out, so I'd recommend moving up to it. (Hint: use git to make it easy to pull the latest version and either 'quilt' or 'stgit' to manage your changes on top of the mainline tree; it will make up/downgrading to different kernel version much easier) Second question: In addition I wanted to ask you about u-boot tree which you have mentioned in the post on u-boot mailing list. This post was about uart lite for ml403 in u-boot. I was not able to find the project which you have mentioned there: git://git.secretlab.ca/git/u-boot.git That's because there is not such tree. :-) I retired that tree a while ago because it's no longer current. You can use the mainline u-boot tree: git://www.denx.de/git/u-boot.git This what interests me in particular concerning u-boot is the uart lite and temac interfaces from ml403. :-( I don't think either uartlite or temac drivers has been ported to u-boot. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
On 8/30/07, Miroslaw Dach [EMAIL PROTECTED] wrote: When I try to start zImage.elf with bootelf command the system hangs during uncompressing. When I try to start uImage with bootm command the image is uncompressed but it does not start properly. Ugh, I'm stumped. Sorry. I'd spend some more quality time with your debugger to trace the exact boot path. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
Hi Grant, My zImage.elf has 1.1 MB and uImage 968 KB. Could you tell me please how to hook up GDB to debug u-boot? I have examined the file in u-boot which does the bootelf: cat common/cmd_elf.c: int do_bootelf (cmd_tbl_t *cmdtp, int flag, int argc, char *argv[]) : : : : addr = load_elf_image (addr); printf (## Starting application at 0x%08lx ...\n, addr); /* * QNX images require the data cache is disabled. * Data cache is already flushed, so just turn it off. */ if (dcache_status ()) dcache_disable (); /* * pass address parameter as argv[0] (aka command name), * and all remaining args */ rc = ((ulong (*)(int, char *[])) addr) (--argc, argv[1]); : : } and I have determined that the system hangs just after the command: rc = ((ulong (*)(int, char *[])) addr) (--argc, argv[1]); This command starts executing the linux image from the location: 0x0040 On the console it is printed the following stuff: loaded at: 0040 004F3138 board data at: 004F1120 004F1138 relocated to: 004040B4 004040CC zimage at: 00404E59 004F003D avail ram: 004F4000 01FF Linux/PPC load: console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=virtex4-mirek:eth0:dhcp panic=1 Uncompressing Linux... It seems to be that it is the Linux kernel which does the uncompression and it hangs. The question remain why? Maybe it is not enough space in RAM or the address in RAM where the uncompression is done is wrong. When I load the u-boot to ram via jtag it is placed under the address: 0x80 as follows: section, .text: 0x0080-0x0081513c section, .resetvec: 0x0081513c-0x00815140 section, .rodata: 0x00815140-0x00817ce0 section, .reloc: 0x00817d00-0x00818674 section, .data: 0x00818674-0x00818b08 section, .data.rel: 0x00818b08-0x00818b34 section, .data.rel.local: 0x00818b34-0x00818f6c section, .u_boot_cmd: 0x00818f6c-0x008191dc section, .bss: 0x00819200-0x0081dd04 Than I load the zImage.elf via tftp to the memory location 0xf0. When I issue the command bootelf 0xf0 the zImage.elf is placed in the memory: 0x40 as follows: section, .text: 0x0040-0x004036cc section, .data: 0x00404000-0x004f7000 section, .bss: 0x004f7000-0x004f9138 After that uncompression of zImage.elf starts. I am just wandering which memory location is involved for that? My evaluation board has 32 MB of SDRAM address range: (0x-0x01ff) DDR_SDRAM_1 plb Any Idea? Best Regards Mirek On Tue, 28 Aug 2007, Grant Likely wrote: On 8/28/07, Miroslaw Dach [EMAIL PROTECTED] wrote: This buffer refers to the kernel which I boot straight from jtag but not u-boot. /me remembers something How big is your kernel image? Seems to me I've had problems with kernel images that were too large not being uncompressed properly. Can you hook up GDB and debug u-boot? Find out where it is hanging? g. -- = Miroslaw Dach ([EMAIL PROTECTED]) - SLS/Controls Group PSI - Paul Scherrer Institut CH-5232 Villigen = ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
Hi Grant, Yes you are right that I should use uImage instead of zImage.elf I have tried first bootm and uImage but it also hanged during uncompression so next I have tried bootelf zImage.elf to see how this works because I was able to run zImage.elf straight from EDK via jtag. Cheers Mirek On Wed, 29 Aug 2007, Grant Likely wrote: On 8/29/07, Miroslaw Dach [EMAIL PROTECTED] wrote: Hi Grant, My zImage.elf has 1.1 MB and uImage 968 KB. Could you tell me please how to hook up GDB to debug u-boot? Ah-HA! You're using the wrong type of kernel image. When booting from u-boot, you should be using a 'uImage', not a 'zImage.elf'. (generated with 'make uImage' in the kernel tree). An you should use the 'bootm' command to boot the kernel. With bootm, u-boot can pass parameters to the kernel and it is u-boot that does the uncompression (instead of the zImage wrapper). Cheers, g. -- = Miroslaw Dach ([EMAIL PROTECTED]) - SLS/Controls Group PSI - Paul Scherrer Institut CH-5232 Villigen = ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
I have done further investigation with bootelf and zImage.elf (from u-boot) and it seems to be that the system fails during image uncompression: The last command executed is: r = zlib_inflate(s, Z_FINISH); /* file: ./arch/ppc/boot/common/misc-common.c */ zlib_inflate function code is in ./lib/zlib_inflate/inflate.c Mirek On Tue, 28 Aug 2007, Grant Likely wrote: On 8/28/07, Miroslaw Dach [EMAIL PROTECTED] wrote: This buffer refers to the kernel which I boot straight from jtag but not u-boot. /me remembers something How big is your kernel image? Seems to me I've had problems with kernel images that were too large not being uncompressed properly. Can you hook up GDB and debug u-boot? Find out where it is hanging? g. -- = Miroslaw Dach ([EMAIL PROTECTED]) - SLS/Controls Group PSI - Paul Scherrer Institut CH-5232 Villigen = ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
I have done additional test with my u-boot and linux kernel. I have downloaded u-boot(.elf) and zImage.elf via jtag to SDRAM: The SDRAM has 32 MB: Address Map for Processor ppc405_0 (0x-0x01ff) DDR_SDRAM_1 plb The steps I have doe are as following: 1. XMD% dow -data zImage.elf 0xe0 2. XMD% dow u-boot.elf section, .text: 0x0080-0x0081513c section, .resetvec: 0x0081513c-0x00815140 section, .rodata: 0x00815140-0x00817ce0 section, .reloc: 0x00817d00-0x00818674 section, .data: 0x00818674-0x00818b08 section, .data.rel: 0x00818b08-0x00818b34 section, .data.rel.local: 0x00818b34-0x00818f6c section, .u_boot_cmd: 0x00818f6c-0x008191dc section, .bss: 0x00819200-0x0081dd04 Downloaded Program u-boot.elf Setting PC with program start addr = 0x00800100 PC reset to 0x00800100, Clearing MSR Register 3. XMD% run -- output on the serial port -- U-Boot 1.2.0 (Aug 28 2007 - 11:56:19) U-Boot: checkboard DRAM: U-Boot: initdram 32 MB Using default environment In:serial Out: serial Err: serial Hit any key to stop autoboot: 0 = U-Boot 1.2.0 (Aug 27 2007 - 14:23:15) U-Boot: checkboard DRAM: U-Boot: initdram 32 MB Using default environment In:serial Out: serial Err: serial Hit any key to stop autoboot: 0 = bootelf 0xe0 Loading .text @ 0x0040 (14028 bytes) Loading .data @ 0x00404000 (995328 bytes) Clearing .bss @ 0x004f7000 (8504 bytes) ## Starting application at 0x0040 ... loaded at: 0040 004F9138 board data at: 004F7120 004F7138 relocated to: 004040B4 004040CC zimage at: 00404E59 004F6EE8 avail ram: 004FA000 01FF Linux/PPC load: console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=virtex4-mirek:eth0:dhcp panic=1 Uncompressing Linux... After that system just hangs. I do not understand why it is possible to run zImage.elf straight from jtag but it hangs when started from u-boot. Is it any fundamental problem with running Linux from u-boot on ML403 (Virtex-4) boards? Best Regards Mirek ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
On 8/28/07, Miroslaw Dach [EMAIL PROTECTED] wrote: Linux/PPC load: console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=virtex4-mirek:eth0:dhcp panic=1 Uncompressing Linux... After that system just hangs. I do not understand why it is possible to run zImage.elf straight from jtag but it hangs when started from u-boot. Is it any fundamental problem with running Linux from u-boot on ML403 (Virtex-4) boards? No there isn't. It should work. Most likely the kernel did not hang immediately, but rather the console is not setup correctly. You need to halt the processor after the hang and look at __log_buf in memory (Find the address in System.map). Cheers, g. Best Regards Mirek -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
On 8/28/07, Miroslaw Dach [EMAIL PROTECTED] wrote: Hi Grant, Thanks for your answer. I have found in the System.map : c020f0c4 b __log_buf Is the address c020f0c4 relative to the .data segment? 0xc000 are virtual kernel addresses; not physical addresses. If the MMU is still on, then you need to use the virtual address to examine memory. If the MMU is off (such as after reloading u-boot), then you need to change 0xCxxx to 0x0. I understand that when the system hangs I should type in the XMD window stop. Is there anyway to examine the memory from the XMD window? or should I reload the u-boot and examine the memory from u-boot? I don't know; I've never used XMD. Read the XMD documentation. You can do it from u-boot too. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
Hi Grant, Thanks for your answer. I have found in the System.map : c020f0c4 b __log_buf Is the address c020f0c4 relative to the .data segment? I understand that when the system hangs I should type in the XMD window stop. Is there anyway to examine the memory from the XMD window? or should I reload the u-boot and examine the memory from u-boot? Best Regards Mirek On Tue, 28 Aug 2007, Grant Likely wrote: On 8/28/07, Miroslaw Dach [EMAIL PROTECTED] wrote: Linux/PPC load: console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=virtex4-mirek:eth0:dhcp panic=1 Uncompressing Linux... After that system just hangs. I do not understand why it is possible to run zImage.elf straight from jtag but it hangs when started from u-boot. Is it any fundamental problem with running Linux from u-boot on ML403 (Virtex-4) boards? No there isn't. It should work. Most likely the kernel did not hang immediately, but rather the console is not setup correctly. You need to halt the processor after the hang and look at __log_buf in memory (Find the address in System.map). Cheers, g. Best Regards Mirek -- = Miroslaw Dach ([EMAIL PROTECTED]) - SLS/Controls Group PSI - Paul Scherrer Institut CH-5232 Villigen = ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
On 8/28/07, Miroslaw Dach [EMAIL PROTECTED] wrote: This buffer refers to the kernel which I boot straight from jtag but not u-boot. /me remembers something How big is your kernel image? Seems to me I've had problems with kernel images that were too large not being uncompressed properly. Can you hook up GDB and debug u-boot? Find out where it is hanging? g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
Hi Grant, I have did as you suggested: 1. I have started u-boot 2. I have loaded zImage.elf to the memory 0xf0 3. I have typed: bootelf 0xf0 Linux has hanged during uncompressing 4. I have stopped the system and reloaded u-boot to examine __log_buf ( address 0x20f0c4) Unfortunately all the bytes were set just to zero. 5. I have stopped the system 6. I have downloaded via jtag the zImage.elf and started it the system has started properly 7. I have stopped the system and reloaded u-boot to examine the memory 8. I have typed: md 0x20f0c4 100 and it showed me the buffer: 0020f0c4: 3c353e5b 20202020 302e3030 303030305[0.00 0020f0d4: 5d204c69 6e757820 76657273 696f6e20] Linux version 0020f0e4: 322e362e 32312d72 63362028 726f6f742.6.21-rc6 (root 0020f0f4: 40706335 32313529 20286763 63207665@pc5215) (gcc ve 0020f104: 7273696f 6e20342e 302e3229 20233136rsion 4.0.2) #16 0020f114: 204d6f6e 20417567 20323720 31323a33 Mon Aug 27 12:3 0020f124: 373a3038 20434553 54203230 30370a3c7:08 CEST 2007. 0020f134: 363e5b20 20202030 2e303030 3030305d6[0.00] 0020f144: 2058696c 696e7820 4d4c3430 33205265 Xilinx ML403 Re 0020f154: 66657265 6e636520 53797374 656d2028ference System ( 0020f164: 56697274 65782d34 20465829 0a3c373eVirtex-4 FX).7 0020f174: 5b202020 20302e30 30303030 305d2045[0.00] E 0020f184: 6e746572 696e6720 6164645f 61637469ntering add_acti 0020f194: 76655f72 616e6765 28302c20 302c2038ve_range(0, 0, 8 0020f1a4: 31393129 20302065 6e747269 6573206f191) 0 entries o 0020f1b4: 66203235 36207573 65640a3c 343e5b20f 256 used.4[ 0020f1c4: 20202030 2e303030 3030305d 205a6f6e 0.00] Zon 0020f1d4: 65205046 4e207261 6e676573 3a0a3c34e PFN ranges:.4 So it seams to be that the address points to the __log_buf (I hope). Does it mean that when I try to start zImage kernel from u-boot it hangs during uncompressing the image and it does even start booting? Best Regards Mirek On Tue, 28 Aug 2007, Grant Likely wrote: On 8/28/07, Miroslaw Dach [EMAIL PROTECTED] wrote: Hi Grant, Thanks for your answer. I have found in the System.map : c020f0c4 b __log_buf Is the address c020f0c4 relative to the .data segment? 0xc000 are virtual kernel addresses; not physical addresses. If the MMU is still on, then you need to use the virtual address to examine memory. If the MMU is off (such as after reloading u-boot), then you need to change 0xCxxx to 0x0. I understand that when the system hangs I should type in the XMD window stop. Is there anyway to examine the memory from the XMD window? or should I reload the u-boot and examine the memory from u-boot? I don't know; I've never used XMD. Read the XMD documentation. You can do it from u-boot too. g. -- = Miroslaw Dach ([EMAIL PROTECTED]) - SLS/Controls Group PSI - Paul Scherrer Institut CH-5232 Villigen = ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
On 8/28/07, Miroslaw Dach [EMAIL PROTECTED] wrote: 8. I have typed: md 0x20f0c4 100 and it showed me the buffer: 0020f0c4: 3c353e5b 20202020 302e3030 303030305[0.00 0020f0d4: 5d204c69 6e757820 76657273 696f6e20] Linux version 0020f0e4: 322e362e 32312d72 63362028 726f6f742.6.21-rc6 (root 0020f0f4: 40706335 32313529 20286763 63207665@pc5215) (gcc ve 0020f104: 7273696f 6e20342e 302e3229 20233136rsion 4.0.2) #16 0020f114: 204d6f6e 20417567 20323720 31323a33 Mon Aug 27 12:3 0020f124: 373a3038 20434553 54203230 30370a3c7:08 CEST 2007. 0020f134: 363e5b20 20202030 2e303030 3030305d6[0.00] 0020f144: 2058696c 696e7820 4d4c3430 33205265 Xilinx ML403 Re 0020f154: 66657265 6e636520 53797374 656d2028ference System ( 0020f164: 56697274 65782d34 20465829 0a3c373eVirtex-4 FX).7 0020f174: 5b202020 20302e30 30303030 305d2045[0.00] E 0020f184: 6e746572 696e6720 6164645f 61637469ntering add_acti 0020f194: 76655f72 616e6765 28302c20 302c2038ve_range(0, 0, 8 0020f1a4: 31393129 20302065 6e747269 6573206f191) 0 entries o 0020f1b4: 66203235 36207573 65640a3c 343e5b20f 256 used.4[ 0020f1c4: 20202030 2e303030 3030305d 205a6f6e 0.00] Zon 0020f1d4: 65205046 4e207261 6e676573 3a0a3c34e PFN ranges:.4 So it seams to be that the address points to the __log_buf (I hope). Does it mean that when I try to start zImage kernel from u-boot it hangs during uncompressing the image and it does even start booting? Think about what you're looking at. That buffer is ASCII text. Does it look like the entire buffer is displayed, or does it look like there is more? g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
This buffer refers to the kernel which I boot straight from jtag but not u-boot. Below I attach whole buffer printout: = 0x20f0c4 200 0020f0c4: 3c353e5b 20202020 302e3030 303030305[0.00 0020f0d4: 5d204c69 6e757820 76657273 696f6e20] Linux version 0020f0e4: 322e362e 32312d72 63362028 726f6f742.6.21-rc6 (root 0020f0f4: 40706335 32313529 20286763 63207665@pc5215) (gcc ve 0020f104: 7273696f 6e20342e 302e3229 20233136rsion 4.0.2) #16 0020f114: 204d6f6e 20417567 20323720 31323a33 Mon Aug 27 12:3 0020f124: 373a3038 20434553 54203230 30370a3c7:08 CEST 2007. 0020f134: 363e5b20 20202030 2e303030 3030305d6[0.00] 0020f144: 2058696c 696e7820 4d4c3430 33205265 Xilinx ML403 Re 0020f154: 66657265 6e636520 53797374 656d2028ference System ( 0020f164: 56697274 65782d34 20465829 0a3c373eVirtex-4 FX).7 0020f174: 5b202020 20302e30 30303030 305d2045[0.00] E 0020f184: 6e746572 696e6720 6164645f 61637469ntering add_acti 0020f194: 76655f72 616e6765 28302c20 302c2038ve_range(0, 0, 8 0020f1a4: 31393129 20302065 6e747269 6573206f191) 0 entries o 0020f1b4: 66203235 36207573 65640a3c 343e5b20f 256 used.4[ 0020f1c4: 20202030 2e303030 3030305d 205a6f6e 0.00] Zon 0020f1d4: 65205046 4e207261 6e676573 3a0a3c34e PFN ranges:.4 0020f1e4: 3e5b2020 2020302e 30303030 30305d20[0.00] 0020f1f4: 2020444d 41202020 20202020 20202020 DMA 0020f204: 20203020 2d3e2020 20202038 3139310a 0 - 8191. 0020f214: 3c343e5b 20202020 302e3030 303030304[0.00 0020f224: 5d202020 4e6f726d 616c2020 20202020] Normal 0020f234: 20383139 31202d3e 20202020 20383139 8191 - 819 0020f244: 310a3c34 3e5b2020 2020302e 303030301.4[0. 0020f254: 30305d20 6561726c 795f6e6f 64655f6d00] early_node_m 0020f264: 61705b31 5d206163 74697665 2050464eap[1] active PFN 0020f274: 2072616e 6765730a 3c343e5b 20202020 ranges.4[ 0020f284: 302e3030 30303030 5d202020 2020303a0.00] 0: 0020f294: 20202020 20202020 30202d3e 202020200 - 0020f2a4: 20383139 310a3c37 3e5b2020 2020302e 8191.7[0. 0020f2b4: 30303030 30305d20 4f6e206e 6f64652000] On node 0020f2c4: 3020746f 74616c70 61676573 3a2038310 totalpages: 81 0020f2d4: 39310a3c 373e5b20 20202030 2e30303091.7[0.000 0020f2e4: 3030305d 20202044 4d41207a 6f6e653a000] DMA zone: 0020f2f4: 20363320 70616765 73207573 65642066 63 pages used f 0020f304: 6f72206d 656d6d61 700a3c37 3e5b2020or memmap.7[ 0020f314: 2020302e 30303030 30305d20 2020444d 0.00] DM 0020f324: 41207a6f 6e653a20 30207061 67657320A zone: 0 pages 0020f334: 72657365 72766564 0a3c373e 5b202020reserved.7[ 0020f344: 20302e30 30303030 305d2020 20444d41 0.00] DMA 0020f354: 207a6f6e 653a2038 31323820 70616765 zone: 8128 page 0020f364: 732c204c 49464f20 62617463 683a300as, LIFO batch:0. 0020f374: 3c373e5b 20202020 302e3030 303030307[0.00 0020f384: 5d202020 4e6f726d 616c207a 6f6e653a] Normal zone: 0020f394: 20302070 61676573 20757365 6420666f 0 pages used fo 0020f3a4: 72206d65 6d6d6170 0a3c343e 5b202020r memmap.4[ 0020f3b4: 20302e30 30303030 305d2042 75696c74 0.00] Built 0020f3c4: 2031207a 6f6e656c 69737473 2e202054 1 zonelists. T 0020f3d4: 6f74616c 20706167 65733a20 38313238otal pages: 8128 0020f3e4: 0a3c353e 5b202020 20302e30 30303030.5[0.0 0020f3f4: 305d204b 65726e65 6c20636f 6d6d616e0] Kernel comman 0020f404: 64206c69 6e653a20 636f6e73 6f6c653dd line: console= 0020f414: 74747955 4c302c39 36303020 726f6f74ttyUL0,9600 root 0020f424: 3d2f6465 762f6e66 73207277 206e6673=/dev/nfs rw nfs 0020f434: 726f6f74 3d313239 2e313239 2e313434root=129.129.144 0020f444: 2e313133 3a2f6f70 742f656c 646b3431.113:/opt/eldk41 0020f454: 2f707063 5f347878 2c746370 20206970/ppc_4xx,tcp ip 0020f464: 3d3a3a3a 3a766972 74657834 2d6d6972=virtex4-mir 0020f474: 656b3a65 7468303a 64686370 2070616eek:eth0:dhcp pan 0020f484: 69633d31 0a3c363e 5b202020 20302e30ic=1.6[0.0 0020f494: 30303030 305d2058 696c696e 7820494e0] Xilinx IN 0020f4a4: 54432023 30206174 20307834 31323030TC #0 at 0x41200 0020f4b4: 30303020 6d617070 65642074 6f203078000 mapped to 0x 0020f4c4: 46444646 46303030 0a3c343e 5b202020FDFFF000.4[ 0020f4d4: 20302e30 30303030 305d2050 49442068 0.00] PID h 0020f4e4: 61736820 7461626c 6520656e 74726965ash table entrie 0020f4f4: 733a2031 32382028 6f726465 723a2037s: 128 (order: 7 0020f504: 2c203531 32206279 74657329 0a3c343e, 512 bytes).4 0020f514: 5b202020 20302e30 30303237 385d2043[0.000278] C 0020f524: 6f6e736f 6c653a20 636f6c6f 75722064onsole: colour d 0020f534: 756d6d79 20646576 69636520 38307832ummy device 80x2 0020f544: 350a3c34 3e5b2020 2020302e 303030365.4[0.0006 0020f554: 30335d20 44656e74 72792063 6163686503] Dentry cache 0020f564: 20686173 68207461
Linux doesn not boot from u-boot on ML403
in the first case. my bootargs are: console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=virtex4-mirek:eth0:dhcp panic=1 Those bootargs where tested with zImage.elf and seem to be fine. Does somebody has some suggestion? Thank you in advance for any hint on that. Mirek -- View this message in context: http://www.nabble.com/Linux-doesn-not-boot-from-u-boot-on-ML403-tf4335322.html#a12347049 Sent from the linuxppc-embedded mailing list archive at Nabble.com. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
On 8/27/07, Mirek23 [EMAIL PROTECTED] wrote: 4. I am trying to start the kernel = bootm 0x100 ## Booting image at 0100 ... Image Name: Linux-2.6.21-rc6 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:991375 Bytes = 968.1 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK Have you looked in __log_buf for kernel messages? What does your u-boot env look like? Do you have 'console=ttyUL0' or 'console=ttyS0' in the kernel command line? Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
Hi Grant, Thank you for your response. My u-boot bootargs is set to: console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=virtex4-mirek:eth0:dhcp panic=1 where I can find __log_buf for kernel messages? Best Regards Mirek On Mon, 27 Aug 2007, Grant Likely wrote: On 8/27/07, Mirek23 [EMAIL PROTECTED] wrote: 4. I am trying to start the kernel = bootm 0x100 ## Booting image at 0100 ... Image Name: Linux-2.6.21-rc6 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:991375 Bytes = 968.1 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK Have you looked in __log_buf for kernel messages? What does your u-boot env look like? Do you have 'console=ttyUL0' or 'console=ttyS0' in the kernel command line? Cheers, g. -- = Miroslaw Dach ([EMAIL PROTECTED]) - SLS/Controls Group PSI - Paul Scherrer Institut CH-5232 Villigen = ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Linux doesn not boot from u-boot on ML403
On 8/27/07, Miroslaw Dach [EMAIL PROTECTED] wrote: Hi Grant, Thank you for your response. My u-boot bootargs is set to: console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=virtex4-mirek:eth0:dhcp panic=1 Drop the ',9600'. It's irrelevant for uartlite. where I can find __log_buf for kernel messages? Search for __log_buf in System.map (in the kernel source tree). Use a debugger to look at the memory. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
U-boot on ML403
Ming Liu wrote: Dear Frank, I know you are using U-boot on ML403 now. So can you say something about how to configure U-boot as ML403 board? I noticed that in U-boot 1.1.4, there is only ML300 supported. So if I want to configure the board as ML403 and some other customed options(e.g. no EEPROM), what shall I do? Thanks for your help. Regards Ming Ming, I received an updated version of the Xilinx xapp542 directly from Xilinx. We had to sign a non-disclosure agreement before they would send it to me. This update provided the necessary pieces to allow XPS to generate a U-Boot BSP and a modified U-Boot tree with support for additional mlXXX boards. I would recommend contacting Xilinx for this. Sorry I can't be of greater assistance. Frank
U-boot on ML403
Ming Liu wrote: Dear Frank, So you mean, you built your ML403 system with U-Boot supported according to the updated version of xapp542, right? There are NOT some patches open to everyone to include ML403 support into the U-Boot tree, right? If both answers for the two questions are yes, then I have to contact Xilinx to ask for help. Anyway, thanks for your information and reply. Regards Ming Ming, There may be public patches available, but I don't know where to obtain them. I used the patches from Xilinx. Frank
U-boot on ML403
Dear Frank, OK then. I have tried to find the patch. But I failed. So maybe it's better to contact Xilinx. Thanks for your help anyway. Regards Ming From: Frank D Lombardo lombardo at mdivac.com To: Ming Liu eemingliu at hotmail.com CC: linuxppc-embedded at ozlabs.org Subject: Re: U-boot on ML403 Date: Fri, 11 Aug 2006 11:39:59 -0400 Ming Liu wrote: Dear Frank, So you mean, you built your ML403 system with U-Boot supported according to the updated version of xapp542, right? There are NOT some patches open to everyone to include ML403 support into the U-Boot tree, right? If both answers for the two questions are yes, then I have to contact Xilinx to ask for help. Anyway, thanks for your information and reply. Regards Ming Ming, There may be public patches available, but I don't know where to obtain them. I used the patches from Xilinx. Frank _ ?? MSN Messenger: http://messenger.msn.com/cn
U-boot on ML403
Dear Frank, I know you are using U-boot on ML403 now. So can you say something about how to configure U-boot as ML403 board? I noticed that in U-boot 1.1.4, there is only ML300 supported. So if I want to configure the board as ML403 and some other customed options(e.g. no EEPROM), what shall I do? Thanks for your help. Regards Ming _ MSN Explorer: http://explorer.msn.com/lccn
