From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ilya Yanok Date: Tue, 13 Dec 2011 23:44:11 +0400 Subject: [U-Boot] [PATCH V4 2/2] mcx: support for HTKW mcx board In-Reply-To: References: <1323731713-5460-1-git-send-email-yanok@emcraft.com> <1323731713-5460-3-git-send-email-yanok@emcraft.com> <4EE7A3BC.2040304@emcraft.com> Message-ID: <4EE7AB0B.4010006@emcraft.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Tom, On 13.12.2011 23:30, Tom Rini wrote: >>>> +#define CONFIG_SYS_TEXT_BASE 0x80008000 >>> [snip] >>>> +#define CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR 0x300 /* address 0x60000 */ >>>> +#define CONFIG_SYS_MMC_SD_FAT_BOOT_PARTITION 1 >>>> +#define CONFIG_SPL_FAT_LOAD_PAYLOAD_NAME "u-boot.img" >>> >>> You're able to have CONFIG_SYS_TEXT_BASE that low and not have the >>> corruption problem devkit8000 had? >> >> No, I can't see any problems. I have to say I can't do _real_ MMC boot, >> as my board lacks the required jumper, so I'm testing it but starting >> SPL from NAND, rewriting omap3_boot_device to be MMC with BDI and >> running it further. It reads u-boot.img from MMC and starts it without >> any problem. > > Well, is it just your board that's missing the jumper, or the MCX HTWK > lacks the jumper? If the latter, just drop the MMC bits out :) I can't ;) this was an explicit requirement. As for the devkit8000 boot problem, I have BSS set up close to the top of the RAM. Probably that's the reason I don't see any problems. Unfortunately, I can't recall why I had moved BSS... It clashed with something but I don't remember the details. Regards, Ilya.