-
I cannot get the GTR firmware to compile using ATOM, or VSCODE, the guide that the documentation refers to is for another board entirely, I spent 70 bucks getting this thing to me and I'm very offset …
-
Hello,
I have some problems with compiling the firmware. I followed the instructions as they described. However, there are also errors (letters exchanged) within some files which I could correct to…
-
@valeros I changed my platform.ini file as you said. But it did not solve my issue. I get the same issure as #281 .
Glad if you can help
-
What kind of issue is this?
- [X] **PlatformIO Core**.
If you’ve found a bug, please provide an information below.
*You can erase any parts of this template not applicable to your Issue.*…
-
Hello,
I already ported various custom targets with succes in the past (STM32F103CBT6, STM32F303CCT6, STM32L151C8T6, STM32L462CEU6), i now have to port our latest target STM32L451CEU6, unfortunately …
-
### Description
Dear experts,
There are two header files mbed_rtx_conf.h and RTX_Config.h with a lot of duplicated defines such as `OS_STACK_SIZE`, `MBED_CONF_APP_THREAD_STACK_SIZE`. And different v…
-
Hi, I cannot compile, I used the fix for --gc-sections in the other post, however I now get this.
```
Compiling file: crc16.c
Linking target: FruityMesh.elf
"/usr/local/gcc-arm-none-eabi-4_9-2015q2/b…
kabez updated
6 years ago
-
This is probably window-specific error -- path too long
--- Here is the error message --
$ make --trace > make_armc5-error.txt
C:/Users/alachu01/work/oob-1-3/mbed-os-example-bootloader/Makefile:9…
-
The exporter doesn't include the rtos source files when exporting a program using rtos to uvision. I tested this with the RTOS_1 program and NUCLEO_F411RE. The export succeeded, but the build in uvi…