Which tool is best for me?
All described tools aim at embedded design, troubleshooting and real-time test. Default feature of all tools is on-chip debugging, which provides a detailed insight into the microcontroller and application run/stop control.
Optionally all tools support trace functionality, providing detailed time measurements of the application behavior (program, data). Available software functionalities based on this information help troubleshooting simple and complex problems, optimizing application execution times (profiler), finding time constrained bottlenecks, detecting executed and not executed code (coverage), verifying test code efficiency, etc...
Certain tools can be also extended with an I/O module, which can stimulate and measure analog or digital signals around the target microcontroller. This makes possible to build an affordable Hardware-In-The-Loop (HIL) test target system.
iC6000 (USB 3.0, TCP/IP) is a high end solution supporting the latest trace protocols based on Aurora physical interface running in Gigabit/s range (e.g. Infineon Tricore, NXP/ST Qorivva). The tool also supports standard Nexus trace protocols such as ARM ETM, NXP/ST Qorivva Nexus, Renesas RH850 Nexus. This tool is a recommended choice when starting a project based on a microcontroller featuring Aurora trace interface or when the tool is going to be used some time in the future in conjunction with the microcontroller featuring Aurora trace interface.
iC5700 (USB 3.0, TCP/IP) provides best performance and investment for microcontrollers featuring Nexus trace protocols such as ARM ETM, NXP/ST Qorivva Nexus, Renesas RH850 Nexus, etc... With its USB 3.0 interface to the PC and optimal trace buffer size, it often provides infinite trace, profiler and coverage sessions.
iC5000 (USB 2.0, TCP/IP) provides a bit less performance (shorter trace sessions) for less money comparing to the iC5700. It's a good choice for projects with very tight budgets or projects based on a microcontroller without any trace port or a microcontroller featuring only on-chip trace buffer. There is no noticeable difference (comparing to iC5700) when using on-chip debug features without trace functionalities.
The tool supports Nexus trace protocols such as ARM ETM, NXP/ST Qorivva Nexus, Renesas RH850 Nexus, ... and provides shorter trace, profiler, coverage session times when trace upload over the USB 2.0 interface cannot keep up with the broadcasted microcontroller trace port data. When session time is important, user should opt for the iC5700.
iC3000 (USB 2.0, TCP/IP) is the oldest platform among these tools. It supports also in-circuit emulation technology next to the on-chip debugging. It's not recommended when buying a new tool for a microcontroller architecture featuring on-chip debug support. The iC3000 is still up to date platform for in-circuit emulation debug and test.
Potential customers are encouraged to contact iSYSTEM sales. Together we can discuss all aspects and requirements of your project and find optimal solution. We will be glad to listen and assist you!