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.

Code Composer flash burning on OMAP 35xx

Other Parts Discussed in Thread: CODECOMPOSER

Apologies if this is a dumb question - but I haven't seen it addressed in the FAQ.  Also if this is the wrong forum - wasn't sure to post here or in the OMAP3 group.

We have existing F28xx-based product.  On the manufacturing line, they're used to hooking up the JTAG cable, downloading the firmware image (using CodeComposer Tools->F28xx On-chip Flash Programmer), and they're done.

Now we're looking at an OMAP35xx-based product.  First time we've used this processor.

Our manufacturing folks would like the same kind of process - when they get a fresh new board off the line with virgin flash, they need to load up the flash, which they're used to doing over JTAG, with minimal operator intervention (just a couple clicks in Code Composer).

Problem is, I don't see where CodeComposer has a similar capability for burning on-board flash for the OMAP35xx like it does for the F28xx.

Is there a way to use CodeComposer (we're currently on 3.3) to burn x-loader, u-boot, Linux kernel, filesystem, etc. in flash directly without first booting the target board into u-boot?

What kind of process would be used on, say, a freshly built Beagleboard or EVM board (assuming you take off the MMC connector)?


Thx for any advice!

Ken