still not there, but one step further:
../newt target show
targets/my_blinky_sim
app=apps/blinky
bsp=@apache-mynewt-core/hw/bsp/native
build_profile=debug
../newt run my_blinky_sim
No download script for BSP hw/bsp/native
Debugging
Hi David,
On Sat, May 28, 2016 at 06:05:10PM -0700, David Moshal wrote:
> how do I find the name of the target?
newt target show
e.g.,
[ccollins@iori:~/tmp/newttest]$ newt target show
targets/blink_nordic
app=apps/blinky
bsp=@apache-mynewt-core/hw/bsp/nrf52pdk
Newt target show. In your case it's my_blinky_sim. I can tell because it's in
the path to the elf file-- every target's build is put in a separate directory.
Sterling
> On May 28, 2016, at 6:05 PM, David Moshal wrote:
>
> how do I find the name of the target?
> Dave
>
agreed
David
On Sat, May 28, 2016 at 3:54 PM, Sterling Hughes
wrote:
> I agree - it should just default to 0 imo. When I run on real targets I
> usually just provide 0.0.0.
>
> Failing a default, it should work consistently and display an error when you
>
```
⇒ ../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
I agree - it should just default to 0 imo. When I run on real targets I
usually just provide 0.0.0.
Failing a default, it should work consistently and display an error when you
don't provide a version.
Sterling
> On May 28, 2016, at 3:48 PM, Christopher Collins
On Sat, May 28, 2016 at 01:38:48PM -0700, Sterling Hughes wrote:
> $ newt run
>
> 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
I think you want newt run blinky
Blinky is the target. newt knows how to find it.
dg
> On May 28, 2016, at 4:46 PM, David Moshal wrote:
>
> sorry, my question could have been clearer, what's the path and target
> name for your 'Create First Project' project?
>
>
sorry, my question could have been clearer, what's the path and target
name for your 'Create First Project' project?
http://mynewt.apache.org/os/get_started/project_create/
I tried:
```
../newt run ./bin/my_blinky_sim/apps/blinky/blinky.elf
Error: Invalid target name:
$ newt run
Will do this for you. No need to call binary directly.
Newt run also will upload targets to the host device for you, when you connect
one.
Not sure about the mapping, I'll let Todd and Chris chime in.
Sterling
> On May 28, 2016, at 1:26 PM, David Moshal
ok, so Docker knowledge is a pre-requisite, has been ages since I last
used Docker.
what's the host directory mapped to?
Dave
On Sat, May 28, 2016 at 1:18 PM, Sterling Hughes
wrote:
> Newt run target name will run it in the container-- when using docker the
Newt run target name will run it in the container-- when using docker the sim
binary is compiled under Linux to run on Linux.
Sterling
(Thumb typing)
> On May 28, 2016, at 1:07 PM, David Moshal wrote:
>
> Not sure if this is the best place to put this, I managed to get
>
On 28 May 2016, at 10:38, aditi hilbert wrote:
I think John D. Ament raised some good points.
* Nothing in our binaries say Mynewt - do we need to by Apache rules?
* Our repos already include mynewt - so we should be fine there.
* the package "apache-newt" lacks a NOTICE/LICENSE file
* our
Hello all,
This thread is for any and all discussion regarding the release of
apache-mynewt-0.9.0-incubating-rc2. All feedback is welcome.
Thanks,
Chris
14 matches
Mail list logo