Yotta install on windows

I have a working install in Windows but have a problem with:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd C:\FreeScale\mbedos\blinky

C:\FreeScale\mbedos\blinky>yotta search blinky
blinky 0.0.0:
Having fun and blinking leds
blinky
mcoenen
example-mbedos-blinky 0.0.0:
simple example program to blink an LED on an mbed board with mbed OS
blinky, mbed OS, getting started
mbedAustin
example-mbedos-ws2812-rgb 0.0.3:
Example software for controlling a WS2812 RGB LED array via network
blinky, ws2812, mbed OS, mbed, mbed-official
Milosch Meriac milosch.meriac@arm.com

C:\FreeScale\mbedos\blinky>yotta install blinky
info: get versions for win
error: could not install target win at for win
error: win does not exist in the targets registry. Check that the name is
correct, and that it has been published.

C:\FreeScale\mbedos\blinky>

The search functions ok but the install fails. Your help would be appreciated.

@kg1 what are you trying to achieve? You haven’t set the target (check yotta Documentation - Using Targets to Compile for Different Platforms ).

Looking at yotta install command help -

Add a specific module as a dependency, and download it, or install all dependencies for the current module.

It fetches the dependencies (=target dependencies) for win target. win does not exist yet as yotta target. Please set the target first, something like frdm-k64f-gcc.

@Kojto
Thank you Kojto. If I understand you correctly yotta install is used to add dependences not to establish an example project. Hence I when directly to:

https://github.com/ARMmbed/example-mbedos-blinky

C:\FreeScale\mbedos> git clone https://github.com/ARMmbed/example-mbedos-blinky.git
Cloning into ‘example-mbedos-blinky’…
remote: Counting objects: 75, done.
emote: Total 75 (delta 0), reused 0 (delta 0), pack-reused 75
Unpacking objects: 100% (75/75), done.
Checking connectivity… done.
C:\FreeScale\mbedos> cd example-mbedos-blinky
C:\FreeScale\mbedos\example-mbedos-blinky [master]> dir

Directory: C:\FreeScale\mbedos\example-mbedos-blinky

Mode LastWriteTime Length Name


d---- 5/01/2016 2:29 p.m. source
-a— 5/01/2016 2:29 p.m. 140 .gitignore
-a— 5/01/2016 2:29 p.m. 11560 LICENSE
-a— 5/01/2016 2:29 p.m. 581 module.json
-a— 5/01/2016 2:29 p.m. 3090 README.md

C:\FreeScale\mbedos\example-mbedos-blinky [master]> yotta init
info: The current directory already a contains a module: existing description

will be modified
Enter the module name:
Enter the initial version: <1.0.0>
Is this an executable (instead of a re-usable library module)?
Short description: <simple example program to blink an LED on an mbed board

with mbed OS>
Author: kg1
C:\FreeScale\mbedos\example-mbedos-blinky [master +0 ~1 -0]> yotta target

frdm-k64f-gcc
info: get versions for frdm-k64f-gcc
info: download frdm-k64f-gcc@2.0.0 from the public module registry
info: get versions for kinetis-k64-gcc
info: download kinetis-k64-gcc@2.0.0 from the public module registry
info: get versions for mbed-gcc
info: download mbed-gcc@1.1.0 from the public module registry
C:\FreeScale\mbedos\example-mbedos-blinky [master +0 ~1 -0]> yotta build
info: get versions for mbed-drivers
info: download mbed-drivers@0.11.6 from the public module registry
info: get versions for mbed-hal
info: download mbed-hal@1.2.0 from the public module registry
info: get versions for cmsis-core
info: download cmsis-core@1.1.0 from the public module registry
info: get versions for ualloc
info: download ualloc@1.0.3 from the public module registry
info: get versions for minar
info: download minar@1.0.1 from the public module registry
info: get versions for core-util
info: download core-util@1.0.1 from the public module registry
info: get versions for compiler-polyfill
info: download compiler-polyfill@1.2.1 from the public module registry
info: get versions for mbed-hal-freescale
info: download mbed-hal-freescale@1.0.0 from the public module registry
info: get versions for mbed-hal-ksdk-mcu
info: download mbed-hal-ksdk-mcu@1.0.6 from the public module registry
info: get versions for uvisor-lib
info: download uvisor-lib@1.0.11 from the public module registry
info: get versions for mbed-hal-k64f
info: download mbed-hal-k64f@1.0.1 from the public module registry
info: get versions for cmsis-core-freescale
info: download cmsis-core-freescale@1.0.0 from the public module registry
info: get versions for cmsis-core-k64f
info: download cmsis-core-k64f@1.0.0 from the public module registry
info: get versions for mbed-hal-frdm-k64f
info: download mbed-hal-frdm-k64f@1.0.0 from the public module registry
info: get versions for dlmalloc
info: download dlmalloc@1.0.0 from the public module registry
info: get versions for minar-platform
info: download minar-platform@1.0.0 from the public module registry
info: get versions for minar-platform-mbed
info: download minar-platform-mbed@1.0.0 from the public module registry
info: generate for target: frdm-k64f-gcc 2.0.0 at C:\FreeScale\mbedos

