Howto use Amontec JTAGkey- Tiny on

Size: px

Start display at page:

Download "Howto use Amontec JTAGkey- Tiny on"

Dylan Kelley
6 years ago
Views:

Howto use Amontec JTAGkey- Tiny on PN IO Development Kit for ERTEC 200P with

2 Disclaimer of Liability We have checked the contents of this manual for agreement with the hardware and software described. Since deviations cannot be precluded entirely, we cannot guarantee full agreement. However, the data in this manual are reviewed regularly. Necessary corrections are included in subsequent editions. Suggestions for improvement are welcomed. Copyright Siemens AG All rights reserved The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. All product and system names are registered trademarks of their respective owner and must be treated as such. Technical data subject to change. Copyright Siemens AG All rights reserved. 2 Howto use Amontec JTAGkey-Tiny

3 Preamble This document assist you to integrate the Amontec JTAGkey-Tiny on the Development Kit DK-ERTEC200P PN IO with operating system ecos and comes without any warranty, there is no additional support by Siemens. Copyright Siemens AG All rights reserved. 3 Howto use Amontec JTAGkey-Tiny

4 Index of contens 1 Introduction Necessary Hardware Required Software Tools Eclipse Version: OpenOCD Amontec JTAGkey-Tiny Driver GDB Integration of Amontec JTAGkey-Tiny Step 1 Unpack Eclipse Step 2 install Eclipse plugin Step 3 Install OpenOCD Step 4 Install Amontec JTAGKey Tiny driver Step 5 Configure Eclipse Overview installed Debug System Hints / Restrictions Annex Configuration File for EB 200P and OpenOCD Miscellaneous Abbreviations: Copyright Siemens AG All rights reserved. 4 Howto use Amontec JTAGkey-Tiny

5 1 Introduction This document describes how to integrate the Amontec JTAGkey-Tiny to use it on Development Kit DK- ERTEC 200P with operating system ecos. There is no support on preconfigured GNU toolchains from Siemens side, please refer according suppliers: Amontec: Yagarto: Tools versions you download may differ, it is your challenge to modify settings suited. We recommend to us the same Version as described. Please see also Chapter 6 Hints / Restrictions. 2 Necessary Hardware The Hardware Debugger can ordered under following address: Amontec, Gauch La Grand Fin Vuippens Switzerland Fax +41 (0) info@amnotec.com This Howto was tested with following Target Board: Siemens Profinet Evaluation Board EB 200P 3 Required Software Tools This Howto requires that the DK-ERTEC 200P PN IO V4.0 with ecos is already installed. 3.1 Eclipse Version: You will find Eclipse on the Development kit CD in subdirectory \tools\eclipse. It contains version with all necessary plugins to work with OpenOCD JTAG debugger. Eclipse could also be downloaded from following website: Copyright Siemens AG All rights reserved. 5 Howto use Amontec JTAGkey-Tiny

6 Be sure that the version you download include following plugins: CDT C Development Toolkit GDB Hardware Debugging If you use the following link, both CDT and GDB Hardware Degugging plugins are included: zip If Eclipse is already installed you could check plugins by: Menu: Help About Eclipse Platform Plug-in Details 3.2 OpenOCD You find OpenOCD on the Development Kit CD in the subdirectory \tools\openocd. OpenOCD could also be downloaded from following Adresse: We attached configuration files for version Amontec JTAGkey-Tiny Driver Driver is included in OpenOCD installation. libusb-win32 driver is used. Note: For Win7/ 64Bit OpenOCD driver is necessary, function was verified with version dev GDB A suitable ARM gdb must be referenced in the eclipse Debug configuration. After installation of the development kit CD it is located in the following folder: PNIODevKit/msys/1.0/local/bin/arm-none-eabi-gdb.exe 4 Integration of Amontec JTAGkey-Tiny 4.1 Step 1 Unpack Eclipse Unpack Eclipse into a user defined folder, e.g. D:\eclipse. Start eclipse by double clicking on file eclipse.exe and set workspace to the folder required by DK- ERTEC 200/ 400 PN IO (e.g. D:\PNIODevkit ). 4.2 Step 2 install Eclipse plugin This step can be skipped, if Eclipse is installed from the PROFINET IO Devkit CD. In this case all necessary plugins are already installed. Plugin s have to be installed by using Eclips install process. We suppose following: 1) Unzip the downloaded plugin package described under 3.1 Copyright Siemens AG All rights reserved. 6 Howto use Amontec JTAGkey-Tiny

