$ newt run my_blinky_sim
Just the name of the target, don’t provide the binary path. All of
the commands run based on the name of the target.
We’ll update the documentation here:
http://mynewt.apache.org/os/get_started/project_create/
to use newt run. It was written prior to the Docker image being
supported, and works with the native toolset.
Newt run is documented here:
http://mynewt.apache.org/newt/command_list/newt_run/, albeit it should
probably have better documentation for simulated targets.
Sterling
On 28 May 2016, at 16:18, David Moshal wrote:
```
⇒ ../newt run ./bin/my_blinky_sim/apps/blinky/blinky 0
Error: Invalid target name: ./bin/my_blinky_sim/apps/blinky/blinky
```
Undocumented cryptic commands required for 'getting started' project ?
Not good, and doesn't inspire newbies to donate their time to the
project, just saying.
For reference: it took me 5 mins from zero to blinky light on the mBed
platform, which seems like a reasonable alternative to MyNewt, best as
I can tell, so there's room for improvement if you want to grow the
platform.
David
On Sat, May 28, 2016 at 3:48 PM, Christopher Collins
<[email protected]> wrote:
On Sat, May 28, 2016 at 01:38:48PM -0700, Sterling Hughes wrote:
$ newt run <target-name>
Will do this for you. No need to call binary directly.
If you are building for real hardware (i.e., not sim), then you need
to
add a version number to the end of the command. So, the command
would
look something like this:
newt run myblinky 0
If you leave off the 0, you will get a cryptic and intimidating error
message.
I was thinking we might want to make the version number optional.
When
people use the run command, most of the time they probably don't care
what version number the produced image has.
Chris
