[U-Boot-Users] mpc8260 serial console works under uboot, but not under linux
Hi, We have ported u-boot on a mpc8260 based design of ours. We try to boot linux on it (built with TQM8260_defconfig), as a first step. But when we use the u-boot "bootm" command to boot linux from flash, we get nothing displayed after the kernel is uncompressed and jumped into. I know there is a FAQ: http://www.denx.de/wiki/view/DULG/LinuxHangsAfterUncompressingKernel But I don't think it applies as using the BDI2000 we can trace the kernel running all the way until around the point where it starts the init process. We were surprised to see that a "make uImage" would use the vmlinux.gz kernel (linked at 0xc000.0000) and not the zImage.elf(linked at 0x0040.0000), which includes the files in arch/ppc/boot/simple. The serial console is initialized and handled in ./arch/ppc/boot/simple/m8260_tty.c, and we suspect that since this is not included in vmlinux, that is the reason why we don't see any messages. Should we try to somehow add it to vmlinux (if this is possible)?
I know this is not the list, but why is the linux make file is generating these two different files? My guess is that zImage is for systems with no u-boot bootloader. Thanks a lot, -jf simon
[bmc@Linux188 linux-2.6.15.1]$ make CHK include/linux/version.h CHK include/linux/compile.h CHK usr/initramfs_list UIMAGE arch/ppc/boot/images/uImage Image Name: Linux-2.6.15.1 Created: Tue Mar 14 07:01:49 2006 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 869873 Bytes = 849.49 kB = 0.83 MB Load Address: 0x00000000 Entry Point: 0x00000000 Image: arch/ppc/boot/images/uImage is ready AS arch/ppc/boot/simple/head.o AS arch/ppc/boot/simple/relocate.o CC arch/ppc/boot/simple/misc-embedded.o CC arch/ppc/boot/simple/embed_config.o arch/ppc/boot/simple/embed_config.c:29: warning: 'bdinfo' defined but not used arch/ppc/boot/simple/embed_config.c:415: warning: 'clk_8260' defined but not use d arch/ppc/boot/simple/embed_config.c:457: warning: 'clk_8280' defined but not use d CC arch/ppc/boot/simple/m8260_tty.o ppc_6xx-objcopy -O elf32-powerpc \ --add-section=.image=arch/ppc/boot/images/vmlinux.gz \
--set-section-flags=.image=contents,alloc,load,readonly,data \ arch/ppc/boot/simple/dummy.o arch/ppc/boot/simple/image.o ppc_6xx-ld -m elf32ppc -T /home/bmc/tools/eldk4.0/ppc_6xx/usr/src/linux-2.6.15.1 /arch/ppc/boot/ld.script -Ttext 0x00400000 -Bstatic -o arch/ppc/boot/simple/zvml inux arch/ppc/boot/simple/head.o arch/ppc/boot/simple/relocate.o arch/ppc/boot/s imple/misc-embedded.o arch/ppc/boot/simple/embed_config.o arch/ppc/boot/simple/m 8260_tty.o arch/ppc/boot/simple/image.o arch/ppc/boot/common/lib.a arch/ppc/boot /lib/lib.a ppc_6xx-objcopy -O elf32-powerpc arch/ppc/boot/simple/zvmlinux arch/ppc/boot/sim ple/zvmlinux -R .comment -R .stab \ -R .stabstr -R .ramdisk cp -f arch/ppc/boot/simple/zvmlinux arch/ppc/boot/images/zImage.elf rm -f arch/ppc/boot/simple/zvmlinux Building modules, stage 2. MODPOST [bmc@Linux188 linux-2.6.15.1]$
___________________________________________________________________________ Nouveau : t�l�phonez moins cher avec Yahoo! Messenger ! D�couvez les tarifs exceptionnels pour appeler la France et l'international. T�l�chargez sur http://fr.messenger.yahoo.com
Am Dienstag, 14. März 2006 16:28 schrieb jfaslist:
Hi, We have ported u-boot on a mpc8260 based design of ours. We try to boot linux on it (built with TQM8260_defconfig), as a first step. But when we use the u-boot "bootm" command to boot linux from flash, we get nothing displayed after the kernel is uncompressed and jumped into.
Hi,
is there a VGA adapter in your system with linux driver support enabled? If yes, you have to use the kernel parameter 'console=device,options' to use a serial port as console ... see linux/Documentation/serial-console.txt
best regards, Stephan Linz
I know there is a FAQ: http://www.denx.de/wiki/view/DULG/LinuxHangsAfterUncompressingKernel But I don't think it applies as using the BDI2000 we can trace the kernel running all the way until around the point where it starts the init process. We were surprised to see that a "make uImage" would use the vmlinux.gz kernel (linked at 0xc000.0000) and not the zImage.elf(linked at 0x0040.0000), which includes the files in arch/ppc/boot/simple. The serial console is initialized and handled in ./arch/ppc/boot/simple/m8260_tty.c, and we suspect that since this is not included in vmlinux, that is the reason why we don't see any messages. Should we try to somehow add it to vmlinux (if this is possible)?
I know this is not the list, but why is the linux make file is generating these two different files? My guess is that zImage is for systems with no u-boot bootloader. Thanks a lot, -jf simon
[bmc@Linux188 linux-2.6.15.1]$ make CHK include/linux/version.h CHK include/linux/compile.h CHK usr/initramfs_list UIMAGE arch/ppc/boot/images/uImage Image Name: Linux-2.6.15.1 Created: Tue Mar 14 07:01:49 2006 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 869873 Bytes = 849.49 kB = 0.83 MB Load Address: 0x00000000 Entry Point: 0x00000000 Image: arch/ppc/boot/images/uImage is ready AS arch/ppc/boot/simple/head.o AS arch/ppc/boot/simple/relocate.o CC arch/ppc/boot/simple/misc-embedded.o CC arch/ppc/boot/simple/embed_config.o arch/ppc/boot/simple/embed_config.c:29: warning: 'bdinfo' defined but not used arch/ppc/boot/simple/embed_config.c:415: warning: 'clk_8260' defined but not use d arch/ppc/boot/simple/embed_config.c:457: warning: 'clk_8280' defined but not use d CC arch/ppc/boot/simple/m8260_tty.o ppc_6xx-objcopy -O elf32-powerpc \ --add-section=.image=arch/ppc/boot/images/vmlinux.gz \
--set-section-flags=.image=contents,alloc,load,readonly,data \ arch/ppc/boot/simple/dummy.o arch/ppc/boot/simple/image.o ppc_6xx-ld -m elf32ppc -T /home/bmc/tools/eldk4.0/ppc_6xx/usr/src/linux-2.6.15.1 /arch/ppc/boot/ld.script -Ttext 0x00400000 -Bstatic -o arch/ppc/boot/simple/zvml inux arch/ppc/boot/simple/head.o arch/ppc/boot/simple/relocate.o arch/ppc/boot/s imple/misc-embedded.o arch/ppc/boot/simple/embed_config.o arch/ppc/boot/simple/m 8260_tty.o arch/ppc/boot/simple/image.o arch/ppc/boot/common/lib.a arch/ppc/boot /lib/lib.a ppc_6xx-objcopy -O elf32-powerpc arch/ppc/boot/simple/zvmlinux arch/ppc/boot/sim ple/zvmlinux -R .comment -R .stab \ -R .stabstr -R .ramdisk cp -f arch/ppc/boot/simple/zvmlinux arch/ppc/boot/images/zImage.elf rm -f arch/ppc/boot/simple/zvmlinux Building modules, stage 2. MODPOST [bmc@Linux188 linux-2.6.15.1]$
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&da... _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Hi, No, we don't use any graphic. We want the console on smc0. Thanks, -jfs
Stephan Linz wrote:
Am Dienstag, 14. März 2006 16:28 schrieb jfaslist:
Hi, We have ported u-boot on a mpc8260 based design of ours. We try to boot linux on it (built with TQM8260_defconfig), as a first step. But when we use the u-boot "bootm" command to boot linux from flash, we get nothing displayed after the kernel is uncompressed and jumped into.
Hi,
is there a VGA adapter in your system with linux driver support enabled? If yes, you have to use the kernel parameter 'console=device,options' to use a serial port as console ... see linux/Documentation/serial-console.txt
best regards, Stephan Linz
I know there is a FAQ: http://www.denx.de/wiki/view/DULG/LinuxHangsAfterUncompressingKernel But I don't think it applies as using the BDI2000 we can trace the kernel running all the way until around the point where it starts the init process. We were surprised to see that a "make uImage" would use the vmlinux.gz kernel (linked at 0xc000.0000) and not the zImage.elf(linked at 0x0040.0000), which includes the files in arch/ppc/boot/simple. The serial console is initialized and handled in ./arch/ppc/boot/simple/m8260_tty.c, and we suspect that since this is not included in vmlinux, that is the reason why we don't see any messages. Should we try to somehow add it to vmlinux (if this is possible)?
I know this is not the list, but why is the linux make file is generating these two different files? My guess is that zImage is for systems with no u-boot bootloader. Thanks a lot, -jf simon
[bmc@Linux188 linux-2.6.15.1]$ make CHK include/linux/version.h CHK include/linux/compile.h CHK usr/initramfs_list UIMAGE arch/ppc/boot/images/uImage Image Name: Linux-2.6.15.1 Created: Tue Mar 14 07:01:49 2006 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 869873 Bytes = 849.49 kB = 0.83 MB Load Address: 0x00000000 Entry Point: 0x00000000 Image: arch/ppc/boot/images/uImage is ready AS arch/ppc/boot/simple/head.o AS arch/ppc/boot/simple/relocate.o CC arch/ppc/boot/simple/misc-embedded.o CC arch/ppc/boot/simple/embed_config.o arch/ppc/boot/simple/embed_config.c:29: warning: 'bdinfo' defined but not used arch/ppc/boot/simple/embed_config.c:415: warning: 'clk_8260' defined but not use d arch/ppc/boot/simple/embed_config.c:457: warning: 'clk_8280' defined but not use d CC arch/ppc/boot/simple/m8260_tty.o ppc_6xx-objcopy -O elf32-powerpc \ --add-section=.image=arch/ppc/boot/images/vmlinux.gz \
--set-section-flags=.image=contents,alloc,load,readonly,data \ arch/ppc/boot/simple/dummy.o arch/ppc/boot/simple/image.o ppc_6xx-ld -m elf32ppc -T /home/bmc/tools/eldk4.0/ppc_6xx/usr/src/linux-2.6.15.1 /arch/ppc/boot/ld.script -Ttext 0x00400000 -Bstatic -o arch/ppc/boot/simple/zvml inux arch/ppc/boot/simple/head.o arch/ppc/boot/simple/relocate.o arch/ppc/boot/s imple/misc-embedded.o arch/ppc/boot/simple/embed_config.o arch/ppc/boot/simple/m 8260_tty.o arch/ppc/boot/simple/image.o arch/ppc/boot/common/lib.a arch/ppc/boot /lib/lib.a ppc_6xx-objcopy -O elf32-powerpc arch/ppc/boot/simple/zvmlinux arch/ppc/boot/sim ple/zvmlinux -R .comment -R .stab \ -R .stabstr -R .ramdisk cp -f arch/ppc/boot/simple/zvmlinux arch/ppc/boot/images/zImage.elf rm -f arch/ppc/boot/simple/zvmlinux Building modules, stage 2. MODPOST [bmc@Linux188 linux-2.6.15.1]$
___________________________________________________________________________ Nouveau : t�l�phonez moins cher avec Yahoo! Messenger ! D�couvez les tarifs exceptionnels pour appeler la France et l'international. T�l�chargez sur http://fr.messenger.yahoo.com
In message 4416E11D.6060807@yahoo.fr you wrote:
We have ported u-boot on a mpc8260 based design of ours. We try to boot linux on it (built with TQM8260_defconfig), as a
This is off topic here. Please post to a Linux related list.
But I can tell you so much: just chosing a random board configuration and hoping it would work is always a pretty reliable way for a big disappointment. You actually have to *port* Linux to your hardware.
We were surprised to see that a "make uImage" would use the vmlinux.gz kernel (linked at 0xc000.0000) and not the zImage.elf(linked at 0x0040.0000), which includes the files in arch/ppc/boot/simple.
Why are you surprised?
The serial console is initialized and handled in ./arch/ppc/boot/simple/m8260_tty.c, and we suspect that since this is not included in vmlinux, that is the reason why we don't see any messages.
You misunderstand. The Linux bootstrap loader is never used with U-Boot.
Should we try to somehow add it to vmlinux (if this is possible)?
Don't.
I know this is not the list, but why is the linux make file is generating these two different files? My guess is that zImage is for systems with no u-boot bootloader.
Right.
Best regards,
Wolfgang Denk
participants (3)
-
jfaslist -
Stephan Linz -
Wolfgang Denk