Introduction

This page is a quick start guide to program and debug on the ADAU1860 evaluation board platform. Here is a summary of what is included in this document:

• Xtensa tool installation on Windows Platform
• Connecting JTAG probe hardware to the evaluation platform
• Building programs
• Linker support Packages
• Downloading and executing examples provided

Xtensa Tool Installation

Hardware requirements.

Windows host computer is required to run the following software:

• Xtensa IDE (xplorer)
• Xtensa XCOD (xtensa on chip debug) daemon

If you want to use ADAU1860 hardware, then the following components are also required:

• Hardware to drive the JTAG debug interface (e.g. mIDAS-Link)
• ADAU1860 Evaluation Board Platform
• Mini USB Cable

Tools install Package and SW Requirements.

Core Configuration

Those files can be obtained on https://tensilicatools.com/.

RI_2022.10 → hifi3z_lark_RI_2022_10_win32_redist.tgz

SDK

Please find latest SDK version from https://www.analog.com/en/products/adau1860.html#product-requirement

Xtensa Tools

This userguide has been tested using Xtensa Xplorer version 9.0.20, Xtensa on chip debug (XOCD) 15.03 and build tools RI_2022.10. Those files can be obtained on https://tensilicatools.com/.

Installing ADAU1860 Core Configuration

• Click on File | New | Xtensa configuration
• Select “Install a new build from downloaded bundle as the new configuration”.

• Browse to the downloaded core configuration based on the build tools installed.
• Select *_win32_redist.tgz for file type.

• Press “Add Build” button and “Finish”.

Linker Support Packages (LSPs)

A linker support package (LSP) specifies object files to pull into an executable using a specific memory map and is used as a convenient short-hand for telling the linker what it needs for a particular target environment. Thus, an LSP ties together components that may need to be adapted as an Xtensa processor is used in different systems, including various portions of the Xtensa software development kit.

The gdbio LSP is used to build an application to be executed on a target controlled using an Xtensa debugger and the Xtensa OCD Daemon. It interacts with the debugger to route all file and console I/O, as well as a few other system calls, to the host running the debugger. The C library’s standard input and output go to the debugger’s console.

User can define a custom LSP based on gdbio according to customer’s system, here are steps for define customer LSP:

• Copy gdbio LSP provided to desired target path. It can be found on any of the example projects available on the different FAQ pages.
• Modify memmap.xmm settings if required.
• Run “.bat” files attached based on the build tools you plan to use.

Configure Xtensa On Chip Debug

This chapter covers the following topics related to configure Xtensa on chip debug.

• Configuring the On-Chip debug.
• Check XOCD communication.

It is important to highlight that in order to have Xtensa Xplorer communicating with Hifi3z in ADAU1860. It is important that before powering the board P26 (Self_Boot) and P23 (Rom_Boot) needs to be placed in High position. It is also possible to enable the communication if Power & Clock registers have been configured previously.

Configuring Xtensa On Chip Debug (XOCD)

Here are steps for configuring Xtensa On Chip Debug (XOCD) and making a connection to the XOCD Manager: Before that it is important to highlight that selfboot jumper must be set on high prior to power the board so the HifiCore it is initialize by default.

• Open the Debug Configuration Editor by selecting the menu "Debug->Debug Configurations…" as shown in next figure.

• Create a new Xtensa On Chip Debug configuration as shown in next figure

• Check the box "Use OCD Manager". The "Host name" should be "local host", which is the default. The "XOCD Manager Port" should be 20900, which is the default.

• Rename the new configuration as you wish.

J-Link (USB) for XOCD / GDB Server Communication

Select JTAG Probe by pressing dropdown list and select J-Link (USB), the default JTAG probe speed for communication between the XOCD daemon and the GDB server is 10000000. Please input USB serial number based on your J-Link hardware S/N.

Diagnose XOCD Server Communication

• Click “Diagnose…”
• Check the box “Advance Diagnostic”
• Click "Query" and wait diagnostic finished, XCOD is working if the log as show in next figure.

Import Project / Workspace

Import project

If the project already exits, we can import it to workspace, here are the steps to import project.

• Open the import menu by selecting the menu “File -> Import…”
• Select “General -> Existing Projects into Workspace” and click on “Next”.

• Browse and select the folder that contains the project

• Click on “Finish”

Import Workspace

If a workspace file was already generated, it can be imported.

• Open the import menu by selecting the menu “File -> Import…”
• Select “Xtensa Xplorer -> Import Xtensa Xplorer Workspace” and click on “Next”.
• Browse and select the folder that contains the workspace.

• Select the project and click on “Finish”.

Running Example on the Evaluation Board

This chapter covers the following topics:

• Configuring the target project and core configuration.
• Compiling and download the program.

Project configuration

• First select the project.

• Then configure the core configuration. In the snapshot attached is using the latest core configuration, but depending on the build tools you might need to use different core configuration.

• Go to debug and click on “Modifiy" to change the LSP files.

• The workspace shared already points to the correct path to the LSP files, but if you have different LSP files to use, browse to the correct folder

Compiling and downloading

• First click on “build active” to get the code compiled.

• Once the code it is compiled, you can click on debug.

• Finally click on yes to download the code into the core.