Re: [U-Boot-Users] U-Boot and S3c2410
I'm far from an expert on the matter ;) But I would try to set the addresses to 0x30000000 then. The kernel will be expanded to RAM first and then a jump will be made to the address in the RAM to start executing the kernel.
In my situation, I used 0x0 as start/entry. RAM starts on that address too.
Regards, Gerrit
On Mon, 2004-02-23 at 16:20, asnua@eircom.net wrote:
So what is the difference between the load and entry addresses? All of the examples I've seen have the load and entry addresses set to be the same...ish. 0x00000000 & 0x0000000c for PPC In my case my SDRAM starts at 0x30000000 and ends at 0x33FFFFFF. My Flash and hence U-Boot is at 0x00.
Does the load and entry address vary depending on whether you are using vmlinux/vmlinux compressed/zImage?
Thanks, Dave
In message 1077551762.4835.50.camel@nios you wrote:
I'm far from an expert on the matter ;) But I would try to set the addresses to 0x30000000 then. The kernel will
This depends on how the kernel was linked.
be expanded to RAM first and then a jump will be made to the address in the RAM to start executing the kernel.
In my situation, I used 0x0 as start/entry. RAM starts on that address too.
This is correct on PowerPC, but wrong on all other systems.
The address to be used is defined in the Linux kernel's linker commands / scripts; seach which value of PTEXTADDR gets defined in "arch/arm/Makefile" for your board; in your "arch/arm/boot/Makefile" you should then have a build target like this:
uImage: compressed/piggy.gz mkimage -A arm -O linux -T kernel -C gzip \ -a $(PTEXTADDR) -e $(PTEXTADDR) \ -n 'ARM Linux-$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)' \ -d compressed/piggy.gz $@
Best regards,
Wolfgang Denk
participants (2)
-
Gerrit Van de Velde -
Wolfgang Denk