• 3-1 Download Hexfile • 3-2 Cautions for Debugging Appendix • 4-1 SDK DLL Compatibility according to IAR Versions • 4-2 Number Limitation of Built-in Breakpoints for each Device • 4-3 Number of Built-in Breakpoints: ABOV Devices End of Document Confidential...
1. Introduction ▪ This user guide introduces a method to develop ABOV devices in the 8051 debugger of IAR (C-SPY) environment. • How to connect and detect the OCD/ OCD II/ E-OCD II dongle. • How to detect ABOV’s 8051 device.
» It requires an installation of Kernel Driver on a PC. » While operating the OCD Debugger Setup Program that is provided by ABOV, necessary files are copied. » You can refer to ABOV’s OCD Debugger Manual for the information of the driver installation.
» IAR selectively provides basic DLL only for some companies such as TI, Infineon, and Segger. - Products of other companies are connected by using Third Party Drivers. » ABOV developed DLLs to support its dongles and devices by using SDK sources of IAR. • SDK DLL compatibility between IAR versions »...
Page 6
2. IAR Debugger Connections (continued) • IAR project settings ① Select “Options…”, then select “Debugger”. ② Press “OK” button to connect to the Third-Party Driver. Confidential...
Page 7
(continued) • IAR Third-Party Driver settings ① Select “Options…”, then select “Debugger”. Finally select “Third-Party Driver”. ② Press “OK” button to connect to an SDK DLL file provided by ABOV (Check the IAR version for the compatibility of SDK DLL).
3. Use of IAR Debugger 3-1 Download Hexfile • By pressing a debugging button ( ), you can proceed operations consecutively. ① Detect OCD/ OCD II/ E-OCD II dongle. ② For each dongle, select POR (Power-on Reset) for the series to which a target device belongs. When connecting OCD dongle When connecting...
Page 9
3. Use of IAR Debugger (continued) • If the target is turned off, a dialog box is displayed as shown below: • If the target is turned on, but an unregistered product is detected, a dialog box is displayed as shown below: •...
Page 10
3. Use of IAR Debugger (continued) • If a target device has options, » After downloading a Hex file, the corresponding option dialog for the device is displayed. » Example option dialog for MC96F8204 is shown below: Confidential...
3. Use of IAR Debugger (continued) 3-2 Cautions for Debugging • Use the functions of IAR debugger without changes. » Remember only that the number of Breakpoints is limited. Confidential...
Page 12
(continued) • After downloading a Hex file, it displays the number limit of the Breakpoints. » ABOV’s devices limit the number of built-in Breakpoints. - The number of Breakpoints for each device is different. - It displays the number of Breakpoints available for developers, except for Breakpoints used by IAR debugger.
Workbench. » Some of SDK DLL are not compatible if their Embedded Workbenches have different versions. » As of 2019, ABOV supports the version 8.0 and 8.1 of Embedded Workbench. » Check the IAR version by following the procedure below: Start the IAR.
Page 14
4. Appendix (continued) • IAR version table » Since IAR GUI requires different SDK DLL to be developed and supported for each version, it is not easy to manage and distribute the SDK DLL. IAR version Detailed version: released year Matched SDK DLL version 10.30.x : 2019 10.30...
(continued) 4-2 Number Limitation of Built-in Breakpoints for each Device • Number of Breakpoint logics that are built in ABOV’s device: » OCD IP has 8 Breakpoints that is defined in a default spec. » OCD II IP has 12 Breakpoints that is defined in a default spec.
Need help?
Do you have a question about the EW8051 and is the answer not in the manual?
Questions and answers