2) Add package to Available Software under Eclipse by Menu: Help Software Updates and Addons Availabel Software -> Add Side, choose Local and browse to the package described above.

7 2) Add package to Available Software under Eclipse by Menu: Help Software Updates and Addons Availabel Software -> Add Side, choose Local and browse to the package described above. 3) The package should now be available in the Available Software window, you could install it by highlight it and pressing the left mouse button and select Install. 4.3 Step 3 Install OpenOCD OpenOCD is located on the Development Kit CD in the subdirectory \tools\openocd. To use this version, unpack openocd zip and install it by double click on the file openocd.msi. Newer OpenOCD versions for MS Windows can be downloaded from Inside the ZIP file, there is MSI installer. OpenOCD is installed by running this installer. There is however no guarantee for compatibility with actual configuration scripts. 4.4 Step 4 Install Amontec JTAGKey Tiny driver After successful installation, in the OpenOCD s drivers\ directory, there is ZIP file called libusbwin32_ft2232_driver zip 1. Unpack the abovementioned ZIP file to some directory 2. Connect JTAGKey Tiny to EB 200P and power up the board 3. Plug the Amontec JTAGKey Tiny in the PC 4. After you are asked for driver, use the libusb-win32_ft2232_driver.inf 5. Execute Batchfile startocd200p_debug.bat. This batch starts OpenOCD with correct parameters. Following should be displayed (version 0.4.0): Note: OpenOCD must be run simultaneously with Eclipse for debugging. 6. Check OpenOCD is running by open an telnet connection,execute following on command window: telnet localhost The Following should be displayed: Copyright Siemens AG All rights reserved. 7 Howto use Amontec JTAGkey-Tiny

8 This check is just to know if OpenOCD is running. It is not necessary for debugging by Eclipse/gdb. By typing help you will get a list of all available functions (read/ write memory, read/write register, etc.). 4.5 Step 5 Configure Eclipse 1) Run Eclipse 2) Generate Debug Configuration, by Menu Run Debug Configurations... Copyright Siemens AG All rights reserved. 8 Howto use Amontec JTAGkey-Tiny

4) On the Main site make following settings: Copyright Siemens

5) On Debugger site check following settings and set path to ARM gdb:

6) On Startup site make following settings: Note: The command monitor reset init is passed via gdb to the OpenOCD monitor and execute the reset-init sequence specified in the configuration file.

12 6) On Startup site make following settings: Note: The command monitor reset init is passed via gdb to the OpenOCD monitor and execute the reset-init sequence specified in the configuration file. load fore the gdb to load the elf file via OpenOCD to the target. Note: Enable resume will start application immediately after download. 7) Save modification on press Apply button 8) Compile your system (ecos and PNIO Application) as mention in DevKit manual 9) Run Debugger by Menu Run Debug or press F11, ELF file will be downloaded and debugger stops at reset_vector. Now you could add a breakpoint and start debugging. Note: OpenOCD must be running. Note: If there is now a breakpoint set, the SW will be downloaded and started. Copyright Siemens AG All rights reserved. 12 Howto use Amontec JTAGkey-Tiny

5 Overview installed Debug System The graphic below shows the whole Software development

14 6 Hints / Restrictions 1) This Howto is based on Siemens Profinet DK 200P PN IO V4.0 2) OpenOCD recommends to disable MMU, MPU and Cache for debugging. The actual configurations script s doesn t disable this functions, therefore ist isn t possible to set Software Breakpoints. 3) On ERTEC200P there are two Hardware Breakpoints available. If single step debugging is selected, then just one Hardware Breakpoint is available, the other one is for stepping necessary. 4) Actual is no Working Area defined, test shows that downloadspeed will double. 5) Till now Flash programming is supported only without Working area set. 6) The debug performance will decrease if several variables are under oberservation. 7) For Win7/ 64Bit libusb-win32 driver fromopenocd is necessary. 8) JTAG download speed (defined by variable jtag_khz in eb200p_amontec.cfg) is limited by Amontec debbuger (maximum is 3MHz; jtag_khz 3000), This parameter influences mainly the firmware download time to RAM. 7 Annex 7.1 Configuration File for EB 200P and OpenOCD # openocd script for ERTEC 200P # set ports telnet_port 4444 gdb_port 3333 #interface/ Dongle configuration interface ft2232 ft2232_device_desc "Amontec JTAGkey" ft2232_layout jtagkey ft2232_vid_pid 0x0403 0xcff8 if { [info exists CHIPNAME] { set _CHIPNAME $CHIPNAME else { set _CHIPNAME ertec200p if { [info exists ENDIAN] { set _ENDIAN $ENDIAN else { set _ENDIAN little if { [info exists CPUTAPID ] { set _CPUTAPID $CPUTAPID else { # force an error till we get a good number set _CPUTAPID 0x # jtag speed. We need to stick to 16kHz until we've finished reset. jtag_khz 16 #use combined on interfaces or targets that can't set TRST/SRST separately reset_config trst_and_srst #jtag scan chain #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask) jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0x0f -expected-id $_CPUTAPID Copyright Siemens AG All rights reserved. 14 Howto use Amontec JTAGkey-Tiny

