Hi Neil, These download/debug scripts are board-specific (aka BSP specific), so for a custom board you can have versions which use the multilink software to do their thing. The versions checked in to mynewt repository are all done as shell scripts, which get their parameters passed in as environment variables. So you can check what the current scripts do (e.g. read frdm-k64_download.sh), and then do the same; assuming multilink comes with some command line tools also.
But, should you still want to use the KinetisStudio, it should be easy to add build rule for your project which invokes newt to do the build (newt build, newt create-image), and then uses the KinetisStudio to do the download, and subsequent debug session. Hope this helps, M > On Jan 31, 2017, at 12:10 PM, Neilh <[email protected]> wrote: > > Marko: > > YES - that worked with slight modification - flashing RED tri-coloured led. > [~/dkr/myproj]$ /usr/local/bin/pyocd-flashtool -se --address 0x8000 > bin/targets/blinky/app/apps/blinky/blinky.img bin > > So next question - sorry - > for accessing a custom board with PE Microsystems Multlink is that possible. > The "SDA USB" port device is a PE software - so not sure what the standards > are > here. > regards > > Neil Hancock > > On 1/31/2017 11:52 AM, marko kiiskila wrote: >>> 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. >> >> >> >> >
