You can return to the ACE Application User Guide Homepage here:
The Tool Views are a collection of views that add functionality to the main views. The Tool Views is found in the Tools drop-down on the side bar of the main window, as seen in Figure 1. Tool Views that were open when the application is closed will reopen when the application starts up again. The following are the available tools in ACE Software:
The Macro Tool View, as seen in Figure 2, allows commands to be recorded and played back. Macros can be created to configure a chip, to share a series of steps with other users, or to perform common tasks multiple times.
The Macro Toolbar, as seen in Figure 3, can be used to open, record, save, close, or delete Macros. While recording, the Commands List will automatically be populated when any interaction with the device is performed. By default, the Commands List is populated with top level commands, and it can be extended to show sub-commands by checking the Record Sub-Commands box prior to recording.
Sub-commands are denoted by a “>” symbol for each level of the tree.
|Records all transactions done by the user in the user interface consisting of top-level commands extended with sub-commands
|Stops recording of the macro commands
|Plays the recorded macro commands or plays the imported macro file
|Edits the recorded macro commands or edits the imported macro file
|Saves changes to the current opened macro
|Saves the recorded macro commands or saves the imported macro file as a new file
|Opens the saved macro file
|Closes the currently opened macro
|Deletes the currently opened macro
|Generates scripts that perform the recorded actions in a supported language of choice (C#, ACE Hex, Hex, ACE Macro, MATLAB, Python)
Click the subsections below to expand/collapse the details:
The System Explorer, as seen in Figure 8, is used to navigate and show all the subsystems that have been added by the user to the system. By definition, a subsystem is a unit that represents a placeholder for hardware components grouped together under a system. It represents a group of physically connected boards. A subsystem can consist of just a single component at a minimum.
Subsystem details include boards, chips (or components), chip memory maps, controllers, FPGA memory maps, and interposers. Memory maps to both the chip and FPGA can be accessed using System Explorer where you can write, read, or reset register settings.
The Register Address Dropdown is populated with a list of all registers in the chip where the user can write or read from. When the Write button is selected, the hexadecimal value in the Write Data Textbox will be written to the selected register and this action added to the history grid.
Similarly when the Read button is selected, the selected register is read from and its value populates the Read Data Textbox. It is important to note that since this view preforms raw writes, there is no write verification step, so the value on the hardware after the write may not match the value that was written.
The History Grid shows previous writes and reads performed from within this view. These writes and reads can be repeated by selecting the step to be repeated and clicking the Repeat button. All previous actions can be removed from the History Grid using the Clear button.
Figure 9. Register Debugger View
The Events Tool View, as seen in Figure 10, contains a list of event logs including error and warnings generated within the application software. Messages are divided into the following sections:
The SDP-K1 Recovery Tool is used to recover the firmware loaded to the SDP-K1 Controller Board. The SDP-K1 board is designed to be used in conjunction with various ADI evaluation boards as part of a customer evaluation environment. To know more about SDP-K1, refer to SDP-K1 wiki page.
To use the SDP-K1 Recovery Tool, refer to Figure 11 and follow the steps below: