Contact: SweePoh, Quek (Kevin)
Testech Electronics Pte Ltd. Blk 1014, #02-194, Geylang East Ave 3, Singapore 389729.
Tel: (+65)-67492162 Fax: (+65)-67494246. Email: sales@testech-elect.com
Web: www.testech-elect.com
Requirements:
1. Microcross Visual-X, GNU-X Windows for ARM-ELF.
2. ARM Based Target Board.
Procedures:
1. Click on "Project -> New". Select GNU arm-elf C/C++ Wizard and create a new workspace. Select the correct target toolchain (in this case, ARM-ELF) and click OK.
2. The following dialog appears.. Select the C executable project.
3. The application type dialog appears. Select Än empty project".
4. A choice of "Build Systems" dialog appear. Slect the "Build with an auto-generated, autom-maintained makefile".
5. Select "Finish" and the New Project Information will show a summary of the project created.
6. Click OK, and the Project.. Under the File tab, navigate to the <drive>\Cygwin\home\test directory and select the "pascal.c"source file. Click on Add button to add this file to the project files. Click OK to finish setting up the project.
7. Double click on the source file "pascial.c" to open teh source file. The developer can edit or view the source content. Beliw is a screenshot of the Visual X-Tools IDE.
8. Click on Build -> Compile from the mini or the mini toolbar icon
9. The below screen shows the compiled result.
10. Click on Build -> build or click on Build Project icon on the min toolbar. Below shows the make results.
11. Click on Build -> Debug with GDB from the menu or click on the mini-toolbar bug symbol. Type "target sim"to select simulator, and then type "load" to load the program. Then type "Run"". To exit, type "quit"and the program will returns. This is a short tutorial using command line GDB for simulator target.
12. Click on Build -> Debug iwth Visual GDB. To select a breakpoint, move a mouse over the left edge of the window and click on a line to set the breakpoint. Then select the Left Most icon (like a running person) on the toolbar. When prompt, select "Target -> Simulator"on the drop down select box. After debugging, you can click on File -> exit to ext visual GDB.
Note that GDB support Hardware assisted debug interface such as EPI MAJIC JTAG for ARM/XScale/MIPS, Abatron BDI2000 for ARM/Xscale/MIPS core. In this case, select ARM Remote/Serial or ARM Remote/Ethernet and the JTAG probe must support GDB backend (such as EPI MAJIC or EPI JEENI, Abatron BDI2000 JTAG Interface). Using Hardware JTAG Debug offer you non-intrusive using onchip debug hardware of the ARM Core (and some core even support hardware trace or onchip HW trace), Hardware Breakpoint, debug code in Flash and debug Kernel as well.
13. You can open memory window, watch window, local variable window, current register window. Below is screen shot.
14. Click on Build -> GNU X-Tools options. Below shows the dialog and the compiler setting. Turn on the verbose output.
15. On the "Misc" tab, expand the "machine" folder. You can set the various arm-elf architecture code generation specific options here. See below screen.
16. Click on the "Code Generation" tab. You can set optimisation, debug symbols option.
17. Click on "Linker" tab. You can set linker option here.
18. Click on the "Run/Debug" tab. Select ARM-ELF-GDB for the debugging.
This ends our short tour of the Visual-X Tools and GNU-X Tools from Microcross for embedded development.
Back to Microcross Main Page | Back to Testech Home Page | Compiler | RTOS | Emulator/Debugging