18
Getting Started Getting Started With EDP V1.1 Date: 20/6/08 © Electrocomponents plc Page 1
Getting Started
Getting Started With EDP
V1.1
Date: 20/6/08
© Electrocomponents plc Page 1
Getting Started
© Electrocomponents plc Page 2
Contents 1. Getting Started With EDP 3
2. EDP Development Tools 4 2.1 EDP Based On The XC167 Module ................................................ 4 2.1.1 The Infineon Device Access Server ................................................ 4 2.1.2 Setting Up The Infineon DAS USB-JTAG Interface ........................... 4 2.1.3 Setting Up Hitex HitopXC ............................................................. 4 2.1.4 Compiler/Debugger IDE’s .............................................................. 5 2.1.5 Testing The Keil Tools .................................................................. 5 2.1.6 Example Programs For EDP Fitted With The XC167 Module .............. 6 2.1.7 More Example Programs ............................................................... 7 2.1.8 EDP-CM-XC167 I2C Driver Library ................................................. 7 2.1.9 Alternative C166 Tools That Can Be Used ...................................... 8 2.2 EDP Systems Using The STR9 Module ........................................... 9 2.2.1 Tool Combinations Currently Available ........................................... 9 2.2.2 Example Programs ....................................................................... 9 2.2.3 Keil RV-MDK ARM (a.k.a. uVISION ARM) ..................................... 10 2.2.4 HiTOPARM With GNU-C/C++ .................................................... 11 2.2.5 Testing The Keil uVISION With RealView Installation ...................... 12 2.2.6 Testing The Keil uVISION With GNU-C Installation ......................... 13 2.2.7 More STR9 Example Programs .................................................... 14 2.3 Alternative But Untested STR9 Toolchains .................................... 15 2.3.1 Using IAR EWARM CSPY With The EDP-CM-STR9 ......................... 15 2.3.2 Rowley CrossWorks ARM v1.7 ................................................... 17
Getting Started
1. 0Getting Started With EDP
© Electrocomponents plc Page 3
Getting Started
2. 1EDP Development Tools
2.1 2EDP Based On The XC167 Module
2.1.1 5The Infineon Device Access Server
All C166 tools are able to connect to the FT2232 USB-JTAG interface on the XC167 module. This is made possible by the Infineon Device Access Server (DAS). This low-level driver is required in all XC167 debuggers such as HitopXC, Keil uVISION and Tasking Crossview. The DAS server to be separately installed by the user so you must install this before any other software! You have a choice of how to use the XC167 tools. The Keil uVISION166 IDE can be used for editing, compiling and debugging. Alternatively, you can edit and compile in uVISION and then download into the XC167 FLASH for debugging using HiTOPXC. To just blow a program into FLASH, the Infineon serial bootstrap-loaded FLASH program can be used.
2.1.2 6Setting Up The Infineon DAS USB-JTAG Interface
All C166 tools are able to connect to the FT2232 USB-JTAG interface on the XC167 module. This is made possible by the Infineon Device Access Server (DAS). Thus before installing any debugger or compiler IDE, install the DAS v2.6 package. You can find it on the EDP installation CD or here: http://www.infineon.com/DAS If you have an existing DAS installation then you must use this latest version otherwise you may have difficulties getting the HiTOPXC or uVISION debugger to connect to the module.
2.1.3 7Setting Up Hitex HitopXC
HiTOPXC is a powerful debug and FLASH programming tool for the XC16x family. It is able to load and debug programs created with any C166 compiler. It has (optional) advanced features such as coverage analysis and real time performance analysis. HitopXC is a dedicated debugger that uses the Infineon DAS to work with the XC167 module’s built-in USB to JTAG interface. You are strongly advised to install HitopXC before any other XC development tool. HitopXC can be found on the EDP installation CD or at:
http://www.hitex.de/service/support/z-16x/20080528HITOP53-EDP-XC167setup.exe
Make sure the EDP system is not connected to your PC when installing. Once the installation has completed, power up the EDP system and connect the mini-USB port on the baseboard to your PC’s USB connector. Windows should detect the presence of the XC167 module and automatically load the drivers. HitopXC can then be used.
© Electrocomponents plc Page 4
Getting Started
2.1.3.1 2 3Testing The HitopXC Installation
The first program to try is the BLINKY example. This does nothing more than flash the yellow ”User LED” on the module but it will prove that HitopXC is properly installed. To run this, power up the EDP system and connect the USB cable to your PC. When the HiTOPXC licence manager asks, choose “Continue Evaluation”... ... and then load the project: C:\hitex\HiTOP53-EDP-XC167\Examples\RS-EDP-CM-XC167\Blinky\BLINK.HTP HiTOPXC will blow this into the XC167 FLASH. Click on the Target Reset button ( ) and the click on the green traffic light icon to start the program. The LED on the XC167 module should now start to flash.
2.1.4 8Compiler/Debugger IDE’s
The Keil uVISION compiler for XC166, the Tasking “Classic” and VX tools for XC166 can be used, however to date only Keil has been tested. The Keil C166 evaluation edition compiler can be found on the EDP CD or at: https://www.keil.com/demo/eval/c166.htm This allows the creation of programs of up to 4k executable code size, plus up to another 4k of library code. The uVISION debugger can make use of the FTDI FT2232 USB-JTAG interface on the XC167 module to access the OCDS1 debug unit on the CPU. The connection to the host PC is via the mini-USB connector on the EDP baseboard. It allows programs to be created of up to 8K. There are a number of test programs available that make use of the I2C system, Ethernet, comms module and DC motor module. Some examples are too big to compile with the 4k limited compiler so in these cases a special version of the project is provided with an “_8K.UV2” suffix.
2.1.5 9Testing The Keil Tools
To test that the Keil tools are properly installed, open the BLINKY project in uVISION located at: C:\hitex\HiTOP53-EDP-XC167\Examples\RS-EDP-CM-XC167\Blinky\Blinky.uv2 Rebuild it and then before entering debug mode, use the FLASH tools menu to do download the program into the module. If the FLASH download fails, unplug the USB cable and power down the EDP system for a
© Electrocomponents plc Page 5
Getting Started
few seconds. Then re-power it and insert the USB cable again. Wait for 60 seconds to make sure that Windows has detected the presence of the XC167 module. Then try the FLASH programming again. If this succeeds, go ahead and start debugging by clicking the icon. The uVISION debugger will load the program and run until main(). From there you can run at full speed by clicking the button. The LED on the XC167 module with then start to flash at 1Hz.
2.1.6 1 0Example Programs For EDP Fitted With The XC167 Module
These programs are designed to show the main features of the EDP system when fitted with the EDP-CM-XC167 CPU module. They are compiled with the Keil uVISION166 IDE and blown into the XC167 FLASH and debugged with either uVISION's own debugger or the advanced HiTOPXC debugger and performance analyser. More examples are always being added to the EDP website so please make sure you check it!
2.1.6.1 2 4 Examples Supplied
BLINKY: Simple program that flashes the user LED on the XC167 module at 1Hz. CAN: Simple program based on DAvE that sends and receives CAN messages between CAN0 and CAN1. This requires a EDP-AM-CO1 comms module to be fitted. EasyWEB: Simple webserver that generates a webpage at 192.168.1.199 (alterable). Hello_World: Simple DAvE program that sends "Hello World" through XC167 ASC0. This requires a EDP-AM-CO1 comms module to be fitted. I2C_DRIVER: Large program that tests an entire EDP system. It has a simple menuing system that runs through XC167 ASC0 so this requires a EDP-AM-CO1 comms module to be fitted. Note: C:\Hitex\HiTOP53-EDP-XC167\Examples\RS-EDP-CM-XC167\I2C_Driver\XC167\XC167_SYSTEM\I2C_INT.UV2 will only compile with the full Keil PK166 kit. If you are using the EK166 4K-limited version, please open: C:\Hitex\HiTOP53-EDP-XC167\Examples\RS-EDP-CM-XC167\I2C_Driver\XC167\XC167_SYSTEM\I2C_INT_8K.UV2. This has the bulk of the program in a library to avoid hitting the 4k code limit. PID_V3: This requires the MC1 DC brushed motor controller, a Crouzet 12V motor and 1ppr encoder. It reads the accel ramp pot. on the MC1 module and controls the speed of the motor using a simple PID in the range of 0 - 3250rpm. It also generates a webpage at IP address 192.168.1.199 . It will not compile with the EK166 limited compiler.
© Electrocomponents plc Page 6
Getting Started
PID_V3_NoWeb: This requires the MC1 DC brushed motor controller, a Crouzet 12V motor and 1ppr encoder. It reads the accel ramp pot. on the MC1 module and controls the speed of the motor using a simple PID in the range of 0 - 3250rpm. It will compile as-is with the EK166 limited compiler. PID_V3_Web: This requires the MC1 DC brushed motor controller, a Crouzet 12V motor and 1ppr encoder. It reads the accel ramp pot. on the MC1 module and controls the speed of the motor using a simple PID in the range of 0 - 3250rpm. It also generates a webpage at IP address 192.168.1.199 . Two projects are supplied: - HITEX.UV2 is intended for the full PK166 package and is able to build a library that contains the TCP/IP stack. - HITEX_8K.UV2 is designed for the EK166 limited compiler and uses this library to get access to the TCP/IP stack without exceeding the code size limit.
2.1.7 1 1More Example Programs
Within the Keil C166 compiler installation there are many more example programs. These can be found at: C:\Keil\C166\Boards C:\Keil\C166\Examples\XC16x Devices Any intended for the Infineon evalulation boards will function.
2.1.8 1 2EDP-CM-XC167 I2C Driver Library
To allow the creation of new programs that make use of the I2C devices used on the EDP system, as series of simple usage examples has been supplied. These can be found in: C:\hitex\HiTOP53-EDP-XC167\Examples\RS-EDP-CM-XC167\Drivers These examples are simple programs that show the basic functions for accessing I2C devices used in the EDP system. The functions required to access the devices are held in the library "EDPXC167_LIB.LIB" held in the "LIB" subdirectory. The library has been built using the Keil XLARGE memory model for convenience and all the examples have been built the same way to avoid linking errors. The programs contain all the settings required for user’s own program development. For most I2C devices, functions are available to use all the modes and features of the device, although they are not shown in the examples. Each example contains a text file which gives the details of all the functions listed in the device-specific header files.
© Electrocomponents plc Page 7
Getting Started
2.1.8.1 2 5Examples Supplied
AN16: Setup AD5263 and MAX1138 Read all MAX1138 channels Read all CPU ADC channels DIO54: Read all I2C GPIO inputs ("GPIO_IN_Pxx") Write all I2C GPIO outputs ("GPIO_OUT_Pxx") BaseBoard: Read and write 24LC32 EEPROM Read 8-way DIL switch CO1-PCF8583: Set real time clock time Read real time clock EE24LC32: Read and write 24LC32 EEPROM
2.1.9 1 3Alternative C166 Tools That Can Be Used
2.1.9.1 2 6Tasking (Netherlands)
The “Classic” compiler is a widely-used C166 toolchain which has limited support for the XC167. The VX compiler has specific support and optimisations for the XC and later CPUs and runs under Eclipse. Example programs produced with these tools can be downloaded into the XC167 module via HitopXC or via Tasking’s own debuggers as the Infineon DAS is used universally.
2.1.9.2 2 7 Hightech-EDV (Germany)
Long-standing GNU-C166 tools (chargeable). Example programs produced with these tools can be downloaded into the XC167 module via HitopXC or via PLS’s FASTVIEW debugger as the Infineon DAS is used universally.
2.1.9.3 2 8 KPIT Cummins (India)
Eclipse-based GNU-C166 tools (chargeable). Example programs produced with these tools can be downloaded into the XC167 module via HitopXC.
© Electrocomponents plc Page 8
Getting Started
2.2 3EDP Systems Using The STR9 Module There are currently two toolchains available for the STR9 that have been tested. Others are available but these have not been tested to any great extent and are covered at the end of this section. Regardless of which toolchain you intend to work with, it is recommended to install the Hitop debugger. This installation contains the low-level USB-JTAG drivers that are required by other compiler’s debuggers to communicate with the FTDI device on the STR9 module. Installing HiTOPARM also gives the option of installing the GNU-ARM compiler that comes with number of useful examples of the STR9 peripherals such as Ethernet, the ADC, UART and CAN.
2.2.1 1 4Tool Combinations Currently Available
You can create programs in the following ways using the tools supplied: Editor/IDE Compiler Debugger uVISION ARM RealView HiTOPARM uVISION Hitex GNU-C HiTOPARM HITOPARM Hitex GNU-C HiTOPARM uVISION ARM RealView uVISION using ULINKME USB-JTAG uVISION ARM RealView uVISION using FT2232 USB-JTAG on STR9 module Other tool combinations are covered at the end of this section. Note: please visit the EDP website to download an upgrade that will allow the final tool combination to be realised. At the time of writing, the DLL that interfaces uVISION directly to the STR9 module is still in beta testing.
2.2.2 1 5Example Programs
The installation CD will copy a set of example programs to C:\Hitex\HITOP53-EDP-STR9\Examples\EDP-STR9. The contents are described in the following.
© Electrocomponents plc Page 9
Getting Started
2.2.3 1 6Keil RV-MDK ARM (a.k.a. uVISION ARM)
This toolchain can be used in two main ways. The current recommended approach is to use the Keil uVISION IDE to edit and compile programs and then use the HiTOPARM debugger to blow the programs into the STR9 FLASH. To use the uVISION debugger directly with the STR9 module requires the fitting of the low-cost uLINKME USB-JTAG interface and a 0.05” to 0.1” JTAG adaptor. By the end of June there will be a direct interface between the Keil uVISION debugger and the FTDI USB-JTAG interface on the STR9 module which will render the uLINKME redundant. The Keil RV-MDK compiler can be found on the installation CD or at: https://www.keil.com/demo/eval/arm.htm This allows the creation of programs of up to 16k executable. Warning: Do not install the GNU-ARM compiler from the Keil installer if you have already installed it from Hitop. This is the old GNU-C v3 compiler whereas the Hitex GNU tools are v4.1.1.
2.2.3.1 2 9uVISION Example Programs Supplied
The installation CD will copy the following examples onto your hard disk: GNU-UVISION: These are the basic files required to create a new application for the GNU-C compiler under uVISION. RealView-HiTOP: This contains a HiTOARM project (.HTP file) that is configured to load RealView programs into the STR9 and debug them. RVMDK: This is a complete EDP system test program that uses the RealView compiler and HiTOPARM debugger. It is a source of a lot of useful drivers for the various peripherals (especially I2C) on the EDP modules. TIMx: A simple program to FLASH the LED on the STR9 using the Keil RealView compiler under uVISION. The program is downloaded into the STR9 using HiTOPARM. TIMx_GNU: A simple program to FLASH the LED on the STR9 using the GNU-C compiler under uVISION. The GNU-C compiler can also be run from HiTOPARM debugger. The program is downloaded into the STR9 using HiTOPARM. RS_Virtual_Com_Port: This program allows the STR9 USB port to be used as a virual COM port. Thus characters written to the USB can be viewed using a PC terminal program connected to the virtual COM port created. The .INF file supplied is used to tell the PC how to treat the STR9 USB device. Note: The EDP-AM-CO1 module is required to access STR9 USB port EASYWEB: A simple webserver that displays a webpage at IP address 192.168.1.199. Edit TCPIP.H to change this to suit your network.
© Electrocomponents plc Page 10
Getting Started
2.2.4 1 7HiTOPARM With GNU-C/C++
HiTOPARM can be used to debug programs compiled with the Keil RealView compiler in the uVISION IDE or allow the creation of programs in its own IDE using the GNU-C ARM compiler. When installing HiTOPARM, you will be given the option of installing the GNU-C compiler, something which is recommended. The GNU-C compiler is unlimited but the HiTOPARM debugger is restricted to programs of 32k in code size. The first time you start HiTOPARM, you will be given the choice of whether to use this restricted mode, purchase an unlimited licence or apply for a time-limited unrestricted licence.
2.2.4.1 3 0 HiTOPARM/GNU-C Example Programs Supplied
These are programs designed to be used with GNU-C compiler under uVISION, with HiTOPARM being used to download into FLASH and debugging. The programs in the HitexExamples directory designed to be used with the following tools: - Keil uVISION IDE, configured to use GNU-C rather than RealView compiler - Hitex GNU Tool Package For ARM - HitopARM debugger for EDP STR9 The examples are: ADC: This is a small implementation of the UART0 feature sending AD converted values. Ethernet: An example based on the uIP TCP/IP stack originated by Adam Dunkels. It is a small implementation of the stack enabling a web server and basic Ethernet function. You can change the IP address used to suit your network environment and rebuild, if required. FULLCAN: - A small implementation of CAN feature receiving CAN messages. - A small implementation of CAN feature sending CAN messages. UART: The code is based on usage of the STmicro library functions and is a small implementation of UART1 feature echoing an external input.
© Electrocomponents plc Page 11
Getting Started
2.2.5 1 8Testing The Keil uVISION With RealView Installation To make sure the uVISION and RealView compiler are correctly installed, start uVISION and open the project: C:\hitex\HITOP53-EDP-STR9\examples\EDP-STR9\TIMx\timebase.uv2 Build the program using the “Build All” button. No errors or warnings should result. To load the program into the STR9 module, make sure the EDP system is powered up and connected by USB to your PC then start the HiTOPARM debugger. Next open the HiTOP project file: C:\hitex\HITOP53-EDP-STR9\examples\EDP-STR9\TIMx\TIMx.htp When asked by the HiTOP licence manager, choose “Continue Evaluation”. After a short time, HiTOPARM will load the program into the STR9 FLASH. Click on the green RESET button to make sure the STR9 is ready to run and then click the green traffic light button to execute the program. The LED on the STR9 module should now start to FLASH.
© Electrocomponents plc Page 12
Getting Started
© Electrocomponents plc Page 13
2.2.6 1 9Testing The Keil uVISION With GNU-C Installation To make sure the uVISION and GNU-C compiler are correctly installed, start uVISION and open the project: C:\hitex\HITOP53-EDP-STR9\examples\EDP-STR9\TIMx_GNU\TIMx_GNU.uv2 As this is the first time uVISION will have been asked to open a GNU-C based project, you need to tell it where to find the GNU-C tools, assuming that you have already installed them. This is done via the
Component/Environment/Books button which reveals this menu: Configure this menu as s e then click OK. Then build the program using the “Build All” button. No errors or warnings should result.
how vn abo
If you have not installed the GNU-C compiler either as part of the HiTOPARM installation or on its own, you are likely to get an error message!
To load the program into the STR9 module, make sure the EDP system is powered up and connected by USB to your PC then start the HiTOPARM debugger. Next open the HiTOP project file: C:\hitex\HITOP53-EDP-STR9\examples\EDP-STR9\TIMx_GNU\TIMx_GNU.htp When asked by the HiTOP licence manager, choose “Continue Evaluation”.
Getting Started
After a short time, HiTOPARM will load the program into the STR9 FLASH. Click on the green RESET button to make sure the STR9 is ready to run and then click the green traffic light button to execute the program. The LED on the STR9 module should now start to FLASH.
2.2.7 2 0More STR9 Example Programs
There are dozens of STR9 example programs contained in the Keil ARM compiler installation. You can find these at: C:\Keil\ARM\Boards\Keil\MCBSTR9 C:\Keil\ARM\Boards\ST\STR910 C:\Keil\ARM\Examples\ST\STR91xLib C:\Keil\ARM\Boards\ST\STR9_DONGLE Most of these will run as-is but the EDP-CM-STR9 module uses a different set of pins for UART0 and UART1 so some adaptation may be required.
© Electrocomponents plc Page 14
Getting Started
2.3 4Alternative But Untested STR9 Toolchains
2.3.1 2 1Using IAR EWARM CSPY With The EDP-CM-STR9
The Embedded Workbench CSPY access the STR9 module via its GDB interface and the OPENOCD USB-JTAG server. The latter can be downloaded from: ftp://hitex.podzone.net/pub/hitex/edp/str9/OPENOCD.zip Install OPENOCD as directed. Before trying to connect CSPY to the STR9 module, run the RS-EDP-STR9.bat file to start the OPENOCD JTAG server.
Note: you must leave the OPENOCD command line window running in the background at all times when using CSPY!
© Electrocomponents plc Page 15
Getting Started
Before starting the CSPY debugger, there are a few things to check. Go to the Project Options menu and check that the debugger type is set to “GDB”. Next, click on the Breakpoints tab and set the default breakpoint type to “Auto”. Having done this, you can safely start CSPY.
© Electrocomponents plc Page 16
Getting Started
2.3.2 2 2Rowley CrossWorks ARM v1.7
You will need to download the STR9-COMSTICK driver kit from: http://www.rowleydownload.co.uk/arm/packages/Hitex_STR9_comStick.htm And follow the instructions given. The Hitex STR9COMSTICK uses the same STR9 CPU and FT2232 USB-JTAG interface as the EDP STR9 module so the driver is very similar.
You will need to enter the PROPERTIES menu for the STR9COMSTICK to change the product ID (“PID”) from “2C” to “2E” otherwise the debugger will not connect.
© Electrocomponents plc Page 17
Getting Started
© Electrocomponents plc Page 18
