Hi all,
Joakim is right - there are several reports of broken/non-working firmwares
compiled with the arm-none-eabi-gcc and libs provided by Ubuntu:Bionic
see for instance:
- https://bugs.launchpad.net/ubuntu/+source/gcc-arm-none-eabi/+bug/1767223
-
Hi,
I don't believe that we require GCC 7 anywhere, it should still work
fine to build with for example the ARM provided GCC 6 release, or the
older Ubuntu/Debian toolchains. It seemed more like there is a problem
with the Ubuntu packaged arm-none-eabi toolchain that produces broken
binaries.
Hey Alex,
Thanks, that did the trick. Wow, what happened with that compiler?
I now see that we have PR #10404 and a few issues about it. Hmm,
that PR could have given me a warning.
-- Kees
On 05-12-18 21:20, Alexandre Abadie wrote:
Hi Kees,
You need a more recent version of the GNU ARM
Hi Kees,
You need a more recent version of the GNU ARM compiler, 7.x, and you only have
6.3. The recommended toolchain is the official one from ARM that can be
downloaded at [1].
Just uncompress the archive somewhere in your filesystem (in /opt for example)
and update your PATH variable. This
Hi,
This may sound like a stupid question, but I can't get output
from hello world anymore. On my Sodaq Explorer and also on my
Sodaq One.
I have been away from RIOT for a few weeks and now that I get back
there is no output on UART0, and the LEDs don't work either.
Since last time, I upgraded
Thanks a lot for answering .I modified esp32-mh-et-live-minikit but they told
me that for the sake of learning I should ask you how to support an unsupported
board.Sorry to ask again but could you please tell me how to do so?
Thank you in advance,
Sent from
