Changes between Version 6 and Version 7 of Hardware/jCM/cCM2/bDev

Timestamp:

Oct 16, 2008, 6:33:10 PM (16 years ago)

Author:

Joseph F. Miklojcik III

Comment:

updated to reflect improvements in dev tools

Hardware/jCM/cCM2/bDev

@@ -34 +34 @@
 It is listening for gdb connections on default port 3333. Note that openocd daemon is started automatically and should be up and running at all times.
 
+You can develop on your private system and run {{{arm-elf-gdb}}} against openocd remotely.  sb3 does not expose an ssh port, but you can tunnel through {{{gw.orbit-lab.org}}} with a command like the following.
+
+{{{
+  $ ssh gw.orbit-lab.org -L 3333:sb3.orbit-lab.org:3333
+}}}
+
 == Cross-compiler ==
 
-Software development environment is based on [http://www.codesourcery.com/gnu_toolchains/arm GNU Toolchain for ARM Processor]. Downloaded tarball is installed in /usr/{bin,lib,libexec}. The toolcahin was compiled with the ''arm-elf'' prefix so that (for example) compiler can be invoked with:
+Software development environment is based on the latest version of gcc, binutils, and newlib.  There are two tricks to compiling these tools: one is to use separate build directories, the other is to bootstrap a C compiler against the newlib headers, compile newlib with that compiler, then compile another C compiler with newlib installed.  Interwork and Multilib support are necessary.
+
 {{{
-  arm-elf-gcc program.c -o program
+  $ # unpack tarballs in $SRC_TOP
+  $ mkdir $SRC_TOP/binutils-build
+  $ cd $SRC_TOP/binutils-build
+  $ ../binutils-$BINUTILS_VERSION/configure --target=arm-elf --enable-interwork --enable-multilib
+  $ make && sudo make install
+  $ mkdir $SRC_TOP/gcc-build 
+  $ cd $SRC_TOP/gcc-build 
+  $ ../gcc-$GCC_VERSION/configure --target=arm-elf --enable-interwork --enable-multilib --enable-languages=c --with-newlib --with-headers=../newlib-$NEWLIB_VERSION/newlib/libc/include
+  $ make all-gcc && sudo make install-gcc
+  $ mkdir $SRC_TOP/newlib-build
+  $ cd $SRC_TOP/newlib-build
+  $ ../newlib-$NEWLIB_VERSION/configure  --target=arm-elf --enable-interwork --enable-multilib
+  $ make all && sudo make install
+  $ cd $SRC_TOP/gcc-build
+  $ make all && sudo make install
+  $ mkdir $SRC_TOP/gdb-build
+  $ cd $SRC_TOP/gdb-build
+  $ ../gdb-$GDB_VERSION/configure --target=arm-elf
+  $ make all && sudo make install
 }}}
 
-You can also get the latest version of gcc, binutils, and newlib, and compile these as {{{configure --target=arm-elf}}}.  Both the Makefile and the loader know (at least in theory) how to deal with ELF format CM2 images.  In this case tools are prefixed with "arm-elf", so for example an appropriate value for {{{CC}}} in the {{{Makefile}}} would be {{{CC=/usr/local/arm-elf-gcc}}}
+CM2 build configuration is done by overriding variables from the first few hundred lines of the Makefile on the {{{make}}} command line.
 
 == Debugger ==
 
-Use [source:CM2/trunk/gdbinit gdb initialization file] to set it up to work with JTAG debugger:
+Use [source:CM2/trunk/gdbinit-rom gdb initialization file] to properly interact with the JTAG debugger:
 
 {{{
-  arm-elf-gdb -x gdbinit
+  $ arm-elf-gdb --annotate=3 -x gdbinit-rom main.elf
 }}}
 
-Then, once you get the gdb prompt issue
-
-{{{
-  load main.elf
-}}}
+This will load and run the CM2 with a breakpoint set at {{{main()}}}.