Re: newNewt

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

Re: newNewt

> On Jan 31, 2017, at 11:44 AM, Neilh 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

Re: newNewt

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

Re: newNewt

Thanks. I'm trying to understand the way it works including docker. There seems to be some comment on the internet that docker gets in the way, only supports one process, (so anything spawning a process isn't going to work ?) - so I started down that route as it seems to be the easiest way

Re: newNewt

Hello Marko Thanks for the suggestion. I was surprised as well, which is why I thought I'd send it out. Still doesn't work with the hardcoded address via newt: [~/dkr/myproj]$ newt load boot_kinetis Loading bootloader Error: Downloading

Re: newNewt

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

Re: newNewt

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\

Re: newNewt

On Thu, Jan 26, 2017 at 09:14:02AM -0800, Christopher Collins wrote: > Plug your board in and attach a debugger if necessary, and try running > blinky on your board: > > newt run blinky-frdm-k64f That should be: newt run blinky-frdm-k64f 0 (append a zero!) Chris

Re: newNewt

Hi Neil, Sounds like a fun project! I’ll let Marko or the Linaro folks chime in on the K64F, however, I wanted to point to the excellent article the code coup guys wrote on running Mynewt with Eclipse: https://www.codecoup.pl/blog/hacking-mynewt-in-eclipse/ Sterling On 25 Jan 2017, at

newNewt

Hi I'm liking the myNewt direction and thanks for the explanations, wiki and videos. I've got a Nxp/Freescale Kinetis custom board with a MK26 (flash1M/ram200k 2*otg) KinetisK that is similar to MK64F on FRDM-MK64F I have a FRDM-MK64F board and also an olimex-H407 (same processor as