 |
|
Development tools and features of eBinder |
|
|
|
|
|
| Configuration and build tools |
|
|
| Parts packages, including OS middleware, contain configurable switches for compile options. Configure and build with the GUI. |
|
| A C/C++ compiler is bundled with eBinder. eBinder supports ARM's genuine compiler (RVCT) and GNU GCC. |
|
|
|
| Task-level and system level debugging |
|
|
| Using the task-level debugger, open a debug window for each task. You can debug a single task without stopping the whole system. Tasks within a process can also be debugged. Of course, the debugger can be used for conventional debugging from the system context. |
|
| The host shell can be used to execute any linked function on the target, reference a directory of the target file system, control target execution, run scripts, and more. |
|
|
|
| EvenTrek — event log analyzer |
|
|
| EvenTrek inspects and analyzes the event log which includes RTOS API calls, interrupts, and task switches. It displays task state transitions, API events for middleware, and user-defined events. |
|
|
|
| PartScope — system snapshot browser |
|
|
| PartScope acquires and displays administrative information such as the list of OS processes and tasks, or details of allocated semaphores. You can view middleware information such as the status of currently opened files and/or socket states. |
|
|
|
| Realtime Profiler — system profiling tool |
|
|
The Realtime profiler helps you find out where bottlenecks in your program are affecting the overall system performance. With this tool, you can acquire system performance data that shows which task and its functions are taking up how much time, in both relative percentages and actual microseconds.
Using the Realtime profiler with Eventrek, which traces and displays task state transitions, provides you with an exact picture of system behavior, making it very easy to verify that your program works just the way you designed it.
The Realtime profiler collects data by sampling, thus keeping the overhead to the system at a minimum, as opposed to tools that trace the data. |
|
|
|
| PackageBuilder — Software component packaging tool |
|
|
| PackageBuilder packages user-created software components such as a library, a device driver, or a BSP for a custom board. |
|
|
|
| Dynamic loading and run-time task-creation features |
|
|
| You can dynamically load an object into the target board and create a run-time task for it while the system is running. You don't have to link and load the entire system when there is a minor change in the object module. Therefore, development time is shortened. |
|
|
|
| Platform packaging (PLP) feature |
|
|
Using eBinder's platform packaging feature, platform developers can create a platform package (PLP) from an already-verified and configured platform a set of verified software and configurations for the target to distribute to platform users. Platform developers can issue a module in binary form, or lock the configuration to prevent platform users from accidentally modifying or misconfiguring anything. Creating a PLP simplifies software distribution and version control. Coordinating application development among multiple platform users is made easy.
|
|
The resident unit loader is a utility to download resident units (**1) from an FTP server and Logical file system (LFS), and load them into RAM and Flash ROM on the target board, by saving the ICE environment. Embedding the resident unit loader into your final system allows you easier maintenance, including program replacement.
(**1)
The resident unit is a base program for a system. It consists of an RTOS, middleware, and verified user-made modules.
|
|
eBinder offers a communication feature and an execution control feature with a JTAG ICE.
Communication feature:
All eBinder features (multi-programming tool, system analysis tool, software component packaging tool, etc.) are available by setting the JTAG port as the debug port.
Execution control feature:
Features unique to a JTAG ICE are available from eBinder.
|
|
|
|
| eB-SIM — instruction set simulator |
|
|
| eB-SIM, a simulation environment for eBinder, provides a target development environment on a host computer. This is best for starting software development when the hardware is not yet complete or when minimizing the number of JTAG ICEs or evaluation boards.
|
|
|
|
| Multi-target debugging option |
|
|
| Using a single host PC, programs running on different target CPUs can be debugged. There is no need to use more than one PC to debug programs running on different multiple CPUs. Multiple eBinder instances can be executed on a single PC and can be used for debugging. For example, in a system where eT-Kernel and PrKERNELv4 are on ARM and SH processor, respectively, both applications can be debugged simultaneously using this feature. Multiple processors on different target boards and multiple processors on the same target board can both be debugged using multiple eBinder instances. |
|
|
|
| Multi-core processor support |
|
|
Just like development on a single-core processor, you can utilize eBinder's task-based iterative development model, and debug both SMP and AMP programs.
|
|
|
|
| Memory protection and system protection |
|
|
eBinder supports memory protection using MMU and the process model.
Memory protection feature:
Detects and prevents an executing process from accidentally destroying another process窶冱 memory area or kernel resource.
Process model support:
Offers a UNIX-like process management function using virtual addressing.
|
|
|
|
