Advice For Beginning CF2 Users
If you are a first time user of the CF2 computer system, please review these tips and advice.
Make sure you are thoroughly familiar with "The C Programming Language" by Brian W. Kernighan and Dennis M Ritchie. This is the Bible of C programming.
Persistor's documentation does NOT teach you how to use the CodeWarrior programming environment beyond the basic installation and first sample program compile. This must be learned from CodeWarrior's own documentation.
Persistor's documentation does NOT teach you about the 68332 architecture. You must understand how the microprocessor works before you can program for it. After you have installed the PicoDEV set up, you will find PDFs for the 68332 and its submodules here; C:\Program Files\Persistor\MotoCross Support\CFX\Docs\pdf
Your first interaction with the CF2 and programming should be guided by the CF2 Getting Started Guide.
After getting through the getting started guide, learn to use the documentation index. It is located in your PC Start> Programs> Persistor> PicoDEV Documentation Index.
Review the CF2 Programmers Manual. Programming for embedded applications is much different from programming for the PC. This manual doesn't touch on every facet of programming for the CF2 but it is a great introduction.
Locate the CF2 API reference. When you program for the CF2, you are either using Persistor's PicoDOS functions and macros OR you are using CodeWarrior's' standard C functions. Only the functions and macros listed in the Persistor API are supported by Persistor. The standard C functions are documented by CodeWarrior (Freescale).
When you are working in a compiled project, you can get a list of all the headers that are used by the project by clicking the header files button in the main.c window. This is where you will find the most true information about error codes (_cfx_errors.h) or persistent environment variables (_cfx_globals.h) memory map (_CFX_memmap.h) and function definitions and constants. You should rarely need to ever touch these header files but they are a resource for information.
After you have done a PicoDEV installation, you will find many programming example projects here; C:\Program Files\Persistor\MotoCross Support\CFX\Examples. You may also find newer examples on our WEB page here;http://www.persistor.com/pii/support/examples.html
Before the CF2, there was a CF1 which was very similar to the CF2. The big difference was the CF1 had a Counter Timer Module while the CF2 has a Timer Processor Unit. The CTM or TPU are used as either basic I/O or the alternate module purposes for the pins can be used instead. But the CF1 HTML interactive manual still contains some information that never got ported to the CF2. Particularly helpful will be the discussion of programming for the MAX146 on the CF1. The educational text is still correct but the A-DExamples in C:\Program Files\Persistor\MotoCross Support\CFX\Examples should be used instead of the Max146Examples referenced by the test.
If you need help developing your application or writing programs, there is a list of consultants who are familiar with the CF2. The list may be found here; http://www.persistor.com/pii/support/3rdparty/thirdparty.html. Persistor Instruments normally does not assist customers with hardware design or programming. We will investigate any report of a software bug or a lack of documentation but we must otherwise resort to recommending third parties for application or design assistance.
If you need technical support from Persistor Instruments, PLEASE contact us by email. We do not have persons sitting by the phone waiting to troubleshoot your problem. A clearly written question has a much better chance of getting answered quickly, and correctly, then a telephone call. Any examples should be reduced to the minimal bit of code required to demonstrate the problem. Even an expert programmer takes a lot of time to understand many lines of code. In tech support the golden rule also applies; Ask a question as you would like a question asked of you.
If you find this list could be improved for the next beginning CF2 user, please email us your suggestion.