Giter VIP home page Giter VIP logo

mbed-os-example-blinky's Introduction

Blinky Mbed OS example

The example project is part of the Arm Mbed OS Official Examples and is the getting started example for Mbed OS. It contains an application that repeatedly blinks an LED on supported Mbed boards.

You can build the project with all supported Mbed OS build tools. However, this example project specifically refers to the command-line interface tools, Arm Mbed CLI 1 and Mbed CLI 2.

(Note: To see a rendered example you can import into the Arm Online Compiler, please see our import quick start.)

Mbed OS build tools

Mbed CLI 2

Starting with version 6.5, Mbed OS uses Mbed CLI 2. It uses Ninja as a build system, and CMake to generate the build environment and manage the build process in a compiler-independent manner. If you are working with Mbed OS version prior to 6.5 then check the section Mbed CLI 1.

  1. Install Mbed CLI 2.
  2. From the command-line, import the example: mbed-tools import mbed-os-example-blinky
  3. Change the current directory to where the project was imported.

Mbed CLI 1

  1. Install Mbed CLI 1.
  2. From the command-line, import the example: mbed import mbed-os-example-blinky
  3. Change the current directory to where the project was imported.

Application functionality

The main() function is the single thread in the application. It toggles the state of a digital output connected to an LED on the board.

Note: This example requires a target with RTOS support, i.e. one with rtos declared in supported_application_profiles in targets/targets.json in mbed-os. For non-RTOS targets (usually with small memory sizes), please use mbed-os-example-blinky-baremetal instead.

Building and running

  1. Connect a USB cable between the USB port on the board and the host computer.

  2. Run the following command to build the example project and program the microcontroller flash memory:

    • Mbed CLI 2
    $ mbed-tools compile -m <TARGET> -t <TOOLCHAIN> --flash
    • Mbed CLI 1
    $ mbed compile -m <TARGET> -t <TOOLCHAIN> --flash

Your PC may take a few minutes to compile your code.

The binary is located at:

  • Mbed CLI 2 - ./cmake_build/<TARGET>/develop/<TOOLCHAIN>/mbed-os-example-blinky.bin
  • Mbed CLI 1 - ./BUILD/<TARGET>/<TOOLCHAIN>/mbed-os-example-blinky.bin

Alternatively, you can manually copy the binary to the board, which you mount on the host computer over USB.

Expected output

The LED on your target turns on and off every 500 milliseconds.

Troubleshooting

If you have problems, you can review the documentation for suggestions on what could be wrong and how to fix it.

Related Links

License and contributions

The software is provided under Apache-2.0 license. Contributions to this project are accepted under the same license. Please see CONTRIBUTING.md for more info.

This project contains code from other projects. The original license text is included in those source files. They must comply with our license guide.

mbed-os-example-blinky's People

Contributors

0xc0170 avatar adbridge avatar bogdanm avatar cmonr avatar evedon avatar gpsimenos avatar harmut01 avatar harrisonmutai-arm avatar hugueskamba avatar iriark01 avatar jainvikas8 avatar janjongboom avatar jaustin avatar jeromecoutant avatar kegilbert avatar ldong-arm avatar marcelosalazar avatar mbedmain avatar mlnx avatar patater avatar rajkan01 avatar rwalton-arm avatar saheerb avatar sg- avatar theotherjimmy avatar urutva avatar wernerlewis avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mbed-os-example-blinky's Issues

Compile error in online compiler, report_status.h

Upon creating a new program within the online compiler (My target is mbed LPC1768), selecting the mbed-os-example-blinky, and making no changes to the example, compilation fails with the following:

Error: Identifier "MBED_MAX_MEM_REGIONS" is undefined in "stats_report.h", Line: 45, Col: 30
In stats_report.h, if I comment out the following for loops that use this define, the program compiles fine:

        for (int i = 0; i < MBED_MAX_MEM_REGIONS; i++) {
            if (sys_stats.ram_size[i] != 0) {
                printf("RAM%d: Start 0x%lx Size: 0x%lx \r\n", i, sys_stats.ram_start[i], sys_stats.ram_size[i]);
            }
        }
        for (int i = 0; i < MBED_MAX_MEM_REGIONS; i++) {
            if (sys_stats.rom_size[i] != 0) {
                printf("ROM%d: Start 0x%lx Size: 0x%lx \r\n", i, sys_stats.rom_start[i], sys_stats.rom_size[i]);
            }
        }

It looks like MBED_MAX_MEM_REGIONS was added to mbed_stats.h in commit ad736e989466da375e20cf776409225f25045854 and this appears to be in the 5.11-rc1 branch.

So my guess here is that mbed-os-blinky merged in code intended to work with 5.11 but which fails with 5.10.whatever.

compiling problem of exported project from online IDE

I export the program mbed-os-example-blinky from online IDE to uvision5 on FRDM-K64F. When compiling. it shows the errors as below:

*** Using Compiler 'V5.06 update 1 (build 61)', folder: 'C:\Keil_v5\ARM\ARMCC\Bin'
Build target 'mbed-os-example-blinky'
compiling main.cpp...
main.cpp(1): error: #5: cannot open source input file "mbed.h": No such file or directory
main.cpp: 0 warnings, 1 error
"..build\uvision5\mbed-os-example-blinky.axf" - 1 Error(s), 0 Warning(s).
Target not created.
Build Time Elapsed: 00:00:00

It seems all related mbed-os files are not exported successfully.
I add the mbed-os.lib into the project manually, but still the same error.

Can't export to uVision for Pearl Gecko

When exporting to uvision for the Pearl Gecko, it is reported as not supporting that toolchain:

$ mbed export -m EFM32PG_STK3401 -i uvision

Failed:
  * EFM32PG_STK3401::uvision
Sorry, the target EFM32PG_STK3401 is not currently supported on the uvision toolchain.
Please refer to <a href='/handbook/Exporting-to-offline-toolchains' target='_blank'>Exporting to offline toolchains</a> for more information.

NUCLEO_L476RG led1.read() shows wrong value

Hi,

NUCLEO_L476RG led1.read() shows wrong value.
This is the blinky code with logs.

#include "mbed.h"

DigitalOut led1(LED1);

// main() runs in its own thread in the OS
int main() {
    while (true) {
        led1 = !led1;
        printf("Changed the LED(%d)\n", led1.read());
        wait(0.5);
    }
}

This is the output.

Changed the LED(1)
Changed the LED(1)
Changed the LED(1)

The expected output is following.

Changed the LED(0)
Changed the LED(1)
Changed the LED(0)
Changed the LED(1)

I tested with following mbed-os-example-blinky version but failed.

commit 12b6eaeea61c2887dccf1e05c45035b8e545e134
Merge: 83bb825 6d96d2f
Author: Martin Kojtal <[email protected]>
Date:   Fri Sep 15 07:32:34 2017 +0100

    Merge pull request #82 from adbridge/master

    Updating mbed-os to mbed-os-5.5.7

Then I changed mbed-os to mbed-os-5.6 branch and the result is same.

Thanks,

mbedls not working on Realtek RTL8195AM

mbedls and mbed detect don't work on the Realtek RTL8195AM board(https://os.mbed.com/platforms/Realtek-RTL8195AM/).

I connect the board over USB, it appears as USB mass storage device but it's not recognised by mbedls.
Here's the output that I get on Windows

`C:\Users\geogek01\Documents\mbedCLIproj\mbed-os-example-blinky [mbed-os-5.7.0-oob ≡ +1 ~1 -0 !]> mbedls

C:\Users\geogek01\Documents\mbedCLIproj\mbed-os-example-blinky [mbed-os-5.7.0-oob ≡ +1 ~1 -0 !]> mbed detect
[mbed] No mbed targets were detected on your system.`
C:\Users\geogek01\Documents\mbedCLIproj\mbed-os-example-blinky [mbed-os-5.7.0-oob ≡ +1 ~1 -0 !]> mbedls --version
1.2.14

How can I fix this issue?

Thanks,
George

[OOB mbed-os-5.4] Compilation failure in uVision for MTS_MDOT_F411RE , NUCLEO_F411RE

Description

Target: MTS_MDOT_F411RE and NUCLEO_F411RE
Toolchain: export uvision5
mbed-os version: 5.4 OOB
Error:

Object main.o contains Build Attributes that are incompatible with the provided attributes.
    Tag_FP_arch = VFPv4 instructions were permitted, but only citing registers D0-D15 (=6)
    Tag_ABI_HardFP_use = This code should execute on the single-precision variant derived from Tag_FP_arch (=1)
    Tag_FP_HP_extension = Use of the optional half-precision extension to VFPv3/Advanced SIMDv1 was permitted (=1)
.\BUILD\mbed-os-example-blinky.axf: Error: L6367E: main.o(i.__sti___8_main_cpp_led1) attributes are not compatible with the provided attributes .
Object timeout.o contains Build Attributes that are incompatible with the provided attributes.
    Tag_FP_arch = VFPv4 instructions were permitted, but only citing registers D0-D15 (=6)
    Tag_ABI_HardFP_use = This code should execute on the single-precision variant derived from Tag_FP_arch (=1)
    Tag_FP_HP_extension = Use of the optional half-precision extension to VFPv3/Advanced SIMDv1 was permitted (=1)
.\BUILD\mbed-os-example-blinky.axf: Error: L6367E: timeout.o(.rrx_text) attributes are not compatible with the provided attributes .
Object timeout.o contains Build Attributes that are incompatible with the provided attributes.
    Tag_FP_arch = VFPv4 instructions were permitted, but only citing registers D0-D15 (=6)
    Tag_ABI_HardFP_use = This code should execute on the single-precision variant derived from Tag_FP_arch (=1)
    Tag_FP_HP_extension = Use of the optional half-precision extension to VFPv3/Advanced SIMDv1 was permitted (=1)
.\BUILD\mbed-os-example-blinky.axf: Error: L6367E: timeout.o(i._ZN4mbed7Timeout7handlerEv) attributes are not compatible with the provided attributes .

Can't compile for NUCLEO_F746ZG using IAR

When compiling for NUCLEO_F746ZG using IAR, it reports and invalid processor type, with the following error:

$ mbed compile -m NUCLEO_F746ZG -t IAR
Building project mbed-os-example-blinky (NUCLEO_F746ZG, IAR)
Scan: .
Scan: FEATURE_BLE
Scan: FEATURE_CLIENT
Scan: FEATURE_COMMON_PAL
Scan: FEATURE_UVISOR
Scan: FEATURE_IPV4
Scan: FEATURE_IPV6
Scan: FEATURE_STORAGE
Scan: mbed
Scan: env
Compile: main.cpp
[ERROR] Command line error: in "--cpu Cortex-M7":
          Invalid processor type: Cortex-M7

[mbed] ERROR: "python" returned error code 1.
[mbed] ERROR: Command "python -u C:\Work\OOB\mbed-os-example-blinky\mbed-os\tools\make.py -t IAR -m NUCLEO_F746ZG --source . --build .\.build\NUCLEO_F746ZG\IAR" in "C:\Work\OOB\mbed-os-example-blinky"

make_iar test failure

Here are the details:

