Good day everyone!
I'm owning STM32F446RE Nucleo board and have OSX Yosemite installed on my Mac. I've installed mbed-cli, setted up toolchain (GCC ARM), cloned blinky example and tried to detect target for compilation. Unfortunately it fails :(
$ mbed target
[mbed] detect
$ mbed detect
[mbed] No mbed targets were detected on your system.
$ mbed compile
[mbed] ERROR: No targets were detected.
[mbed] ERROR: Please make sure a target board is connected to this system.
-
Target board is connected (jumper conf is ok), firmware is upgraded (did it on my other Windows PC, now its: Version: 0221, Build: Jun 23 2017 17:43:45), mass storage is presented in system. Also dropping/moving_in_bash of bin files from online compiler works fine (although it popups "Disk not ejected properly, eject NODE_F446RE before disconnecting or turning it off" after burning process and LD1 became green).
What's wrong happened and how can I fix it?
Good day everyone!
I'm owning STM32F446RE Nucleo board and have OSX Yosemite installed on my Mac. I've installed mbed-cli, setted up toolchain (GCC ARM), cloned blinky example and tried to detect target for compilation. Unfortunately it fails :(
$ mbed target [mbed] detect
$ mbed detect [mbed] No mbed targets were detected on your system.
$ mbed compile [mbed] ERROR: No targets were detected. [mbed] ERROR: Please make sure a target board is connected to this system.
-Target board is connected (jumper conf is ok), firmware is upgraded (did it on my other Windows PC, now its: Version: 0221, Build: Jun 23 2017 17:43:45), mass storage is presented in system. Also dropping/moving_in_bash of bin files from online compiler works fine (although it popups "Disk not ejected properly, eject NODE_F446RE before disconnecting or turning it off" after burning process and LD1 became green).
What's wrong happened and how can I fix it?