Summary of Contents for Asus AAEON UP Xtreme UP-WHL01
Page 1
UP Xtreme Maker Board UP-WHL01 User’s Manual 1 Last Updated: November 18, 2019...
Page 2
Copyright Notice This document is copyrighted, 2019. 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
Acknowledgement 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 Core are registered trademarks of Intel Corporation ⚫ ITE is a trademark of Integrated Technology Express, Inc. ⚫...
Page 4
Packing List Before setting up your product, please make sure the following items have been shipped: Item Quantity UP-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/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 that you keep this manual for future references 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 10
China RoHS Requirement (EN) Poisonous or Hazardous Substances or Elements in Products AAEON Main Board/ Daughter Board/ Backplane Poisonous or Hazardous Substances or Elements Hexavalent Polybrominated Polybrominated Component Lead Mercury Cadmium Chromium Biphenyls Diphenyl Ethers (Pb) (Hg) (Cd) (Cr(VI)) (PBB) (PBDE) PCB &...
Table of Contents Chapter 1 - Product Specifications..................1 Specifications ......................2 Chapter 2 – Hardware Information ..................5 Dimensions ....................... 6 Jumpers and Connectors ..................7 List of Jumpers and Connectors ................9 2.3.1 Power Button (SW2) ................... 10 2.3.2 RTC (CN1) ......................
Page 12
Driver Download and Installation............... 32 Appendix A – UP Framework SDK Installation ..............33 Introduction ......................34 Installation for Windows 10.................. 34 Installation for Windows IoT Core ..............37 Appendix B – Cables and Connectors ................39 Cables and Connectors ..................40 Appendix C –...
Specifications System Intel® WHL-UE (Core i3/5/7 Ultra Low Power - 15 W) Intel® Celeron™ 4305UE (up to 2.0 GHz) Memory Onboard Single/Dual Channel DDR4 memory, Max 16GB Graphics Intel® Graphics , GEN 9 Display Out HDMI 2.0 x1 (CEC support) DP 1.2 x 1 eDP x 1 Storage...
Page 15
System Expansion Slot Minicard x 1 (PCIe [x1] Gen 3 x 1 (mSATA optional), USB 2.0 x 1) with SIM card M.2 2230 E Key x 1 (PCIe [x1] Gen 3 x 1, USB 2.0 x 2, CNVI x 1) M.2 2280 (double fixing hole) B/M Key x1 (PCIe Gen 3 x 2 / SATA x 1) Expansion HAT (40pin)
Page 16
Internal I/O Connectors eDP with Backlight control Header x 1 10 pin x 1 for USB 2.0 x 1 / HSUART (TTL) x 1 SATA Connector with power connector x 1 4 pin Fan connector x 1 Power Button header x 1 Reset Pin header x 1 M.2 2230/ E Key x 1 M.2 2280 B+M Key x 1...
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 LAN2 CN10 HDMI/DP CN11 DOCKING I...
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...
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...
Signal Signal 3.3V 3.3V 3.3V 3.3V 3.3V 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...
2.3.13 USB 2.0 1x10P Wafer (CN16) Signal Signal USB2_D1- USB2_D1+ UART_RX UART_TX 2.3.14 FAN (CN19) Signal Signal VCC_FAN_CPU_CON FAN_TAC_CPU_CON FAN_CTL_CPU_CON Chapter 2 – Hardware Information...
2.3.15 DC Jack (DC: 24~50V) (CN20) Signal Signal DC_IN 2.3.16 HAT 40 (CN22) Signal Signal 3.3V I2C1_DAT I2C1_CLK ANALOG_DATA1 UART_TX UART_RX ANALOG_DATA2 I2S_BCLK Chapter 2 – Hardware Information...
Driver Download and Installation * Please access https://www.up-community.org and go to the Downloads section>UP Xtreme to find the relevant drivers. Chapter 3 – Drivers Installation...
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 47
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 48
Step 4 Press “Close” to exit once setup is complete. Appendix A – UP Framework SDK Installation...
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 50
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 –...
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...
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 56
CEC Client Installation Supplemental Appendix for UP Xtreme CEC Client Installation...
Page 57
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 58
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 ....................
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 62
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...
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.
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.
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 66
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 67
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 68
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 69
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...
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.
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”.
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.
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”...
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...
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 76
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...
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 78
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 79
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.
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 81
● 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.
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...
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...
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: ●...
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...
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>.
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 92
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]...
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 94
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>...
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...
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 97
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...
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>...
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.
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>...
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 102
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 103
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...
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>...
Need help?
Do you have a question about the AAEON UP Xtreme UP-WHL01 and is the answer not in the manual?
Questions and answers