Assembling and Configuring the Starter Kit Components

This document contains complete information on how to build an AudioworX Starter Kit by interfacing and configuring hardware components from the ground up. The scope of the document is limited to the steps that are required to be completed as a pre-requisite to the Getting Started Guide in AudioworX Starter Kit Overview only when the components of the Starter Kit are sourced independently.

Caution: Some of the steps given here require careful handling of the electronic components and we encourage users to observe caution during the hardware installation steps.

Required Components


Following is a list of hardware components along with approx. cost (without shipping and taxes) and their recommended variants to be procured before getting started with the assembly of the AudioworX Starter Kit.

# Item Description Approx. Cost
1 Raspberry Pi 5 Kit

  1. Raspberry Pi 5
  2. Power adapter for Raspberry Pi
  3. Micro SD Card
The main processing unit of the AudioworX Starter Kit.
Recommended Variants:

  1. Raspberry Pi 5 – 8 GB variant for better performance
  2. MicroSD card – 16GB or higher
$150
2 HiFiBerry DAC8x Sound card (output only)  $65
3 HiFiBerry ADC8x Add-on Sound card (input only)  $75
4 JBL DSP 4086 – 8-channel amplifier

or

Infinity DSP6840 – 8-channel amplifier

Power amplifier to drive passive speakers. Only required when using the Starter Kit with a passive speaker system.

Users may choose any other power amplifier depending on their setup.

$440
5 12V 20A power supply for the JBL/Infinity amplifier  Power supply for the JBL DSP-4086/Infinity DSP6840 amplifier. $20
6 Miscellaneous items
  • Audio cables for providing audio input to the Starter Kit audio input ports (3.5mm to 3.5 mm Stereo Audio Cable) – 1 for stereo input or 4 for 7.1 input.
  • Audio cables to connect speakers/power amplifier to the Starter Kit audio output ports (3.5 mm to RCA audio cables) – 3 for 5.1 output or 4 for 7.1 output.
  • Connectors for interfacing speakers to the amplifier,
  • MicroSD Card Reader (if not included in the Raspberry Pi kit)
Total Cost (without shipping and taxes)  = $750

Assembling the HiFiBerry HATs on to the Raspberry Pi 5


In the latest version of the AudioworX Starter Kit, the HiFiBerry DAC8x (8-channel line audio input HAT) and the HiFiBerry ADC8x Add-on (8-channel line audio output HAT) are the default and recommended audio interface for the setup’s compactness, robust interfacing and multi-channel capabilities.

The HiFiBerry HATs must be stacked on top of the Raspberry Pi 5 (the bottom-most layer in the stack) using the 40-pin header in the given order:

  1. HiFiBerry DAC8x (middle layer in the stack) on top of the Raspberry Pi,
  2. HiFiBerry ADC8x Add-on (top-most layer in the stack) on top of the DAC8x.

Observe caution when stacking the HATs. Disconnect the power from the Raspberry Pi 5 before installing the HATs.

It is important that the pins perfectly align with no open pins visible upon installation. Use the plastic spacers provided with the HiFiBerry HATs to ensure that the hardware is secured in place and does not budge while connecting cables to the audio input and output ports.

The below figure shows a complete Starter Kit setup.

A Fully Setup AudioworX Starter Kit (Bottom Layer: Raspberry Pi 5, Middle Layer: HiFiBerry DAC8x, Top Layer: HiFiBerry ADC8x Add-on)

