I'm developing a single-purpose DM6467T product that does nothing but automatically run a single codec, that's intended to sit in the middle of a video input/output stream. I'm not, but imagine I'm doing chroma keying to put the weather girl in front of the weather map. (Hmmm... an existing complete chroma keying app for the DaVinci would be a good starting point for me if someone has one to share.)
I'm coming around to believing the following: All I need is a [custom?] NAND memory image with associated NAND writing program and instructions. The NAND memory image should contain an appropriate UBL, U-Boot, and a FILE SYSTEM image (within NAND, I have no hard disk). The FILE SYSTEM should contain some type of autorun file that's automatically run when Linux loads. This something should lead to executing my codec, with no intervening user input since power up.
The fact that my codec is unique means the NAND image is at least partially custom, for the FILE SYSTEM portion. The fact that my hardware has no hard disk suggests that U-Boot or whatever might be a little customized too.
Finally, within all this, I would love to have a CCS project that's ready-to-go in compiling a generic or do-nothing codec, along with instructions for how to "connect" this codec to my boot above. Then I'll take my legacy codec source code and insert it, rebuild the codec, rebuild the NAND memory image, and write it to the EVM.
Thusly, the EVM will then boot up and without intervening user input start showing on the video output the result of my codec action on the video input.
MIGHT I BE SO FORTUNATE that the right person, perhaps within TI, finds this post. This person has already done all the NAND boot stuff, including hopefully file system, and can just plop me right into position, ready to run. Even better, they or the next person within TI has a project shell I can use for my codec work. After all, all that I'm really interested in is doing the codec work.
Thanks very much, with fingers crossed.
-Helmut