Try running pyocd-flashtool manually with the arguments newt would pass to it. If that works, then at least you have the jtag communications working ok. Or just try changing the download script to use absolute path.
Obviously the shell running trying to execute pyocd-flashtool does not have the /usr/local/bin in it’s path. I’m not sure where it picks it’s environment variables from. I’m a bit surprised that /usr/local/bin is not in the path, as that’s where I’d expect openocd to be at (i.e. for other boards). > On Jan 26, 2017, at 6:19 PM, Neilh <neil...@biomonitors.com> wrote: > > Thanks for the tips. > > I had followed the docker install and then olimex instructions and subsituted > _kinetis > > So I have the FRDM-K64F connected with a multlink JTAG/USB/Ubuntu, and the > J11 cut for SWD operation > I also found i needed to add > > sudo -Hpip install --pre -U pyocd > > which added > > /usr/local/bin/pyocd-flashtool > /usr/local/bin/pyocd-gdbserver > /usr/local/bin/pyocd-tool > /usr/local/lib/python2.7/dist-packages/pyOCD > > > > [~/dkr/myproj]$ newt load boot_kinetis > > Loading bootloader > Error: Downloading > /workspace/bin/targets/boot_kinetis/app/apps/boot/boot.elf.bin to 0x0 > /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:pyocd-flashtool: > not found > > But I have pyocd-flashtool > > [~/dkr/myproj]$ whereis pyocd-flashtool > pyocd-flashtool: /usr/local/bin/pyocd-flashtool > > Any suggestions? is this a docker issue? > thanks > > > Neil Hancock > > On 1/26/2017 9:32 AM, Christopher Collins wrote: >> Sorry, there's something else I forgot to mention. You'll need to put >> the boot loader on your board as well. You can do this before or after >> uploading blinky. >> >> newt target create boot-frdm-k64f && >> newt target set boot-frdm-k64f app=@apache-mynewt-core/apps/boot \ >> bsp=@apache-mynewt-core/hw/bsp/frdm-k64f \ >> build_profile=optimized >> >> Then build and upload the boot loader to your board: >> >> newt build boot-frdm-k64f >> newt load boot-frdm-k64f >> >> Chris >> >> >> On Thu, Jan 26, 2017 at 09:14:02AM -0800, Christopher Collins wrote: >>> To start with, I would create a blinky-frdm-k64f target: >>> >>> newt target copy my_blinky_sim blinky-frdm-k64f >>> >>> Then configure your new target to use the frdm-k64f BSP: >>> >>> newt target set blinky-frdm-k64f >>> bsp=@apache-mynewt-core/hw/bsp/frdm-k64f >>> >>> Plug your board in and attach a debugger if necessary, and try running >>> blinky on your board: >>> >>> newt run blinky-frdm-k64f >>> >>> If everything works, a gdb window will come up. Type c <enter>, and >>> check if your board's LED is blinking. >>> >>> After you have blinky working on your board, you might want to try one >>> of these other sample apps: >>> slinky: Includes shell over UART and newtmgr over shell. >>> bleprph: Includes BLE stack and newtmgr over BLE. >>> >>> Thanks, >>> Chris >>> >>>> Alternatively, I could familiarize myself work through the Olimex-E407 >>>> >>>> My environment so far has been IDE Freescale Kinetis Design >>>> Studio/Eclipse building nuttx OS, and with integration to Multilink JTAG >>>> for blowing the flash. >>>> >>>> There was a new feature request for an Eclipse plugin for myNewt, but it >>>> was marked as dup, and I haven't seen any other mention of Eclipse IDE so >>>> far. >>>> >>>> Any recommendation on getting started with FRDM-K64F? or should I >>>> start with Olimex >>>> >>>> thanks >>>> >>>> >>>> -- >>>> Neil Hancock >>>> >>>> >>>> >> >
