Blog Archives
How to install libgen for GNU Arm Embedded on Linux host
Hello, Thank you for reaching out to us. Firstly, we recommend making sure that the Libgen installer is in the same folder in which you try to execute it. Secondly, if you have a 64bit Ubuntu 18.04 we suggest installing
binutils-2.24_2019Q2 rebuilding method
Hello, Thank you for reaching out to us! Could you please let us know what the issue that prevents you to use the .run for installing the toolchains is? If your OS is 64bits, you need to install the 32bit support to
The usage for ”.arm”(.code 32) of ARM Machine Directives
Hello, Thank you for your reply! When writing thumb instructions you also need to add the .syntax unified directive because the default, divided, uses the old style where ARM and THUMB instructions had their own, separate syntaxes. I have tried
The usage for ”.arm”(.code 32) of ARM Machine Directives
Hello, Thank you for reaching out to us! Your target device RA6M1 comes with an ARM cortex-m4 processor which is a Thumb-only processor. Hence the directive you want to use is .thumb. Changing the .arm directive to .thumb should fix
GCC 8.3.0.202002-GNURX the stack usage calculation is still incorrect
Hello, Thank you for reporting this issue to us! We already found a fix for this issue and we will provide it in a future GCC RX release. Best Regards, The GNU Tools Team
build GCC fails on Debian x64 platform.
On 64-bit Debian, installation of these packages resolved the issue with gcc-8.3.0.201904-GNURX-ELF.run : sudo apt-get install libc6-i386 sudo apt-get install lib32stdc++6 By the way, why there is no official Debian package for the toolchain?
e2 Studio stalls when configuring GDB
Hi RalfZim, We are very sorry for the delayed response to your problem. Are you still experiencing this issue? We do not think this is a GDB problem, but an e2 studio one. There is a new release of e2
Debugger won’t load (stalls) when trying to enter debug mode
It looks like I am having a pretty similar situation here, however, I was not able to find a solution. Therefore, I wrote another question on this topic, describing my setup.
“undefined reference to `memset’” bug
Hello, This is not a bug in the toolchain: it is the intended behavior. Even the native gcc is having the same behavior. The reason is that the linker, on it’s own, does not know where to look for the
“undefined reference to `memset’” bug
Hello, Thank you for reaching out to us. We managed to reproduce the issue and we recommend using gcc to link as opposed to the linker (ld). By linking only with ld, there are some additional flags missing from your

日本語