̾ŲؤλΤǤ
ZedboardбTOPPERS/FMPδʰץѥå ޤΤǤΤ餻פޤ
ZedboardʤΥܡɤǡ$395,ǥߥå$299XILINXҤZYNQ-7000ARM Cortex-A9
MPCore 2 + FPGAˤܤޤ
ʲURL饽ɤɤǤޤ
http://www.toppers.jp/download.cgi/fmp_zedboard_gcc_20121030.tar.gz
ӥɤưˤĤơѥåäƤ륯åɡREADME-EN.txtˤͤƤ
TOPPERS/FMPħ
• マルチプロセッサ対応のRTOS
• 静的なタスクのプロセッサへの割り当て
• カーネルによるタスクスケジューリングはコア毎
• TOPPERS/ASPカーネル機能互換
• APIによるタスクマイグレートのサポート
• ユーザーレベルでマイグレーション機構を実現可能
ʾ塤ꤤޤ
̾Ų
-------------------------------------------------------------------
Dear all,
I'm glad to inform you that a porting of the TOPPERS/FMP kernel to the
Zedboard has been released.
The link below contains the TOPPERS/FMP source code (including
Zedboard-dependent code) and a quickstart manual (README-EN.txt) that
includes instructions for compiling a sample application and loading
it into the board:
http://www.toppers.jp/download.cgi/fmp_zedboard_gcc_20121030.tar.gz
TOPPERS/FMP (http://www.toppers.jp/en/fmp-kernel.html) is an RTOS that
follows a specification based on uITRON4.0 (an RTOS specification
especially popular in the Japanese embedded arena) and with support
for multi-core processors. It is developed by the TOPPERS project
(http://www.toppers.jp/en/index.html) and distributed as open source
code through the TOPPERS license
(http://www.toppers.jp/en/license.html).
The main characteristics of FMP are:
- Kernel and applications are linked in a single monolithic binary
without memory protection (target applications are usually small scale
and with high efficiency requirements).
- Tasks are assigned to processor cores through a configuration file (.cfg).
- The kernel will not automatically migrate tasks (i.e., it does not
include load balancing) during the execution of the system.
- However, the API allows migrating a task to a different processor
core at run time (therefore, load balancing can be implemented in the
application side).
- The execution of FMP can be traced and displayed graphically through
the TLV tracelog visualizer (http://www.toppers.jp/tlv.html).
If you have any doubts or you need support, please get in contact with
us (check the README-EN.txt file for detailed information).
Best regards
Daniel