PS C:\> mbed import mbed-os-example-blinky
[mbed] Importing program "bed-os-example-blinky" from "https://github.com/ARMmbed/mbed-os-example-blinky" at latest revi
sion in the current branch
[mbed] Adding library "mbed-os" from "https://github.com/ARMmbed/mbed-os" at rev #ca661f9d2852
PS C:\> cd mbed-os*
PS C:\mbed-os-example-blinky> mbed update mbed-os-5.6-oob
[mbed] Updating program "mbed-os-example-blinky" to branch mbed-os-5.6-oob
[mbed] Updating library "mbed-os" to rev #a4056fb8bf3e
PS C:\mbed-os-example-blinky> mbed config --list
[mbed] Global config:
ARM_PATH=C:\Keil_v5
IAR_PATH=C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0\arm

[mbed] Local config (C:\mbed-os-example-blinky):
No local configuration is set
PS C:\mbed-os-example-blinky> mbed export -m NUCLEO_F429ZI -i make_iar
Scan: .
Scan: FEATURE_LWIP
PS C:\mbed-os-example-blinky> make
C:/mbed-os-example-blinky/makefile:700: warning: overriding commands for target `.s.o'
C:/mbed-os-example-blinky/makefile:695: warning: ignoring old commands for target `.s.o'
"Compile: main.cpp"
process_begin: CreateProcess(NULL, iccarm --no_wrap_diagnostics -e --diag_suppress=Pa050,Pa084,Pa093,Pa082 -On -r -DMBED
_DEBUG -DMBED_TRAP_ERRORS_ENABLED=1 --cpu Cortex-M4F --thumb --dlib_config DLib_Config_Full.h --c++ --no_rtti --no_excep
tions --guard_calls --no_static_destruction --guard_calls --no_static_destruction -DTARGET_STM32F429xx -DDEVICE_SPISLAVE
=1 -DFEATURE_LWIP=1 -D__MBED__=1 -DDEVICE_I2CSLAVE=1 -D__FPU_PRESENT=1 -DTRANSACTION_QUEUE_SIZE_SPI=2 -DUSBHOST_OTHER -D
DEVICE_PORTINOUT=1 -DTARGET_RTOS_M4_M7 -DTARGET_NUCLEO_F429ZI -DDEVICE_LOWPOWERTIMER=1 -DDEVICE_RTC=1 -DTOOLCHAIN_object
 -DTARGET_STM32F4 -D__CMSIS_RTOS -DDEVICE_CAN=1 -DTARGET_CORTEX_M -DTARGET_DEBUG -DDEVICE_I2C_ASYNCH=1 -DTARGET_LIKE_COR
TEX_M4 -DDEVICE_ANALOGOUT=1 -DTARGET_M4 -DTARGET_UVISOR_UNSUPPORTED -DDEVICE_PORTOUT=1 -DDEVICE_SPI_ASYNCH=1 -DTOOLCHAIN
_IAR -DDEVICE_INTERRUPTIN=1 -DTARGET_CORTEX -DDEVICE_I2C=1 -DTARGET_STM32F429 -D__CORTEX_M4 -DDEVICE_STDIO_MESSAGES=1 -D
DEVICE_PWMOUT=1 -DTARGET_FAMILY_STM32 -DTARGET_FF_ARDUINO -DDEVICE_PORTIN=1 -DTARGET_STM -DDEVICE_SERIAL_FC=1 -DDEVICE_T
RNG=1 -DTARGET_LIKE_MBED -DTARGET_STM32F429ZI -D__MBED_CMSIS_RTOS_CM -DDEVICE_SLEEP=1 -DMBED_BUILD_TIMESTAMP=1505759437.
6 -DDEVICE_SPI=1 -DUSB_STM_HAL -DTARGET_STM32F429xI -DDEVICE_ANALOGIN=1 -DDEVICE_SERIAL=1 -DDEVICE_FLASH=1 -DARM_MATH_CM
4 --preinclude=mbed_config.h -I../ -I../. -I.././img -I.././mbed-os -I.././mbed-os/cmsis -I.././mbed-os/cmsis/TARGET_COR
TEX_M -I.././mbed-os/cmsis/TOOLCHAIN_IAR -I.././mbed-os/drivers -I.././mbed-os/events -I.././mbed-os/events/equeue -I../
./mbed-os/features -I.././mbed-os/features/FEATURE_LWIP -I.././mbed-os/features/FEATURE_LWIP/lwip-interface -I.././mbed-
os/features/FEATURE_LWIP/lwip-interface/lwip -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip-eth -I.././mbed-os
/features/FEATURE_LWIP/lwip-interface/lwip-eth/arch -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip-eth/arch/TA
RGET_STM -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip-eth/arch/TARGET_STM/TARGET_STM32F4 -I.././mbed-os/feat
ures/FEATURE_LWIP/lwip-interface/lwip-eth/arch/TARGET_STM/TARGET_STM32F4/TARGET_NUCLEO_F429ZI -I.././mbed-os/features/FE
ATURE_LWIP/lwip-interface/lwip-sys -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip-sys/arch -I.././mbed-os/feat
ures/FEATURE_LWIP/lwip-interface/lwip/src -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/api -I.././mbed-o
s/features/FEATURE_LWIP/lwip-interface/lwip/src/core -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/core/i
pv4 -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/core/ipv6 -I.././mbed-os/features/FEATURE_LWIP/lwip-int
erface/lwip/src/include -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/include/lwip -I.././mbed-os/feature
s/FEATURE_LWIP/lwip-interface/lwip/src/include/lwip/priv -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/in
clude/lwip/prot -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/include/netif -I.././mbed-os/features/FEATU
RE_LWIP/lwip-interface/lwip/src/include/netif/ppp -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/include/n
etif/ppp/polarssl -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/netif -I.././mbed-os/features/FEATURE_LWI
P/lwip-interface/lwip/src/netif/ppp -I.././mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/netif/ppp/polarssl -I..
/./mbed-os/features/filesystem -I.././mbed-os/features/filesystem/bd -I.././mbed-os/features/filesystem/fat -I.././mbed-
os/features/filesystem/fat/ChaN -I.././mbed-os/features/frameworks -I.././mbed-os/features/frameworks/greentea-client -I
.././mbed-os/features/frameworks/greentea-client/greentea-client -I.././mbed-os/features/frameworks/greentea-client/sour
ce -I.././mbed-os/features/frameworks/unity -I.././mbed-os/features/frameworks/unity/source -I.././mbed-os/features/fram
eworks/unity/unity -I.././mbed-os/features/frameworks/utest -I.././mbed-os/features/frameworks/utest/source -I.././mbed-
os/features/frameworks/utest/utest -I.././mbed-os/features/mbedtls -I.././mbed-os/features/mbedtls/importer -I.././mbed-
os/features/mbedtls/inc -I.././mbed-os/features/mbedtls/inc/mbedtls -I.././mbed-os/features/mbedtls/platform -I.././mbed
-os/features/mbedtls/platform/inc -I.././mbed-os/features/mbedtls/platform/src -I.././mbed-os/features/mbedtls/src -I../
./mbed-os/features/mbedtls/targets -I.././mbed-os/features/mbedtls/targets/TARGET_STM -I.././mbed-os/features/mbedtls/ta
rgets/TARGET_STM/TARGET_STM32F4 -I.././mbed-os/features/nanostack -I.././mbed-os/features/netsocket -I.././mbed-os/featu
res/netsocket/cellular -I.././mbed-os/features/netsocket/cellular/generic_modem_driver -I.././mbed-os/features/netsocket
/cellular/utils -I.././mbed-os/features/storage -I.././mbed-os/hal -I.././mbed-os/hal/storage_abstraction -I.././mbed-os
/platform -I.././mbed-os/rtos -I.././mbed-os/rtos/TARGET_CORTEX -I.././mbed-os/rtos/TARGET_CORTEX/rtx4 -I.././mbed-os/rt
os/TARGET_CORTEX/rtx5 -I.././mbed-os/rtos/TARGET_CORTEX/rtx5/TARGET_RTOS_M4_M7 -I.././mbed-os/rtos/TARGET_CORTEX/rtx5/TA
RGET_RTOS_M4_M7/TOOLCHAIN_IAR -I.././mbed-os/targets -I.././mbed-os/targets/TARGET_STM -I.././mbed-os/targets/TARGET_STM
/TARGET_STM32F4 -I.././mbed-os/targets/TARGET_STM/TARGET_STM32F4/TARGET_STM32F429xI -I.././mbed-os/targets/TARGET_STM/TA
RGET_STM32F4/TARGET_STM32F429xI/TARGET_NUCLEO_F429ZI -I.././mbed-os/targets/TARGET_STM/TARGET_STM32F4/TARGET_STM32F429xI
/device -I.././mbed-os/targets/TARGET_STM/TARGET_STM32F4/TARGET_STM32F429xI/device/TOOLCHAIN_IAR -I.././mbed-os/targets/
TARGET_STM/TARGET_STM32F4/device -o main.o ../main.cpp, ...) failed.
make (e=2): The system cannot find the file specified.
make[1]: *** [main.o] Error 2
make: *** [all] Error 2
PS C:\mbed-os-example-blinky>

NRF51_DK: Export to GCC_ARM doesn't work; generated binaries look dodgy (small?)

Platform

NRF51_DK

OS

Linux Ubuntu 14.04
MacOS (10.11.6)

Steps

  1. mbed export -i GCC_ARM -m NRF51_DK
  2. make

Results

LED stay off

arm-none-eabi-objcopy -O binary Unnamed_Project.elf Unnamed_Project.bin
arm-none-eabi-size Unnamed_Project.elf
   text    data     bss     dec     hex filename
  60180     264    3168   63612    f87c Unnamed_Project.elf
 $ ls -lh .build/
total 800
-rwxr-xr-x  1 barsza01  staff    42K 27 Jul 10:53 Unnamed_Project.bin
-rwxr-xr-x  1 barsza01  staff   219K 27 Jul 10:53 Unnamed_Project.elf
-rw-r--r--  1 barsza01  staff   119K 27 Jul 10:53 Unnamed_Project.hex
-rw-r--r--  1 barsza01  staff   8.8K 27 Jul 10:52 main.d
-rw-r--r--  1 barsza01  staff   3.4K 27 Jul 10:52 main.o
drwxr-xr-x  5 barsza01  staff   170B 27 Jul 10:52 mbed-os

while mbed cli generated binaries:

+----------------------+-------+-------+------+
| Module               | .text | .data | .bss |
+----------------------+-------+-------+------+
| Fill                 |   127 |     3 |   29 |
| Misc                 |  8152 |   120 |  500 |
| features/FEATURE_BLE | 21670 |    13 |  835 |
| features/frameworks  |  3142 |    92 |  336 |
| features/net         |    16 |     0 |    0 |
| hal/common           |  2472 |     4 |  269 |
| hal/targets          |  2794 |     8 |  209 |
| rtos/rtos            |   442 |     4 |    0 |
| rtos/rtx             |  5137 |    20 |  990 |
| Subtotals            | 43952 |   264 | 3168 |
+----------------------+-------+-------+------+
Allocated Heap: 17048 bytes
Allocated Stack: 2048 bytes
Total Static RAM memory (data + bss): 3432 bytes
Total RAM memory (data + bss + heap + stack): 22528 bytes
Total Flash memory (text + data + misc): 44216 bytes
$ ls -lh .build/NRF51_DK/GCC_ARM/
total 3344
-rw-r--r--  1 barsza01  staff   3.6K 27 Jul 10:09 main.d
-rw-r--r--  1 barsza01  staff   3.4K 27 Jul 10:09 main.o
drwxr-xr-x  5 barsza01  staff   170B 27 Jul 10:09 mbed-os
-rwxr-xr-x  1 barsza01  staff   219K 27 Jul 10:09 mbed-os-example-blinky.elf
-rwxr-xr-x  1 barsza01  staff   413K 27 Jul 10:14 mbed-os-example-blinky.hex
-rw-r--r--  1 barsza01  staff   1.0M 27 Jul 10:09 mbed-os-example-blinky.map
-rw-r--r--  1 barsza01  staff   614B 27 Jul 10:14 mbed-os-example-blinky_map.csv
-rw-r--r--  1 barsza01  staff   1.5K 27 Jul 10:14 mbed-os-example-blinky_map.json

