Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[David Moshal]

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 /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf
GNU gdb (Ubuntu 7.10-1ubuntu2) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
---Type  to continue, or q  to quit---


Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf...done.
(gdb)




On Sat, May 28, 2016 at 6:18 PM, Sterling Hughes
 wrote:
> 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
>>
>>
>>> On Sat, May 28, 2016 at 4:46 PM, Sterling Hughes  
>>> wrote:
>>> $ 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
  wrote:
>
>> 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 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

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[Christopher Collins]

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
build_profile=debug
targets/my_blinky_sim
app=apps/blinky
bsp=@apache-mynewt-core/hw/bsp/native
build_profile=debug
targets/nrf52_boot
app=@apache-mynewt-core/apps/boot
bsp=@apache-mynewt-core/hw/bsp/nrf52pdk
build_profile=optimized

The "targets/" prefix is optional.  To run the my_blinky_sim target, I
would execute the following command:

newt run my_blinky_sim

Chris

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[Sterling Hughes]

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
> 
> 
>> On Sat, May 28, 2016 at 4:46 PM, Sterling Hughes  wrote:
>> $ 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
>>>  wrote:
 
> 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 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

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[David Moshal]

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 
> don't provide a version.
>
> Sterling
>
>> On May 28, 2016, at 3:48 PM, Christopher Collins  wrote:
>>
>>> 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 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

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[David Moshal]

```
⇒  ../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
 wrote:
> 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 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

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[Sterling Hughes]

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  wrote:
> 
>> 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 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

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[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 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

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[David G. Simmons]

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?
> 
> 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: ./bin/my_blinky_sim/apps/blinky/blinky.elf
> ```
> 
> Dave
> 
> On Sat, May 28, 2016 at 1:38 PM, Sterling Hughes
>  wrote:
>> $ 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  wrote:
>>> 
>>> 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 
 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
