More info.. Below is what I see on bootup.
My env is at 0x100000 from base of sd card. It seems something happened on the hash insert. >>>>>>>>>>>>> Boot Log >>>>>>>>>>>>> U-Boot SPL 2013.01.01 (May 02 2014 - 11:49:21) BOARD : Altera SOCFPGA Cyclone V Board SDRAM: Initializing MMR registers SDRAM: Calibrating PHY SEQ.C: Preparing to start memory calibration SEQ.C: CALIBRATION PASSED ALTERA DWMMC: 0 U-Boot 2013.01.01 (Sep 03 2014 - 15:12:29) CPU : Altera SOCFPGA Platform BOARD : Altera SOCFPGA Cyclone V Board DRAM: 512 MiB MMC: ALTERA DWMMC: 0 env offset 1048576 CRC from Header 0x6cf572d5 Computed CRC 0x6cf572d5 " (type: m)lags type check failure for "ethaddr" <= "04:25:fe:ed:00:18 " into hash tableinsert "ethaddr=04:25:fe:ed:00:18 " (type: m)lags type check failure for "ethaddr" <= "00:b0:19:00:01:02 " into hash tableinsert "ethaddr=00:b0:19:00:01:02 In: serial Out: serial Err: serial Net: mii0 Warning: failed to set MAC address Hit any key to stop autoboot: 0 reading u-boot.scr **Unable to read file u-boot.scr Optional boot script not found. Continuing to boot normally ' - try 'help'd ' ' - try 'help'd 'fatload ' - try 'help'd 'fatload " not definedcboot From: Hannes Petermaier <[email protected]> To: "Peter A. Bigot" <[email protected]>, Cc: [email protected], Naitik Amin <[email protected]> Date: 09/03/2014 10:14 AM Subject: Re: [U-Boot] uboot env in mmc partition > > On 09/03/2014 07:54 AM, Naitik Amin wrote: > > Hi Hannes, > > > > So I did as you had indicated and made some progress, so now, my #defines > > look as below. > > #define CONFIG_SYS_MMC_ENV_DEV 0 /* device 0 */ > > #define CONFIG_ENV_OFFSET 0x21900000 > > > > I calculated the env offset from the block number it was on based on the > > first block number of the partition. > > > > Doing this on uboot startup, I dont get the warning saying, using default > > environment. Neither it complained abt crc error. So it liked it seems. > > But what it did is it trashed the partition which had my dtb and zImage. > > Its a completely different partition. So after that, the bootup gets > > halted. Any ideas ? What may have trashed the partition ? > > Look at: http://www.mail-archive.com/[email protected]/msg146396.html > > and see if that's relevant, specifically the second patch which restores > the mmc device offset calculations to the values that correspond to the > partition number that's represented in the device structure. > > Peter Hi Peter, i don't think that your patch has influence on this issue, due to no partition switching is done anymore. Further i would like to check your patch series, i am not sure if there is everything ok. I will do so tommorow - i am right in thinking that you are using MMC not eMMC ? best regards, Hannes
_______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
