Some optimizations verge on second-guessing the programmer. In some cases, especially those with possible side-effects, obeying the source code as written is preferable to reordering instructions, even if it means wasting an instruction or two.
No. eTPU is the successor of TPU3 and shares some design heritage, but that's about it. They are completely different processors, both in functionality and programming terms.
Functions are not reentrant. The local variables are not placed on a stack; their address is set at compile time. If a function calls itself, or a function is being executed from both the main loop and within an interrupt, the second call to the function will use the same memory. In this case local variables will become corrupted.
ETPU_functions are reentrant, in the sense that multiple channels can dispatch the same function.
C functions called from within ETPU_functions are not reentrant.
I have an application developed with an old version. Will it compile properly with the latest version?Submitted by Kirk Zurell on Tue, 2007-11-20 21:01. C38 | C6805 | C6808 | COP8C | Cypress C | eTPU_C | Fuzz-C | MPC | support | SXC | Z8C
Yes. If you have written your program according to our recommended practices in the product documentation, upgrading should be seamless. All Byte Craft Limited Code Development Systems have backward compatibility with previous language constructs.
- Improvements in the compiler can alter the generated code; this may impact your testing.
- Device header files may change between versions. If you've written customized device header files, they may require some revision. Simply examine the stock headers that we ship with the product.
See Distributors for an updated list of distributors.
We're listed on Freescale's Compass Extranet.
For external participants, choose:
For Freescale-internal participants, our extranet project name is "Byte Craft".
We've posted some useful PowerPoint packages about our technology that you can cut and paste directly into your client presentations.
Consult these resources for more information on eTPU_C and the eTPU:
Lauterbach offers the eTPU Debugger, which is compatible with eTPU_C. It includes support for breakpoints, subinstruction disassembly and high-level language support, and the PRACTICE scripting language for automation.