Any class-compliant USB audio interface can be used with the Starter Kit. The SKUtility Tool allows users to configure their choice of audio interface for use with the AWX Amp application (see Audio Config in SKUtility Tool – Graphical Application.
The Starter Kit has been tested to work stably with the following audio interfaces:
Focusrite Scarlett 2i2
TASCAM US-16X08
RME Fireface UCX-II
DigitalLife U2Audio7
UGREEN USB to 3.5mm Headphone Audio Adapter

Flashing the AudioworX Starter Kit Custom Image on the MicroSD Card


The AudioworX download page contains a Starter Kit Package, which is a pre-configured disk image for the Raspberry Pi 5, pre-installed with all dependencies and configured to run the AWX Amp application with the Starter Kit example SFD upon successful boot-up (refer to Getting Started with the Example Project. This section provides instructions on how to make a bootable MicroSD card for the Raspberry Pi 5 using the custom image.

Requirements

Hardware Required Software Required
  1. Raspberry Pi 5 (recommended: 8GB RAM variant),
  2. MicroSD card (recommended: 16 GB or more),
  3. MicroSD card reader.
  1. Raspberry Pi Imager: Download and install this application for flashing the custom image on to the Micro SD card.
  2. Custom AudioworX Starter Kit disk image

Steps for Flashing the Custom Raspberry Pi Image

  1. Mount the SD card in the card reader and plug it into your PC for flashing.
  2. Open the Raspberry Pi Imager. Under “Device”, select the “Raspberry Pi 5”.
  3. Under “Operating System”, click “Choose OS”, scroll down and click “Use Custom”.
  4. In the pop-up, browse for the downloaded image file and select it.
  5. Now, in the main Raspberry Pi Imager window click the “Choose Storage” button, select the mounted drive to be flashed and click “next”.
  6. The Imager will then show a prompt for OS customizations. Click on “Edit Settings”.
  7. In the OS Customization → General tab (shown below):
    1. Enter “awx” in both the username and password fields. Alternatively, users may enter a username and password of their choice and use the same in the SKUtility to login to the Starter Kit later.
    2. (Optional) If direct ethernet connection between the Raspberry Pi and the PC is not possible:
      1. Tick the check box “Configure Wireless LAN” and enter your home Wi-Fi/mobile hotspot credentials in the SSID (Wi-Fi name) and password fields,
      2. Specify the Wireless LAN country code according to the country that the Starter Kit is being used from the drop-down menu. Here, it is set to GB (Great Britain).

        Direct ethernet connection between the PC and the Raspberry Pi is recommended for stable connection to the Starter Kit. Refer to the Troubleshooting Guide for alternative ways to establish connection between the PC and the Raspberry Pi.

  8. In the “Services” tab, enable SSH login and click “Save”.
  9. In the following window, click “Yes” to apply OS customizations.
  10. You might see a warning (shown below). Click on “Yes” to continue.
  11. Once the image has been flashed, eject the MicroSD card from the card reader, insert it into the Raspberry Pi’s Micro SD card slot on the underside (shown below) and power it on.

First-time boot could take a few minutes since the disk partitions get resized at this time. The Power LED on the Raspberry Pi 5 will turn static Red after some time, after which the power needs to be reset by pulling out the power cable and plugging it back in. On successful boot-up, the Power LED will light-up Green and blink randomly, indicating disk activity. A noticeable pattern in the Power LED blinking could indicate a possible issue in booting. Refer to Unresponsive Raspberry Pi5 on First Boot – Troubleshooting Steps for instructions on how to fix the issue.

Verifying the Setup using the SKUtility


To verify if the Raspberry Pi has been configured properly, connect it to the host PC using an ethernet cable (or ensure that the PC and the Raspberry Pi are configured to connect to the same network), run the SKUtility Diagnostics as described “Verifying Hardware Connections with the AudioworX Starter Kit Utility” section in Hardware Components Setup. This tool is installed as part of the Global Tuning Tool (for instructions on installation of GTT, refer to Installing AudioworX Setup.

Verify from the log printed on the right-hand side pane if step 1 of the diagnostics is successful, i.e., the PC can reach the Raspberry Pi over the network. If the Raspberry Pi is inaccessible even after resetting power, follow the instructions in the next section to troubleshoot.

Unresponsive Raspberry Pi5 on First Boot – Troubleshooting Steps


There may be cases where the Raspberry Pi is inaccessible due to issues while booting up. In such cases, the Power LED on the Raspberry Pi may flash in a regular pattern corresponding to an error code listed in the official Raspberry Pi website. One common issue when using a PC that has USB-write restrictions to flash the MicroSD card could be the “start*.elf not found” error preventing the Raspberry Pi from booting up. In this case, the Power LED flashes 4 times in short bursts, followed by a pause and repeats the same pattern.

The following are the steps to fix this issue:

  1. Remove SD card from Raspberry Pi, insert it into the Micro SD card reader and plug it into the PC.
  2. Open the Raspberry Pi Imager tool, select the “Erase” option in the “Operating System” menu and select the inserted SD card in the Storage menu.
  3. Click the next button in the main menu and click on “Erase” when prompted to fully format the SD card.
  4. Once the formatting is complete, from the main menu of the Raspberry Pi Imager:
    1. Select “Raspberry Pi 5” in the “Raspberry Pi Device” menu,
    2. Open the “Operating System” menu and select “Misc Utility Images → Boot loader (Pi 5 family) → SD card Boot”.
    3. Select the SD card in the “Storage” menu and write the image.
  5. Now, insert the SD card in the Raspberry Pi, power it up and wait for the green LED to continuously blink at a constant interval.

The final step is critical in configuring the boot loader of the Raspberry Pi 5. Complete all the steps in the same order to rectify the issue.

Once the above steps are completed, follow the steps in Steps for Flashing the Custom Raspberry Pi Image to reflash the custom image and boot up the Raspberry Pi again. Then, follow the steps in Verifying the Setup using the SKUtility. If the Raspberry Pi is still unresponsive, it could indicate a different issue. Please contact Harman AudioworX (AudioworXSupport@harman.com) support for further assistance.

Upgrading the Starter Kit Software from an Earlier Release of AudioworX


The AudioworX Starter Kit software binaries and other resources are installed on the PC along with GTT to allow for upgrading an existing Starter Kit to the version of GTT installed. The SKUtility Tool can be used to upgrade the version as detailed below.

Before upgrading the AudioworX installation on the Starter Kit, it is highly recommended to take a back-up of the exiting AudioworX installation directory Raspberry Pi.
If the pre-installed AudioworX version on the Starter Kit is before Y-release (v25.x.x.x), run the below command using the older version of the SKUtility Tool (CLI tool installed with the old version of GTT):
python3 SKUtility.py rmt -snp
For AudioworX installations on the Starter Kit post Y-release, use the SKUtilityGUI using the Remote > Snapshot option.
The back-up will be saved in C:/ProgramData/Harman/StarterKit (SKSnap_<date_and_time_stamp>.zip).

Steps for Upgrading the AudioworX Version on the Starter Kit

  1. Install the latest version of GTT (refer to Installing AudioworX Setup),
  2. Open the SKUtilityGUI from the start menu,
  3. Connect to the Starter Kit,
  4. Go to Configuration > Factory Reset,
  5. Click Yes to install the version of AudioworX on the Starter Kit hardware associated with the GTT installation,
  6. Finally, reboot the Starter Kit using Remote > Reboot.

Since the binaries and data files for the Starter Kit are installed along with GTT, the above instructions can also be used to revert to any older releases of the AudioworX Starter Kit post W+1 (v24.1.1.2444) by performing Factory Reset with the SKUtility Tool associated with the GTT installation.

The Starter Kit software can be installed on an existing Raspberry Pi 5 with the Raspbian OS using the SKUtility Tool by logging into a sudo user account following the same steps as above. However, there could be missing dependencies that may need to be installed before being able to use the Raspberry Pi 5 as an AudioworX Starter Kit.

Additional Changes Required for HiFiBerry HATs on Older Releases of the Starter Kit

The support for the HiFiBerry DAC8x and ADC8x Add-on HATs with the Starter Kit has been added by default in the custom image only from the Y-release of AudioworX (July 2025). However, if using an existing release of the AudioworX Starter Kit or if installing the Starter Kit software on an existing Raspberry Pi 5 with the Raspbian OS, additional steps are required for enabling their use.

The support for HiFiBerry ADC8x Add-on HAT was added to the official Linux Kernel’s February 2025 release (see the official HiFiBerry post on this topic). This necessitates a Kernel update on Raspberry Pies with older kernels.

Step 5 (Linux Kernel update) requires internet access in the Raspberry Pi and using direct ethernet connection to the PC may not work. The recommended method for enabling support for the HiFiBerry HATs is by using the custom image for Y-release of AudioworX (see Flashing the AudioworX Starter Kit Custom Image on the MicroSD Card).
To install support on an existing Starter Kit, ensure that the Starter Kit and the PC are connected to a Wi-Fi network or a wired-LAN with internet access. To configure the Starter Kit to connect to an external Wi-Fi, refer to “Starter Kit Configuration > Wi-Fi Config” in SKUtility Tool – Graphical Application.

  1. SSH into the Raspberry Pi 5 using the Windows Command Prompt by running the following command:
    ssh awx@raspberrypi.local
    Enter the password when prompted (The password will not appear as you type. Type the full password and hit the “Enter” key.). If the hostname and username are different from that of the default Starter Kit, run the SSH command as given below:
    ssh <username>@<hostname>
  2. Run the following command in the ssh terminal:
    sudo nano /boot/firmware/config.txt
  3. Add the following line to the end of the file:
    dtoverlay=hifiberry-dac8x
  4. Press Crtl+S to save the file and Crtl+X to exit.
  5. Update the Linux Kernel on the Raspberry Pi by running the following command:
    sudo rpi-update

Reboot the Raspberry Pi from the SKUtility Tool (Remote > Reboot) to complete the installation.

To verify that the HiFiBerry HATs are accessible using the SKUtility Tool, connect to the Starter Kit, go to Configuration > Audio Config, and verify that “sndrpihifiberry” is available under both, the input and output audio device drop-down menu as shown below:

HiFiBerry HATs Chosen as the Audio Interface in the SKUtility Tool

Configuring the JBL DSP-4086/Infinity DSP6840 Amplifier (Only for Passive Speaker Systems)


The JBL DSP-4086 amplifier and Infinity DSP6840 are the recommended amplifiers for the Starter Kit for their robustness in car systems. Users may choose to opt for an amplifier of their choice depending on the speaker specification and availability of the amplifier.

The JBL DSP-4086 and the Infinity DSP6840 (both amplifiers are very similar in appearance and identical in specification and operation) are capable of simple DSP operations for equalizations, volume and distance tuning which can be configured via the DSP tuning application provided. In the Starter Kit context, ideally, the DSP processing is expected to be confined to the Starter Kit hardware (Raspberry Pi 5). The JBL DSP-4086 and the Infinity DSP6840 must be reconfigured for the Starter Kit use-case to turn off all DSP processing. The following are instructions to reconfigure the amplifier.

Requirements

Hardware Requirements Software Applications
  1. JBL DSP-4086 Amplifier or Infinity DSP6840,
  2. USB Cable included with the amplifier,
  3. 12V 20A Power Supply.
  1. Amplifier’s DSP tuning application (this application can also be installed from the USB thumb-drive supplied with the amplifier):
    1. JBL DSP application for the JBL DSP-4086 amplifier, or,
    2. Infinity DSP application for the Infinity DSP6840.
  2. AWX_SKAmpConfig.bin – Preset file containing the required configuration of the amplifier.

Instructions for Configuring the Amplifier

  1. Download and install the DSP tuning application.
  2. Power up the amplifier as follows:
    1. Connect the SMPS power supply’s AC power input using the 3-pin Power Cord (exact connections shown in the image below)
    2. Connect the Power Harness of the amplifier as follows:
      1. Red thick wire (+12V) to the +V port of the SMPS power supply,
      2. Black thick wire (0V COM) to the -V port of the SMPS power supply,
      3. Blue thin wire (Remote In) to the +V port of the SMPS power supply.
  3. Connect the amplifier to the PC via USB (USB cable supplied with the amplifier).
  4. If using the JBL DSP-4086 amplifier, set the PC to flight mode.
  5. Now, open the JBL/Infinity DSP application from the Windows Start menu. If the amplifier is properly connected, it will be clearly shown on the top-left of the application.
  6. Download the AWX_SKAmpConfig.bin file.
  7. Load the file from the “Save File → Load Scene” menu:

    In this configuration, output channels 7 and 8 of the amplifier are unused. They may be enabled to drive additional speakers with signals derived from the 6 input channels. For example, an additional sub-woofer or front stereo tweeters may be driven by the amplifier.
  8. Finally,
    1. Select preset “1” from the top-right preset list,
    2. Click the “Write” button,
    3. Select the first row,
    4. Click “Ok” in the renaming window,
    5. Click “Save” in the “Save as Default Scene” window to write the preset into the amplifier.

The amplifier configuration is now complete, and the amplifier may be unplugged from the PC.

Step 4 above (putting the PC in Flight-mode when using the JBL DSP-4086 amplifier) is necessary to ensure that the DSP software starts up correctly and connects to the amplifier (as mentioned in this post). Once the application starts up and the amplifier is connected, Flight-mode may be deactivated.

SKUtility Developer Options

This page contains information relevant to the developer features of the AudioworX Starter Kit, which require a special license. Write to AudioworXSupport@harman.com for details on how to avail the license.

The Starter Kit Utility (SKUtility) includes options for developers to build, flash, run and debug the AWX Amp application on the Starter Kit hardware. Following is the help text for the developer options:
python3 SKUtility.py dev -h

A screenshot of a computer program Description automatically generated
SKUtility developer options help text

Following are the developer actions that can be executed using the SKUtility Tool:

Developer Function Command
Build the AWX Amp application (rpiVirtualAmp) To build the AWX Amp application with the modified AWX External Object, run the command:
python3 SKUtility.py dev -pr rpiVirtualAmp -b
Build the DSP library (VirtualAmp.dll) for GTT To build the DSP library to be used in GTT with the modified AWX External Object, run the command:
python3 SKUtility.py dev -pr virtualAmp -b
Clean the build directory To remove traces of previous builds of either the AWX Amp application or the DSP library in the build directory, run the command:
python3 SKUtility.py dev -pr <rpiVirtualAmp/virtualAmp> -c
Flash the AWX Amp application To flash the custom AWX Amp application (built with the modified AWX External Object) on the Starter Kit hardware, run the command:
python3 SKUtility.py dev -pr rpiVirtualAmp -f
Start the AWX Amp application To start the newly flashed AWX Amp application, run the command:
python3 SKUtility.py dev -pr rpiVirtualAmp -rAlternatively, the following command can be used to reset the AWX Amp application on the Starter Kit hardware:
python3 SKUtility.py rmt -rst

Build AWX External Object

This page contains information relevant to the developer features of the AudioworX Starter Kit, which require a special license. Write to AudioworXSupport@harman.com for details on how to avail the license.

The GTT installation includes the source code for an example audio object called the “AWXAudioObjExt” in the following directory:

C:\Program Files\Harman\HarmanAudioworX\ext-reference-algorithms\external

It is accompanied by an audio object specification document named “AwxAudioObjExt.pdf” in the “docs” directory, explaining how the AO interacts with Extendable Audio Framework (xAF) API to implement a simple gain object.

The files “inc\AwxAudioObjExt\AwxAudioObjExt.h” and “src\AwxAudioObjExt\generic\AwxAudioObjExt.cpp” implement a class named “CAwxAudioObjExt”, which contain the functions that are called by the audio framework during initialization, tuning and run-time:

  1. init(): Called during initialization of the SFD. Assigns memory records and sets up initial states for the AO.
  2. calc(): Called at runtime with input and output stream buffers. Receives audio input frames from the framework and returns processed output audio frames in real-time.
  3. tuneXTP(): Called by a parallel tuning thread to change tuning states of the AO.

These functions can be modified as required to implement a custom audio processing algorithm.

Further information can be found APIs Basic Features and APIs.

C:\Program Files\Harman\HarmanAudioworX\ext‑reference‑algorithms\external\docs\AwxAudioObjExt\AwxAudioObjExt.pdf

The custom AO source code must then be compiled and built into the DSP library for GTT and the AWX Amp application for the Starter Kit hardware, both of which can be executed using the SKUtility tool. The following sections provide instructions on building the custom dll and executable for using the custom AWX External Object.

Building DSP Library with Custom Audio Object


The “ext-reference-algorithms” directory in the installation folder contains build configuration files to build the AWX External Object. Since the modifications are assumed to be made within the existing source code, the custom DSP library for GTT file can be built directly without any updates to the build configuration files by running the following commands in the “StarterKitUtility” directory of the installation folder:

python3 SKUtility.py dev -pr virtualAmp -c # clean the build directory

python3 SKUtility.py dev -pr virtualAmp -b # build the VirtualAmp.dll file

Upon successful compilation of the code, the output DSP library dll can be found in the following location in the installation folder.

xAF\public\lib\win64\Release\VirtualAmpExternal.dll

However, if there are additional files to be compiled along with the AWX External Object source files, they must be included in the below CMake file.

ext-reference-algorithms\external\src\AwxAudioObjExt\CMakeLists.txt

A close-up of a computer screen Description automatically generated

Loading the Custom DSP Library in GTT

The DSP library provides a toolbox of AOs for use in a signal flow, with information on configurations and tuning parameters and their memory requirements on different core types. To be able to use the custom AO in an SFD, the custom-built DSP library must be imported into GTT.

  1. First, start a new instance of GTT in “administrator” mode from the start menu, by right-clicking GTT and clicking Run As Administrator.
  2. In the home screen of GTT, go to the “Audio Library Manager’ and click the Load Audio Library button.
    A screenshot of a computer Description automatically generated
  3. Select the newly built “VirtualAmpExternal.dll” and click Open.
    A screenshot of a computer Description automatically generated
    GTT may show a warning if the imported DSP library has the same version number as an existing one in the library manager. It is recommended that a backup of any previously loaded DSP library is taken for safety. The default DSP library can still be found in the “AudioFrameworkDLLs” of the installation directory.
  4. Once the new DSP library is loaded, the custom AWX External Object can be accessed from the “Toolbox” panel under “External” tab in the signal flow designer view.
    A screenshot of a computer Description automatically generated

Building AWX Amp Application with the Custom Audio Object


The GTT installation also includes the necessary files to build the AWX Amp application along with the custom AO in “StarterKitrpiamp” directory of the installation folder.
To build the custom AWX Amp application, run the following commands from the “StarterKitUtility” folder.

python3 SKUtility.py dev -pr rpiVirtualAmp -c

python3 SKUtility.py dev -pr rpiVirtualAmp -b

A screen shot of a computer program

On successful completion, the “rpiVirtualAmp” executable can be found in the below location.

StarterKit\public\bin\arm64‑v8a\Release\rpiVirtualAmp

Flash the custom AWX Amp application on to the Starter Kit hardware by running the command:

python3 SKUtility.py dev -f

To start the AWX Amp application in the Starter Kit, run the command:

python3 SKUtility.py dev -r

Running Debug Session

This page contains information relevant to the developer features of the AudioworX Starter Kit, which require a special license. Write to AudioworXSupport@harman.com for details on how to avail the license.

The AudioworX Starter Kit facilitates remote debugging of custom Audio object code on the hardware with VS Code using a VS Code workspace and debug configurations that are included in the GTT installation.

Running a remote debug session requires some essential Linux packages to be present on the Raspberry Pi, which are pre-installed in the custom Raspberry Pi image. When using the official Raspbian OS, these packages can be installed using the SKUtility tool by running the command.

python3 SKUtility.py dev -stp

The Raspberry Pi must be connected to the internet to install the required packages.

Running a Debug Session for the Custom AWX External Object

The below steps illustrate how to start a remote debug session and step-through the source code of the custom AWX External Object in an SFD on the Starter Kit hardware.

  1. First, set the Starter Kit to developer mode using the interactive configuration as explained in Starter Kit Utility Tool.
  2. Build the AWX Amp application in “debug” mode, flash it on to the Starter Kit, and start the AWX Amp application on the Starter Kit hardware by running the following commands.
    python3 SKUtility.py dev -pr rpiVirtualAmp -b -d
    python3 SKUtility.py dev -pr rpiVirtualAmp -f -d
    python3 SKUtility.py dev -r
  3. Now, in the GTT window, include the AWX External Object from the toolbox into the SFD, save the SFD and click “Send Device Config” from the “Device Designer” tab of GTT to flash the SFD on to the Starter Kit.
  4. Open a new window of VS Code, go to File > Open Workspace from File, and select the VS Code workspace file named “StartKitDebug.code-workspace” in “StarterKit” directory of the installation directory.
    A screenshot of a computer Description automatically generated
  5. Open the AWX External Object source file “external\src\AwxAudioObjExt\generic\AwxAudioObjExt.cpp” from the file tree.
    A screenshot of a computer Description automatically generated
  6. Place breakpoints in the source code by clicking to the left of the line number intended as shown below (line 42):
    A screenshot of a computer Description automatically generated
  7. Press the “F5” key to start the debug session. This step makes use of the following files to first start a “gdbserver” on the Starter Kit hardware, and thstarts a debug session on VS Code that attaches to the remote gdbserver.
StarterKit\StarterKitUtility\.vscode\launch.json

StarterKit\StarterKitUtility\.vscode\tasks.json

Once the debug session has started, the code will stop at the placed breakpoints as shown below.
A screenshot of a computer

Overview

The AudioworX Starter Kit is intended as a simple and quick-setup tool to fully experience the design and development workflows of audio processing pipelines with AudioworX. It is comprised of commonly available hardware components to ease their sourcing across geographical locations and enable simple assembly, interfacing and usage world-over. Although the Starter Kit is still only available to users in its fully-packaged form on request (write to AudioworXSupport@harman.com), the Starter Kit is designed in a modular fashion to enable interested users even with little to no embedded-system experience to source the hardware components on their own, interface the components and configure the software to prepare the Starter Kit.

The Starter Kit also caters to more advanced users like audio DSP and algorithm engineers with developer options* enabling users to create custom audio objects for use in the AudioworX framework. The software package of the Starter Kit includes the source code for an example custom audio object, and VS Code workspace files for debugging. Additionally, the Starter Kit Utility Tool (SKUtility) is also built with developer options to streamline development and testing.

*The developer features of the AudioworX Starter Kit require a special license. Write to AudioworXSupport@harman.com for details on how to avail the license.

This document provides instructions on assembling a Starter Kit from scratch, setting up the developer environment for building and testing custom Audio Objects, building the custom executable to be run on the Starter Kit hardware, and finally running a debug session to step-through code remotely on the Starter Kit.

Related Topics

Setting Up the Developer Environment

This page contains information relevant to the developer features of the AudioworX Starter Kit, which require a special license. Write to AudioworXSupport@harman.com for details on how to avail the license.

Following is a list of software applications to be installed on a Windows PC to develop, build and debug custom audio objects (AOs) on the Starter Kit:

Download and install the above-mentioned pre-requisites on a Windows 10 or 11 PC.

For steps on how to install GTT and its pre-requisites, Refer Installing AudioworX Setup

The Raspberry Pi Toolchain


The main audio processing component of the AudioworX Starter Kit is the Raspberry Pi 5, which has ARM v8a (64-bit) cores. To cross-compile source code for this architecture, the GCC 10.2.1 toolchain is recommended and can be downloaded from GCC 10.2.1 toolchain:

A screenshot of a computer Description automatically generated
Tool chain Installation

Install the toolchain in the default location (C:\SysGCC\raspberry64).

Python Dependencies

The GTT installation includes the Starter Kit Utility tool (SKUtility), a Python command-line application that provides the ability to remotely operate the Starter Kit hardware over the network. This tool is installed in the following directory (default GTT installation folder):

C:\Program Files\Harman\HarmanAudioworX\StarterKit\StarterKitUtility

For more information on Starter Kit installation and setup, refer to the “Required Software Applications” section of Starter Kit Requirements.