• Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 308 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OMAP5912 to OMAP35xx DSP software migration.

DaveB123
Expert 4745 points

I'm searching from some FAQ and tips and tricks that would give some guidance as to the scope of migrating between OMAP generations (ARM9/55xx to Cortex A8/64x+.)

Currently the most daunting task is scoping the effort to reengineer the 55xx software to run on the 64x+ architecture.  Yes, the code is in C already...

This issue could also be addressed by any generic C5000 to C6000 code migration collateral as well.

DB

 

  • Expert 1120 points

    My 2 cents:

    1. MIPS wise, If your software runs well on 55xx, it shouldn't sweat on a 64x+. Of course, if you need to squeeze MIPS for other applications, that's a different story.

    2. The scope of the effort really depends on how your C code was written. If it's generic ANSI C, maybe all you need to do is re-compile the C code. But if your C code has lots of 55xx tweaks (intrinsics, etc) or makes heavy use of the peripherals, you'll have to re-write your C code.

    3. The scope of the effort also depends on your performance target. The TI compiler for C64+ usually does a decent job generating optimized code. But if you have very tight MIPS budget, the compiler alone may not be enough. You will need to hand-optimize your code.