Asus Aaeon UP Xtreme UPX-WHL01 User Manual
  1. Manuals
  2. Brands
  3. Asus Manuals
  4. Motherboard
  5. Aaeon UP Xtreme UPX-WHL01
  6. User manual
Asus Aaeon UP Xtreme UPX-WHL01 User Manual

Asus Aaeon UP Xtreme UPX-WHL01 User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
UP Xtreme
Maker Board UPX-WHL01
User's Manual 6
Edition
th
Last Updated: June 1, 2021

Advertisement

Table of Contents
loading

Related Manuals for Asus Aaeon UP Xtreme UPX-WHL01

Summary of Contents for Asus Aaeon UP Xtreme UPX-WHL01

  • Page 1 UP Xtreme Maker Board UPX-WHL01 User’s Manual 6 Edition Last Updated: June 1, 2021...
  • Page 2 Copyright Notice This document is copyrighted, 2021. All rights are reserved. The original manufacturer reserves the right to make improvements to the products described in this manual at any time without notice. No part of this manual may be reproduced, copied, translated, or transmitted in any form or by any means without the prior written permission of the original manufacturer.
  • Page 3 Acknowledgements All other product names or trademarks are properties of their respective owners. Microsoft Windows and Windows 10 are registered trademarks of Microsoft ⚫ Corp. Intel® and Celeron® are registered trademarks of Intel Corporation ⚫ Intel Core™ is a registered trademark of Intel Corporation ⚫...
  • Page 4 Packing List Before setting up your product, please make sure the following items have been shipped: Item Quantity UPX-WHL01 If any of these items are missing or damaged, please contact your distributor or sales representative immediately. Preface...
  • Page 5 About this Document This User’s Manual contains all the essential information, such as detailed descriptions, and explanations on the product’s hardware and software features (if any), its specifications, dimensions, jumper/connector settings and definitions, and driver installation instructions (if any) to facilitate users in setting up their product Users may refer to the product page at AAEON.com for the latest version of this document.
  • Page 6 Safety Precautions Please read the following safety instructions carefully. It is advised to keep a printed copy of this manual in an easy to access location for reference. All cautions and warnings on the device should be noted. Make sure the power source matches the power rating of the device. Position the power cord so that people cannot step on it.
  • Page 7 If any of the following situations arises, please the contact our service personnel: Damaged power cord or plug Liquid intrusion to the device iii. Exposure to moisture Device is not working as expected or in a manner as described in this manual The device is dropped or damaged Any obvious signs of damage displayed on the device...
  • Page 8 FCC Statement This device complies with Part 15 FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received including interference that may cause undesired operation.
  • Page 9 China RoHS Requirements (CN) 产品中有毒有害物质或元素名称及含量 AAEON System QO4-381 Rev.A0 有毒有害物质或元素 部件名称 铅 汞 镉 六价铬 多溴联 多溴二苯 苯(PBB) 醚(PBDE) (Pb) (Hg) (Cd) (Cr(VI)) 印刷电路板 × ○ ○ ○ ○ ○ 及其电子组件 外部信号 × ○ ○ ○ ○ ○ 连接器及线材 外壳 ○...
  • Page 10 China RoHS Requirement (EN) Hazardous and Toxic Materials List AAEON System QO4-381 Rev.A0 Hazardous or Toxic Materials or Elements Component Name PCB and Components Wires & Connectors for Ext.Connections Chassis CPU & RAM HDD Drive LCD Module Optical Drive Touch Control Module Battery This form is prepared in compliance with the provisions of SJ/T 11364.

  • Page 11: Table Of Contents

    Table of Contents Chapter 1 - Product Specifications ..................1 Specifications ........................2 Chapter 2 – Hardware Information ..................4 Dimensions ........................5 Jumpers and Connectors ....................6 List of Jumpers and Connectors .................. 8 2.3.1 Power Button (SW2) .................... 9 2.3.2 RTC (CN1) .......................
  • Page 12 Chapter 3 – Drivers Installation .................... 30 Driver Download and Installation ................31 Appendix A – UP Framework SDK Installation ..............34 Introduction ........................35 Installation for Windows 10 ..................35 Installation for Windows IoT Core ................38 Appendix B – Cables and Connectors ................40 Cables and Connectors ....................

  • Page 13: Chapter 1 - Product Specifications

    Chapter 1 Chapter 1 - Product Specifications...

  • Page 14: Specifications

    Specifications System 8th generation Intel® Core i7/i5/i3/Celeron Processor Processor SoC Graphics Intel® Graphics, GEN 9 RJ45 Ethernet Connector x 2 HDMI/DP STACK Connector x 1 Power Button / LED x 1 Audio Jack (Line out + MIC) x 1 DC connector (Lockable) x 1 STM32 connector x 1 eDP with Backlight control Header x 1 10 pin 1xUSB2.0 x 1 / HSUART (TTL) x 1...
  • Page 15 System Expansion M.2 2230 E Key x 1 M.2 2280 M/B+M Key x 1 (M key connector with up to two-lane PCIe) mPCIe slot x 1 100pin connector x 1 40pin HAT RTC battery, CR2032 x 1 Power 12V - 60VDC Dimension 122 x 120 mm Memory...

  • Page 16: Chapter 2 - Hardware Information

    Chapter 2 – Hardware Information Chapter 2...

  • Page 17: Dimensions

    Dimensions Chapter 2 – Hardware Information...

  • Page 18: Jumpers And Connectors

    Jumpers and Connectors Top: Chapter 2 – Hardware Information...
  • Page 19 Bottom: Chapter 2 – Hardware Information...

  • Page 20: List Of Jumpers And Connectors

    List of Jumpers and Connectors Please refer to the table below for all of the board’s jumpers that you can configure for your application Label Function PWR button MINI-CARD M.2_2230_E-KEY M.2 SLOT_M key SATA Connector SATA POWER LAN1 i210 LAN2 i219 CN10 HDMI/DP CN11...

  • Page 21: Power Button (Sw2)

    2.3.1 Power Button (SW2) Signal Signal PWR_SW#_CTL_R PWR_SW#_CTL_R SW1_LED_P SW1_LED_N 2.3.2 RTC (CN1) Signal RTC_VCC Chapter 2 – Hardware Information...

  • Page 22: Mini-Card (Cn2)

    2.3.3 Mini-Card (CN2) Signal Signal WAKE_MINI_N VCC3_MINIPCIE V1.5S P_UIM_PWR P_UIM_DAT PCIE_REFCLK5_P2_N P_UIM_CLK PCIE_REFCLK5_P2_P P_UIM_RST P_UIM_VPP 3G_EN 3G_RST PERN0_MSATA_R+ VCC3_MINIPCIE PERP0_MSATA_R- V1.5S PETN0_MSATA_T- PETP0_MSATA_T+ USB2_DN_R USB2_DP_R VCC3_MINIPCIE VCC3_MINIPCIE Chapter 2 – Hardware Information...

  • Page 23: 2230 E-Key (Cn3)

    Signal Signal MSATA_PCIE_SEL_C V1.5S VCC3_MINIPCIE 2.3.4 M.2 2230 E-Key (CN3) Signal Signal +3.3VAUX_WIFI BT_DP +3.3VAUX_WIFI BT_DM CNV_WR_LANE1_DN CNV_RF_RST# CNV_WR_LANE1_DP CNV_PCMOUT_CLKREQ_ CNV_WR_LANE0_DN CNV_WR_LANE0_DP CNV_WR_CLK_DN CNV_RGI_RSP_R CNV_WR_CLK_DP Chapter 2 – Hardware Information...
  • Page 24 Signal Signal GPP_F6_CNV_RGI_DT_UA RT0_TXD CNV_BRI_DT_R PCIE_C_TXP10 CNV_BRI_DT PCIE_C_TXN10 PCIE_P10_RX_DP PCIE_P10_RX_DN PCIE_REFCLK5_P1_P PCIE_REFCLK5_P1_N SUS_CLK_CPU WIFI_RST# PCIE_M2_CLKREQ# BT_EN WAKE_M2_N WIFI_EN CNV_WT_LANE1_DN CNV_WT_LANE1_DP CLKIN_XTAL_LCP_R CNV_WT_LANE0_DN CNV_WT_LANE0_DP CNV_WT_CLK_DN 3.3VAUX_WIFI CNV_WT_CLK_DP 3.3VAUX_WIFI Chapter 2 – Hardware Information...

  • Page 25: Slot M-Key (Cn4)

    2.3.5 M.2 Slot M-Key (CN4) Signal Signal PCIE_P15_SATA_P1B_TXN +3.3V PCIE_P15_SATA_P1B_TXP +3.3V VPU_EN FULL_CARD_PWR_OFF# PCIE_TXN0 PCIE_TXP0 +3.3V PCIE_RXN0 +3.3V PCIE_RXP0 +3.3V PLT_RST# +3.3V PCIE_CLKREQ# PCIE_CLK_N WAKE_M2 Chapter 2 – Hardware Information...
  • Page 26 Signal Signal PCIE_CLK_P +3.3V PCIE_P15_SATA_P1B_RXN +3.3V PCIE_P15_SATA_P1B_RXP +3.3V Chapter 2 – Hardware Information...

  • Page 27: Sata Connector (Cn5)

    2.3.6 SATA Connector (CN5) Signal Signal SATA_TXP0_C SATA_TXN0_C SATA_RXN0_C SATA_RXP0_C 2.3.7 SATA Power (CN6) Signal Signal +V5S Chapter 2 – Hardware Information...

  • Page 28: Lan1/ Lan2 (Cn7 I210/ Cn8 I219)

    2.3.8 LAN1/ LAN2 (CN7 i210/ CN8 i219) Signal Signal LAN1_TMDI0+ LAN1_TMDI2- LAN1_TMDI0- LAN1_TMDI1- LAN1_TMDI1+ LAN1_TMDI3+ LAN1_TMDI2+ LAN1_TMDI3- 2.3.9 HDMI/ DP (CN10) Signal Signal DDI0_TXP_DP_0 DDI0_TXN_DP_0 DDI0_TXP_DP_1 DDI0_TXN_DP_1 DDI0_TXP_DP_2 DDI0_TXN_DP_2 PORT0_CLK+ PORT0_CLK- CONFIG1 CONFIG2 DP_AUX_P DP_AUX_N DDI0_TYPE_C_HPD Chapter 2 – Hardware Information...

  • Page 29: Docking I (Cn11)

    Signal Signal 3.3V DDI1_TXP_HDMI_0 DDI1_TXN_HDMI_0 DDI1_TXP_HDMI_1 DDI1_TXN_HDMI_1 DDI1_TXP_HDMI_2 DDI1_TXN_HDMI_2 DDI1_CLK+_HDMI DDI1_CLK-_HDMI HDMI1_CEC_D DDC_CLK DDC_DATA DDI1_TYPE_C_HPD 2.3.10 DOCKING I (CN11) Note: Output 12V/2A Signal Signal +12V PCIE_REFCLK2_N +12V PCIE_P3_TXN +12V +12V +12V PCIE_TXP2 +12V PCIE_P3_RXP_SWITCH +12V PCIE_TXN2 Chapter 2 – Hardware Information...
  • Page 30 Signal Signal +12V PCIE_P3_RXN_SWITCH PCIE_RXP2 SATA_P1_USB3_P5_RXN PCIE_RXN2 SATA_P1_USB3_P5_RXP SATA_P1_USB3_P5_TXN SATA_P1_USB3_P5_TXP SATA_RXN0 SATA_RXP0 USB2_DP3 SATA_TXP0 PCIE_REFCLK0_P USB2_DN3 PCIE_REFCLK1_P SATA_TXN0 PCIE_REFCLK0_N PCIE_REFCLK1_N Chapter 2 – Hardware Information...
  • Page 31 Signal Signal PCIE_RXP0 PCIE_RXP1 PCIE_RXN0 PCIE_RXN1 SATA_LED_N PCIE_TXP0 PLTRST_PNLBKLEN PCIE_TXP1 PCIE_TXN0 PCIE_WAKE0_N PCIE_TXN1 PCIE_CLKREQ0# PCIE_WAKE1_N PCIE_CLKREQ1# PCIE_REFCLK2_P PCIE_WAKE2_N PCIE_P3_TXP PCIE_CLKREQ2# Chapter 2 – Hardware Information...

  • Page 32: Edp (Cn13)

    2.3.11 EDP (CN13) Signal Signal data positive 0 data negative 0 data positive 1 data negative 1 data positive 2 data negative 2 data positive 3 data negative 3 AUX positive AUX negative Hot Plug Detect Back Light Control VDD Enable Back Light Enable I2C_CLK I2C_DAT...

  • Page 33: Usb Type A Connector (Cn14/ Cn15)

    2.3.12 USB Type A Connector (CN14/ CN15) Signal Signal USB2_D1- USB2_D1+ USB3_RX1- USB3_RX1+ USB3_TX1- USB3_TX1+ USB2_D2- USB2_D2+ USB3_RX2- USB3_RX2+ USB3_TX2- USB3_TX2+ Chapter 2 – Hardware Information...

  • Page 34: Usb 2.0 1X10P Wafer (Cn16)

    2.3.13 USB 2.0 1x10P Wafer (CN16) Signal Signal USB2_D1- USB2_D1+ UART_RX UART_TX 2.3.14 CPLD and BIOS Update (CN18) Signal Signal JTAG_TCK JTAG_TDO 1.8V JTAG_TMS SPI_CS SPI_CLK SPI_MISO JTAG_TDI SPI_MOSI SPI_HOLD Chapter 2 – Hardware Information...

  • Page 35: Fan (Cn19)

    2.3.15 FAN (CN19) Signal Signal VCC_FAN_CPU_CON FAN_TAC_CPU_CON FAN_CTL_CPU_CON 2.3.16 DC Jack (DC: 12~60V) (CN20) Signal Signal DC_IN Chapter 2 – Hardware Information...

  • Page 36: Hat 40 (Cn22)

    2.3.17 HAT 40 (CN22) Note: Output 3.3V/2A, 5V/2A Signal BIOS GPIO0/I2C1_SDA GPIO1 GPIO1/I2C1_SCL GPIO2 GPIO2/ADC_in1 GPIO3 GPIO15/UART_TXD GPIO16 GPIO16/UART_RXD GPIO17 GPIO3/UART_RTX/ADC_in2 GPIO4 GPIO17/I2S_BCLK GPIO18 GPIO4/ADC_in3 GPIO5 GPIO5/ADC_in4 GPIO6 GPIO18 GPIO19 GPIO19 GPIO20 GPIO6/SPI_1_TXD GPIO7 GPIO7/SPI_1_RXD GPIO8 Chapter 2 – Hardware Information...
  • Page 37 Signal BIOS GPIO20 GPIO21 GPIO8/SPI_1_CLK GPIO9 GPIO21/SPI_1_FSO GPIO22 GPIO22/SPI_1_FS1 GPIO23 GPIO9/I2C0_SDA GPIO10 GPIO23/I2C0_SCL GPIO24 GPIO10 GPIO11 GPIO11 GPIO12 GPIO24 GPIO25 GPIO12 GPIO13 GPIO13/I2S_WS_SYNC GPIO14 GPIO25/UART_CTS GPIO26 GPIO14 GPIO15 GPIO26/I2S_SDI GPIO27 GPIO27/I2S_SDO GPIO28 Note: Open-drain I2C bus. Needs the pullup resistors to external 3.3V. Chapter 2 –...

  • Page 38: Audio Jack (Cn24)

    2.3.18 Audio Jack (CN24) Signal Signal MIC_LR_CN AGND LOUT_R LOUT_L 2.3.19 STM32 MCU (CN25) Signal Signal +3V_MCU +3V_MCU STM32_PB1 STM32_VBAT STM32_PB7 STM32_PC8 STM32_PB6 STM32_PB9 STM32_PB5 STM32_PC15 STM32_PB4 MCU_NRST_R STM32_PB3 MCU_WKUP_R USB_RENUMn STM32_PA1 Chapter 2 – Hardware Information...

  • Page 39: Docking Ii (Cn26)

    Signal Signal SWDCLK_R STM32_PA2 SWDIO_R STM32_PA3 STM32_PA4 STM32_PA5 STM32_PA10 STM32_PA6 STM32_PA9 STM32_PA7 STM32_PA8 HDMI1_CEC_D STM32_PB15 STM32_PB2 STM32_PB14 HOST_I2C_SCL STM32_PB13 HOST_I2C_SDA MCU_INT_R +V5S 2.3.20 DOCKING II (CN26) Signal Signal SLP_S3# V1.8S STACK_GPIO1 V1.8S STACK_GPIO2 LPC_AD0 STACK_GPIO3 LPC_AD1 STACK_GPIO4 LPC_AD2 STACK_GPIO5 LPC_AD3 STACK_GPIO6 LPC_FRAME_R BUF_PLT_RST#...

  • Page 40: Reset Pin Header (Cn27)

    Signal Signal STACK_GPIO7 SMB_CLK_A I2C_SCL4_1V8 SMB_DATA_A I2C_SDA4_1V8 INT_SERIRQ_3P3 +V3.3S +V3.3S +V5S +V5S 2.3.21 Reset Pin Header (CN27) Signal PMU_RSTBTN_N Chapter 2 – Hardware Information...

  • Page 41: Com Port 1/ Port 2 (Com1/Com2)

    2.3.22 COM Port 1/ Port 2 (COM1/COM2) Signal DCDA / RS422TX- / RS485- RXA / RS422TX+ / RS485+ TXA / RS422RX+ DTRA / RS422RX- DSRA RTSA CTSA Chapter 2 – Hardware Information...

  • Page 42: Chapter 3 - Drivers Installation

    Chapter 3 Chapter 3 – Drivers Installation...

  • Page 43: Driver Download And Installation

    Driver Download and Installation Access https://www.up-community.org and go to the Downloads Section> UP Xtreme to find the relevant drivers. After downloading and installing the drivers you will see three unknown devices in Windows Device Manager. Unknown Device 1: Multimedia Audio Controller To clear this, go to CBR setup and navigate to the following menu: CRB Chipset >...
  • Page 44 Unknown Device 2: AANT0F04 AANT0F04 is the 40pin HAT CPLD, there is no Windows driver for this device. Unknown Device 3: ADC081C ADC081C is ADC, there is no Windows driver for this device Chapter 3 – Drivers Installation...
  • Page 45 Unknown USB Device Some users may see an “Unknown USB Device (Device Descriptor Request Failed)” in Windows Device Manager. This is a common occurrence in Windows. The issue occurs because there is no corresponding device firmware or driver available for the USB port connecting to ST stm32f microcontroller (CN25).

  • Page 46: Appendix A - Up Framework Sdk Installation

    Appendix A Appendix A – UP Framework SDK Installation...

  • Page 47: Introduction

    Introduction This section provides instructions for the installation of the UP Framework SDK. Instructions are provided for Windows 10 and Windows IoT Core. You can download the latest version of UP Framework SDK from the UP community: https://downloads.up-community.org/download/up-sdk-for-windows-10-and-windows-iot/ Installation for Windows 10 Step 1 Locate the downloaded file UpFrameworkSetup.msi and run the installer.
  • Page 48 Step 2 Select the installation folder. Default destination path is C:\Program Files(x86)\AAEON\ You may also choose to install the UP Framework SDK for all users or only the current user. Press “Next” to continue installation. Step 3 Press “Next” to confirm the installation. Appendix A –...
  • Page 49 Step 4 Press “Close” to exit once setup is complete. Appendix A – UP Framework SDK Installation...

  • Page 50: Installation For Windows Iot Core

    Installation for Windows IoT Core Before you begin, make sure you have downloaded and installed the latest version of the Windows IoT Core image from the UP community. Installation requires using a connected PC with the UP Framework SDK software downloaded and saved.
  • Page 51 Step 2 Download the UP Framework SDK to your PC and unzip the files. Open PowerShell as an Administrator. Run the command RemoteInstallation.ps1 to install the UP Framework SDK. Enter the IP address of the UP IoT Core device when prompted. Appendix A –...

  • Page 52: Appendix B - Cables And Connectors

    Appendix B Appendix B – Cables and Connectors...

  • Page 53: Cables And Connectors

    Cables and Connectors This table provides detailed information about the cables and connectors used by the UP Xtreme (UP-WHL01). If you have any questions about the configuration of your board, please contact your AAEON sales representative. Connector Mating Cable Mating Cable Connector PN Description Label...
  • Page 54 Connector Mating Cable Mating Cable Connector PN Description Label Description (TF)PIN CPLD and BIOS HEADER.6*2P.180D(M CN18 1653006205 Updater ).DIP.1.27mm.Astron.2 7-4121-206-1G-R CPU Smart Fan CPU Cooler.Fan+Heat CN19 165500401A 175920001F Connector (3-pin) Sink.12V.3P.for UPWH 12 ~ 60 VDC Input CN20 165250320K (Lockable, OD/ID: 5.1/2.5 mm) 40-pin HAT CN22...
  • Page 55 Appendix C Appendix C – CEC-Client Installation...
  • Page 56 CEC-Client Installation Manual The CEC-Client Installation Manual is attached to this manual. It provides information for setting up the CEC-Client to allow the UP Xtreme to communicate with CEC enabled devices through the HDMI port. If you have any questions, please contact your AAEON Sales Representative.
  • Page 57 CEC Client Installation Supplemental Appendix for UP Xtreme CEC Client Installation...
  • Page 58 Table of Contents Chapter 1 Introduction ......................4 About this Document ..................... 4 Chapter 2 CEC-Client Installation ................... 4 Introduction ......................4 Windows Installation ....................4 2.2.1 Kodi Installation on Windows ..............8 libCEC and USB-CEC Installation for Ubuntu on UP Xtreme ....... 8 Flashing DFU Firmware on STM Board –...
  • Page 59 5.1.2 Routing Control .................... 35 5.1.3 System Standby .................... 35 5.1.4 One Touch Record ..................35 5.1.5 Timer Programming ..................36 5.1.6 System Information ..................38 5.1.7 Deck Control ....................40 5.1.8 Tuner Control ....................41 5.1.9 Vendor Specific Commands ..............43 5.1.10 OSD Display ....................

  • Page 60: Appendix C - Cec-Client Installation

    Chapter 1 Introduction About this Document This document is included as a supplement to the product manual for the UP Xtreme (UP-WHL01). If you do not have the product manual for your device, please visit the product page on AAEON.com to download the full version. This document is intended for use only with the UP Xtreme product manual and is not for use as a separate document nor for use with any other product.
  • Page 61 Image 1: Select Installation Path (default path shown) Image 2: Create Shortcut CEC Client Installation...
  • Page 62 Image 3: Installing Visual Studio Runtime Libraries Image 4: Finish Installation CEC Client Installation...
  • Page 63 After installation is complete, open the folder location where you installed libCEC- AAEON. The default path location is shown in the image below. Image 5: CEC-Client File Location CEC Client Installation...

  • Page 64: Kodi Installation On Windows

    Open a Command Prompt window in the file location. Run cec-client.exe -h to display all program options. Image 6: CEC-Client Command Prompt 2.2.1 Kodi Installation on Windows Before running Kodi on Windows, copy cec.dll from the CEC-Client folder (Image 5) to the Kodi installation folder.

  • Page 65: Flashing Dfu Firmware On Stm Board - Windows

    CEC-Client and libCEC-AAEON require installing GDebi in order to run on Ubuntu. This step is performed in Terminal (Command Line). In Terminal, enter the command: sudo apt-get install gdebi After the process is completed, libCEC can be installed. Run the installer libcec4_4.0.4.1~bionic_amd64.deb from the deliverables folder.

  • Page 66: Installation Procedure For Dfuse Demo

    Download the .dfu file from the deliverables folder. Extract the files, then connect the board to the PC with a USB-C cable. Flashing the firmware file on board requires it to be transferred using a DFU Bootloader program. The steps show below use DfuSe USB Device Firmware Upgrade to perform these actions.
  • Page 67 The DfuSe application drivers for Windows 10 should be installed automatically. If they are not, follow the procedures below to install DfuSe drivers. When starting driver installation for target device, the “Found New Hardware Wizards” should appear as shown: Image 9: New Hardware Wizard Choose “Install from a list or specific location (Advanced)”...
  • Page 68 In the next window, select “Don’t search. I will choose the driver to install.” Image 10: Choose Install Options If the DfuSe drivers are installed, you will see a list of compatible hardware models. Image 11: DfuSe Drivers are installed CEC Client Installation...
  • Page 69 If there are no models listed, the drivers are not installed. Click on “Have Disk…” to select the drivers. In the Install from Disk dialog box, select browse and select the folder where the drivers are located and press “OK”. Default location is C:/Program Files/STMicroelectronics/DfuSe/Driver Image 12: Install from Disk The installer will automatically find and select the .INF and the hardware model will be...
  • Page 70 Image 13: Installation During installation, the following error message will appear. Click “Continue Anyway” to finish installing DfuSe drivers. Image 14: Continue Anyway CEC Client Installation...

  • Page 71: Installing Dfu-Util On Windows

    Image 15: Installation Finished DfuSe Installation will complete automatically. Click “Finish” once it is complete. Installing dfu-util on Windows This section details how to install dfu-util for programming the flash memory. It can be used to program both the Device OS and application firmware, as well as save and restore configurations.

  • Page 72: Switching Device In Dfu Mode

    Next, open Windows 10 Settings. In the top search field, type “environment” and select “Edit the system environment variables” when it appears. Click the “Environment Variables…” button at the bottom of the page. In the Environment Variables window, select “Path” in the System Variables list (bottom list) and click “Edit”.

  • Page 73: Flashing Dfu Firmware File On Stm Board On Linux

    Flashing DFU firmware file on STM board on Linux 2.8.1 STM32f042k6 This section details how to load the DFU firmware file onto STM32f042k6 MCU on Linux. First, install the required software tool from Terminal using the command: sudo apt-get install dfu-util After installing the dfu-util software tool, use the following procedure to conduct the firmware upgrade and load the upgraded firmware file using dfu-util onto the board’s MCU on Linux software platform.

  • Page 74: Installing Stm32Cubeprogrammer On Windows

    The following software needs to be downloaded before begining: Official Java JRE from the Oracle website, version 8 or higher: https://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads- 2133155.html STM32CubeProgrammer from the official ST site: https://www.st.com/en/development-tools/stm32cubeprog.html For Windows, the driver for ST-Link is also needed: https://www.st.com/en/development-tools/stsw-link009.html 2.9.1 Installing STM32CubeProgrammer on Windows Install Java JRE: Run setup program “jre-8u221-windows-x64.exe”...

  • Page 75: Installing Stm32Cubeprogrammer On Linux

    2.9.2 Installing STM32CubeProgrammer on Linux Install Java Runtime Environment: Unpack Java JRE archive into your home directory tar -xf jre-8u221-linux-x64.tar.gz -C ~ Rename directory "jre1.8.0_221" to "jre" Install STM32CubeProgrammer: Unpack archive "en.stm32cubeprog.zip" with command unzip: unzip en.stm32cubeprog.zip Set permissions for executing using command chmod: chmod +x SetupSTM32CubeProgrammer-2.1.0.linux Run installer using command: JAVA_HOME=~/jre ./SetupSTM32CubeProgrammer-2.1.0.linux...

  • Page 76: Flashing Bootloader Or Combined Image

    Edit file ~/STM32CubeProgrammer/util/openJFXScript.csh Change line 4 from: JAVA_PATH=`which java` JAVA_PATH=~/jre/bin/java Edit file ~/STM32CubeProgrammer/bin/STM32CubeProgrammer Below first line: #!/bin/bash Insert the line: export JAVA_HOME=~/jre 2.9.3 Flashing Bootloader or Combined Image The steps for using STM32CubeProgramer to flash bootloader or combined image is the same for both Windows and Linux.
  • Page 77 Click on "Start Programming" button Restart is needed after flashing combined image to be operative Note: If you are unable to connect to the device, try changing ST-Link configuration option Mode from “Normal” to “Under reset”. CEC Client Installation...

  • Page 78: Chapter 3 Api

    Chapter 3 API Image 17: CEC Network STM32F10xxx device should be connected to Host CPU through USB (Communication Device Class) and HDMI CEC pin of baseboard. Firmware application should re-use already available CEC library from ST and provide adaptation layer which should enable access to CEC bus operation from USB host.
  • Page 79 STM32 device should be detected on USB host as a USB CDC serial device. Each of the API functions and input/output arguments should be serialized in the following way: ● Sending a cec command is executed by sending a string in the following format via CDC: send <address>...
  • Page 80 Image 18: Firmware Sending/Receiving Messages Firmware Command Description help View list of available commands get <name> Returns value of variable with specified name.† set <name> [value] Set value of variable.‡ send <address> [data] Send data over CEC network to specified address. bootloader Call STM bootloader and switch device to DFU mode.

  • Page 81: Chapter 4 Libcec

    Chapter 4 libCEC CEC (Consumer Electronics Control) allows for control of devices through the HDMI port. With the right hardware, libCEC allows control of the device with a TV remote. libCEC is an enabling platform for the CEC bus in HDMI. It allows developers to interact with other HDMI devices without having to worry about communication overhead, handshaking, and various ways of sending a message for each vendor.
  • Page 82 ● CAAEONAdapterCommands is a class that is used to send and receive data from the CDC, as well as for parsing and serializing data between firmware and libCEC format. libCEC Driver for Windows is the standard driver for serial communication included with the Windows installation.

  • Page 83: Demo Application Cec-Client.exe

    Demo Application cec-client.exe To send custom CEC commands from PC to TV through libCEC-AAEON adapter, you will need to install the cec-client. This is an .exe file that is included in the libCEC and Windows driver package. A new CEC-Client was made with libCEC-AAEON adapter and compiled libCEC in which a new adapter was added (3.2.1 Compile libCEC) 4.2.1 CEC-Client...

  • Page 84: Testing Cec-Client

    4.2.2 Testing CEC-Client CEC-Client must be run from Terminal. Type cec-client.exe to run it. After CEC-Client starts, it will open CEC-Client Terminal Application. From CEC-Client Terminal Application, you can send commands for testing. Some CEC-Client commands for testing libCEC are listed in the following table. Command Description tx 10:44:41...

  • Page 85: Chapter 5 Supported Commands

    Chapter 5 Supported Commands This section describes the message transfer and additional details for a number of common features enabled by CEC. Note that where a feature is supported, all messages within that feature should be implemented. Limitations Firmware Limitations: ●...
  • Page 86 CEC Client Installation...
  • Page 87 † Supported by all devices except TVs. CEC Client Installation...
  • Page 88 CEC Client Installation...
  • Page 89 ‡ Some models require you to turn on “Auto-Standby” in the Anynet+settings to enable this feature. CEC Client Installation...

  • Page 90: One Touch Play

    5.1.1 One Touch Play Command Feature: The One Touch Play feature allows a device to be played and become the active source with a single button press. The following messages are used for the One Touch Play feature: <Active Source>, <Image View On>, <Text View On>. OpCode Value Description...

  • Page 91: Routing Control

    5.1.2 Routing Control Command Feature: This feature is used to control the routing of the HDMI network by controlling CEC Switches. The following messages are used for the Routing Control feature: <Active Source>, <Inactive Source>, <Request Active Source>, <Set Stream Path>, <Routing Change>, <Routing Information>.

  • Page 92: Timer Programming

    OpCode Value Description Parameters Response Supported <Record 0x09 Attempt to [Record Enter ‘Recording’ On> record the Source] state and start specified source. recording if possible. Send the initiator <Record Status>. <Record 0x0A Used by a [Record Status> Recording Status Info] Device to inform the initiator of the message...
  • Page 93 OpCode Value Description Parameters Response Supported <Set 0x34 Used to set a [Day of Month] <Timer Status> Analogue single timer [Month of message Timer> block on an Year] Analogue [Start Time] Recording [Duration] Device. [Recording Sequence] [Analogue Broadcast Type] [Analogue Frequency] [Broadcast System]...

  • Page 94: System Information

    OpCode Value Description Parameters Response Supported <Set Timer 0x67 Used to set the [Program Title Recording device Program name of a String] stores title for Title> program future reference. associated with Ignore message if a timer block. it is not the Sent directly immediate next after sending a...
  • Page 95 OpCode Value Description Parameters Response Supported <CEC 0x9E Used to indicate the [CEC Version> supported CEC Version] version, in response to a <Get CEC Version> <Get CEC 0x9F Used by a device to None The source Version> enquire which responds with a version of CEC the <CEC Version>...

  • Page 96: Deck Control

    5.1.7 Deck Control Command Feature: This feature allows a Playback Device (a deck or disc player or recorder) to be controlled by another device (e.g. TV). The following messages are used for the Deck Control feature: <Deck Status>, <Give Deck Status>, <Deck Control>, <Play>. OpCode Value Description...

  • Page 97: Tuner Control

    OpCode Value Description Parameters Response Supported <Play> 0x41 Used to [Play Perform the specified control the Mode] actions, or return a playback <Feature Abort> behavior of a message. If media is source device. available the device enters ‘Deck Active’ state. If the device is in standby, has media available and the parameter is [“Play...
  • Page 98 OpCode Value Description Parameters Response Supported <Select 0x92 Directly selects [Analogue Change to the Analogue an Analogue TV Broadcast selected analogue Service> service Type] service and [Analogue stream its output Frequency] on the HDMI [Broadcast connection. If the System] tuner device is not capable of selecting this service, respond...

  • Page 99: Vendor Specific Commands

    5.1.9 Vendor Specific Commands Command Feature: This feature allows a set of vendor specific commands to be used to communicate between devices. The following messages are used for the Vendor Specific Commands feature: <Device Vendor ID>, <Give Device Vendor ID>, <Vendor Command>, <Vendor Command With ID>, <Vendor Remote Button Down>, <Vendor Remote Button Up>...

  • Page 100: Device Osd Name Transfer

    OpCode Value Description Parameters Response Supported <Set OSD 0x64 Used to send a [Display TV displays the String> text message to Control] message. output on a TV. [OSD String] 5.1.11 Device OSD Name Transfer Command Feature: This feature is used to request the preferred name of a device to be used in any on screen display (e.g.

  • Page 101: Remote Control Passthrough

    OpCode Value Description Parameters Response Supported <User 0x45 Indicates that user None Update display or Control released a remote perform an action, Released> control button (the as required. last one indicated by the <User Control Pressed> message) <Menu 0x8D A request from the [Menu May enter or exit Request>...

  • Page 102: Give Device Power Status

    OpCode Value Description Parameters Response Supported <User 0x44 Used to indicate Update display Control that the user Command] or perform an Pressed> pressed a remote action, as control button or required. switched from one remote control button to another. <User 0x45 Indicates that user None...
  • Page 103 The following messages are used for the System Audio Control feature: <Give Audio Status>, <Give System Audio Mode Status>, <Report Audio Status>, <Set System Audio Mode>, <System Audio Mode Request>, <System Audio Mode Status>, <User Control Pressed>, <User Control Released>. OpCode Value Description...
  • Page 104 OpCode Value Description Parameters Response Supported <System 0x70 A device [Physical The amplifier comes Audio implementing Address] out of standby (if Mode System Audio necessary) and Request> Control and which switches to the has volume relevant connector control RC buttons for device specified (eg TV or STB) by [Physical...

  • Page 105: Audio Rate Control

    5.1.16 Audio Rate Control Command Feature: This feature allows the audio playback rate of a Source Device to be controlled by another device, e.g. an Audio System. The following messages are used for the Audio Rate Control Feature: <Set Audio Rate>...

Table of Contents