[U-Boot-Users] Booting problems for Integrator/CP+ARM920T
Hi,
I have an ARM Integrator/CP board(s) which contains an ARM920T macrocell. I have been trying to use U-Boot(1.1.2) to boot linux2.6.9 (with a patch applied from ARM's website) on this system. As i understand it, U-Boot only supports the ARM926EJS macrocell as the default configuration with the Integrator/CP but i was hoping the same boot process would work with the ARM920T macrocell??
The default kernel command string i use when compiling/building/installing the kernel is: CONFIG_CMDLINE="root=/dev/ram0 video=vc:1-2clcdfb console=ttyAMA0 mem=128M ramdisk_size=17408 initrd=0x24500000,6980391"
I then generate the kernel image using: arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux-2.6.9.bin mkimage -n '2.6.9 Kernel Image' -A arm -O linux -T kernel -C none -a 0x7fc0 -e 0x7fc0 -d linux-2.6.9.bin linux-2.6.9.img
I also generate a RAMDisk image in a similar way.
I load the U-Boot, kernel and RAMDisk images into FLASH at the following addresses: U-Boot image: 0x24000000 kernel image: 0x242C0000 ramdisk image: 0x24500000
Using U-Boot i set the bootargs variable as: setenv bootargs root=/dev/ram0
However when i try to boot the kernel using 'bootm 242c0000 24500000' i get the following message: ## Booting image at 242c0000 ... ... Load Address: 00007fc0 Entry Point: 00007fc0 OK ## Loading Ramdisk Image at 24500000 ... ... ... Load Address: 00000000 Entry Point: 00000000
Starting Kernel ...
Then nothing - the boot process freezes.
Does anybody know what i am doing wrong?? I have tried numerous things such as copying the kernel image to RAM and booting from there but i always get the same message as above. Do i have to configure and build U-Boot to support the ARM920T macrocell with the Integrator/CP??
Any information greatly appreciated, Regards, Alan.
In message 41108D1A000E576D@hawk.dcu.ie you wrote:
I have an ARM Integrator/CP board(s) which contains an ARM920T macrocell. I have been trying to use U-Boot(1.1.2) to boot linux2.6.9 (with a patch applied from ARM's website) on this system. As i understand it, U-Boot only supports the ARM926EJS macrocell as the default configuration with the Integrator/CP but i was hoping the same boot process would work with the ARM920T macrocell??
What exactly do you want to ask? Why are you using code for a ARM926EJS when in fact you have a ARM920T processor? You should use (or create) a port of the ARM920T code for your board.
mkimage -n '2.6.9 Kernel Image' -A arm -O linux -T kernel -C none -a 0x7fc0 -e 0x7fc0 -d linux-2.6.9.bin linux-2.6.9.img
Are you sure that 0x7fc0 is a good choice? Do you have RAM starting at physical address 0?
Starting Kernel ...Then nothing - the boot process freezes.
Does anybody know what i am doing wrong?? I have tried
I have the feeling that you might have missed to read the FAQ, especially http://www.denx.de/twiki/bin/view/DULG/LinuxKernelIgnoresMyBootargs
message as above. Do i have to configure and build U-Boot to support the ARM920T macrocell with the
If you have a ARM920T processor, then yes, you will need a ARM920T configuration.
Best regards,
Wolfgang Denk
Hi,
I am still having trouble booting Linux on the ARM Integrator/CP with an ARM920T macrocell. I have tried Peter Pearse's Patches which enable U-Boot to support the ARM920T macrocell but i can get message as before:
Starting Kernel ...Then nothing - the boot process freezes.
I have the feeling that you might have missed to read the FAQ, especially http://www.denx.de/twiki/bin/view/DULG/LinuxKernelIgnoresMyBootargs
I have checked the above note but this is already the default with Linux-2.6.9 (i.e. i dont have to modify anything here for ARM).
I am trying to boot the kernel(+ramdisk) from RAM so when building the kernel i use the following setting:
CONFIG_CMDLINE="console=ttyUA0 mem=128M root=/dev/ram0 video=vc:1-2clcdfb ramdisk_size=17408 initrd=0x24500000,6980391
And in U-Boot i set: setenv bootargs console=ttyUA0 mem=128M root=/dev/ram0 video=vc:1-2clcdfb
Is this correct? Even if i just try to boot the kernel ignoring the RAMDisk i still get "Starting kernel ..." then freeze nothing happens.
Any info appreciated, Regards, Alan.
"Alan Casey" alan.casey5@mail.dcu.ie writes:
I am still having trouble booting Linux on the ARM Integrator/CP with an ARM920T macrocell. I have tried Peter Pearse's Patches which enable U-Boot to support the ARM920T macrocell but i can get message as before:
Starting Kernel ...Then nothing - the boot process freezes.
Are you sure it is not a problem with the kernel?
CONFIG_CMDLINE="console=ttyUA0 mem=128M root=/dev/ram0 video=vc:1-2clcdfb ramdisk_size=17408 initrd=0x24500000,6980391
And in U-Boot i set: setenv bootargs console=ttyUA0 mem=128M root=/dev/ram0 video=vc:1-2clcdfb
Try "console=ttyAMA0" (and configure the terminal to 38400 8N1), you might be able to get some kernel messages.
Catalin
In message 41108D1A000E81D2@hawk.dcu.ie you wrote:
http://www.denx.de/twiki/bin/view/DULG/LinuxKernelIgnoresMyBootargs
I have checked the above note but this is already the default with Linux-2.6.9 (i.e. i dont have to modify anything here for ARM).
But...
I am trying to boot the kernel(+ramdisk) from RAM so when building the kernel i use the following setting:
CONFIG_CMDLINE="console=ttyUA0 mem=128M root=/dev/ram0 video=vc:1-2clcdfb ramdisk_size=17408 initrd=0x24500000,6980391
... why do you encode a kernel command line at all when this information gets passed to the kernel by U-Boot?
setenv bootargs console=ttyUA0 mem=128M root=/dev/ram0 video=vc:1-2clcdfb
Is this correct? Even if i just try to boot the kernel ignoring the RAMDisk i still get "Starting kernel ..." then freeze nothing happens.
This doesn't make sense to me. I recomnmend to check the passing of the boot arguments again, as outlined in the FAQ mentioned above. Attach a debugger and check what your kernel is doing. At least trry a post-mortemn dump of the log buffer (see FAQ).
Anyway: I don't see how all this is related to U-Boot. Seems to be kernel problem and as such somewhat off-topic here.
Best regards,
Wolfgang Denk
Hi,
Jean-Paul Saman originally raised this issue before Christmas:
I am trying to boot on an ARM-Integrator AP a linux-2.6.9 kernel with
u-boot. I tried u-boot-1.1.1 stable and cvs, but both result in "data
abort" just at the point of "Starting kernel .... ". Here is the dump
from
minicom:
Integrator-AP # bootm 24400000 Boot reached stage 1 ## Booting image at 24400000 ... Boot reached stage 2 Boot reached stage 3 Image Name: Linux-2.6.9 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1216080 Bytes = 1.2 MB Load Address: 00008000 Entry Point: 00008000 Boot reached stage 4 Boot reached stage 5 Boot reached stage 6 OK Boot reached stage 7 Boot reached stage 8 Boot reached stage 14 No initrd Boot reached stage 15 ## Transferring control to Linux (at address 00008000) ...
Starting kernel ...
data abort pc : [<0000801c>] lr : [<0100bcbc>] sp : 00fd7bd4 ip : 00fd7bc4 fp : 00fd7c10 r10: 00000000 r9 : 00fd7c84 r8 : 00fd7fdc r7 : 0100f1b4 r6 : 0100f1b4 r5 : 00000000 r4 : 24400040 r3 : e1a00001 r2 : 00000100 r1 : e1a00000 r0 : 00000000 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ...
I have an Integrator/CP board which contains an ARM920T macrocell but i get a similar message to the above. From the mailing list archives it appears this issue was not resolved?? If it was let me know how to fix it please.
Regards&Thanks, Alan.
participants (3)
-
Alan Casey -
Catalin Marinas -
Wolfgang Denk