How-to manual Installing a toolchain for Cortex-M3/STM32 on Ubuntu

7.1.8 Hints
There exists a lot of documentation and hints about Eclipse – and it seems <strong>to</strong> be necessary. This
chapter intends <strong>to</strong> contain useful know-how about first and standard steps. Hope it's content will
increase by time and with successful usage of the IDE.
Debuggen mit GDB (Gnu DeBugger) unter Eclipse :
http://homepages.thm.de/~bbdw58/anleit/debuggen.pdf
Dokumentieren mit Eclipse und Doxygen:
http://homepages.thm.de/~bbdw58/anleit/doxygen.pdf
EGit/User Guide:
http://wiki.eclipse.org/EGit/User_Guide
Git with Eclipse (EGit) - Tu<strong>to</strong>rial
http://www.vogella.de/articles/EGit/article.html
8 Bugs and Workarounds
8.1 GCC <strong>to</strong>olchain
Bug in Newlib C Library (1.18.0-sg++) (stdlib.h) included in “Sourcery CodeBench Lite” – when
including function “str<strong>to</strong>ull” in program code, communication via USART switches <strong>to</strong> baudrate x 4,
sometimes HardFault_Handler interrupt occurs. Function “str<strong>to</strong>ul” seems <strong>to</strong> be not affected.
Workaround:
1. Do not use corrupted functions from Newlib C Library or do not use this lib at all.
The same effect occurs when adding following content <strong>to</strong> the source code:
long long test1 = 10, test2 = 4, test3;
test3 = test1 / test2;
As soon as the code “division of a long long variable” exists inside the program (no matter where), the
USART behaves strange. Maybe the above mentioned function “str<strong>to</strong>ull” contains a 64-bit division
<strong>to</strong>o. The <strong>manual</strong> "Using the GNU Compiler Collection, chapter 6.9" tells that long long divisions are
open coded and are available only on machines 'providing special support'.
Workaround:
1. do not use long long division.
It would be just of interest how the code of the division can alter the program in a way that:
+ everything still works and debug functionality is fine
+ even the result of the long long division is OK
- the baudrate changes <strong>to</strong> baudrate x 4 (which is defined by the content of a CPU-register, not by the
translated code itself)
8.2 IDE -eclipse
Bug 351549 - IDE shows source has errors, but it builds without errors. Errors in “Problems” terminal
look like: “Type xxx could not be resolved ... Semantic Error”. This error happens on “Eclipse
Plat<strong>for</strong>m 3.7.1.r37” with “Eclipse CDT 8.0.0.”. The IDE can come in<strong>to</strong> this (buggy) state, but it must
not – seems <strong>to</strong> be depending on making project or workspace settings.
Two workarounds known:
1. Switch code analysis off (recommended): Window → Preferences → C/C++ → Code
Analysis → clear all checkboxes → Apply → OK → delete all errors in “Problems” terminal.
2. Add include path <strong>to</strong> project (not recommended): Project → Properties → C/C++ General →
Paths and Symbols → Includes → GNU C → Add “usr/include” → Apply → OK
Page 35 of 38