• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 378 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Saving Environment Variables

Chris Rhodin
Prodigy 40 points

I'm building u-boot according to the instructions in "4AI.1.7_OMAP4_Icecream_Sandwich_Release_Notes".

git clone git://git.omapzoom.org/repo/u-boot.git u-boot
cd u-boot
git checkout 83ec135fba56de2567f93a0b79128f0316470338
make distclean
make ARCH=arm omap44XXtablet_config (for Blaze_Tablet)
make ARCH=arm omap4430sdp_config (for Blaze)
make 2>&1 |tee ${MYDROID}/logs/u-boot_make.out

When built with this configuration saving the u-boot environment variables to eMMC is disabled.  Is there an issue that requires this to be disabled?  I'd like to reenable this capability for use with a Blaze running Android.

Are there any eMMC partitioning requirements to support this?

Thanks,

Chris Rhodin

  • 0
    TI__Expert 8055 points

    Chris,

    Yes, in order to save the environment variables to the eMMC, you would need to add a separate environment partition to eMMC.  

    Are you booting from eMMC?  If so, the bootargs are already wrapped into your boot.img, so they don't need to be saved separately to the eMMC.  

    Alternatively, you could specify the bootargs in the u-boot configuration file, such as u-boot/include/configs/omap4430sdp.h (#define CONFIG_BOOTARGS ...).

    Regards,
    Gina