Especially the .hex file is 413K vs 119K

Blinky example export encounter several issues on VSCode

Before, all of that I've installed
VSCode,
gcc-arm-none-eabi-7-2018-q2-update-win32-sha2,
pyOCD (with pip)
C/C++ plugin (by Microsoft) for VSCode

And as described here https://os.mbed.com/docs/v5.9/tutorials/visual-studio-code.html

I followed these instructions:
Exporting a project/Online Compiler
Configuring the debugger

But at this step "Open the .vscode/launch.json file"
(1) There is the first problem:
There is no .vscode folder launch.json is outside the folder.

I pushed F5 key to debug, in order to let the VSCode program create this folder. And I replaced the created lauch.json file, by ours. It solved the problems of compilation.

I continued following the steps until "Debugging your project"

(2) Here is the second issue, and it is in the documentation :
image

But there is no debug tab by default !
image

You'have to click on view then Debug to make it appear.

After this I clicked on the triangle of the debug tab as explained (equivalent of F5), then third issue occurs !

(3) It says that make.exe is unfoundable:
image

I remind that I've already installed GNU GCC tools for arm and added them to the PATH, like this:
image

So here I'm blocked, I don't kown how to go further.

(4) The fourth problem is that : On the getting started file
2018-08-15 03_25_10-gettingstarted html - notuptodate

When you click on this : https://os.mbed.com/docs/v5.6/tools/exporting.html/

You get this :
image

(5) The other remark is it is the 5.6 version, and it is not up to date.

(6) I don't know even after making the json file at the good place, I still have these dependancy warnings:
image

GCC_ARM won't link on NRF51822: cannot move location counter backwards

Won't link when building for NRF51822 like so: (trying to build for micro:bit)

$ mbed compile -t GCC_ARM -m NRF51822
Building project mbed-os-example-blinky (NRF51822, GCC_ARM)
Scan: .
Scan: FEATURE_UVISOR
Scan: FEATURE_BLE
Scan: FEATURE_CLIENT
Scan: FEATURE_COMMON_PAL
Scan: FEATURE_IPV4
Scan: FEATURE_IPV6
Scan: FEATURE_STORAGE
Scan: mbed
Scan: env
Link: mbed-os-example-blinky
./mbed-os/hal/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM/TARGET_MCU_NRF51_16K_S130/NRF51822.ld:133 cannot move location counter backwards (from 0000000020003d60 to 0000000020003800)
collect2: error: ld returned 1 exit status
[ERROR] ./mbed-os/hal/targets/cmsis/TARGET_NORDIC/TARGET_MCU_NRF51822/TOOLCHAIN_GCC_ARM/TARGET_MCU_NRF51_16K_S130/NRF51822.ld:133 cannot move location counter backwards (from 0000000020003d60 to 0000000020003800)
collect2: error: ld returned 1 exit status

[mbed] ERROR: "python" returned error code 1.
[mbed] ERROR: Command "python -u /home/user/Programming/mbed/mbed-os-example-blinky/mbed-os/tools/make.py -t GCC_ARM -m NRF51822 --source . --build ./.build/NRF51822/GCC_ARM" in "/home/user/Programming/mbed/mbed-os-example-blinky"

---

The same toolchain builds for lpc1768 and lpc11u24 fine (the only other two platforms I have).
Have also reproduced with a different (gcc 5.2.0, newlib 2.2.0) toolchain on ARMv7 built via crosstool-ng.

Online compiler error for the Realtek RTL8195AM board

I'm unable to compile blinky in the online compiler for the Realtek RTL8195AM board. I'm on the mbed-os-5.7.0-oob branch. I'm getting Error L6236E. See the screenshot for the complete error message
image

Can you please fix this issue?

Regards,
George

[OOB mbed-os-5.4] Post binary hook not run on make for target MTS_MDOT_F411RE

Description

Target: MTS_MDOT_F411RE
Toolchain: export make_gcc_arm
mbed-os version: 5.4 OOB
Error: Does not run application

Details

Correctly runs post binary hook:
mbed compile -t GCC_ARM -m MTS_MDOT_F411RE

Does not run post binary hook and therefore will not run the application:
mbed export -i make_gcc_arm
make

Application crash when target default build is "small"

If the target default_build option is set to small then if the program is compiled with the instructions provided in the readme and run, it will crash at the instantiation of the thread.

A small build will force the use of nanolib and restrict the number of threads to one, the main thread. In that configuration, instantiating a thread will crash the application.

One easy fix would be to update the compilation instruction to:

mbed compile -m <target_name> -t GCC_ARM -o big-build

Or provide and errata indicating the list of targets concerned by this issue and that -o big-build should be added to the command line.

The list of the targets using nano lib is:

CM4_UARM
CM4_ARM
CM4F_UARM
CM4F_ARM
LPC1114
LPC11U24
OC_MBUINO
LPC11U34_421
MICRONFCBOARD
LPC11U35_401
LPC11U35_501
LPC11U35_501_IBDAP
XADOW_M0
LPC11U35_Y5_MBUG
LPC11U37_501
LPCCAPPUCCINO
ARCH_GPRS
LPC11U68
LPC1549
LPC810
LPC812
LPC824
SSCI824
LPC11U37H_401
ELEKTOR_COCORICO
KL05Z
NUCLEO_F030R8
NUCLEO_F031K6
NUCLEO_F042K6
NUCLEO_F070RB
NUCLEO_F072RB
NUCLEO_F091RC
NUCLEO_F103RB
NUCLEO_F302R8
NUCLEO_F303K8
NUCLEO_F303RE
NUCLEO_F334R8
NUCLEO_F401RE
NUCLEO_F410RB
NUCLEO_F411RE
ELMO_F411RE
NUCLEO_F446RE
B96B_F446VE
NUCLEO_L031K6
NUCLEO_L053R8
NUCLEO_L073RZ
NUCLEO_L152RE
NUCLEO_L476RG
STM32F3XX
DISCO_F051R8
DISCO_F100RB
DISCO_F303VC
DISCO_F334C8
DISCO_F429ZI
DISCO_F469NI
DISCO_L053C8
DISCO_L476VG
MOTE_L152RC
UBLOX_C029
NZ32_SC151
MCU_NRF51
MCU_NRF51_16K_BASE
MCU_NRF51_16K_BOOT_BASE
MCU_NRF51_16K_OTA_BASE
MCU_NRF51_16K
MCU_NRF51_S110
MCU_NRF51_16K_S110
MCU_NRF51_16K_BOOT
MCU_NRF51_16K_BOOT_S110
MCU_NRF51_16K_OTA
MCU_NRF51_16K_OTA_S110
MCU_NRF51_32K
MCU_NRF51_32K_BOOT
MCU_NRF51_32K_OTA
NRF51822
NRF51822_BOOT
NRF51822_OTA
ARCH_BLE
ARCH_BLE_BOOT
ARCH_BLE_OTA
ARCH_LINK
ARCH_LINK_BOOT
ARCH_LINK_OTA
SEEED_TINY_BLE
SEEED_TINY_BLE_BOOT
SEEED_TINY_BLE_OTA
HRM1017
HRM1017_BOOT
HRM1017_OTA
RBLAB_NRF51822
RBLAB_NRF51822_BOOT
RBLAB_NRF51822_OTA
RBLAB_BLENANO
RBLAB_BLENANO_BOOT
RBLAB_BLENANO_OTA
NRF51822_Y5_MBUG
WALLBOT_BLE
WALLBOT_BLE_BOOT
WALLBOT_BLE_OTA
DELTA_DFCM_NNN40
DELTA_DFCM_NNN40_BOOT
DELTA_DFCM_NNN40_OTA
NRF51_DK
NRF51_DK_BOOT
NRF51_DK_OTA
NRF51_DONGLE
NRF51_DONGLE_BOOT
NRF51_DONGLE_OTA
NRF51_MICROBIT
NRF51_MICROBIT_BOOT
NRF51_MICROBIT_OTA
NRF51_MICROBIT_B
NRF51_MICROBIT_B_BOOT
NRF51_MICROBIT_B_OTA
TY51822R3
TY51822R3_BOOT
TY51822R3_OTA
EFM32ZG_STK3200
EFM32HG_STK3400

That is a total of 119 targets out of the 184 available in targets.json.

[OOB 5.5.0] REALTEK_RTL8195AM export make_gcc flash failure

Flashing a binary compiled with the makefile exported from make_gcc_arm times out for REALTEK_RTL8195AM

mbed OS: 92fbf2a9b3988d430482fc25a6077f2462e2a634
mbed CLI version: 1.1.1

Command to reproduce:

mbed export -i make_gcc_arm
make

Fail message:

The transfer timed out.

Daplink details:

# DAPLink Firmware - see https://mbed.com/daplink
Unique ID: 46000000061593ce00000000000000000000000097969902
HIC ID: 97969902
Auto Reset: 0
Automation allowed: 0
Daplink Mode: Interface
Interface Version: 0241
Git SHA: e6046fae5e2d3433b04ed95bb80a96375e8db68b
Local Mods: 1
USB Interfaces: MSD, CDC, HID
Interface CRC: 0xb2086ac7

mbed export: argument -n mbed-os-example-blinky not recognized

mbed export -m K64F -i uvision -n mbed-os-example-blinky
usage: project.py [-h] [-m MCU] [-i IDE] [-c] [-p PROGRAM] [-n PROGRAM]
                  [-b BUILD] [-L] [-S] [-E] [--source SOURCE_DIR] [-D MACROS]
project.py: error: argument -n: Program with name 'mbed-os-example-blinky' not found. Supported tests are:
EXAMPLE LIST*

*didn't want to copy the whole thing

Misleading output about VK_RZ_A1H and RZ_A1H in 5.7

Branch: mbed-os-5.7.0-oob

It seems VK_RZ_A1H and RZ_A1H (Cortex-A) are not supported.

We should update the message "Will be supported in mbed OS 5.6" with something like "Will be supported in a future version of Mbed OS"

@0xc0170

mac:~/mbed/OOB/5.7/mbed-os-example-blinky$ mbed compile -t GCC_ARM -m VK_RZ_A1H
Building project mbed-os-example-blinky (VK_RZ_A1H, GCC_ARM)
Scan: .
Scan: mbed
Scan: env
Scan: FEATURE_LWIP

Could not compile for VK_RZ_A1H: VK_RZ_A1H Will be supported in mbed OS 5.6. To use the VK_RZ_A1H, please checkout the mbed OS 5.4 release branch. See https://developer.mbed.org/platforms/Renesas-GR-PEACH/#important-notice for more information

This example does not work after exporting on Keil µVision 5

