This project is intended to help you get familiar with the QCA4020 System-On-Chip (SoC) Product Development kit. The QCA4020 IoT solution offers Wi-Fi, Bluetooth low energy (BLE), and 802.15.4 capable radios in a single-chip package.CLI- based demo application that is included in the SKD provides a mechanism to demonstrate different features and technologies that QCA402x supports.Objective
The objective of this demo is to get familiar with the QCA4020 development kit and understand how developers can test all the features using the QCLI_Demo application.What is the QCLI_Demo application?
QCLI_Demo is a sample application that is included in the SDK. It is designed to provide a command line interface to most of the features available on the QCA402x development platform. The command framework is implemented as a set of nested menus and each menu provides a list of sub-commands that correspond to a feature or technology.How does the QCLI_Demo tap into various features of the QCA4020 development kit?
The QCLI_Demo uses the QAPIs framework to demonstrate different features. It is designed to provide a reference implementation and usage of customer facing QAPI’sSo, what are QAPIs?
Qualcomm® API (QAPI) is an interface provided by Qualcomm Technologies, Inc. and/or its subsidiaries to abstract OEM software from low-level system software. QAPI provides access to low-level system software exposing SoC hardware/peripherals, I/O interfaces, communication interfaces, network services, security services, hardware/software conﬁguration and power management interfaces, and all other associated functionality deemed part of a chip support package. QAPI is meant to enhance portability of application-speciﬁc OEM software by abstracting it from low-level system software provided by Qualcomm Technologies.Materials Required / Parts List / ToolsAdditional ResourcesBuild / Assembly InstructionsIn the Box
The contents of the QCA4020 Development kit, as seen above, include:
- QCA4020 development board
- USB to Micro USB cables
- Power supply
- Setup guide
For the time being, you can set the kit aside while you install the software components and set up the development environment on your computer. During the setup process, you will only briefly use the kit while installing the FTDI drivers for JTAG.Setup the development environment
- Install Python version 2.7.XSome of the support scripts are Python-based so be sure to install Python 2.7.X because the support scripts do not support Python 3. After installation, add the path to python. Example: If python.exe is in the folder
C:\CRMApps\Apps\Python276-64set path as follows:
- Install Eclipse IDE for C/C++: GUI based integrated development environment Supported Version: Oxygen version - Release 4.7.2 Install Java: Eclipse IDE has dependency on Java, JDK 8 or higher. After installation, add path to Java. Example: If Java.exe is in
C:\ProgramData\Oracle\Java\javapathset path as follows:
%PATH%=%PATH%: C:\Program Files\Java\jdk1.8.0_161\bin
- Install OpenOCD version 0.10.0 [2017-06-09] which is available here. OpenOCD plugin is required to establish the connection between Eclipse IDE and onboard FTDI JTAG debugger. After installation, add the path to OpenOCD. Example: If openocd.exe is in
C:\Program Files\OpenOCD-20170609\binset path as follows:
set %PATH%=%PATH%:C:\Program Files\OpenOCD-20170609\bin
- Download GNU Arm Embedded toolchain version 6.x (gcc-arm-none-eabi-6-2017-q2-update). Install by running the ".exe" file and make sure you select the option to "Add path to environment variables" during the final step.
- Setup OpenOCD plugin usage with Eclipse Install GNU MCU plugin for Eclipse
Go to Help > Install new softwarein Eclipse IDE
- In the Available Software window, click "Add" and enter the Name and Location of the repository. Location: "
http://gnu-mcu-eclipse.netlify.com/v4-neonupdates" Enter details and click "OK" as seen below.
- Select "
GNU ARM & RISC-V C/C++ Cross Development Tools" and click "Next" as seen below.
- You will see the list of Items to be installed as seen below. click "Next".
- Follow the on-screen instructions and select "Finish" to complete the installation.
- Restart the Eclipse IDE
- Set path to openOCD Restart the Eclipse IDE and under
Window > preferencesset path to openOCD as seen below.
- Set the Debug Config Go to
Run >Debug Configurations > GDB OpenOCD DebuggingSet the Application and OpenOCD options as show in the images below.
- Select Quartz.elf as the C/C++ application. If you have already built the image, select Disable auto build. If image is not built, select Use workspace settings.
- In the Debugger window, provide the openocd executable path with config option,
- Provide the arm-none-eabi-dgb executable path for the GDB client as seen below.
- Download "QCA4020 OEM SDK+CDB" which is available under the Qualcomm Developer Network software section here. The SDK contains sample demo applications with source code to demonstrate different features and technologies that QCA402x supports. Demos are in the following folder:
- Install the QCA plugin jar file available at
- Copy the jar file (QCA402x_plugin.jar) to the "dropin" folder under the Eclipse IDE installed folder.
- Restart the Eclipse IDE if running. To restart Eclipse, click on the File menu of Eclipse IDE and select the Restart menu item after the plug-in is installed.
- Install FTDI driver for JTAG
- Download the zadig application from http://zadig.akeo.ie/.
- Connect the J85 connector on the development board to the host PC using the included Micro-USB cable.
- Once the QCA4020 Development board is connected to the host PC, the Device Manager shows two COM ports. The lower port number is for JTAG and the upper port number is for serial connection.
- Run zadig.exe file and go to
Options > List All devicesand select the device in the drop down. Dual RS232-HS (interface 0) represents lower port number and dual RS232-HS (interface 1) represents higher port number. The following example shows Select Dual RS232-HS (interface 0) to install FTDI on the WinUSB driver for JTAG interface.
- After installing the FTDI driver, the Device Manager will look as seen below.
Make sure that the paths are set correctly under the environment variables. They should be set as seen below.
Congratulations, you have now successfully set up the development environment for the QCA4020 development kit. The next section shows you how to import the sample “Hello World” application.Import sample "QCLI_Demo" application
- Install Eclipse project files for sample demo applications. To install there is
eclipseSupport.batfor Windows and
eclipseSupport.shfor Linux in
- Open a terminal window and navigate to
- Run the
eclipseSupport.batcommand. After executing the script, the Eclipse project files.cproject,.project and.settings folder are updated in the respective folders of the demo applications.
- Open the Eclipse application.
- Go to
File > Open Projectsfrom File System and set import source for the demo application.
- You should be able to see the import source as an Eclipse project.
- Click Finish.
Next, build the application.Build the Application
- Configure the QCLI demo:The QCLI demo provides a CLI menu for all the features and technologies supported on QCA402x. A user may choose to disable certain features (for example, due to lack of flash space). For this purpose, a configuration file is provided in the SDK that allows configuring each feature to “true” or “false”. For example:To disable the Zigbee feature, edit the env.config file:
Change: ‘CFG_FEATURE_ZIGBEE=true’ To: ‘CFG_FEATURE_ZIGBEE=false’
- To apply the new configuration:On Windows, run ‘setenv.bat’.On Linux, run ‘. setenv.sh’.
- Go to:
Project properties > Configure buildsetting.
- Right click on the project name in project explorer and go to “Properties”.
- Verify the build command and the build directory in the Builder settings tab.
- Go to C/C++ build and set the build command to “build.bat”, and the build directory to “path to source”.
- Click “Apply and Close”.
- Build the application and you should see the following messages in Console Window.
- Next flash the application.
Alright, time to start playing with the Developer Kit.
- Setup the QCA4020 development board as described in Appendix A, "CDB2x board setup" in QCA402x-CDB2x development kit user’s guide.
- Put the jumper on J31 1&2 on the QCA4020 development board. Tip: There is a "Dot" next to each header that indicates the position of Pin Number 1. After the flashing through JTAG is done, remove the jumper. Jumpers on the developer board should be as seen below.
- Jumper on J31 (Pins 1 and 2), Cross connect pins 2 and 3 of J38 and J39
- Jumpers on J30 and J32
- Jumpers on J57 and J36
- Open Eclipse IDE and navigate to:
Run > External Tools > External Tools Configuration
- Click on the program, create a new launch configuration and update the paths as shown below in the Main tab.
- Provide the path for "flash_openocd.bat" or "flash_openocd.sh" in the location box.
- To flash the program, click Run > External Tools > OpenOCD JTAG Flashing The flashing logs can be seen on the Eclipse console. You will see the following lines at the end of the log:
[2018-07-17 16:51:24,434] INFO: Script finished processing generated_fwd_table.xml File:flash_through_gdb.py:699 Function:main Flash Operation Completed Successfully... SUCCESS: The process "openocd.exe" with PID 17776 has been terminated.
- The application was flashed successfully on the development board.
The Autoboot mode refers to the mode where the system boots up on a power cycle and no JTAG connectivity is required. Follow the below steps to run the application in Autoboot mode.
- Remove the jumper on J31.This was connected to flash the image on the board.
- Power cycle the system.
Once the board powers up, open a serial console on your host PC.
Connect it to the com port number assigned to the USB-serial connection with the following settings.
- Baud Rate: 115200
- Data Bits: 8
- Parity: None
- Stop bit: 1
- Flow Control: None
You should see the following CLI menu on the serial console. You can now type the commands to test the system features.
The CLI menu is divided in groups and sub-groups. Each level/menu provides a list of sub-commands that correspond to a feature or technology.
Two example command lists are shown below − the first being at the top-level and the second after navigating into the WLAN group.
Command List:Commands: 1. Help 2. Exit Subgroups: 3. HMI 4. WLAN 5. Net
WLAN group command list
Command List:Commands: 1. Help 2. Up 3. Root 4. Enable 5. Connect 6. Disconnect Subgroups: 7. SupPart1 8. SupPart2
Congratulations! You have set up with QCA4020 development environment and flashed the board with the QCLI_Demo. You can now start testing various features by sending commands over serial port.What can you do with the QCLI_Demo?
There are subgroups and sub-commands for:
- Certificate management demo
- Firmware Update
- Low Power
- File System
- Secure FS
- AWS demo
For more information on all the sub-commands, please check out section 6, page 69 of the QCA4020 development kit user’s guide.