\example-mbedos-blinky\yotta_targets\frdm-k64f-gcc
GCC version is: 5.2.1
– The ASM compiler identification is GNU
– Found assembler: C:/Program Files (x86)/GNU Tools ARM Embedded/5.2

2015q4/bin/arm-none-eabi-gcc.exe
– Configuring done
– Generating done
– Build files have been written to: C:/FreeScale/mbedos/example-mbedos-

blinky/build/frdm-k64f-gcc
[130/130] Linking CXX executable source/example-mbedos-blinky
C:\FreeScale\mbedos\example-mbedos-blinky [master +0 ~1 -0]> dir

Directory: C:\FreeScale\mbedos\example-mbedos-blinky

Mode LastWriteTime Length Name


d---- 5/01/2016 2:38 p.m. build
d---- 5/01/2016 2:29 p.m. source
d---- 5/01/2016 2:33 p.m. test
d---- 5/01/2016 2:38 p.m. yotta_modules
d---- 5/01/2016 2:35 p.m. yotta_targets
-a— 5/01/2016 2:29 p.m. 140 .gitignore
-a— 5/01/2016 2:35 p.m. 58 .yotta.json
-a— 5/01/2016 2:29 p.m. 11560 LICENSE
-a— 5/01/2016 2:33 p.m. 594 module.json
-a— 5/01/2016 2:29 p.m. 3090 README.md

C:\FreeScale\mbedos\example-mbedos-blinky [master +0 ~1 -0]> cd C:\FreeScale

\mbedos\example-mbedos-blinky\build\frdm-k64
f-gcc\source
C:\FreeScale\mbedos\example-mbedos-blinky\build\frdm-k64f-gcc\source [master

+0 ~1 -0]> dir

Directory: C:\FreeScale\mbedos\example-mbedos-blinky\build\frdm-k64f-gcc

\source

Mode LastWriteTime Length Name


d---- 5/01/2016 2:38 p.m. CMakeFiles
-a— 5/01/2016 2:38 p.m. 883 CMakeLists.txt
-a— 5/01/2016 2:38 p.m. 961 cmake_install.cmake
-a— 5/01/2016 2:38 p.m. 355 CTestTestfile.cmake
-a— 5/01/2016 2:38 p.m. 685760 example-mbedos-blinky
-a— 5/01/2016 2:38 p.m. 37352 example-mbedos-blinky.bin
-a— 5/01/2016 2:38 p.m. 333729 example-mbedos-blinky.map

yotta init is for creating a new yotta module. When you clone already existing yotta module (=app in this case), set your target, build, then use either yt debug (pyocd gdb or uvision currently supported there), or use provided binary in the build/‘your_target_name’/source/‘example_name’.bin/.hex

The shared output with dir is not much readable, please use code highlighter if needed to share cmd line output.

@kojto Thank you for your reply. Please guide me to the editing tips for this forum. The document for “Running your first mbed OS application” has been updated since I read it. I apologise for any misunderstanding on my part.

Try these two videos, they should help clear up how to use yotta: