From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Sat, 09 Oct 2010 11:23:45 +0200 Subject: [U-Boot] new uboot with relocation change cannot boot when download the bin file to different address than TEXT_BASE In-Reply-To: References: <4CB01D2A.1000708@free.fr> <4CB0238F.8090702@free.fr> <4CB02E65.70205@free.fr> Message-ID: <4CB034A1.4010006@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le 09/10/2010 11:08, Lei Wen a ?crit : > Ok, I know what the difference between our opinion now... > You means the uboot should always loaded to TEXT_BASE(for nand case, > as you said). > So when we run to board_init_f, we don't need any relocation. > > I am just feel put the code arrange like this would lose a good > feature as original, tftp the uboot to > a different place and use the go command to debug it. This does not lose said feature. You can still disable relocation altogether by defining CONFIG_SKIP_RELOCATE_UBOOT (watch out then; you're responsible for linking u-boot for its intended *final* location). > Another question here, why the original implementation now call as > CONFIG_SYS_ARM_WITHOUT_RELOC? Means "this ARM build is without relocation", which is what the option does. > I think CONFIG_SYS_ARM_WITH_RELOC is correct, for it do the relocation > at the very begining. :-p Read the code carefully. You'll see that the old code is used when CONFIG_SYS_ARM_WITHOUT_RELOC is defined, and the new (reloc) code used when CONFIG_SYS_ARM_WITHOUT_RELOC is not define. > Best regards, > Lei Amicalement, -- Albert.