Debugging in Eclipse
Contents
1. BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE Igi xi filter text Environment Z d Resource Builders C C Build Configuration Default 7 Manage configurations Discovery options Environment Settings Tool chain editor Environment variables to set New Variables C C General PWD CilezeeNetiDebugTest Select Project References CWD C eZeeNet DebugTest Edit Refactoring History _ RunjDebug Settings Remove Undefine Append variables to native environment Replace native environment with specified one Restore Defaults Apply Figure 10 Properties dialog 2 Click the New button in Properties dialog see Figure 10 Enter ZBN_DIR inthe Name text box and full path to the ZigBeeNet directory of your ZDK installation in the Value text box like seen in Figure 11 below Name ZBN DIR Value C 2DK ZIGBEENET Variables Add to all configurations Figure 11 Variable definition dialog IMPORTANT You have to use forward slash rather than back slash V in path names 3 Click OK to close the window A new variable will be added to the list 2008 MeshNetics Page 18 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE 4 Repeat the same steps to create the second variable PRJ HOME2. llleshilletics cD ZigBeeNet Software 1 0 Application Note Creating building amp debugging ZigBeeNet applications in Eclipse Doc AN 481 08 v 2 0 March 2008 2008 MeshNetics B na BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE Document Summary This document gives a brief introduction to the process of creating building and debugging ZigBeeNet based projects using the open source IDE Eclipse WinAVR compiler and JTAGICE mkll hardware on a PC running Microsoft Windows 2000 XP In this tutorial we will create a small project that controls one of the LEDs on MeshNetics MeshBean development board and try to debug it using Eclipse and JTAGICE hardware Document Conventions Buttons Dialog button names are denoted in Courier OK Cancel Menu Menu items are denoted in Courier and shown in order they must commands be selected File gt Open Keyboard Several keys should be pressed simultaneously in the order they shortcuts are listed F7 Ctrl Shift F5 Source code Code snippets are shown in colored text ROR ROKR KK Kk ko ke kk IK ko kk kk ke kk ko kk kkk IR IK ke kk IK ke kk ke eG User s entry KOKCKCKCkCkckckckok kc ko kk kk ko kc kc I ko kk ko A KA I ko koe koe ke ke oe e x x void fw userEntry FW ResetReason t resetReason File and File and directory names are taken in single quotes directory bin avr gdb exe names Int
3. To use the programming debugging features of JTAGICE mkll in Eclipse we ll have to set up 2 external tools that will be run every time you need to program the device with new image and before starting the debugging session Since WinAVR is a command line set of tools programming the module with image we build is done by a command line tool avarice exe We just set up a wrapper for this tool so that we do not have to type in anything every time we need to run it 1 Select Run gt External Tools gt External Tools Dialog from the menu see Figure 5 2 New launch configuration button in toolbar in the upper left corner ofthe External Tools dialog see Figure 7 3 Enter Burn image in the Name text box Click the Browse File System button under the Location text box navigate to the WinAVR installation directory and select the avarice exe file usually located in the bin subdirectory of WinAVR 4 Browse Workspace button under the Working Directory text box and select your current project DebugTest then press OK Note that text box contents change to workspace_loc DebugTest which is not a standard path name but an environment variable we will discuss these later in this document Type 2 repf DebugTest elf j usb in the Arguments text box 6 Go to the Common subtab see Figure 8 and check the External tools checkbox in the D
4. between usb then click Apply Click Close to close the dialog 2008 MeshNetics Page 11 22 A B BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE Creating a makefile WinAVR toolchain requires the use of a so called makefile a plain text file that contains all the settings compiler switches paths libraries etc required to build the target image We supply with a sample makefile that you can use a reference in future projects see below To add a makefile to your project select File gt New gt File see Figure 5 or right click the Project Explorer window and select New gt File from the pop up menu New File me xf File Create a new file resource Enter or select the parent folder DebugTest LAN DebugTest File name makefile Advanced gt gt Figure 9 New File dialog Enter makefile in the File name text box and click Finish to close the dialog see Figure 9 An empty makefile will be created and opened in the source code editor Paste the following sample makefile contents into the editor 2008 MeshNetics Page 12 22 m A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE 2008 MeshNetics AE AE AE AE aE aE aE AE aE AE aE aE AE aE aE AE E EE EE EE EE EE EE EEE EEE EEE EEE EEE EEE EEE Makefile for the proj FEAE E
5. 1 STACK DIR SystemEnvironment include 5 5 DIR APS include 5 5 DIR NWK include I STACK_DIR ZDO include I STACK DIR MAC PHY include I STACK DIR MAC PHY MAC PHY include 1 STACK DIR MAC_PHY MAC_HWI include I STACK DIR HAL PATH HAL HWI include 1 STACK HAL PATH HAL HWD include I STACK_DIR BSP include I STACK DIR ConfigServer include I STACK DIR PersistDataServer include 1 STACK DIR Security BuildingBlocks include LIB LIBDIRS 1 DIR APS lib L STACK DIR ZDO lib L NWK 1lib L STACK_DIR 1 L HAL PATH lib L STACK DIR SystemEnvironment lib 1 DIR BSP lib 15 5 DIR Security BuildingBlocks lib L DIR PersistDataServer lib Libraries LIBS 1 5 1ZDO 1 HAL LIB 1BSP 1NWK lSystemEnvironment 1 MAC_LIB 1 1ZDO 1 HAL LIB 1 5 1NWK lSystemEnvironment 1SSPsw lPersistDataServer AS CROSS COMPILE as LD 55 1 CROSS COMPILE gcc 2008 MeshNetics Page 14 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE CPP CROSS COMPILE g AR 5 55 COMPILE ar NM CROSS COMPILE nm STRIP
6. 4 2 f framework h Main loop gpio h TH apptimer h void LED mainLoop void Addtional user s activities 4 timerFired void 259 userEntry FW ResetReason t void 9 mainLoop void timerFired void Blink timer handler void timerFired 4 static bool on 0 gpio setState LED on 0 1 Toggle eof DebugTest c E console 3 72 Tasks 12 Problems 0 Memory Ex ee Debug C C Local Application C eZeeNet DebugTest DebugTest elf 23 10 07 17 56 al writable smart Insert 44 16 al mea Figure 14 Project perspective screen You can switch between debug and project perspectives at any time using the Debug and C C buttons in the top right corner of the Eclipse window Execution should now break on the line we ve set a breakpoint at You can use the vast Eclipse debugging facilities to see stack trace memory variables registers and many other things The Window gt Show view menu gives you quick access to any of the debugging windows The Run menu contains most of the debugging features you need like step into d step over run to line and others 5 Press F8 or select Run Resume from the menu to resume execution 6 Select Run gt Terminate to stop debugging 2008 MeshNetics Page 22 22
7. AE AE FE a ET aaa ct DebugTest CROSS COMPILE avr CPU atmegal281 PROJNAME DebugTest PROJECT PROJNAME elf SHELL bin bash COMPILER FLAGS CFLAGS mmcu CPU CFLAGS CFLAGS 4 CFLAGS Wall W CFLAGS ffunction sections CFLAGS Wl gc sections Initial DebugTest interval CFLAGS DDebugTest P D Can be AT86RF230 MAC AT86RF230 Can be 1281 HAL ATMEGA1281 AT AT86RF230 MAC LIB MACrf230 else ifeq MAC MAC LIB MACrf230b else ifeq AT86RF231 MAC LIB MACrf231 else ifeq S MAC AT86RF212 MAC LIB MACrf212 else MAC LI endif endif endif endif ifeq B MACrf230 115 ERIOD 1000 EFINES FLAGS AT86RF230B AT86RF231 915 7 256 AT86RF230B AT86RF212 Page 13 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE ifeq HAL ATMEGA1281 HAL PATH HAL atmegal281 HAL LIB HALatmegal281 else HAL PATH HAL at91sam7x256 HAL LIB HALat91sam7x256 endif STACK DIR 5 DIR Components PATHS FLAGS OF INCLUDES INCLUDEDIRS I include
8. CROSS COMPILE strip OBJCOPY CROSS COMPILE objcopy OBJDUMP CROSS_COMPILE objdump SIZE 5 55 COMPI size BUILDDIR PRJ HOM objects X BUILDDIR objs DebugTest o 5 5 DIR ConfigServer objs ConfigServer o Build all objects PROJECT PROJNAME hex objects 5 S CFLAGS INCLUDEDIRS c o 58 5 BUILDDIR objs DebugTest o BUILDDIR DebugTest c STACK ConfigServer objs ConfigServer o 5 ConfigServer src configServer c S PROJECT objects 6 objects STACK DIR S HAL PATH lib WdtInit o CFLAGS INCLUDEDIRS S LIBDIRS LIBS lm o PROJI 5 5 td 5 5 5 gal H 5 PROJNAME srec 5 O srec srec len 128 5 PROJNAME srec 5 PROJNAME hex S OBJCOPY O ihex PROJECT S PROJNAME hex burn avarice 2epf S TARGET j dev ttySO Clean target clean rm rf TARGET objects PROJECT PROJNAME PROJNAME eep PROJNAME srec End of makefile 2008 MeshNetics Page 15 22 m BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE Adding source files to the project 2008 MeshNetics Now t
9. RAE ER EUER EUER ATER A TES h d aps void TaskHandler t BLINK DELAY blinkTimer AppTimer StartBlinkTimer void TimerFired void ZDO StartNetworkConf zC 2 MgmtNwkLipdateNotf ZDO WakeUpInd void ZDO SleepInd void APL TaskHandler void StartBlinkTimer void TimerFired void ZDO StartNetworkConf zC ZDO_MamtNiwkUpdateNotf ZDO WakeUpInd void ZDO SleepInd void o StartBlinkTimer void StartBlinkTimer blinkTimer interval BLINK_DELAY blinkTimer mode TIMER REPEAT MODE blinkTimer callback TimerFired Start ppTimer amp blinkTimer void TimerFired ecooooottitittexEEEEEE ToggleLed LED RED The following functions MUST be present to build the executable image void ZDO_StartNetworkConf ZDO_StartNetworkConf_t confirmInfo void 2 0 MgmtHwkUpdateNotf 2 0 MomtNwkUpdateNotf t nwkParams void 200 WakeUpInd aj 2 Tasks 22 Console Properties amp xi H D items 1 Description Resource Path Location T Writable Smart Insert 80 15 5 Figure 12 Debug screen Once the programming is finished an error message USB bulk read error usb reap async error device attached to the system is not functioning might be displayed Just ignore it Don t forget you have to reprogram the MeshBean every time you make changes to your code and rebuild
10. T APPLICATIONS IN ECLIPSE APPLICATION NOTE 2008 MeshNetics Hardware Update Wizard Welcome to the Hardware Update Wizard This wizard helps you install software for USB Device If your hardware came with an installation CD lt 6 or floppy disk insert it now What do you want the wizard to do C Install the software automatically Recommended Click Next to continue Figure 2 Hardware Update Wizard starting screen Page 5 22 Meshilet 5 E AA BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE 3 Click Next gt to continue In the next window see Figure 3 select Don t search I will choose the driver to install andclick Next to continue Hardware Update Wizard Please choose your search and installation options Search removable media floppy ED HGM Jv Include this location in the search Figure 3 Hardware Update Wizard search options screen 2008 MeshNetics Page 6 22 A n BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE 4 Click Next gt again then click the Have Disk button in the window that appears see Figure 4 Hardware Update Wizard Select the device driver you want to install for this hardware a Select the manufacturer and model of your hardware device and then click Next If you have a disk that contains the driver y
11. e workspace for embedded development and another one for writing Windows applications A project can belong to different workspaces By default Eclipse creates a new workspace in the Windows user directory C Documents and Settings or whatever it is called on your computer This is not the best place to keep projects in because WinAVR tools do not like spaces in directory names We recommend creating a separate directory for ZigBeeNet projects for example ZigBeeNet We will use this directory from now on Select File gt Switch workspace Other from Eclipse application menu and enter ZigBeeNet in the Workspace textbox the directory will be created if it does not exist Eclipse will restart and open new workspace Page 8 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE 4 Select File gt New gt Project from menu expand the C section is the list that appears select C Project and click Next gt button to continue Enter the project name DebugTest in the Project name text box and click Finish Sometimes the following window will pop up Open Associated Perspective This kind of project is associated with the C C perspective Do you want to open this perspective now Remember my decision Figure 6 Open Associated Perspective dialog 5 Just click ves to continue Setting up external tools
12. ended Audience This document is intended for developers wanting to get familiar with writing ZigBee 802 15 4 applications using MeshNetics ZigBeeNet ZigBee stack Related Documents 1 _ ZigBit Development Kit User s Guide MeshNetics Doc S ZDK 451 2 JTAGICE mkll Quick Start Guide http Awww atmel com dyn resources prod_documents doc2562 pdf 3 WinAVR User Manual Ed by B Weddington 4 AVR Studio User Guide Available in HTML Help with the product http www atmel com dyn products tools card asp tool id 2725 2008 MeshNetics Page 2 22 Meshhetics BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE Pre requisites Make sure you have the latest versions of JAVA Run time Environment JRE download from http www javasoft com Eclipse for C development download from http www eclipse org and WinAVR http winavr sourceforge net installed on your PC You ll also need 1 MeshBean board 1 and 1 Atmel JTAGICE device 2 You will also have to install the JTAGICE USB driver that comes with WinAVR 9 see next chapter Installing the JTAGICE driver WARNING If you install this driver you won t be able to use JTAGICE with AVR Studio Error Reference source not found If you want to use AVR Studio you ll have to reinstall the driver located in the usb folder of AVR Studio installation usually Program files Atmel AVR tools u
13. hat we can add a source c file that contains the code we re going to build to the project Select File gt New gt Source file from the application menu see Figure 5 or right click the Project Explorer window and select New gt Source file from the pop up menu Enter DebugTest c the Source File text box and click the Finish button to continue Note that you have to specify the extension of the file Here s the sample code we re going to use in this example below include lt apsTimer h gt include lt leds h gt include lt zdo h gt include lt aps h gt variables defines functions void StartBlinkTimer void TimerFired confirmInfo nwkParams void ZDO WakeUpInd void ZDO SleepInd Application task void APL TaskHandler StartBlinkTimer void StartBlinkTimer blinkTimer interval include lt taskManager h gt define BLINK DELAY 500 static HAL AppTimer t blinkTimer KK IK RR RK I IR RK RK KK KK KK LED Blinking Implementation Project C Fe A A eA A A k Ck k Ck kCk kk k Ck k k k Ck k k k include lt configServer h gt Period of blinking void ZDO StartNetworkConf ZDO StartNetworkConf t void ZDO MgmtNwkUpdateNotf 2 0 MgmtNwkUpdateNotf t BORK KKK IK IK KK I I I I IA IR I I OK FO KK I Ck kc kk kck ck k kc k k kc k Ck kck ck kck ck kck ck kck ck IK I I kok ok ke ke e kx kx bl
14. inkTimer mod blinkTimer callback BLINK DELAY TIMER REPEAT MODI TimerFired HAL StartAppTimer amp blinkTimer Source 16 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE void TimerFired BSP ToggleLed LED RED The following functions MUST be present to build the executable image void ZDO StartNetworkConf ZDO StartNetworkConf t confirmInfo void ZDO MgmtNwkUpdateNotf 2 0 MgmtNwkUpdateNotf t nwkParams void ZDO WakeUpInd void ZDO SleepInd eof DebugTest c Using environment variables in makefile 2008 MeshNetics Notice the following lines in the makefile text Path to Stack STACK DIR ZBN DIR Components Modules directories paths BUILDDIR S PRJ HOME ZBN DIR and PRJ HOME are environment variables that point to the API folder of ZigBeeNet installation and directory containing your project files respectively By using variables you can avoid specifying paths directly in the makefile and thus the need to modify the makefile for every project you create Instead you can use the variables in Eclipse to specify the paths 1 Select Project Properties from the application menu or right click the project name in Project explorer and select Properties from the pop up menu Page 17 22
15. isplay in favourites menu list 7 Click the Apply button to save new settings 2008 MeshNetics Page 9 22 Meshilet 5 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE External Tools Create manage and run configurations Run 4 program Filter text E 9 Program E H 9 Debug mode CiWinAVRTbinlavarice exe workspace_loc DebugTest 2 repf DebugTest elf j usb Filter matched 3 of 3 items Figure 7 External Tools dialog Main subtab 2008 MeshNetics Page 10 22 Meshilet 5 E 105 AA BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE External Tools Create manage and run configurations Run a program filter text E 9 Program o mpm Debug mode Q External Tools Filter matched 3 of 3 items Figure 8 External Tools dialog Common subtab WOTKSpace e The avarice exe program also needs to be run every time you want to start a debugging session so we set up another external tool entry for this called Debug mode see Figure 7 Click the New launch configuration button again and enter Debug mode in the Name text box Once again enter full path to avarice exe inthe Location text box and current project path in the Working Directory text box In the Arguments text box enter 2 j usb 2525 note the space
16. ols output is shown in the console window in the bottom of the screen see Figure 12 Programming the device with newly built image Once the image is successfully built we need to program the MeshBean with it via JTAG 1 2008 MeshNetics Connect your JTAG device to the MeshBean by using supplied connector and to your PC using USB cable and power up both devices Page 19 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE 2 NowselectRun External tools Burn image we ve created this entry earlier If all connections and settings are fine then node programming will start with progress indicator in the console window C C DebugTest DebugTest c Eclipse Platform ixi File Edit Refactor Navigate Search Run Project AVR Target Window Help n els 7 6 6 6 amp 6 9 0 9 9i 6l Ei amp Project Explorer 9 0 s Makefile DebugTest c 3 gt A BE Outin EUN Male B fee BA void 200 MgmtNwkUpdateNotf ZDO MomtNwkUpdateNotf t nwkParams 1 252 B ix DebugTest 252 b den apsTimer h es do voi 51 4 leds h DebugTest c taskManager h a QOEGOOHGGORR GGG GG Y 4 434 TARA RATA AAA A RARER AAR ARATE ATTA 4444444 AAAAARITITNIIMI ITI I f 3A Makefile zdo h Application task canfigsarverih WGORAGOR UR BUR UR UR AUC AERA AEA ERA EAA EA EER UR AERA EAR EEA ER AERA T
17. ou want to install click Have Disk M Standard CD ROM drives Sf CD ROM Drive force accurate Cile siae cor CD ROM Drive force CODDA inaccurate _ 5 CD ROM Drive force IMAPI disable CD ROM Drive IMAPI settings 0 1 7 This driver is digitally signed Have Disk Tell me why driver signing is important lt Back Cancel Figure 4 Hardware Update Wizard device driver screen 5 Click Browse navigate to the WinAVR installation directory and then to the Utils Libusb Bin folder select jtagice2 inf and click the Open button then click OK 6 Click Next gt inthe window that appears and wait while the driver is installed Click Finish to close the wizard Creating a New project in Eclipse 1 Start Eclipse IDE by running eclipse exe If this is the first time you re running Eclipse a similar screen will appear see Figure 5 2008 MeshNetics Page 7 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE Ele Edit Navigate Search Project Run Window Help Figure 5 Eclipse starting screen 2 2008 MeshNetics Click the rightmost button Go to Workbench or click the x button next to Welcome on top of the window Like many modern IDEs Eclipse has a workspace concept a common space for several projects say you can have a separat
18. porates views For displaying the debug stack variables and breakpoint management Do you want to open this perspective now Remember my decision Mo Figure 13 Perspective confirmation 4 Click ves to switch the view or in Eclipse terminology perspective to debugging mode The screen layout will change into something like this seen in Figure 14 2008 MeshNetics Page 21 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE Debug DebugTest DebugrTest c Eclipse Platform File Edit Refactor Navigate Search Run Project Window Help 21613 0 11 E 5 Debug Debug 3 _ d gt 2 5 V 2 2 9o Breakpoints Ifi Registers m Modules xt s o7 Debug mode Program Name value C Winayrbin avarice exe 09 on false E Debug C C Local Application 2 gdbserver Debugger 23 10 07 17 56 Suspended 5 22 Thread 0 Suspended Breakpoint hit 6 timerFired c ezeenet debugtest DebugTest c 45 0x000002d6 5 Timer__Timer 0x00014bf4 4 Timer__signalOneTimer 0x00014c06 3 TOSH_run_next_task 0x00011228 2 TOSH run task 0x00011232 1main 0x000112e0 CUWinAVRIbinlavr gdb exe 23 10 07 17 56 pi CrleZeeNetlDebugTestiDebugTest elf 23 10 07 17 56 zi c makefile c DebugTest c 3 El BE outline 3 i
19. sb The following instructions are for Windows XP 1 Connect your JTAGICE mkll to your PC turn it on and open Windows Device manager If you did not install the driver that comes with AVR Studio you will See a USB Device with question mark under the Other devices branch see Figure 1 2008 MeshNetics Page 3 22 A BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE EZ Device Manager File Action Help 05 Computer we Disk drives B Display adapters amp DVD CD ROM drives E Floppy disk controllers JB Floppy disk drives 39 Human Interface Devices 523 IDE ATA ATAPI controllers gt Keyboards 77 Mice and other pointing devices Monitors 88 Network adapters Other devices USB Device E Portable Devices imf Nokia 93001 7 Ports COM amp LPT SM Processors Sound video and game controllers System devices Universal Serial Bus controllers E E E E E ED E E 2 E ED ED 8 0 Figure 1 Device Manager screen 2 If you did install the driver from Atmel there will be a JTAGICE mkII item under the Jungo branch Right click either of these items and select Update driver from the menu In the next window see Figure 2 select Install from a list or specific location Advanced 2008 MeshNetics Page 4 22 A BUILDING amp DEBUGGING ZIGBEENE
20. the image Debugging the application Once the MeshBean is programmed with the executable image we can start the debugging session 1 First lets set up a breakpoint in one of the functions void TimerFired see Figure 12 Position the cursor on the second line of this function and 2008 MeshNetics Page 20 22 m BUILDING amp DEBUGGING ZIGBEENET APPLICATIONS IN ECLIPSE APPLICATION NOTE select Run Toggle breakpoint from the menu or press Ctrl Shift B The line will be marked by a round symbol to the left of it 2 Tostart the debugging first select Run gt External tools gt Debug mode this is the second entry we ve created earlier This will put your JTAGICE into debug mode and allow further control of the target device You need to run this command every time you want to start a debugging session The output in the console window should look like this AVaRICE version 2 6 May 15 2007 17 07 24 Defaulting JTAG bitrate to 1 MHz Make sure that the target frequency is at least 4 MHz or you will likely encounter failures controlling the target 3 Next select Run Debug from the application menu or press F11 The following window may appear see Figure 13 Confirm Perspective Switch x 9 This kind of launch is configured to open Debug perspective when it P suspends This Debug perspective is designed to support application debugging It incor
21. with value set to the directory of your current project ZigBeeNet debugtest or similar 5 Click Apply then OK to close the dialog Setting up the debugger Select Run gt Open Debug Dialog from application menu Right click the C C Local application and select New from the pop up menu In the dialog that appears take the following steps 1 2 o 9 10 11 12 13 14 Enter Debug in the Name text box Click Browse next to Project text box select your project DebugTest from the list that appears and click Enter DebugTest elf inthe C C Application textbox Click App1y button Click Debugger tab Select gdbserver Debugger from the Debugger list Uncheckthe Stop on startup at checkbox Click Browse next to Debugger text box and navigate to bin subfolder of WinAVR installation directory Select the avr gdb exe file and click Open or just enter the full path to avr gdb exe usually something like C WinAVR bin avr gdb exe Clear the GDB command file text box Click the Connection subtab Change connection type to TCP and port number to 2525 Click the Common subtab Check the Debug item in the Display in favourites menu list Click Apply then Close Building the image Once we ve set everything up it is time to build the image we re going to debug Select Project Build project from the application menu WinAVR to
Download Pdf Manuals
Related Search