1 / 11

Cygwin/GNU Tools

This guide provides an extensive overview of using Cygwin and GNU development tools, including installation steps, configuration for various targets (like ARM and M68K), and tips for troubleshooting common issues. It covers essential components such as GCC, GDB, and graphical front-ends like GDBTK. Discover how to utilize hardware breakpoints, manage POSIX file build problems, and leverage Jeeni for debugging. Learn about the pros and cons of GNU tools and find valuable documentation to support your development process.

olinda
Télécharger la présentation

Cygwin/GNU Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cygwin/GNU Tools

  2. / home tuttle local x-arm x-m68k … NetOS Cygwin bash usr opt The GNU Development Tools … run in a UNIX shell emulation called Cygwin

  3. Cygwin1.3.22 gcc3.2 • Install • Possible POSIX files build problem • gdbtk • Hardware breakpoint with RAVEN • Using jeeni • gdbThreadx

  4. Install • Install—delete Cygnus Solution in registry, clean up all the path. • One CD for cygwin, xtools and netos6_gnu, the installer will do the above clean up • Cygwin 1.3.22, gcc v3.2 • Binutils v2.12 • Gdb v5.3, gdbtk v5.3 • Newlib v1.11, libstdc++ v3.0

  5. Dev. Tools binutils 2.10 gcc 2.95.2 newlib 1.8.1 libstdc++ 2.81 gdb 5.0 Insight/gdbtk Covering the Tools w/ graphical FEs

  6. GDBTK - Insight – A graphical FE for GDB

  7. gdbtk works better • To stop, click on “stop” in source window. Improved stability • Compatible with tcl 8.4 library • Compatible cygwin 1.3.22

  8. Hardware breakpoint • Hardware breakpoint with RAVEN • For detail, refer to netos/howToUseRaven.txt • ocdLibRemote with chip options for netsilicon chip instead netsiliconLibRemote

  9. Using jeeni • Use script gdbnet50.jeeni target rdi e=<<put your JEENI IP here>> • To see debug printf in command window need to rebuild libc.a and crt0.o using netos/gnusrc/jeeni.mak need to copy libc.a and crt0.o to netos\lib\32b\gnu

  10. gdbThreadx • Cool tool to check if there is any stack over flow for threads • How to use (arm-gdb) source ../../../../gdbThreadx (arm-gdb) b netosStartup Breakpoint 1 at 0x802ce58: file common/bsproot.c, line 372. (arm-gdb) c Continuing. Breakpoint 1, netosStartup (not_used=0) at common/bsproot.c:372 372 if (NAFlashCreateSemaphores () == NAFLASH_SEMAPHORE_CREATE_FAILED) (arm-gdb) threadlist • Any thread with stack overflow will be marked

  11. Pros and Cons of using GNU Tools • The GNU development tools are open source • GNU tools are the most powerful and flexible development tools which allow to deliver virtually any kind of embedded solution • GNU tool flexibility extends beyond the target domain • GNU tools are well supported • Base distribution does not contain a graphical IDE • Documentation is good but widely spread • New users can’t get started quickly

More Related