This is an old revision of the document!
The ADuCM360_demo_cli is a Command Line Interpreter (CLI) demo project for the EVAL-ADICUP360 base board, created using the GNU ARM Eclipse Plug-ins in Eclipse environment.
The purpose of this project is to help you to get used with UART peripheral of ADuCM360 microcontroller. The source code example can serve as a template for a resident command line interpreter, complementing any other user application functionality.
Interrupt-based receiving of text commands from the UART is implemented. As soon as a command is entered, an execution request flag is raised to signal the main loop. The commands are recognised and may be executed immediately or later depending on the priority of the current tasks.
You can use any Terminal session you want, such as Putty or Serial Terminal with Eclipse Kepler (incorporated in Eclipse environment).
A serial connection of a PC to the EVAL-ADICUP360 board using the user USB connector is required to test and use the CLI application (EVAL-ADICUP360 board incorporates an FTDI USB-to-serial converter). Any terminal application run on a PC at 9600-8-N-1 without flow control can be used to 'talk' to the EVAL-ADICUP360 board. After connecting and sending CR (by pressing Enter), the command prompt '»' and a welcome message should appear.
Command | Description |
---|---|
help | Display available commands |
version | Display SW version of CLI project |
dump [begaddr] [count] | Display up to 0x40 consecutive byte-size locations from any address of the ADuCM360 memory space. One should be careful not to request locations which are not decoded because the hardware_fault exception code will block the board. |
reset | Perform a HW reset which also initialize the application |
The following is a list of items needed in order to replicate this demo.
In order to program the EVAL-ADICUP360 you need to use the DEBUG USB. The jumper set up is shown in the next figure. The important jumpers are highlighted in red.
The ADuCM360_cli_demo can connect to the serial port of a PC through two different USB ports on the board:
A bank of jumpers provided near the PMOD ports of the EVAL-ADICUP360, makes this easy to configure. The jumpers required for particular configurations are provided in the images below. Ensure that the pins you select in the hardware configuration, also match what is in your software pin definition.(UART_PINS)
Using UART via USER USB (P0.1, P0.2)
Using UART via USER USB (P0.6, P0.7)
Using UART via DEBUG USB (P0.1, P0.2)
We recommend not opening the project directly, but rather import it into Eclipse and make a local copy in your Eclipse workspace.
For more information on importing, debugging, or other tools related questions, please see the tools user guide.
UART Configuration Settings can be found in the Communications.h file.
/* UART pins */ #define UART_PINS_12 1 /* Connected to P0.1, P0.2 */ #define UART_PINS_67 2 /* Connected to P0.6, P0.7 */ #define UART_PINS UART_PINS_12 /* Select UART pin destination */ /* The serial port may be used in polling or interrupt mode */ #define UART_MODE UART_INT_MODE
Following is the UART configuration.
Select COM Port Baud rate: 9600 Data: 8 bit Parity: none Stop: 1 bit Flow Control: none
The user must type the word <help> in order to bring up the CLI menu shown below.
Command | Description |
---|---|
help | Display available commands |
version | Display SW version of CLI project |
dump [begaddr] [count] | Display up to 0x40 consecutive byte-size locations from any address of the ADuCM360 memory space. One should be careful not to request locations which are not decoded because the hardware_fault exception code will block the board. |
reset | Perform a HW reset which also initialize the application |
The official tool we promote for use with the EVAL-ADICUP360 is CrossCore Embedded Studio. For more information on downloading the tools and a quick start guide on how to use the tool basics, please check out the Tools Overview page.
For more detailed instructions on importing this application/demo example into the CrossCore Embedded Studios tools, please view our How to import existing projects into your workspace section.
For more detailed instructions on importing this application/demo example into the CrossCore Embedded Studios tools, please view our How to configure the debug session section.
The ADuCM360_demo_cli project Project structure is shown below:
This project contains: initialization part - disabling watchdog, setting system clock, enabling clock for peripheral; UART interrupt service; port configuration for UART use; UART read/write management; command line interpreter application.
In the src and include folders you will find the source and header files related to CLI application. You can modify as you wanted those files. The Communication.c/h files contain UART specific data, meanwhile the cli.c/h files contain the command interpreter data.
The RTE folder contains device and system related files:
End of Document