ColdFire, Codewarrior

embOS for Coldfire was developed for and with Metrowerks Codewarrior version 7.0 and supports all memory models and calling conventions offered by this compiler. It comes with easy to use start projects for the Metrowerks Codewarrior workbench.

Resources and performance data

Memory usage
Kernel size (ROM) approx. 1200 bytes
Kernel RAM usage 38 bytes
RAM usage per task control block 30 bytes
RAM usage per resource semaphore 14 bytes
RAM usage per counting semaphore 8 bytes
RAM usage per mailbox 22 bytes
RAM usage per software timer 18 bytes
RAM usage event 6 bytes
Min. stack-size per task (RAM) 72 bytes
Timing
Context switch time approx. 4.95 µs
Interrupt latency time zero
Kernel CPU usage/TICK less than .2% of total calculation time at 1000 Interrupts/second (1ms TICK)
Basic time unit (TICK) typ. 1 ms, min. 20 µs (50 kHz interrupt frequency)
Features
Max. no. of tasks Unlimited (by available RAM only)
Max. no. of mailboxes unlimited (by available RAM only)
Max. no. of semaphores (resource/binary/counting) unlimited (by available RAM only)
Max. no. of software timers unlimited (by available RAM only)
Max. no. of priorities 255
Stack size idle task (RAM) 0(no memory needed)
Nested interrupts permitted
Task switches from within ISR possible

embOSView offers system analysis during runtime


Available Emulators

  • J-Link for Coldfire
  • Multilink (P&E Micro)

Additional information

Freescale Web site for additional cpu info / support

Board support packages

embOS comes with lots of ready to go start projects and support packages for various ColdFire CPUs and starterboards.

CPU Eval board
Freescale PCF52223CAF80 Freescale M52223EVB
Freescale PCF52233CAF60 Axiom M52233DEMO
Freescale PCF5329 Logic-PD M5329
Freescale PCF52223CAF80 IAR M52233-SK

 


 

Release notes

  1. Tool chain used for build
  2. New features
  3. Improvements
  4. Program corrections
  5. Known problems/limitations
  6. Release history
  7. Miscellaneous

Tool chain used for build

The following tools have been used:

Compiler:  Codewarrior MWCCMCF  V7.0
Assembler: Codewarrior MWASMMCF V7.0
Librarian: Codewarrior MWLDMCF  V7.0
Workbench: Codewarrior IDE      V7.0

New features

Version 3.60d

  1. BSP for MCF5329 added.
    embOS for ColdFire now comes with a project for the MCF5329 CPU which is ready to run on the Logic-PD Fire-Engine.
  2. Support for Cache added.
    Some highlevel functions to initialize, enable, clean and invalidate the unified cache are included in the embOS libraries.
  3. Support for all memory models added.
    embOS for ColdFire now comes with libraries for all code/data model combinations (far/near).
  4. Support for all calling conventions added.
    embOS for ColdFire now comes with libraries for all calling conventions.
    Standard, Compact and Register calling conventions are supported now.
  5. New embOS sources
    embOS for ColdFire is based on embOS sources V3.60d. All new features are described in the embOS generic manual.
  6. Update to Codewarrior V7
    Because of new default sections in the ColdFire runtime and system libraries, embOS libraries and startup files built for the Codewarrior V6.3 toolchain can not be used. An update to V7 was required.

Version 3.52d

  1. BSP for MCF52223-SK added.

Version 3.50b

    None.

Improvements

Version 3.50b

    None.

Program corrections

Version 3.60d

  1. UART handler for embOSView corrected.
    The UART receiver error handler did not work correctly. Rx errors were not cleared.
    If an error occured, the communication to embOSView was locked, because normal receive interrupts were not handled as long as the error state was set.
    The problem existed in all BSPs in all previous versions and is fixed with version 3.60d.

Known problems/limitations

Version 3.60d

    NONE

Release history

Version Release date Short explanation
V3.60d 10. Jul 2008 Updated version
V3.52d 08. Nov 2007 BSP for MCF52223-SK added.
V3.50b 31. Jul 2007 First version with release history

Miscellaneous

This document was first released with version 3.50b of the software.
Software released earlier is documented internally. This information is available at request.