Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I started studying emebedded device on a freescale mx5x board, and I am now exploring the boot-mods of the board. depending on the boot-mod choosed, the proper uboot image is needed.
for the mmc boot-mod, the image is uboot-no-padding.bin, which is generated from uboot.bin.
so , my questions :
why is no-padding uboot needed,what is the deffence between the two images ?
Please help, thanks
I am just guessing but normally uboot is put on “naked” flash, where every write happen in erase block size quanta. Thus it makes sense to pad the uboot.bin image to erase block size. MMC is flash based, but the flash is managed by firmware, so you don’t know (or care) about erase block sizes, hence the padding just makes the image bigger for no reason.