15 jtag newtap $_CHIPNAME bs -irlen 4 -expected-id 0x2b900f0f #target configuration set _TARGETNAME $_CHIPNAME.cpu target create $_TARGETNAME arm926ejs -endian $_ENDIAN -chain-position $_TARGETNAME # speed up memory downloads arm7_9 fast_memory_access enable arm7_9 dcc_downloads enable #workaround: HW breakpoints gdb_breakpoint_override hard #flash bank <driver> <base> <size> <chip_width> <bus_width> <target> set _FLASHNAME $_CHIPNAME.flash flash bank $_FLASHNAME cfi 0x x $_TARGETNAME jtag_khz 300 #enable workspace $_TARGETNAME configure -work-area-phys 0x207F0000 -work-area-size 0x0000 #gdb_flash_program disable init reset halt flash banks ##load RAM image #load_image test_ram.bin 0x bin #reg pc 0x #resume ##or load FLASH image #flash erase_sector #flash write_image test_flash.bin 0x bin #reg pc 0x #resume $_TARGETNAME configure -event reset-start { jtag_khz 16 $_TARGETNAME configure -event reset-init { # We can increase speed now that we know the target is halted. jtag_khz 300 puts "Running reset init script for EBx00 Board" #enable clocks mww 0x4000f078 0x00ffffff puts "EMC settings for ERTEC 200P" mww 0x10d x mww 0x10d0000c 0x000003d0 mww 0x10d x3ffffff2 mww 0x10d x3ffffff2 mww 0x10d x3ffffff2 mww 0x10d0001c 0x3ffffff2 mww 0x10d x mww 0x10d x0 mww 0x10d0002c 0x0 mww 0x10d x42 #last write mww 0x10d x # Memory Swap to SDRAM mww 0x4000F030 0x $_TARGETNAME configure -event debug-halted { # puts "Running debug halted script for EB200P Board" $_TARGETNAME configure -event gdb-attach { puts "Running gdb-attach script for EB200P Board" Copyright Siemens AG All rights reserved. 15 Howto use Amontec JTAGkey-Tiny

16 $_TARGETNAME configure -event gdb-detach { puts "Running gdb-detach script for EB200P Board" $_TARGETNAME configure -event gdb-flash-erase-start { puts "Running gdb-flash-erase-start script for EB200P Board" $_TARGETNAME configure -event gdb-flash-erase-end { puts "Running gdb-flash-erase-end script for EB200P Board" $_TARGETNAME configure -event gdb-start { # puts "Running gdb_start script for EB200P Board" $_TARGETNAME configure -event gdb-end { puts "Running gdb_halted script for EB200P Board" Copyright Siemens AG All rights reserved. 16 Howto use Amontec JTAGkey-Tiny

17 8 Miscellaneous 8.1 Abbreviations: CDT C Development toolkit OpenOCD Open On-Chip Debugger OS Operating System gdb GNU Debugger ERTEC Enhanced Real Time Ethernet Controller JTAG Joint Test Action Group, IEEE-Standard SW Software Copyright Siemens AG All rights reserved. 17 Howto use Amontec JTAGkey-Tiny

Howto use Amontec JTAGkey- Tiny on

Howto use Amontec JTAGkey- Tiny on PN IO Development Kits for ERTEC 200/400 with ecos Copyright Siemens AG 2010. All rights reserved. 1 Howto use Amontec JTAGkey-Tiny Disclaimer of Liability We have checked