ARM Software Development: User Manual
Contents
1. will NOT work Your PC must be connected to the Internet during the installation in order to access installation files 1 1 In Circuit Debugging OpenOCD GDB In circuit debugging as described in this Section assumes the use of the Olimex ARM USB OCD JTAG adapter hardware dongle The dongle bridges the PC via USB cable and the target board via a 20 pin JTAG cable MSS e 18221 A Flower Hill Way Gaithersburg Maryland 20879 U S A Telephone 240 631 1111 Facsimile 240 631 1676 www ComBlock com MSS 2010 Issued 3 13 2012 1 1 1 JTAG Communication Check First let s verify that the JTAG communication works properly Power up the target board Highlight the project in Eclipse project explorer then start one of the OpenOCD programs from the Eclipse Run External Tools menu Breakpoint Types FL External Tools d FN 1 OpenOcD Flash FL 2 OpenOcd ram Run s b External Tools Configurations Organize Favorites The console should show the following reports Open On Chip Debugger 0 4 0 2010 02 Z22 19 05 Licensed under GNU GPL v2 Info JTAG tap lpcl768 cpu tap device found 0x4ba00477 mfg Ox23b part Oxba00 ver 0x4 The tap device found message means that the JTAG communication is working between Eclipse and the target ARM processor Two versions of the OpenOCD are supplied one focused on flash programming and or debugging the other focused on RAM debugging 1 12. 2 Flash programming The flash memory area of the ARM processor can be programmed via JTAG This is only one of the several ways of programming the microprocessor Step 1 edit the makefile to set TARGET flash then save the modified makefile Step 2 do a project clean Eclipse Project Clean menu Step 3 build the project Eclipse Project Build Project menu This will create the hex and elf files Step 4 start the OpenOCD flash external tools Eclipse Run External Tools OpenOCD flash menu as discussed in the previous section Step 5 switch Eclipse to the Debug perspective Step 6 run the CB1600flash debug configuration Eclipse Run Debug Configurations Zylin Embedded Debug Native CB1600flash menu The relevant Debug Configuration screens are shown below Debug Confipurations Create manage and run configurations type Filter texi fc CiC Application fe CiC Attach to Application E CiC Postmortem Debugger B E Launch Group cy New configuration Zyvlin Embedded debug Cygwin fylin Embedded debug Native 2G CBL600Flash Debus Configurations Name CB1600Flash FE Main gt F Debugger Z Commands Ee Source Project toptional cB1600 CiC Application CB1600_flash el Sear C Application console Create manage and run configurations fax Ee type Filter tex fie CiC Attach to Application fe CiC Postmortem D
3. Com Block ARM SOFTWARE DEVELOPMENT USER MANUAL This document describes an integrated design environment for developing C language applications for the ARM Cortex M3 processor on the ComBlock modules The environment is based on popular open source programs such as Eclipse which the user may be already familiar with This user manual covers five key topics 1 Installation on a PC of a comprehensive free software development environment Compiling the baseline C program and loading it into the ARM processor Debugging FPGA ARM processor communication USB communication ae This document applies primarily to ComBlock modules equipped with the NXP LPC1759 ARM Cortex M3 processor namely COM 1500 FPGA Spartan 6 LX45 LX150 ARM DDR2 SODIMM socket NAND development platform COM 1600 FPGA Spartan 6 LX16 ARM USB2 DDR2 NAND development platform and any subsequent platforms FPGA developers may skip this document entirely unless they are using the ARM co processor for mixed FPGA ARM custom algorithms 1 Software Development Environment The software development environment comprises four key components 1 GNU GCC C C compiler Yagarto GNU ARM toolchain for Windows and make tools 2 Eclipse IDE for C C Developers Eclipse Galileo CDT 3 Java JRE needed for Eclipse 4 OpenOCD debugger Important Note the GNU programs must be installed in directories without spaces in the name In particular c Program Files
4. ebugger Launch Group oo New configuration Zylin Embedded debug Cygwin fylin Embedded debug Native 3 CB1600Flash wi Hi cr iF Debus Contigurations Name CB1600Flash B Main Ee Debugger E Commands Ee Source Debugger Embedded GCE Debugger Options Main GDB debugger arm none eabi gdb exe GDB command fles warning Some commands in this file may interfere with the startup operation of the debugger for example run GDE command set Standard l Frotocol mi v C verbose console mode C luse Full file path to set breakpoints Create manage and run configurations type Filter text is fc CiC Application fe CAC Attach to Application fc CiC Postmortem Debugger Launch Group oy New configuration Zylin Embedded debug Cygwin fylin Embedded debug Native 2G CBL600Flash Name CB1600Flash B Main E Debugger W Commands Ee Source a Eee eter eee eee eee eee eee eee eee ee eee eee eee ee Ip tips on how to setup GDB init script Initialize commands Run commands target remote localhost 3333 symbol File CB1600_Flash elf monitor reset monitor sleep SOO monitor sorfk_reset_halt monitor Flash erase sector 00 29 monitor Flash write_image CB1600_Flash hex 0x00 PS Environment Common PE Environment E Common PE Environment E Common The screenshot above only shows a partial list
5. hbreak main continue 1 1 4 Debugging 1 1 5 Troubleshooting OpenOCD Debugger Upon starting the OpenOCD from Eclipse run external tools OpenOCD x Project is not open within this message shows up Eclipse or not highlighted Go back to the C C perspective and highlight the project before running openOCD x Problem Occurred x Launching OpenQcD ran has encountered a problem Variable references non existent resource 4oroject loc Upon starting the OpenOCD from Eclipse run external tools this message shows up Show Error Log Error unable to open ftdi device device not found Command handler execution failed Upon starting the OpenOCD from Eclipse run external tools this message shows up Bros aLi Zeroes JTAG scan chain interrogation failed Upon starting a new debugging session this message pops up __ E Embedded GDB 871710 127535 PM X Execution is suspended because of error Details gt Verify that the USB cable is connected between the ARM USB OCD dongle and the PC A green LED will then light up on the dongle Verify that the JTAG cable between the dongle and the target board is connected and that the target board 1s powered Make sure the JTAG connector orientation matches the outline printed on the target circuit board Make sure there 1s only one debug session started Terminate other debug sessions The main OpenOCD documentati
6. ing command in upper case O001SMI1600 lt enter key gt in the case of the COM 1600 Wait 5 seconds Verify that the command was successful by clicking on the detect button again The module should now appear as COM 1600 FPGA ARM Development platform or similar
7. of Run commands The complete list of GDB commands for flash programming followed by debugging is as follows target remote localhost 3333 symbol file CB1600_flash elf monitor reset monitor sleep 500 monitor soft_reset_halt monitor flash erase_sector 0 0 29 monitor flash write_image CB1600_flash hex 0x00 thbreak main cont 1 1 3 Loading the program in RAM Alternatively the program can be loaded into the RAM memory area of the ARM processor prior to debugging Please note that the RAM area is much small than the Flash area and thus cannot be used for full size programs Step 1 edit the makefile to set TARGET ram then save the modified makefile Step 2 do a project clean Eclipse Project Clean menu Step 3 build the project Eclipse Project Build Project menu This will create the hex and elf files Step 4 start the OpenOCD ram external tools Eclipse Run External Tools OpenOCD_ flash menu as discussed previously Step 5 switch Eclipse to the Debug perspective Step 6 run the CB1600ram debug configuration Eclipse Run Debug Configurations Zylin Embedded Debug Native CB1600ram menu The GDB commands for loading the program in RAM before debugging is as follows target remote localhost 3333 monitor reset monitor sleep 500 monitor soft_reset_halt set VITOR to SRAM mon mww OxEQOOED08 0x10000000 load CB1600_ram elf monitor reg pc 0x10000004 symbol file CB1600_ram elf t
8. on is available at http openocd berlios de doc html index html If all else fail re start with a clean slate Turn off on the target board power unplug and replug the JTAG pod USB cable stop restart the OpenOCD x external tool stop restart the GDB debugging session 2 Baseline C Program The baseline C program includes essential functions used at power up or reset such as turning the power ON configuring the FPGA using configuration file stored in Flash memory writing new FPGA configuration files into Flash memory from an external PC passing user control and monitoring commands via USB to the FPGA or adjacent Comblocks In the absence of user activity the ARM processor is idle after completing its configuration tasks at power up or reset The ARM processor can therefore be used for additional co processing tasks to complement the parallel signal processing tasks implemented in the FPGA The best way to develop custom program is to add onto the baseline C program 3 After programming the ARM processor After programming the ARM processor flash memory the board must be given a name To do so connect the board to a PC via the USB Start the ComBlock Control Center program Power up the board and detect the board from the ComBlock Control Center 2 button from left It will appear as unknown In the ComBlock Control Center open the terminal emulator window rightmost button Type the follow
Download Pdf Manuals
Related Search