> On Jan 31, 2017, at 11:44 AM, Neilh <[email protected]> wrote: > > Hello Marko > > Thanks for the tips. > > That's great that it loads directly through the "SDA USB" - worth documenting > as its simple and straightforward like on https://developer.mbed.org/ > > When I plug in FRDM-K64F I get a window pop up with the version and then > > $ lsusb -d0d28: -v > > shows three interface descriptors. > > > #newt load boot-kinetis- doesn't work but using details, can program ot > > $/usr/local/bin/pyocd-flashtool -se --address 0 > bin/targets/boot_kinetis/app/apps/boot/boot.elf.bin > > > $newt run blinky - > > Loading app image into slot 1 > Error: Downloading /workspace/bin/targets/blinky/app/apps/blinky/blinky.img > to 0x8000 > /workspace/repos/apache-mynewt-core/hw/bsp/frdm-k64f/frdm-k64_download.sh: > 41: > /workspace/repos/apache-mynewt-core/hw/bsp/frdm-k64f/frdm-k64_download.sh: > /usr/local/bin/pyocd-flashtool: not found > > > # doesn't work and no blinky.img - should there be a blinky.img ? am I > missing a step? > > /usr/local/bin/pyocd-flashtool -se --address 0x8000 > bin/targets/blinky/app/apps/blinky/blinky.elf.bin >
Do the following: newt build blinky newt create-image blinky 1.2.3.4 /usr/local/bin/pyocd-flashtool -se —address 0x8000 bin/targets/blinky/app/apps/blinky.img bin Note create-image step (creates .img file) and the ‘bin’ argument to pyocd-flashtool.