The example works well on Arm mbed Online Compiler but after exporting on Keil and building, it says at least two errors:

  1. /filer/workspace_data/exports/8/8bbbb9b5d0fe7814b65b507b54bb7d92/mbed-os-example-blinky/mbed_config.h contains an incorrect path

image

  1. After building it make at least one error which is underlined in #include "mbed.h". It says: error in include chain (mbed_assert.h): invalid token at start of a preprocessor expression

image

Can't compile using IAR for Pearl Gecko

When compiling using mbed-CLI with IAR, this error occurs:

[Warning] serial_api.c@1111,35: [Pe188]: enumerated type mixed with another type
[Error] serial_api.c@1436,35: [Pe661]: expected an integer constant
[ERROR]
      pin_mode(tx, PushPull | 0x10);
                   ^
"C:\Work\OOB\mbed-os-example-blinky\mbed-os\hal\targets\hal\TARGET_Silicon_Labs\TARGET_EFM32\serial_api.c",1111  Warning[Pe188]: enumerated type mixed with another type

          LDMA_Descriptor_t desc = LDMA_DESCRIPTOR_SINGLE_M2P_BYTE(buffer, target_addr, length);
                                   ^
"C:\Work\OOB\mbed-os-example-blinky\mbed-os\hal\targets\hal\TARGET_Silicon_Labs\TARGET_EFM32\serial_api.c",1436  Error[Pe661]: expected an integer constant

          LDMA_Descriptor_t desc = LDMA_DESCRIPTOR_SINGLE_P2M_BYTE(source_addr, buffer, length);
                                   ^
"C:\Work\OOB\mbed-os-example-blinky\mbed-os\hal\targets\hal\TARGET_Silicon_Labs\TARGET_EFM32\serial_api.c",1473  Error[Pe661]: expected an integer constant

[mbed] ERROR: "python" returned error code 1.
[mbed] ERROR: Command "python -u C:\Work\OOB\mbed-os-example-blinky\mbed-os\tools\make.py -t IAR -m EFM32PG_STK3401 -c --source . --build .\.build\EFM32PG_STK3401\IAR" in "C:\Work\OOB\mbed-os-example-blinky"

not able to run test_cmdline

Am I missing something below? The "-vv" very_verbose mode is also not printing all the infos.

C:\Users\[User]\workspace\mbedOS\mbed-os-example-blinky\mbed-os>mbed test -m DISCO_L475VG_IOT01A -t GCC_ARM --icetea -n test_cmdline -DICETEA_EXAMPLE_ENABLED -vv
[mbed-4916] Working path "C:\Users\BTEM7\workspace\mbedOS\mbed-os-example-blinky\mbed-os" (library)
[mbed-4916] Program path "C:\Users\BTEM7\workspace\mbedOS\mbed-os-example-blinky"
[mbed-4916] Exec "c:\python27\python.exe -m pip list -l" in "C:\Users\BTEM7\workspace\mbedOS\mbed-os-example-blinky\mbed-os"
Package                       Version
appdirs                       1.4.3
argcomplete                   1.9.4
asn1ate                       0.6.0
asn1crypto                    0.24.0
beautifulsoup4                4.6.3
certifi                       2018.11.29
cffi                          1.11.5
chardet                       3.0.4
colorama                      0.3.9
coloredlogs                   10.0
cryptography                  2.1.4
Deprecated                    1.2.4
ecdsa                         0.13
enum34                        1.1.6
fasteners                     0.14.1
funcsigs                      1.0.2
functools32                   3.2.3.post2
future                        0.16.0
futures                       3.2.0
fuzzywuzzy                    0.17.0
hgapi                         1.7.4
humanfriendly                 4.17
icetea                        1.1.0
idna                          2.7
intelhex                      2.2.1
intervaltree                  2.1.0
ipaddress                     1.0.22
Jinja2                        2.10
jsonmerge                     1.5.2
jsonpointer                   1.14
jsonschema                    2.6.0
junit-xml                     1.8
lockfile                      0.12.2
Logbook                       1.4.1
lxml                          4.2.5
manifest-tool                 1.4.6
MarkupSafe                    1.1.0
mbed-cli                      1.8.3
mbed-cloud-sdk                2.0.1
mbed-flasher                  0.9.2
mbed-greentea                 0.2.24
mbed-host-tests               1.1.2
mbed-ls                       1.6.2
mbed-test-wrapper             1.0.0
mock                          2.0.0
monotonic                     1.5
ntfsutils                     0.1.4
pathlib                       1.0.1
pbr                           5.1.1
pip                           18.1
prettytable                   0.7.2
project-generator             0.8.17
project-generator-definitions 0.2.38
protobuf                      3.5.2.post1
psutil                        5.4.8
py                            1.7.0
pyasn1                        0.2.3
pycparser                     2.19
pyelftools                    0.23
PyGithub                      1.43.4
PyJWT                         1.7.1
pyocd                         0.14.3
pyOpenSSL                     18.0.0
pyparsing                     2.3.0
pyreadline                    2.1
pyserial                      3.4
pyshark-legacy                0.3.8
python-dateutil               2.7.5
python-dotenv                 0.10.1
pyusb                         1.0.2
pywinusb                      0.4.2
PyYAML                        3.13
requests                      2.20.1
semantic-version              2.6.0
semver                        2.8.1
setuptools                    40.6.3
setuptools-scm-git-archive    1.0
six                           1.11.0
sortedcontainers              2.1.0
trollius                      1.0.4
urllib3                       1.23
valinor                       0.0.15
websocket-client              0.54.0
wrapt                         1.10.11
xmltodict                     0.11.0
yattag                        1.10.1
yotta                         0.18.5
[mbed-4916] Exec "c:\python27\python.exe -u C:\Users\BTEM7\workspace\mbedOS\mbed-os-example-blinky\mbed-os\tools\run_icetea.py -m DISCO_L475VG_IOT01A -t GCC_ARM -n test_cmdline -v --application-list" in "C:\Users\BTEM7\workspace\mbedOS\mbed-os-example-blinky"
[mbed-4916] ERROR: "c:\python27\python.exe" returned error.
       Code: 1
       Path: "C:\Users\BTEM7\workspace\mbedOS\mbed-os-example-blinky"
       Command: "c:\python27\python.exe -u C:\Users\BTEM7\workspace\mbedOS\mbed-os-example-blinky\mbed-os\tools\run_icetea.py -m DISCO_L475VG_IOT01A -t GCC_ARM -n test_cmdline -v --application-list"
       Tip: You could retry the last command with "-v" flag for verbose output
---

I also tried to re-install packages if there was missing any with requirements.txt. Below is the output:

C:\Users\[User]\Desktop>pip install -r requirements.txt
Collecting git+https://github.com/armmbed/[email protected] (from -r requirements.txt (line 20))
  Cloning https://github.com/armmbed/manifest-tool.git (to revision v1.4.6) to c:\users\btem7\appdata\local\temp\pip-req-build-bawebr
Requirement already satisfied (use --upgrade to upgrade): manifest-tool==1.4.6 from git+https://github.com/armmbed/[email protected] in c:\python27\lib\site-packages (from -r requirements.txt (line 20))
Requirement already satisfied: colorama==0.3.9 in c:\python27\lib\site-packages (from -r requirements.txt (line 1)) (0.3.9)
Requirement already satisfied: pyserial<=3.4,>=3 in c:\python27\lib\site-packages (from -r requirements.txt (line 2)) (3.4)
Requirement already satisfied: prettytable==0.7.2 in c:\python27\lib\site-packages (from -r requirements.txt (line 3)) (0.7.2)
Requirement already satisfied: Jinja2<=2.10,>=2.7.3 in c:\python27\lib\site-packages (from -r requirements.txt (line 4)) (2.10)
Requirement already satisfied: intelhex<=2.2.1,>=1.3 in c:\python27\lib\site-packages (from -r requirements.txt (line 5)) (2.2.1)
Requirement already satisfied: junit-xml==1.8 in c:\python27\lib\site-packages (from -r requirements.txt (line 6)) (1.8)
Requirement already satisfied: pyYAML==3.13 in c:\python27\lib\site-packages (from -r requirements.txt (line 7)) (3.13)
Requirement already satisfied: urllib3[secure]==1.23 in c:\python27\lib\site-packages (from -r requirements.txt (line 8)) (1.23)
Requirement already satisfied: requests<2.21,>=2.20 in c:\python27\lib\site-packages (from -r requirements.txt (line 9)) (2.20.1)
Requirement already satisfied: intervaltree<3,>=2 in c:\python27\lib\site-packages (from -r requirements.txt (line 10)) (2.1.0)
Requirement already satisfied: mbed-ls<1.7,>=1.5.1 in c:\python27\lib\site-packages (from -r requirements.txt (line 11)) (1.6.2)
Requirement already satisfied: mbed-host-tests<=1.5,>=1.1.2 in c:\python27\lib\site-packages (from -r requirements.txt (line 12)) (1.1.2)
Requirement already satisfied: mbed-greentea<=1.5,>=0.2.24 in c:\python27\lib\site-packages (from -r requirements.txt (line 13)) (0.2.24)
Requirement already satisfied: beautifulsoup4<=4.6.3,>=4 in c:\python27\lib\site-packages (from -r requirements.txt (line 14)) (4.6.3)
Requirement already satisfied: fuzzywuzzy<=0.17,>=0.11 in c:\python27\lib\site-packages (from -r requirements.txt (line 15)) (0.17.0)
Collecting pyelftools<=0.25,>=0.24 (from -r requirements.txt (line 16))
  Using cached https://files.pythonhosted.org/packages/fa/9a/0674cb1725196568bdbca98304f2efb17368b57af1a4bb3fc772c026f474/pyelftools-0.25.tar.gz
Requirement already satisfied: jsonschema==2.6.0 in c:\python27\lib\site-packages (from -r requirements.txt (line 17)) (2.6.0)
Requirement already satisfied: future==0.16.0 in c:\python27\lib\site-packages (from -r requirements.txt (line 18)) (0.16.0)
Requirement already satisfied: six==1.11.0 in c:\python27\lib\site-packages (from -r requirements.txt (line 19)) (1.11.0)
Requirement already satisfied: mbed-cloud-sdk==2.0.1 in c:\python27\lib\site-packages (from -r requirements.txt (line 21)) (2.0.1)
Collecting icetea<1.1,>=1.0.2 (from -r requirements.txt (line 22))
  Using cached https://files.pythonhosted.org/packages/4a/1f/c9252b4599862a1d86cf599e1f067cbc880448a17bbd4752608d8aa99e86/icetea-1.0.2-py2-none-any.whl
Requirement already satisfied: ecdsa>=0.13 in c:\python27\lib\site-packages (from manifest-tool==1.4.6->-r requirements.txt (line 20)) (0.13)
Requirement already satisfied: cryptography>=2.0.0 in c:\python27\lib\site-packages (from manifest-tool==1.4.6->-r requirements.txt (line 20)) (2.1.4)
Requirement already satisfied: pyasn1<0.3.0,>=0.2.1 in c:\python27\lib\site-packages (from manifest-tool==1.4.6->-r requirements.txt (line 20)) (0.2.3)
Requirement already satisfied: asn1ate>=0.5 in c:\python27\lib\site-packages (from manifest-tool==1.4.6->-r requirements.txt (line 20)) (0.6.0)
Requirement already satisfied: pyparsing>=2.1.0 in c:\python27\lib\site-packages (from manifest-tool==1.4.6->-r requirements.txt (line 20)) (2.3.0)
Requirement already satisfied: protobuf<3.6.0,>=3.5.0 in c:\python27\lib\site-packages (from manifest-tool==1.4.6->-r requirements.txt (line 20)) (3.5.2.post1)
Requirement already satisfied: MarkupSafe>=0.23 in c:\python27\lib\site-packages (from Jinja2<=2.10,>=2.7.3->-r requirements.txt (line 4)) (1.1.0)
Requirement already satisfied: idna>=2.0.0; python_version <= "2.7" and extra == "secure" in c:\python27\lib\site-packages (from urllib3[secure]==1.23->-r requirements.txt (line 8)) (2.7)
Requirement already satisfied: ipaddress; python_version <= "2.7" and extra == "secure" in c:\python27\lib\site-packages (from urllib3[secure]==1.23->-r requirements.txt (line 8)) (1.0.22)
Requirement already satisfied: pyOpenSSL>=0.14; python_version == "2.7" and extra == "secure" in c:\python27\lib\site-packages (from urllib3[secure]==1.23->-r requirements.txt (line 8)) (18.0.0)
Requirement already satisfied: certifi; extra == "secure" in c:\python27\lib\site-packages (from urllib3[secure]==1.23->-r requirements.txt (line 8)) (2018.11.29)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in c:\python27\lib\site-packages (from requests<2.21,>=2.20->-r requirements.txt (line 9)) (3.0.4)
Requirement already satisfied: sortedcontainers in c:\python27\lib\site-packages (from intervaltree<3,>=2->-r requirements.txt (line 10)) (2.1.0)
Requirement already satisfied: fasteners in c:\python27\lib\site-packages (from mbed-ls<1.7,>=1.5.1->-r requirements.txt (line 11)) (0.14.1)
Requirement already satisfied: appdirs>=1.4 in c:\python27\lib\site-packages (from mbed-ls<1.7,>=1.5.1->-r requirements.txt (line 11)) (1.4.3)
Requirement already satisfied: lockfile in c:\python27\lib\site-packages (from mbed-greentea<=1.5,>=0.2.24->-r requirements.txt (line 13)) (0.12.2)
Requirement already satisfied: mock in c:\python27\lib\site-packages (from mbed-greentea<=1.5,>=0.2.24->-r requirements.txt (line 13)) (2.0.0)
Requirement already satisfied: functools32; python_version == "2.7" in c:\python27\lib\site-packages (from jsonschema==2.6.0->-r requirements.txt (line 17)) (3.2.3.post2)
Requirement already satisfied: python-dateutil>=2 in c:\python27\lib\site-packages (from mbed-cloud-sdk==2.0.1->-r requirements.txt (line 21)) (2.7.5)
Requirement already satisfied: python-dotenv>=0.8.2 in c:\python27\lib\site-packages (from mbed-cloud-sdk==2.0.1->-r requirements.txt (line 21)) (0.10.1)
Requirement already satisfied: semver in c:\python27\lib\site-packages (from icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (2.8.1)
Requirement already satisfied: yattag in c:\python27\lib\site-packages (from icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (1.10.1)
Requirement already satisfied: pyshark-legacy in c:\python27\lib\site-packages (from icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (0.3.8)
Requirement already satisfied: mbed-flasher==0.9.* in c:\python27\lib\site-packages (from icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (0.9.2)
Requirement already satisfied: jsonmerge in c:\python27\lib\site-packages (from icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (1.5.2)
Requirement already satisfied: cffi>=1.7; platform_python_implementation != "PyPy" in c:\python27\lib\site-packages (from cryptography>=2.0.0->manifest-tool==1.4.6->-r requirements.txt (line 20)) (1.11.5)
Requirement already satisfied: enum34; python_version < "3" in c:\python27\lib\site-packages (from cryptography>=2.0.0->manifest-tool==1.4.6->-r requirements.txt (line 20)) (1.1.6)
Requirement already satisfied: asn1crypto>=0.21.0 in c:\python27\lib\site-packages (from cryptography>=2.0.0->manifest-tool==1.4.6->-r requirements.txt (line 20)) (0.24.0)
Requirement already satisfied: setuptools in c:\python27\lib\site-packages (from protobuf<3.6.0,>=3.5.0->manifest-tool==1.4.6->-r requirements.txt (line 20)) (40.6.3)
Requirement already satisfied: monotonic>=0.1 in c:\python27\lib\site-packages (from fasteners->mbed-ls<1.7,>=1.5.1->-r requirements.txt (line 11)) (1.5)
Requirement already satisfied: funcsigs>=1; python_version < "3.3" in c:\python27\lib\site-packages (from mock->mbed-greentea<=1.5,>=0.2.24->-r requirements.txt (line 13)) (1.0.2)
Requirement already satisfied: pbr>=0.11 in c:\python27\lib\site-packages (from mock->mbed-greentea<=1.5,>=0.2.24->-r requirements.txt (line 13)) (5.1.1)
Requirement already satisfied: lxml in c:\python27\lib\site-packages (from pyshark-legacy->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (4.2.5)
Requirement already satisfied: py in c:\python27\lib\site-packages (from pyshark-legacy->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (1.7.0)
Requirement already satisfied: trollius==1.0.4 in c:\python27\lib\site-packages (from pyshark-legacy->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (1.0.4)
Requirement already satisfied: logbook in c:\python27\lib\site-packages (from pyshark-legacy->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (1.4.1)
Requirement already satisfied: pyOCD!=0.13.0 in c:\python27\lib\site-packages (from mbed-flasher==0.9.*->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (0.14.3)
Requirement already satisfied: pycparser in c:\python27\lib\site-packages (from cffi>=1.7; platform_python_implementation != "PyPy"->cryptography>=2.0.0->manifest-tool==1.4.6->-r requirements.txt (line 20)) (2.19)
Requirement already satisfied: futures in c:\python27\lib\site-packages (from trollius==1.0.4->pyshark-legacy->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (3.2.0)
Requirement already satisfied: websocket-client in c:\python27\lib\site-packages (from pyOCD!=0.13.0->mbed-flasher==0.9.*->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (0.54.0)
Requirement already satisfied: pyusb>=1.0.0b2 in c:\python27\lib\site-packages (from pyOCD!=0.13.0->mbed-flasher==0.9.*->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (1.0.2)
Requirement already satisfied: pywinusb>=0.4.0 in c:\python27\lib\site-packages (from pyOCD!=0.13.0->mbed-flasher==0.9.*->icetea<1.1,>=1.0.2->-r requirements.txt (line 22)) (0.4.2)
valinor 0.0.15 has requirement pyelftools==0.23, but you'll have pyelftools 0.25 which is incompatible.
Installing collected packages: pyelftools, icetea
  Found existing installation: pyelftools 0.23
    Uninstalling pyelftools-0.23:
      Successfully uninstalled pyelftools-0.23
  Running setup.py install for pyelftools ... done
  Found existing installation: icetea 1.1.0
    Uninstalling icetea-1.1.0:
      Successfully uninstalled icetea-1.1.0
Successfully installed icetea-1.0.2 pyelftools-0.25

Please help me with above issue as I cannot say exactly what is the problem.
Thanks in advance!!

[Mbed-OS 5.9 OOB] RZ_A1H doesn't work with ARM build

Bug

Target
GR-PEACH and GR-LYCHEE

Toolchain:
ARM

Expected behavior
The build binary works on the GR-PEACH/LYCHEE target.

Actual behavior
No LED blinky on the target. No crash log reported.

Steps to reproduce

$ mbed import mbed-os-example-blinky
$ cd mbed-os-example-blinky
$ mbed update mbed-os-5.9.0-oob
$ mbed compile -m RZ_A1H -t ARM

Version hash

mbed-os-example-blinky (#fe1c51632dff, tag: mbed-os-5.9.0-rc1)
`- mbed-os (#6817dc43f9f5, tag: mbed-os-5.9.0-rc1)

Other information

  • Other build (GCC_ARM and IAR) works fine.
  • Last release version (mbed-os-5.8.5 or latest release tag) works fine.
  • Renesas also reported this here

cc @MarceloSalazar

[exporter] DS-5 project could not be generated for RZ_A1H

Testing blinky RC#1
mbed-cli doesn't generate a project for DS-5.

C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky>mbed export -i ds5_5 -m RZ_A1H
Traceback (most recent call last):
  File "C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\tools\project.py", line 145, in <module>
    tmp_path, report = export(project_dir, project_name, ide, mcu, project_dir[0], project_temp, clean=clean, make_zip=zip, extra_symbols=lib_symbols, sources_relative=sources_relative)
  File "C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\tools\export\__init__.py", line 97, in export
    if target not in Exporter.TARGETS or Exporter.TOOLCHAIN not in TARGET_MAP[target].supported_toolchains:
AttributeError: type object 'DS5_5' has no attribute 'TOOLCHAIN'
[mbed] ERROR: "python" returned error code 1.
[mbed] ERROR: Command "python -u C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\tools\project.py -i ds5_5 -m RZ_A1H --source ." in "C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky"

mbed-cli version 0.8.9
progen version 0.9.9
progendef version 0.2.27

cc @0xc0170

Compilation failure with IAR 8 with NUCLEO_F429ZI target

PS C:\Users\vijhar01\mbed-os-example-blinky> mbed detect

[mbed] Detected NUCLEO_F429ZI, port COM6, mounted D:
[mbed] Supported toolchains for NUCLEO_F429ZI
+---------------+-----------+-----------+-----------+-----------+-----------+
| Target | mbed OS 2 | mbed OS 5 | ARM | GCC_ARM | IAR |
+---------------+-----------+-----------+-----------+-----------+-----------+
| NUCLEO_F429ZI | Supported | Supported | Supported | Supported | Supported |
+---------------+-----------+-----------+-----------+-----------+-----------+
Supported targets: 1
Supported toolchains: 3

PS C:\Users\vijhar01\mbed-os-example-blinky> mbed compile -t IAR -m NUCLEO_F429ZI
Building project mbed-os-example-blinky (NUCLEO_F429ZI, IAR)
Scan: .
Scan: mbed
Scan: env
Scan: FEATURE_LWIP
Compile [ 0.2%]: cmain.S
Compile [ 0.5%]: AnalogIn.cpp
Compile [ 0.7%]: BusIn.cpp
Compile [ 1.0%]: BusInOut.cpp
Compile [ 1.2%]: main.cpp
Compile [ 1.5%]: Ethernet.cpp
Compile [ 1.7%]: BusOut.cpp
Compile [ 2.0%]: CAN.cpp
Compile [ 2.2%]: FlashIAP.cpp
Compile [ 2.5%]: I2CSlave.cpp
Compile [ 2.7%]: I2C.cpp
Compile [ 3.0%]: InterruptIn.cpp
Compile [ 3.2%]: InterruptManager.cpp
Compile [ 3.5%]: RawSerial.cpp
Compile [ 3.7%]: SPISlave.cpp
Compile [ 4.0%]: SPI.cpp
Compile [ 4.2%]: Serial.cpp
Compile [ 4.5%]: SerialBase.cpp
Compile [ 4.7%]: Ticker.cpp
Compile [ 5.0%]: Timeout.cpp
Compile [ 5.2%]: TimerEvent.cpp
Compile [ 5.5%]: Timer.cpp
Compile [ 5.7%]: UARTSerial.cpp
Compile [ 6.0%]: equeue.c
Compile [ 6.2%]: EventQueue.cpp
Compile [ 6.5%]: equeue_mbed.cpp
Compile [ 6.7%]: emac_lwip.c
Compile [ 7.0%]: emac_stack_lwip.cpp
Compile [ 7.2%]: equeue_posix.c
Compile [ 7.5%]: stm32f4_eth_conf.c
Compile [ 7.7%]: stm32f4_eth_init.c
Compile [ 8.0%]: lwip_checksum.c
Compile [ 8.2%]: lwip_memcpy.c
Compile [ 8.5%]: EthernetInterface.cpp
Compile [ 8.7%]: stm32xx_emac.c
[Warning] stm32xx_emac.c@98,24: [Pe177]: variable "regvalue" was declared but never referenced
[Warning] stm32xx_emac.c@99,0: [Pe550]: variable "hal_eth_init_status" was set but never used
Compile [ 9.0%]: lwip_random.c
Compile [ 9.2%]: lwip_sys_arch.c
Compile [ 9.5%]: lwip_tcp_isn.c
Compile [ 9.7%]: lwip_api_lib.c
Compile [ 10.0%]: lwip_err.c
Compile [ 10.2%]: lwip_api_msg.c
Compile [ 10.5%]: lwip_netdb.c
Compile [ 10.7%]: lwip_netifapi.c
Compile [ 11.0%]: lwip_netbuf.c
Compile [ 11.2%]: lwip_sockets.c
Compile [ 11.5%]: lwip_autoip.c
Compile [ 11.7%]: lwip_tcpip.c
Compile [ 12.0%]: lwip_icmp.c
Compile [ 12.2%]: lwip_etharp.c
Compile [ 12.5%]: lwip_dhcp.c
Compile [ 12.7%]: lwip_igmp.c
Compile [ 13.0%]: lwip_ip4_addr.c
Compile [ 13.2%]: lwip_ip4.c
Compile [ 13.5%]: lwip_dhcp6.c
Compile [ 13.7%]: lwip_ip4_frag.c
Compile [ 14.0%]: lwip_ethip6.c
Compile [ 14.2%]: lwip_icmp6.c
Compile [ 14.5%]: lwip_inet6.c
Compile [ 14.7%]: lwip_ip6.c
Compile [ 15.0%]: lwip_ip6_addr.c
Compile [ 15.2%]: lwip_mld6.c
Compile [ 15.5%]: lwip_ip6_frag.c
Compile [ 15.7%]: lwip_nd6.c
Compile [ 16.0%]: lwip_def.c
Compile [ 16.2%]: lwip_inet_chksum.c
Compile [ 16.5%]: lwip_dns.c
Compile [ 16.7%]: lwip_ip.c
Compile [ 17.0%]: lwip_init.c
[Warning] lwip_init.c@344,0: [Pe549]: variable "a" is used before its value is set
Compile [ 17.2%]: lwip_mem.c
Compile [ 17.5%]: lwip_memp.c
Compile [ 17.7%]: lwip_raw.c
Compile [ 18.0%]: lwip_netif.c
Compile [ 18.2%]: lwip_pbuf.c
Compile [ 18.5%]: lwip_stats.c
Compile [ 18.7%]: lwip_sys.c
Compile [ 19.0%]: lwip_tcp.c
Compile [ 19.2%]: lwip_tcp_in.c
Compile [ 19.5%]: lwip_timeouts.c
Compile [ 19.7%]: lwip_tcp_out.c
Compile [ 20.0%]: lwip_ethernetif.c
Compile [ 20.2%]: lwip_ethernet.c
Compile [ 20.4%]: lwip_udp.c
Compile [ 20.7%]: lwip_lowpan6.c
Compile [ 20.9%]: lwip_auth.c
Compile [ 21.2%]: lwip_chap-md5.c
Compile [ 21.4%]: lwip_ccp.c
Compile [ 21.7%]: lwip_chap-new.c
Compile [ 21.9%]: lwip_chap_ms.c
Compile [ 22.2%]: lwip_demand.c
Compile [ 22.4%]: lwip_ecp.c
Compile [ 22.7%]: lwip_eap.c
Compile [ 22.9%]: lwip_eui64.c
Compile [ 23.2%]: lwip_fsm.c
Compile [ 23.4%]: lwip_ipcp.c
Compile [ 23.7%]: lwip_ipv6cp.c
Compile [ 23.9%]: lwip_magic.c
Compile [ 24.2%]: lwip_lcp.c
Compile [ 24.4%]: lwip_mppe.c
Compile [ 24.7%]: lwip_multilink.c
Compile [ 24.9%]: lwip_pppapi.c
Compile [ 25.2%]: lwip_ppp.c
Compile [ 25.4%]: lwip_pppcrypt.c
Compile [ 25.7%]: lwip_pppoe.c
Compile [ 25.9%]: lwip_upap.c
Compile [ 26.2%]: lwip_pppol2tp.c
Compile [ 26.4%]: lwip_pppos.c
Compile [ 26.7%]: lwip_utils.c
Compile [ 26.9%]: lwip_vj.c
Compile [ 27.2%]: lwip_arc4.c
Compile [ 27.4%]: lwip_des.c
Compile [ 27.7%]: lwip_md4.c
Compile [ 27.9%]: lwip_md5.c
Compile [ 28.2%]: lwip_sha1.c
Compile [ 28.4%]: ppp_lwip.cpp
Compile [ 28.7%]: Dir.cpp
Compile [ 28.9%]: lwip_stack.c
[Warning] lwip_stack.c@583,18: [Pe174]: expression has no effect
[Warning] lwip_stack.c@609,0: [Pe174]: expression has no effect
Compile [ 29.2%]: File.cpp
Compile [ 29.4%]: FileSystem.cpp
Compile [ 29.7%]: HeapBlockDevice.cpp
Compile [ 29.9%]: ChainingBlockDevice.cpp
Compile [ 30.2%]: MBRBlockDevice.cpp
Compile [ 30.4%]: ccsbcs.cpp
Compile [ 30.7%]: ProfilingBlockDevice.cpp
Compile [ 30.9%]: SlicingBlockDevice.cpp
Compile [ 31.2%]: FATFileSystem.cpp
Compile [ 31.4%]: greentea_serial.cpp
Compile [ 31.7%]: greentea_metrics.cpp
Compile [ 31.9%]: ff.cpp
Compile [ 32.2%]: unity.c
Compile [ 32.4%]: greentea_test_env.cpp
Compile [ 32.7%]: mbed-utest-shim.cpp
Compile [ 32.9%]: unity_handler.cpp
Compile [ 33.2%]: utest_case.cpp
Compile [ 33.4%]: utest_default_handlers.cpp
Compile [ 33.7%]: utest_greentea_handlers.cpp
Compile [ 33.9%]: utest_stack_trace.cpp
Compile [ 34.2%]: mbed_trng.c
Compile [ 34.4%]: utest_harness.cpp
[Warning] utest_harness.cpp@210,0: [Pe111]: statement is unreachable
Compile [ 34.7%]: utest_shim.cpp
Compile [ 34.9%]: aesni.c
Compile [ 35.2%]: arc4.c
Compile [ 35.4%]: utest_types.cpp
Compile [ 35.7%]: asn1parse.c
Compile [ 35.9%]: asn1write.c
Compile [ 36.2%]: base64.c
Compile [ 36.4%]: aes.c
Compile [ 36.7%]: blowfish.c
Compile [ 36.9%]: camellia.c
Compile [ 37.2%]: certs.c
Compile [ 37.4%]: ccm.c
Compile [ 37.7%]: cipher_wrap.c
Compile [ 37.9%]: cipher.c
Compile [ 38.2%]: cmac.c
Compile [ 38.4%]: des.c
Compile [ 38.7%]: dhm.c
Compile [ 38.9%]: ctr_drbg.c
Compile [ 39.2%]: debug.c
Compile [ 39.4%]: ecdh.c
Compile [ 39.7%]: ecjpake.c
Compile [ 39.9%]: ecdsa.c
Compile [ 40.1%]: entropy.c
Compile [ 40.4%]: bignum.c
Compile [ 40.6%]: entropy_poll.c
Compile [ 40.9%]: ecp_curves.c
Compile [ 41.1%]: havege.c
Compile [ 41.4%]: hmac_drbg.c
Compile [ 41.6%]: gcm.c
Compile [ 41.9%]: md2.c
Compile [ 42.1%]: md.c
Compile [ 42.4%]: ecp.c
Compile [ 42.6%]: md4.c
Compile [ 42.9%]: md5.c
Compile [ 43.1%]: md_wrap.c
Compile [ 43.4%]: memory_buffer_alloc.c
Compile [ 43.6%]: net_sockets.c
Compile [ 43.9%]: padlock.c
Compile [ 44.1%]: pem.c
Compile [ 44.4%]: oid.c
Compile [ 44.6%]: pk.c
Compile [ 44.9%]: pkcs11.c
Compile [ 45.1%]: pk_wrap.c
Compile [ 45.4%]: pkcs12.c
Compile [ 45.6%]: pkcs5.c
Compile [ 45.9%]: platform.c
Compile [ 46.1%]: pkwrite.c
Compile [ 46.4%]: error.c
Compile [ 46.6%]: ripemd160.c
Compile [ 46.9%]: pkparse.c
Compile [ 47.1%]: sha1.c
Compile [ 47.4%]: ssl_cache.c
Compile [ 47.6%]: ssl_ciphersuites.c
Compile [ 47.9%]: sha256.c
Compile [ 48.1%]: sha512.c
Compile [ 48.4%]: rsa.c
Compile [ 48.6%]: ssl_cookie.c
Compile [ 48.9%]: ssl_ticket.c
Compile [ 49.1%]: threading.c
Compile [ 49.4%]: timing.c
Compile [ 49.6%]: version.c
Compile [ 49.9%]: version_features.c
Compile [ 50.1%]: ssl_cli.c
Compile [ 50.4%]: x509.c
Compile [ 50.6%]: x509_create.c
Compile [ 50.9%]: ssl_srv.c
[Warning] ssl_srv.c@2689,0: [Pe549]: variable "len" is used before its value is set
Compile [ 51.1%]: x509_crl.c
Compile [ 51.4%]: x509_csr.c
Compile [ 51.6%]: x509write_crt.c
Compile [ 51.9%]: x509write_csr.c
Compile [ 52.1%]: xtea.c
Compile [ 52.4%]: aes_alt.c
Compile [ 52.6%]: md5_alt.c
Compile [ 52.9%]: sha1_alt.c
Compile [ 53.1%]: sha256_alt.c
Compile [ 53.4%]: NetworkInterface.cpp
Compile [ 53.6%]: x509_crt.c
Compile [ 53.9%]: ssl_tls.c
Compile [ 54.1%]: NetworkStack.cpp
Compile [ 54.4%]: Socket.cpp
Compile [ 54.6%]: SocketAddress.cpp
Compile [ 54.9%]: TCPServer.cpp
Compile [ 55.1%]: WiFiAccessPoint.cpp
Compile [ 55.4%]: OnboardCellularInterface.cpp
Compile [ 55.6%]: TCPSocket.cpp
Compile [ 55.9%]: UDPSocket.cpp
Compile [ 56.1%]: mbed_flash_api.c
Compile [ 56.4%]: PPPCellularInterface.cpp
Compile [ 56.6%]: UARTCellularInterface.cpp
Compile [ 56.9%]: nsapi_dns.cpp
Compile [ 57.1%]: mbed_gpio.c
Compile [ 57.4%]: mbed_pinmap_common.c
Compile [ 57.6%]: mbed_lp_ticker_api.c
Compile [ 57.9%]: mbed_ticker_api.c
Compile [ 58.1%]: mbed_us_ticker_api.c
Compile [ 58.4%]: CallChain.cpp
Compile [ 58.6%]: FileBase.cpp
Compile [ 58.9%]: FileHandle.cpp
Compile [ 59.1%]: ATCmdParser.cpp
Compile [ 59.4%]: FilePath.cpp
Compile [ 59.6%]: LocalFileSystem.cpp
Compile [ 59.9%]: FileSystemHandle.cpp
Compile [ 60.1%]: mbed_alloc_wrappers.cpp
Compile [ 60.3%]: Stream.cpp
Compile [ 60.6%]: mbed_application.c
Compile [ 60.8%]: mbed_assert.c
Compile [ 61.1%]: mbed_board.c
Compile [ 61.3%]: mbed_error.c
Compile [ 61.6%]: mbed_critical.c
Compile [ 61.8%]: mbed_mktime.c
Compile [ 62.1%]: mbed_mem_trace.c
Compile [ 62.3%]: mbed_interface.c
Compile [ 62.6%]: mbed_poll.cpp
Compile [ 62.8%]: mbed_sdk_boot.c
Compile [ 63.1%]: mbed_rtc_time.cpp
Compile [ 63.3%]: mbed_retarget.cpp
[Error] mbed_retarget.cpp@850,47: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@850,15: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@851,30: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@851,15: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@852,30: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@852,15: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@865,47: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@865,15: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@866,30: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@866,15: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@867,30: [Pe393]: pointer to incomplete class type is not allowed
[Error] mbed_retarget.cpp@867,0: [Pe393]: pointer to incomplete class type is not allowed
[ERROR]
_file->_Mode = (unsigned short)(_file->_Mode & ~ 0x1000);/* Unset read mode */
^
"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",850 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Mode = (unsigned short)(_file->_Mode & ~ 0x1000);/* Unset read mode */
                                           ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",850 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Rend = _file->_Wend;
           ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",851 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Rend = _file->_Wend;
                          ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",851 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Next = _file->_Wend;
           ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",852 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Next = _file->_Wend;
                          ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",852 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Mode = (unsigned short)(_file->_Mode & ~ 0x1000);/* Unset read mode */
           ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",865 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Mode = (unsigned short)(_file->_Mode & ~ 0x1000);/* Unset read mode */
                                           ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",865 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Rend = _file->_Wend;
           ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",866 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Rend = _file->_Wend;
                          ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",866 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Next = _file->_Wend;
           ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",867 Error[Pe393]: pointer to incomplete c
lass type is not allowed

      _file->_Next = _file->_Wend;
                          ^

"C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\platform\mbed_retarget.cpp",867 Error[Pe393]: pointer to incomplete c
lass type is not allowed

[mbed] ERROR: "C:\Python27\python.exe" returned error code 1.
[mbed] ERROR: Command "C:\Python27\python.exe -u C:\Users\vijhar01\mbed-os-example-blinky\mbed-os\tools\make.py -t IAR -
m NUCLEO_F429ZI --source . --build .\BUILD\NUCLEO_F429ZI\IAR" in "C:\Users\vijhar01\mbed-os-example-blinky"

[OOB 5.5.0] NUCLEO_F767ZI gcc makefile binary not working

Description

  • Type: Bug
  • Priority: Minor

Bug

Target:
NUCLEO_F767ZI

Toolchain:
GCC_ARM

Toolchain version:
6.3.1 20170215

mbed-cli version:
1.1.1

Expected behavior
blinky example should work.

Actual behavior
blinky example did not work (LED1 was not blinking).

Steps to reproduce

$ mbed import mbed-os-example-blinky
$ cd mbed-os-example-blinky
$ mbed update mbed-os-5.5.0-rc1-oob
$ mbed export -m NUCLEO_F767ZI -i make_gcc_arm
$ make
$ copy BUILD/mbed-os-example-blinky.bin f:

Build log file:
build_log.txt

Generated Makefile:
Makefile.zip

Other notes

The binary which build by mbed compile -m NUCLEO_F767ZI -t GCC_ARM, works fine.

mbed compile: path to IAR set to specific version

mbed compile -m RZ_A1H -t IAR

Output:

Building project mbed-os-example-blinky (RZ_A1H, IAR)
Scan: .
Scan: FEATURE_BLE
Scan: FEATURE_UVISOR
Scan: FEATURE_IPV4
Scan: mbed
Scan: env
[ERROR] [Error 2] The system cannot find the file specified
[OS ERROR] Command: C:/Program Files (x86)/IAR Systems/Embedded Workbench 7.3/arm\bin\iccarm --no_wrap_diagnostics -e --diag_suppress=Pa050,Pa084,Pa093,Pa082 --cpu Cortex-A9 --thumb --dlib_config C:/Program Files (x86)/IAR Systems/Embedded Workbench 7.3/arm\inc\c\DLib_Config_Full.h -Oh --c++ --no_rtti --no_exceptions --guard_calls -DTARGET_MBRZA1H -DDEVICE_ERROR_PATTERN=1 -DDEVICE_SPI=1 -D__FPU_PRESENT -D__MBED__=1 -DDEVICE_I2CSLAVE=1 -DTARGET_LIKE_MBED -DDEVICE_PORTINOUT=1 -DDEVICE_PORTIN=1 -DDEVICE_RTC=1 -DTOOLCHAIN_object -D__CMSIS_RTOS -DMBED_BUILD_TIMESTAMP=1469558266.89 -D__EVAL -DFEATURE_IPV4=1 -DTARGET_CORTEX_A -DDEVICE_CAN=1 -DARM_MATH_CA9 -DTARGET_UVISOR_UNSUPPORTED -D__MBED_CMSIS_RTOS_CA9 -DTARGET_LIKE_CORTEX_A9 -DTOOLCHAIN_IAR -DDEVICE_INTERRUPTIN=1 -DDEVICE_I2C=1 -DDEVICE_PORTOUT=1 -DDEVICE_STDIO_MESSAGES=1 -DDEVICE_PWMOUT=1 -DDEVICE_SPI_ASYNCH=1 -DTARGET_RENESAS -DTARGET_RELEASE -DDEVICE_SERIAL_FC=1 -DTARGET_A9 -D__CORTEX_A9 -DTARGET_RZ_A1H -DDEVICE_SERIAL_ASYNCH=1 -DTARGET_FF_ARDUINO -DDEVICE_I2C_ASYNCH=1 -DDEVICE_ETHERNET=1 -DDEVICE_SPISLAVE=1 -DDEVICE_ANALOGIN=1 -DDEVICE_SERIAL=1 -f .\.build\RZ_A1H\IAR\.includes_d631416ea42696208491dba2987cf782.txt --preinclude=.\.build\RZ_A1H\IAR\mbed_config.h --dependencies .\.build\RZ_A1H\IAR\.\main.d -l .\.build\RZ_A1H\IAR\.\main.s.txt -o .\.build\RZ_A1H\IAR\.\main.o .\main.cpp

My path to IAR is C:/Program Files (x86)/IAR Systems/Embedded Workbench 7.2. We can't ask everyone to have 7.3 (7.7 and 7.6 available on website), as I believe that is an old version and hard to find.

Compile problem

Hello
when I compile mbed-os-example-blinky

mbed compile -t GCC_ARM -m NUCLEO_L152RE -c

get error:

usage: make.py [-h] [-m MCU] [-t TOOLCHAIN] [--color] [--cflags CFLAGS]
               [--asmflags ASMFLAGS] [--ldflags LDFLAGS] [-c]
               [--profile PROFILE] [--app-config APP_CONFIG] [-p PROGRAM]
               [-n PROGRAM] [-j JOBS] [-v] [--silent] [-D MACROS]
               [-S [{matrix,toolchains,targets}]] [-f GENERAL_FILTER_REGEX]
               [--stats-depth STATS_DEPTH] [--automated] [--host HOST_TEST]
               [--extra EXTRA] [--peripherals PERIPHERALS]
               [--dep DEPENDENCIES] [--source SOURCE_DIR]
               [--duration DURATION] [--build BUILD_DIR] [-N ARTIFACT_NAME]
               [-d DISK] [-s SERIAL] [-b BAUD] [-L] [--rpc] [--usb] [--dsp]
               [--testlib] [--build-data BUILD_DATA] [-l LINKER_SCRIPT]
make.py: error: Could not find executable for GCC_ARM.
Currently set search path: ~/opt/gcc-arm-none-eabi-6-2017-q2-update/bin/
[mbed] ERROR: "/usr/bin/python" returned error code 2.
[mbed] ERROR: Command "/usr/bin/python -u /home/grega/podatki/seltron/mbed-os-example-blinky/mbed-os/tools/make.py -t GCC_ARM -m K64F --source . --build ./BUILD/K64F/GCC_ARM" in "/home/grega/podatki/seltron/mbed-os-example-blinky"
---

My mbed config --list look like this:

[mbed] Global config:
MBED_GCC_ARM_PATH=~/opt/gcc-arm-none-eabi-6-2017-q2-update/bin/

[mbed] Local config (/home/grega/podatki/seltron/mbed-os-example-blinky):
No local configuration is set

In mbed_settings.py I set:

# GCC ARM
GCC_ARM_PATH = "~/opt/gcc-arm-none-eabi-6-2017-q2-update/bin/"

I tried with new gcc (v7xxx) but I have the same problem.
Where is the problem?

[OOB 5.5.0] REALTEK_RTL8195AM compiles, but fails to flash in uvision

REALTEK_RTL8195AM compiles in uvision, but fails to find the correct target to flash to.

mbed OS: 92fbf2a9b3988d430482fc25a6077f2462e2a634
mbed CLI version: 1.1.1

".\BUILD\mbed-os-example-blinky.axf" - 0 Error(s), 297 Warning(s).
Build Time Elapsed:  00:01:38
Load "C:\\cygwin64\\home\\micray01\\mbed-os\\mbed-os-example-blinky\\BUILD\\mbed-os-example-blinky.axf" 
No Algorithm found for: 10006000H - 1000FFFFH
No Algorithm found for: 10010000H - 10016F83H
Erase skipped!
Error: Flash Download failed  -  "Cortex-M3"
Flash Load finished at 17:34:35

Delay too long on LPC1768 with default GCC profile

When compiling using the default (develop) profile on the mbed cli, the LED toggles every ~5 seconds instead of the desired 0.5 seconds. When building using the debug profile, the program functions as expected. This is using the GCC toolchain.

Can't export to uVision for NUCLEO_F746ZG

When exporting to uVision for NUCLEO_F746ZG, it is reported that the toolchain is not supported:

$ mbed export -m NUCLEO_F746ZG -i uvision

Failed:
  * NUCLEO_F746ZG::uvision
Sorry, the target NUCLEO_F746ZG is not currently supported on the uvision toolchain.
Please refer to <a href='/handbook/Exporting-to-offline-toolchains' target='_blank'>Exporting to offline toolchains</a> for more information.

Exporters not supported for Realtek RTL8195AM

I'm not able to export the blinky project for the Realtek Ameba board.
I'm using Windows10 and I'm getting
C:\Users\geogek01\Documents\mbedCLIproj\mbed-os-example-blinky [mbed-os-5.7.0-oob ≡ +3 ~1 -0 !]> mbed export -i make_iar -m realtek_rtl8195am usage: project.py [-h] [-m MCU] [-i IDE] [-c] [-p PROGRAM] [-n PROGRAM] [-b] [-L] [-S [{matrix,ides}]] [-E] [--source SOURCE_DIR] [-D MACROS] [--profile PROFILE] [--update-packs] [--app-config APP_CONFIG] project.py: error: REALTEK_RTL8195AM not supported by make_iar

I am getting the same error message for make_armc5 and for make_gcc_arm

I'm using mbed-cli 1.1.1

Can you also take a look into this issue please?

Thanks,
George

mbed-os.lib not pointing to mbed 5.6.0 release candidate in branch mbed-os-5.6.0-oob

It appears mbed-os.lib is not pointing to the correct commit number that is tagged as the mbed OS 5.6.0 release candidate in the branch mbed-os-5.6.0-oob. This is causing the CLI and mbed-ls tools to believe it has checked out the correct branch when running mbed update mbed-os-5.6.0-oob but the underlying mbed-os folder is still reporting as being checked out to mbed-os-5.5.0.

For example, when checking out the mbed-os-5.6.0-oob branch:

C:\Users\davwal04\Desktop\Out of box campaigns\mbed OS 5.6\mbed-os-example-blinky>mbed update mbed-os-5.6.0-oob
[mbed] Updating program "mbed-os-example-blinky" to branch mbed-os-5.6.0-oob
[mbed] Updating library "mbed-os" to rev #afffea9a848b
fatal: reference is not a tree: afffea9a848b443796d952cb406206f1a6f8d257
[mbed] ERROR: Unable to update "mbed-os" to rev #afffea9a848b

When looking inside the mbed-os-example-blinky folder:

C:\Users\davwal04\Desktop\Out of box campaigns\mbed OS 5.6\mbed-os-example-blinky>git status
On branch mbed-os-5.6.0-oob
Your branch is up-to-date with 'origin/mbed-os-5.6.0-oob'.
nothing to commit, working tree clean

but when you look into the underlying mbed-os folder:

C:\Users\davwal04\Desktop\Out of box campaigns\mbed OS 5.6\mbed-os-example-blinky>cd mbed-os
C:\Users\davwal04\Desktop\Out of box campaigns\mbed OS 5.6\mbed-os-example-blinky\mbed-os>git status
On branch mbed-os-5.5
Your branch is up-to-date with 'origin/mbed-os-5.5'.
nothing to commit, working tree clean

The correct commit that mbed-os.lib should be pointing to is:
+https://github.com/ARMmbed/mbed-os/#a4056fb8bf3ee10b8e037d332f8fbd0c68169ef1

Please reference PR: 6f8c4e6

Compile main.cpp failed as an test case for (K64F, GCC_ARM)

I need a blinky test case without greentea, so create a new case "mbed-os/TESTS/integration/blinky", and copy mbed-os-example-blinky/main.cpp to mbed-os-example-blinky/mbed-os/TESTS/integration/blinky/main.cpp, then compile this case, get error:

...
Compile: main.cpp
[Error] main.cpp@10,9: 'Thread' has not been declared

After adding this:

#include "rtos.h"

no error exists.

Q:
Same file "main.cpp", different compiling methods get different results:

  • Example "blinky" [no error]
    • file: mbed-os-example-blinky/main.cpp
    • cmd:
mbed compile -t GCC_ARM -m K64F --source ./
  • Test case "blinky" [error]
    • file: mbed-os-example-blinky/mbed-os/TESTS/integration/blinky/main.cpp
    • cmd:
$ mbed test -t GCC_ARM -m K64F --compile  --source ./mbed-os -n TESTS-integration-blinky

@sg- modified main.cpp at reversion ef00724, removed #include "rtos.h". That's ok for example, but as a test case, rtos.h has to be included. Anyone knows what happened?

Export fails when passing `-c`

#description

I imported this example in my environment
mbed import mbed-os-example-blinky

Compiled ok:
mbed compile -t IAR -m NUCLEO_L476RG

Trying export fails:

$ mbed export -i IAR -m NUCLEO_L476RG  -c -vv
Traceback (most recent call last):
  File "C:\Data\Workspace\mbed-os-example-blinky\mbed-os\tools\project.py", line 256, in <module>
    main()
  File "C:\Data\Workspace\mbed-os-example-blinky\mbed-os\tools\project.py", line 248, in main
    rmtree(BUILD_DIR)
  File "c:\python27\lib\shutil.py", line 239, in rmtree
    onerror(os.listdir, path, sys.exc_info())
  File "c:\python27\lib\shutil.py", line 237, in rmtree
    names = os.listdir(path)
WindowsError: [Error 3] The system cannot find the path specified: 'C:\\Data\\Workspace\\mbed-os-example-blinky\\mbed-os\\BUILD/*.*'
[mbed] Working path "C:\Data\Workspace\mbed-os-example-blinky" (program)
[mbed] Exec "c:\python27\python.exe -u C:\Data\Workspace\mbed-os-example-blinky\mbed-os\tools\project.py -i iar -m NUCLEO_L476RG -c --source ." in C:\Data\Workspace\mbed-os-example-blinky
[mbed] ERROR: "c:\python27\python.exe" returned error code 1.
[mbed] ERROR: Command "c:\python27\python.exe -u C:\Data\Workspace\mbed-os-example-blinky\mbed-os\tools\project.py -i iar -m NUCLEO_L476RG -c --source ." in "C:\Data\Workspace\mbed-os-example-blinky"
---

Windows OS, with MINGW64

[exporter] Exported EWARM project failed for K22F build

Exported EWARM project failed for K22F build.

$ mbed export -i IAR -m K22F

Building configuration: Unnamed_Project - Unnamed_Project 
Updating build tree... 
cmain.S 
HAL_CM4.S 
Error[438]: This instruction is not available in the selected cpu/core C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 192 
Error[438]: This instruction is not available in the selected cpu/core C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 213 
Error[438]: This instruction is not available in the selected cpu/core C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 278 
Error[438]: This instruction is not available in the selected cpu/core C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 298 
Error[50]: Undefined symbol:'S16' C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 192 
Error[50]: Undefined symbol:'S31' C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 192 
Warning[408]: Not recommended operand syntax. Duplicate the first register operand, or select option -j (alternative syntax). C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 92 
Warning[408]: Not recommended operand syntax. Duplicate the first register operand, or select option -j (alternative syntax). C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 110 
Warning[408]: Not recommended operand syntax. Duplicate the first register operand, or select option -j (alternative syntax). C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 114 
Warning[408]: Not recommended operand syntax. Duplicate the first register operand, or select option -j (alternative syntax). C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 131 
Warning[408]: Not recommended operand syntax. Duplicate the first register operand, or select option -j (alternative syntax). C:\Users\toywat01\Documents\GitHub\mbed-os-example-blinky\mbed-os\rtos\rtx\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_IAR\HAL_CM4.S 135 
Error while running Assembler 
startup_MK22F12.S 
SVC_Table.S 

(snip)

Total number of errors: 6 
Total number of warnings: 15 

My EWARM version is 7.70.1

Can't Compile Blinky with ARMCC

Building project mbed-os-example-blinky (K64F, ARM)
Scan: .
Scan: FEATURE_COMMON_PAL
Scan: FEATURE_UVISOR
Scan: FEATURE_BLE
Scan: FEATURE_CLIENT
Scan: FEATURE_IPV6
Scan: FEATURE_IPV4
Scan: FEATURE_STORAGE
Scan: mbed
Scan: env
Compile: main.cpp
[Error] Thread.h@59,0: #1209: invalid argument to attribute "deprecated"
[Error] Thread.h@84,0: #1209: invalid argument to attribute "deprecated"
[Error] Thread.h@110,0: #1209: invalid argument to attribute "deprecated"
[Error] Thread.h@135,0: #1209: invalid argument to attribute "deprecated"
[Error] RtosTimer.h@47,0: #1209: invalid argument to attribute "deprecated"
[Error] FunctionPointer.h@32,0: #1209: invalid argument to attribute "deprecated"
[Error] FunctionPointer.h@37,0: #1209: invalid argument to attribute "deprecated"
[Error] FunctionPointer.h@49,0: #1209: invalid argument to attribute "deprecated"
[Error] FunctionPointer.h@54,0: #1209: invalid argument to attribute "deprecated"
[ERROR] "./mbed-os/rtos/rtos/Thread.h", line 59: Error: #1209: invalid argument to attribute "deprecated"
"./mbed-os/rtos/rtos/Thread.h", line 84: Error: #1209: invalid argument to attribute "deprecated"
"./mbed-os/rtos/rtos/Thread.h", line 110: Error: #1209: invalid argument to attribute "deprecated"
"./mbed-os/rtos/rtos/Thread.h", line 135: Error: #1209: invalid argument to attribute "deprecated"
"./mbed-os/rtos/rtos/RtosTimer.h", line 47: Error: #1209: invalid argument to attribute "deprecated"
"./mbed-os/hal/api/FunctionPointer.h", line 32: Error: #1209: invalid argument to attribute "deprecated"
"./mbed-os/hal/api/FunctionPointer.h", line 37: Error: #1209: invalid argument to attribute "deprecated"
"./mbed-os/hal/api/FunctionPointer.h", line 49: Error: #1209: invalid argument to attribute "deprecated"
"./mbed-os/hal/api/FunctionPointer.h", line 54: Error: #1209: invalid argument to attribute "deprecated"
./main.cpp: 0 warnings, 9 errors

[mbed] ERROR: "python" returned error code 1.
[mbed] ERROR: Command "python -u /home/hasnain/Repos/mbed-os-example-blinky/mbed-os/tools/make.py -t ARM -m K64F --source . --build ./.build/K64F/ARM" in "/home/hasnain/Repos/mbed-os-example-blinky"

Blinky example should print something

As there are multiple boards that do not actually have an user controllable LED, those should just print "Blink!" or something - or actually all boards could print something, say every 10 times it's blinked the (imaginary) LED.

[exporter] uvision5 project could not be generated for K22F

Testing blinky RC#1
mbed-cli doesn't generate an uvision5 project for K22F.

$ mbed export -i uvision5 -m K22F

Failed:
  * K22F::uvision5
Sorry, the target K22F is not currently supported on the uvision5 toolchain.
Please refer to <a href='/handbook/Exporting-to-offline-toolchains' target='_blank'>Exporting to offline toolchains</a> for more information.

mbed-cli version 0.8.9
progen version 0.9.9
progendef version 0.2.27

cc @0xc0170

Export "not supported" even though it is in matrix

Hi

When I try to run command:
mbed export -i vscode_gcc_arm -m DISCO_F769NI --profile ..\mbed-os\tools\profiles\debug.json
I get:
"project.py: error: DISCO_F769NI not supported by vscode_gcc_arm"
even though the supported boards matrix says it should be supported.

/Anders

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.