FAQ:Install
From GNU 68HC11/HC12
Contents |
This section lists general questions about:
- The site itself (www.gnu-m68hc11.org, ...)
- How the FAQ works and how you can contribute
What tool do I need to build GEL?
GEL uses Makefiles to automate and help building the various libraries and examples it contains. The Makefiles need a shell (/bin/sh) and some Unix utilities.
On Windows, you should install the MSYS Mingw package which provides these Unix utilities. You can obtain it at:
You can get the MSYS 1.0.9 package at:
[ftp://www.gnu-m68hc11.org/pub/win32/MSYS-1.0.9.exe]
To install this package, just execute the program. This will open a graphical installation that asks you where you want to install those tools. Do not forget to update your PATH to use them.
How can I build GDB for 68HC12?
The 68HC12 is supported by the GNU Debugger. The gdb sources must be configured as follows:
configure --target=m6811-elf --program-prefix=m6811-elf-
The debugger will support both 68HC11 and 68HC12. It will automatically select the processor according to the ELF file you specify.
Why is it still necessary to patch FSF sources?
The 68HC11/68HC12 tool chain is integrated in FSF main sources. When you want to build the tool chain from FSF sources, a set of patchs must be applied. In fact these patchs are not mandatory. They are however strongly recommended:
- Some patchs fix various problems detected after the FSF sources are released. These fixes are provided until the FSF releases a new version.
- Unfortunately, several fixes are not integrated in FSF sources because it takes time to make them approved by FSF maintainers. This is the case for several nasty bugs in the compiler.
- The gdb patch contains a BDM support that can't be integrated in FSF mainline due to the lack of copyright assignment by its author.
Building the tool chain for 68hc12
There seems to be a small problem that shows up if one is building the hc1x toolchain with the --target=m6812 configure switch instead of --target=m6811.
When building the toolchain using --target=m6812, it seems that gcc has difficulties to locate the correct libgcc.a . I.e. when starting to link the applications (compiling and assembling works well), the linker complained about incompatiblity of the libgcc.a . After recompiling the entire toolchain with --target=m6811 everything worked, when using the -m6812 compile switch.
Yours,
Björn bjoern dot m dot haase at web dot de