> MyNewt to build, but ran into same error:
> 
> This was the missing step (duh):
> ```
> ⇒  eval $(docker-machine env default)
> ```
> 
> then:
> ```
> ⇒  ../newt install
> apache-mynewt-core
> ```
> 
> and:
> ```
> ../newt test all
> 
> All tests passed
> ```
> 
> but:
> ```
> ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
> ```
> 
> David
> 
> 
> 
>> On Sat, May 28, 2016 at 12:12 PM, David Moshal  wrote:
>> Ok,
>> 
>> The twin challenges for a double-newbie are:
>> 
>> a) selecting the right toolchain and development tools, ide etc.
>> - so far I've identified at least ten (mbed, platformio, Kiel, IVR,
>> Crossworks, Clion, Sublime (seems most common), etc.
>> 
>> b) evaluating MyNew against alternatives:
>> - no OS (seems most common), FreeRTOS, mBed, etc. etc.
>> 
>> In each case the defacto evaluation task seems to be blinking the 
>> onboard LED.
>> 
>> So, with regards to MyNewt:
>> - I used the Docker install option, but couldn't get the first
>> project to work, the error was:
>> 
>> ```
>> ../newt install
>> docker: Cannot connect to the Docker daemon. Is the docker daemon
>> running on this host?.
>> See 'docker run --help'.
>> ```
>> 
>> Note: Docker machine was started without any problem:
>> ```
>> ⇒  docker-machine start default
>> Starting "default"...
>> (default) Check network to re-create if needed...
>> (default) Waiting for an IP...
>> Machine "default" was started.
>> Waiting for SSH to be available...
>> Detecting the provisioner...
>> Started machines may have new IP addresses. You may need to re-run the
>> `docker-machine env` command.
>> 
>> ⇒  docker-machine env default
>> export DOCKER_TLS_VERIFY="1"
>> export DOCKER_HOST="tcp://192.168.99.100:2376"
>> export DOCKER_CERT_PATH="/Users/davem/.docker/machine/machines/default"
>> export DOCKER_MACHINE_NAME="default"
>> # Run this command to configure your shell:
>> # eval $(docker-machine env default)
>> ```
>> 
>> also the simulated version didn't seem to want to run:
>> 
>> ```
>> ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
>> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
>> ```
>> 
>> 
>> So, that's as far as I got with MyNewt.
>> Hope it helps.
>> 
>> David
>> 
>> ps: do we have a slack channel or Github issue system?
>> Easier to past code with markdown than in email.
>> 
>> 
>> 
>> 
>>> On Sat, May 28, 2016 at 11:54 AM, Sterling Hughes  
>>> wrote:
>>> Hi David,
>>> 
>>> On 28 May 2016, at 11:47, David Moshal wrote:
>>> 
> i’d be interested in what others (especially newcomers) would have 
> found
> helpful in the release tarballs in terms of documentation.  i feel 
> like we
> have a fairly good set of docs on mynewt.apache.org, but that often 
> people
> want to see the docs next to the source code— and not have to wonder 
> what’s
> on a website.  but i’d take others thoughts here: i usually just go 

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[David Moshal]

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: ./bin/my_blinky_sim/apps/blinky/blinky.elf
```

Dave

On Sat, May 28, 2016 at 1:38 PM, Sterling Hughes
 wrote:
> $ 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  wrote:
>>
>> 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 
>>> 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
 MyNewt to build, but ran into same error:

 This was the missing step (duh):
 ```
 ⇒  eval $(docker-machine env default)
 ```

 then:
 ```
 ⇒  ../newt install
 apache-mynewt-core
 ```

 and:
 ```
 ../newt test all
 
 All tests passed
 ```

 but:
 ```
 ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
 zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
 ```

 David



> On Sat, May 28, 2016 at 12:12 PM, David Moshal  wrote:
> Ok,
>
> The twin challenges for a double-newbie are:
>
> a) selecting the right toolchain and development tools, ide etc.
> - so far I've identified at least ten (mbed, platformio, Kiel, IVR,
> Crossworks, Clion, Sublime (seems most common), etc.
>
> b) evaluating MyNew against alternatives:
> - no OS (seems most common), FreeRTOS, mBed, etc. etc.
>
> In each case the defacto evaluation task seems to be blinking the onboard 
> LED.
>
> So, with regards to MyNewt:
> - I used the Docker install option, but couldn't get the first
> project to work, the error was:
>
> ```
> ../newt install
> docker: Cannot connect to the Docker daemon. Is the docker daemon
> running on this host?.
> See 'docker run --help'.
> ```
>
> Note: Docker machine was started without any problem:
> ```
> ⇒  docker-machine start default
> Starting "default"...
> (default) Check network to re-create if needed...
> (default) Waiting for an IP...
> Machine "default" was started.
> Waiting for SSH to be available...
> Detecting the provisioner...
> Started machines may have new IP addresses. You may need to re-run the
> `docker-machine env` command.
>
> ⇒  docker-machine env default
> export DOCKER_TLS_VERIFY="1"
> export DOCKER_HOST="tcp://192.168.99.100:2376"
> export DOCKER_CERT_PATH="/Users/davem/.docker/machine/machines/default"
> export DOCKER_MACHINE_NAME="default"
> # Run this command to configure your shell:
> # eval $(docker-machine env default)
> ```
>
> also the simulated version didn't seem to want to run:
>
> ```
> ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
> ```
>
>
> So, that's as far as I got with MyNewt.
> Hope it helps.
>
> David
>
> ps: do we have a slack channel or Github issue system?
> Easier to past code with markdown than in email.
>
>
>
>
>> On Sat, May 28, 2016 at 11:54 AM, Sterling Hughes  
>> wrote:
>> Hi David,
>>
>> On 28 May 2016, at 11:47, David Moshal wrote:
>>
 i’d be interested in what others (especially newcomers) would have 
 found
 helpful in the release tarballs in terms of documentation.  i feel 
 like we
 have a fairly good set of docs on mynewt.apache.org, but that often 
 people
 want to see the docs next to the source code— and not have to wonder 
 what’s
 on a website.  but i’d take others thoughts here: i usually just go 
 ahead
 and try and break things, and then search for docs after they don’t 
 work.
>>>
>>>
>>> Sterling: I'm a double newcomer, i.e: new to MyNewt, and new to embedded
>>> C.
>>> Does that count?
>>
>> Of course.  We’ll take it in that context, but if you’re willing to take 
>> the
>> time to put your thoughts down- it 

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[Sterling Hughes]

$ 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  wrote:
> 
> 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 
>> 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
>>> MyNewt to build, but ran into same error:
>>> 
>>> This was the missing step (duh):
>>> ```
>>> ⇒  eval $(docker-machine env default)
>>> ```
>>> 
>>> then:
>>> ```
>>> ⇒  ../newt install
>>> apache-mynewt-core
>>> ```
>>> 
>>> and:
>>> ```
>>> ../newt test all
>>> 
>>> All tests passed
>>> ```
>>> 
>>> but:
>>> ```
>>> ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
>>> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
>>> ```
>>> 
>>> David
>>> 
>>> 
>>> 
 On Sat, May 28, 2016 at 12:12 PM, David Moshal  wrote:
 Ok,
 
 The twin challenges for a double-newbie are:
 
 a) selecting the right toolchain and development tools, ide etc.
 - so far I've identified at least ten (mbed, platformio, Kiel, IVR,
 Crossworks, Clion, Sublime (seems most common), etc.
 
 b) evaluating MyNew against alternatives:
 - no OS (seems most common), FreeRTOS, mBed, etc. etc.
 
 In each case the defacto evaluation task seems to be blinking the onboard 
 LED.
 
 So, with regards to MyNewt:
 - I used the Docker install option, but couldn't get the first
 project to work, the error was:
 
 ```
 ../newt install
 docker: Cannot connect to the Docker daemon. Is the docker daemon
 running on this host?.
 See 'docker run --help'.
 ```
 
 Note: Docker machine was started without any problem:
 ```
 ⇒  docker-machine start default
 Starting "default"...
 (default) Check network to re-create if needed...
 (default) Waiting for an IP...
 Machine "default" was started.
 Waiting for SSH to be available...
 Detecting the provisioner...
 Started machines may have new IP addresses. You may need to re-run the
 `docker-machine env` command.
 
 ⇒  docker-machine env default
 export DOCKER_TLS_VERIFY="1"
 export DOCKER_HOST="tcp://192.168.99.100:2376"
 export DOCKER_CERT_PATH="/Users/davem/.docker/machine/machines/default"
 export DOCKER_MACHINE_NAME="default"
 # Run this command to configure your shell:
 # eval $(docker-machine env default)
 ```
 
 also the simulated version didn't seem to want to run:
 
 ```
 ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
 zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
 ```
 
 
 So, that's as far as I got with MyNewt.
 Hope it helps.
 
 David
 
 ps: do we have a slack channel or Github issue system?
 Easier to past code with markdown than in email.
 
 
 
 
> On Sat, May 28, 2016 at 11:54 AM, Sterling Hughes  
> wrote:
> Hi David,
> 
> On 28 May 2016, at 11:47, David Moshal wrote:
> 
>>> i’d be interested in what others (especially newcomers) would have found
>>> helpful in the release tarballs in terms of documentation.  i feel like 
>>> we
>>> have a fairly good set of docs on mynewt.apache.org, but that often 
>>> people
>>> want to see the docs next to the source code— and not have to wonder 
>>> what’s
>>> on a website.  but i’d take others thoughts here: i usually just go 
>>> ahead
>>> and try and break things, and then search for docs after they don’t 
>>> work.
>> 
>> 
>> Sterling: I'm a double newcomer, i.e: new to MyNewt, and new to embedded
>> C.
>> Does that count?
> 
> Of course.  We’ll take it in that context, but if you’re willing to take 
> the
> time to put your thoughts down- it will only help us.
> 
> Thanks,
> 
> Sterling

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[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 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
>> MyNewt to build, but ran into same error:
>>
>> This was the missing step (duh):
>> ```
>> ⇒  eval $(docker-machine env default)
>> ```
>>
>> then:
>> ```
>> ⇒  ../newt install
>> apache-mynewt-core
>> ```
>>
>> and:
>> ```
>> ../newt test all
>> 
>> All tests passed
>> ```
>>
>> but:
>> ```
>> ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
>> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
>> ```
>>
>> David
>>
>>
>>
>>> On Sat, May 28, 2016 at 12:12 PM, David Moshal  wrote:
>>> Ok,
>>>
>>> The twin challenges for a double-newbie are:
>>>
>>> a) selecting the right toolchain and development tools, ide etc.
>>> - so far I've identified at least ten (mbed, platformio, Kiel, IVR,
>>> Crossworks, Clion, Sublime (seems most common), etc.
>>>
>>> b) evaluating MyNew against alternatives:
>>> - no OS (seems most common), FreeRTOS, mBed, etc. etc.
>>>
>>> In each case the defacto evaluation task seems to be blinking the onboard 
>>> LED.
>>>
>>> So, with regards to MyNewt:
>>> - I used the Docker install option, but couldn't get the first
>>> project to work, the error was:
>>>
>>> ```
>>> ../newt install
>>> docker: Cannot connect to the Docker daemon. Is the docker daemon
>>> running on this host?.
>>> See 'docker run --help'.
>>> ```
>>>
>>> Note: Docker machine was started without any problem:
>>> ```
>>> ⇒  docker-machine start default
>>> Starting "default"...
>>> (default) Check network to re-create if needed...
>>> (default) Waiting for an IP...
>>> Machine "default" was started.
>>> Waiting for SSH to be available...
>>> Detecting the provisioner...
>>> Started machines may have new IP addresses. You may need to re-run the
>>> `docker-machine env` command.
>>>
>>> ⇒  docker-machine env default
>>> export DOCKER_TLS_VERIFY="1"
>>> export DOCKER_HOST="tcp://192.168.99.100:2376"
>>> export DOCKER_CERT_PATH="/Users/davem/.docker/machine/machines/default"
>>> export DOCKER_MACHINE_NAME="default"
>>> # Run this command to configure your shell:
>>> # eval $(docker-machine env default)
>>> ```
>>>
>>> also the simulated version didn't seem to want to run:
>>>
>>> ```
>>> ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
>>> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
>>> ```
>>>
>>>
>>> So, that's as far as I got with MyNewt.
>>> Hope it helps.
>>>
>>> David
>>>
>>> ps: do we have a slack channel or Github issue system?
>>> Easier to past code with markdown than in email.
>>>
>>>
>>>
>>>
 On Sat, May 28, 2016 at 11:54 AM, Sterling Hughes  
 wrote:
 Hi David,

 On 28 May 2016, at 11:47, David Moshal wrote:

>> i’d be interested in what others (especially newcomers) would have found
>> helpful in the release tarballs in terms of documentation.  i feel like 
>> we
>> have a fairly good set of docs on mynewt.apache.org, but that often 
>> people
>> want to see the docs next to the source code— and not have to wonder 
>> what’s
>> on a website.  but i’d take others thoughts here: i usually just go ahead
>> and try and break things, and then search for docs after they don’t work.
>
>
> Sterling: I'm a double newcomer, i.e: new to MyNewt, and new to embedded
> C.
> Does that count?

 Of course.  We’ll take it in that context, but if you’re willing to take 
 the
 time to put your thoughts down- it will only help us.

 Thanks,

 Sterling

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[Sterling Hughes]

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
> MyNewt to build, but ran into same error:
> 
> This was the missing step (duh):
> ```
> ⇒  eval $(docker-machine env default)
> ```
> 
> then:
> ```
> ⇒  ../newt install
> apache-mynewt-core
> ```
> 
> and:
> ```
> ../newt test all
> 
> All tests passed
> ```
> 
> but:
> ```
> ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
> ```
> 
> David
> 
> 
> 
>> On Sat, May 28, 2016 at 12:12 PM, David Moshal  wrote:
>> Ok,
>> 
>> The twin challenges for a double-newbie are:
>> 
>> a) selecting the right toolchain and development tools, ide etc.
>> - so far I've identified at least ten (mbed, platformio, Kiel, IVR,
>> Crossworks, Clion, Sublime (seems most common), etc.
>> 
>> b) evaluating MyNew against alternatives:
>> - no OS (seems most common), FreeRTOS, mBed, etc. etc.
>> 
>> In each case the defacto evaluation task seems to be blinking the onboard 
>> LED.
>> 
>> So, with regards to MyNewt:
>> - I used the Docker install option, but couldn't get the first
>> project to work, the error was:
>> 
>> ```
>> ../newt install
>> docker: Cannot connect to the Docker daemon. Is the docker daemon
>> running on this host?.
>> See 'docker run --help'.
>> ```
>> 
>> Note: Docker machine was started without any problem:
>> ```
>> ⇒  docker-machine start default
>> Starting "default"...
>> (default) Check network to re-create if needed...
>> (default) Waiting for an IP...
>> Machine "default" was started.
>> Waiting for SSH to be available...
>> Detecting the provisioner...
>> Started machines may have new IP addresses. You may need to re-run the
>> `docker-machine env` command.
>> 
>> ⇒  docker-machine env default
>> export DOCKER_TLS_VERIFY="1"
>> export DOCKER_HOST="tcp://192.168.99.100:2376"
>> export DOCKER_CERT_PATH="/Users/davem/.docker/machine/machines/default"
>> export DOCKER_MACHINE_NAME="default"
>> # Run this command to configure your shell:
>> # eval $(docker-machine env default)
>> ```
>> 
>> also the simulated version didn't seem to want to run:
>> 
>> ```
>> ⇒  ./bin/my_blinky_sim/apps/blinky/blinky.elf
>> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf
>> ```
>> 
>> 
>> So, that's as far as I got with MyNewt.
>> Hope it helps.
>> 
>> David
>> 
>> ps: do we have a slack channel or Github issue system?
>> Easier to past code with markdown than in email.
>> 
>> 
>> 
>> 
>>> On Sat, May 28, 2016 at 11:54 AM, Sterling Hughes  
>>> wrote:
>>> Hi David,
>>> 
>>> On 28 May 2016, at 11:47, David Moshal wrote:
>>> 
> i’d be interested in what others (especially newcomers) would have found
> helpful in the release tarballs in terms of documentation.  i feel like we
> have a fairly good set of docs on mynewt.apache.org, but that often people
> want to see the docs next to the source code— and not have to wonder 
> what’s
> on a website.  but i’d take others thoughts here: i usually just go ahead
> and try and break things, and then search for docs after they don’t work.
 
 
 Sterling: I'm a double newcomer, i.e: new to MyNewt, and new to embedded
 C.
 Does that count?
>>> 
>>> Of course.  We’ll take it in that context, but if you’re willing to take the
>>> time to put your thoughts down- it will only help us.
>>> 
>>> Thanks,
>>> 
>>> Sterling

Re: [DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[Sterling Hughes]

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 license includes references to code that doesn't match our 
notice - not sure which ones?




We don’t need it to say Mynewt by apache rules, John was pointing out 
that it was confusing to him.


apache-newt does have a NOTICE/LICENSE file now, that is why Chris 
repackaged the release.  for some reason, only the newt directory of 
apache-mynewt-newt was included in the source tarball of newt.


LICENSE/NOTICE issues can be resolved in a subsequent release IMO.  We 
have kept all the license info out of NOTICE, which I actually believe 
is appropriate: I don’t believe we’re required by BSD license to put 
that in a notice file (LICENSE should suffice.)


i’d be interested in what others (especially newcomers) would have 
found helpful in the release tarballs in terms of documentation.  i feel 
like we have a fairly good set of docs on mynewt.apache.org, but that 
often people want to see the docs next to the source code— and not 
have to wonder what’s on a website.  but i’d take others thoughts 
here: i usually just go ahead and try and break things, and then search 
for docs after they don’t work.


cheers,

sterling

[DISCUSS] Release Apache Mynewt 0.9.0-incubating-rc2

[Christopher Collins]

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