Supports Windows CE 5.0/ Windows Embedded CE 6.0
ARM, MIPS, SH CPU
Features
- Source code debugging on Windows CE by ICE
- Debugging the final product software generated by Release Build
- Fast pace debugging is possible with actual running speed without any system load
- Real action speed debugging without system loads like debug monitor etc.
- No connection other than JTAG is required
- Utilize ICE functions like Hardware break
- Event Tracker graphically displays task and process switching in RTOS
- Can use debugger from Visual Studio 2005 by supporting eXDI2
Source Code Debugging on Windows CE by ICE
Supporting Windows CE by PARTNER-Jet enables source code debugging without Platform Builder, Visual eMbedded Visual C++ or Visual Studio 2005. PARTNER, the debugger software, newly supports the debugging information which is generated by Microsoft Compiler for Windows CE. Moreover, as PARTNER also supports the MMU space, you can debug the entire C/C++ software which running on Windows CE, not only debug boot loader or kernel but also application and DLL.
Debugging the Final Product Software Generated by Release Build
Fast pace debugging is possible with actual running speed without any system load, such as debug monitor.
PARTNER-Jet can debug the software by "Release Build" as well as "Debug Build". In addition, no extra debugging component is necessary in Target software. (Debugging by PB, VS, or eMbedded Visual C++ requires monitor programs in target) Therefore, you can debug in the same condition of the end product without CPU load and Memory reduction. It is useful in solving problems of complicated bugs that do not occur in conditions other than the end product. Through this, you can improve the debugging environment without any stress.
No Connection Other than JTAG Required
Until now during debugging by Platform Builder or eMbedded Visual C/C++, it required to communicate with monitor program running on Target through a communication device such as RS232C/Ethernet/USB and so on. For example, in the case of mobile audio players having only USB, it had to share the USB port and bandwidth between application and debugger. This can be reduced the efficiency of debugging. PARTNER-Jet uses JTAG only, and other communication devices are not required to debug. Therefore, the communication devices are able to open up to the application running on Target.
Utilize ICE Functions like Hardware break
With PARTNER-Jet, you can use the advanced debug functions of ICE. It can be monitoring the memory access by utilizing H/W breakpoints. In addition, like ARM9 CPU which hardware functions can be accessed by only JTAG, you can use hardware breakpoints such as data access break at debugging. Apart from this, PARTNER-Jet supports multi-core debugging. It can be used for developing Windows CE devices with multi-core. Also, the existing conventional features of PARTNER-Jet like writing to flash memory are available.
Can Use Debugger from Visual Studio 2005 by supporting eXDI2
PARTNER-Jet Windows CE debug option supports eXDI2 which is the latest specification for using JTAG Emulator from Visual Studio for Windows Embedded CE 6.0. This allows users to use PARTNER-Jet from accustomed Visual Studio 2005. Of course while you are debugging by PARTNER-Jet through Visual Studio 2005, you can launch PARTNER at any time and debug more closely to the Hardware.
PARTNER-Jet Windows CE Debug Option (For ARM, MIPS, SH)
For Windows CE debugging, it is required to have PARTNER-Jet, Windows CE debug Option software, and Annual Support Service.
*Windows CE Debug Option is required for each PARTNER-Jet. In case of debugging the different CPU series, it required the option software for each CPU.
*Windows CE 4.x and earlier version are not supported.
*Microsoft, Windows, and the Windows CE are registered trademarks of Microsoft Corporation in the United States and/or other countries.
*Product and company names mentioned herein may be trademarks of their respective companies. Product specifications are subject to change without notice.
KMC, the KMC logo, PARTNER, PARTNER-Jet, PARTNER-JetM, exeGCC, JTAG-Ether, and Eclipse for PARTNER Cross DevKit are trademarks of Kyoto Microcomputer Co., Ltd. Product and company names mentioned herein may be trademarks of their respective companies. Product specifications are subject to change without notice. This material is provided for informational purposes only; KMC assumes no liability related to its use.
