We're working with Android on the AM3517 EVM (and also on our own hardware platform), and are now moving from an SD boot to a NAND boot. We're pursuing this with UBIFS, feeling the kernel's UBIFS built-in support is a key advantage over YAFFS2.
But, the NAND boot didn't come right up, leading us to a couple of questions to be sure we're on the right track.
1) The TI 2.3.4-2.1 User Guide gives this example for creating a UBIFS image:
$ sudo mkfs.ubifs/mkfs.ubifs -r <path_to_rootfs>/ -m 2048 -e 126976 -c X -o ubifs.img
where the -c argument is the "maximum logical erase block count". Why is this based on the full NAND device size? We would have expected UBIFS to stay within the bounds of the NAND segment assigned for its use, meaning only the max size of the UBIFS segment matters, rather than the full NAND device size.
2) Is there a recommended best approach for burning the ubifs image to NAND? Supposedly it can be done either via U-Boot (Flashboot or u-boot console) or Linux (ubiformat). I've seen postings saying the Linux approach is more dependable, and that doesn't surprise me since the Linux tools apparently come from the UBIFS creators. But, I'd like some perspective on whether the Linux preference is just someone's personal preference, or whether Linux is in fact the safest way. I realize some people may have operational preferences for one or the other, but I'm more intested in which has the best chance of working properly.
Thanks,
Ron