[U-Boot-Users] 2.6.12 with u-boot-1.1.2 on versatile

Greetings!
System details: Board: Versatile-ARM926Ej-S Cross-toolchain: 3.4.3 Linux kernel: 2.6.12 u-boot: 1.1.2
I have been able to successfully cross-compile u-boot, program it to NOR flash, and run it from the SDRAM.
I have also cross-compiled the kernel to create the vmlinux file. I have used the config file provided in arm.com site for this board:
http://www.arm.com/linux/linux_download.html
I then created uImage using:
# arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux.bin # gzip linux.bin # ./mkimage -A arm -O linux -T kernel -C gzip -a 0xc0008000 -e 0xc0008000 -n "Linux Kernel Image" -d linux.bin.gz uImage
The uImage is programmed at 0x36000000 in NOR flash. But, When I try to run the kernel from u-boot it hangs at the following:
## Booting image at 36000000 ... Image Name: Linux kernel image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1112206 Bytes = 1.1 MB Load Address: c0008000 Entry Point: c0008000 Uncompressing Kernel Image ... OK
Starting kernel ...
When I looked through the debugger (Lauterbach), it hung at a virtual address inside panic.c.
If anyone can tell me as to what I am doing wrong, and how I can get the kernel up and running on this board, it will be really helpful.
Thanks,
K Shakthi
-- proudly anti-micro$oft ------------------------------------------------------------ Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shaks@shakthimaan.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India ------------------------------------------------------------
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Shakthi Kannan shakthimaan@yahoo.com wrote:
# ./mkimage -A arm -O linux -T kernel -C gzip -a 0xc0008000 -e 0xc0008000 -n "Linux Kernel Image" -d linux.bin.gz uImage
Try "-a 0x7fc0 -e 0x8000".
The uImage is programmed at 0x36000000 in NOR flash. But, When I try to run the kernel from u-boot it hangs at the following:
You should run "cp 0x36000000 0x7fc0 <size>" before "bootm".

Dear Catalin,
in message tnxoe96d7zy.fsf@arm.com you wrote:
Shakthi Kannan shakthimaan@yahoo.com wrote:
# ./mkimage -A arm -O linux -T kernel -C gzip -a 0xc0008000 -e 0xc0008000 -n "Linux Kernel Image" -d linux.bin.gz uImage
Try "-a 0x7fc0 -e 0x8000".
The uImage is programmed at 0x36000000 in NOR flash. But, When I try to run the kernel from u-boot it hangs at the following:
You should run "cp 0x36000000 0x7fc0 <size>" before "bootm".
Sounds like vodoo programming to me. Or do you have any rational explanation why these bogus statements should help?
Best regards,
Wolfgang Denk

Wolfgang Denk wd@denx.de wrote:
in message tnxoe96d7zy.fsf@arm.com you wrote:
You should run "cp 0x36000000 0x7fc0 <size>" before "bootm".
Sounds like vodoo programming to me. Or do you have any rational explanation why these bogus statements should help?
True, but that's how I managed to get it working. Is bootm supposed to also copy the image from flash before starting it? I had the impression that it doesn't do this.
Catalin

In message tnxackppyqc.fsf@arm.com you wrote:
True, but that's how I managed to get it working. Is bootm supposed to also copy the image from flash before starting it? I had the impression that it doesn't do this.
May I suggest to read the documentation before relying on impressions?
Yes, of course it does that. Guess what the meaning of the "load address" and "entry point" parameters is?
Best regards,
Wolfgang Denk

Hi!
if you are in virtual address space, then you should have console output on the serial port. So it looks for me that your kernel configuration is missing the command line parameter. I had a similar problem with my custom board. It run in a kernel panic because of a missing root file system and rebooted after 3 minutes.
My suggest to you configure in u-boot the command line parameter to pass it trough the kernel. For that you need to edit your custom board file in u-boot\include\configs<yourboard>.h with following:
#define CONFIG_BOOTARGS "console=ttyS1,115200 root=/dev/ram rw"
The console definition is for the console output. Configure ttyS0 for UART0 or ttyS1 for UART1.
Or you configure your kernel command line parameter in linuxkernel\arch\arm\configs<yourboard>_defconfig
CONFIG_CMDLINE="console=ttyS1,115200"
Then you should have console output and could see where your linux kernel hangs.
Best regards,
David
-----Ursprüngliche Nachricht----- Von: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]Im Auftrag von Shakthi Kannan Gesendet: Mittwoch, 13. Juli 2005 16:45 An: u-boot-users@lists.sourceforge.net Betreff: [U-Boot-Users] 2.6.12 with u-boot-1.1.2 on versatile
Greetings!
System details: Board: Versatile-ARM926Ej-S Cross-toolchain: 3.4.3 Linux kernel: 2.6.12 u-boot: 1.1.2
I have been able to successfully cross-compile u-boot, program it to NOR flash, and run it from the SDRAM.
I have also cross-compiled the kernel to create the vmlinux file. I have used the config file provided in arm.com site for this board:
http://www.arm.com/linux/linux_download.html
I then created uImage using:
# arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux.bin # gzip linux.bin # ./mkimage -A arm -O linux -T kernel -C gzip -a 0xc0008000 -e 0xc0008000 -n "Linux Kernel Image" -d linux.bin.gz uImage
The uImage is programmed at 0x36000000 in NOR flash. But, When I try to run the kernel from u-boot it hangs at the following:
## Booting image at 36000000 ... Image Name: Linux kernel image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1112206 Bytes = 1.1 MB Load Address: c0008000 Entry Point: c0008000 Uncompressing Kernel Image ... OK
Starting kernel ...
When I looked through the debugger (Lauterbach), it hung at a virtual address inside panic.c.
If anyone can tell me as to what I am doing wrong, and how I can get the kernel up and running on this board, it will be really helpful.
Thanks,
K Shakthi
--
proudly anti-micro$oft ------------------------------------------------------------ Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shaks@shakthimaan.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India ------------------------------------------------------------
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

In message 000001c58847$041ef380$f201a8c0@SN7606 you wrote:
if you are in virtual address space, then you should have console output on the serial port. So it looks for me that your kernel configuration is missing the command line parameter. I had a similar problem with my custom
This is a Linux issue (hint, hint).
board. It run in a kernel panic because of a missing root file system and rebooted after 3 minutes.
My suggest to you configure in u-boot the command line parameter to pass it trough the kernel. For that you need to edit your custom board file in u-boot\include\configs<yourboard>.h with following:
You never have to edit any file just to set or change an environment variable.That's what the "setevn"/ "saveenv" commands are for.
And BTW: the file name you listed contains several illegal backslash escape sequences.
participants (4)
-
Catalin Marinas
-
David Grab
-
Shakthi Kannan
-
Wolfgang Denk