I'm looking ahead at this point. My custom DM6467T product will use NAND containing UBL, U-Boot, Kernel, and File System objects. Right now, I've tested and gotten all of the ducks in a row to be able to program each of these separately, using three DIFFERENT methods. That's too painful for production. What should I do for production? I'm thinking to somehow make a full image of NAND that includes all four objects. Then I would use the same CCS/nand_flash_writer.out method that I use for UBL and U-Boot. (Alternatively, I know there's a method that uses the serial port, but I had trouble with it an the past. Besides that, I'm thinking it can't be used for the first step with a brain-dead ARM anyway.)
Any other suggestions?
Any suggestions on how an easy way to build the full image? (Cobble together parts on a host, or read out the NAND of a working DM6467T system? I think both require a special program. One concatenates images, the other I would call nand_flash_reader.out)
There's also the Altera CPLD that needs separate programming, of course. But it would be nice to have only two steps to go through. [EDIT:] Oh, there's the MAC address in EEPROM. I guess that makes THREE places to program. Still, three is better than six...
Thanks,
Helmut
