[jira] [Created] (MYNEWT-752) Error in setting the "permanent" flag upon confirm with hash during image upgrade

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-752:


 Summary: Error in setting the "permanent" flag upon confirm with 
hash during image upgrade
 Key: MYNEWT-752
 URL: https://issues.apache.org/jira/browse/MYNEWT-752
 Project: Mynewt
  Issue Type: Bug
Reporter: Aditi Hilbert
Assignee: Christopher Collins


This is an issue seen during image upgrade. When doing  a "confirm" with a 
hash, newtmgr always marks the "permanent" flag for Slot 1 image to "true", 
irrespective of which image the hash matches.

This works fine when we skip the "test" step during image upgrade and we issue 
a "confirm" with a hash of the new image in Slot 1. 

However, if we do the "test" step (when the new image is swapped into Slot 0), 
and we then do a "confirm" with a hash of the new image and reboot, the device 
marks the old image in Slot 1 as "permanent" and swaps it back to Slot 0. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (MYNEWT-582) "go get mynewt.apache.org/newt/newt" fails

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-582.
--
Resolution: Fixed

> "go get mynewt.apache.org/newt/newt" fails
> --
>
> Key: MYNEWT-582
> URL: https://issues.apache.org/jira/browse/MYNEWT-582
> Project: Mynewt
>  Issue Type: Bug
>  Components: Newt
>Reporter: David Brown
>Assignee: Todd Mitton
>Priority: Minor
>
> It isn't possible to develop mynewt using conventional go methods, or to use 
> it as a dependency in another package.
> The problem is that the https://mynewt.apache.org/newt/ doesn't return valid 
> results for subdirectories.
> {code}
> curl https://mynewt.apache.org/newt/
> curl https://mynewt.apache.org/newt/newt/
> curl https://mynewt.apache.org/newt/newt/image/
> {code}
> The first above command returns valid redirects for github, but the second 
> just returns a 404. This causes the git fetch to fail.
> If something such as mcuboot/imgtool tries to use 
> https://mynewt.apache.org/newt/newt/image as a dependency, it also fails to 
> fetch this.
> I believe the fix is to return the metadata page for subdirectories. At least 
> 'newt/newt' and 'newt/newt/image' should be used, the first to make the newt 
> tool itself buildable, and the second to allow the image library to be used 
> as a dependency by mcuboot.
> Probably add the other top level ones, such as newtmgr as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MYNEWT-675) Arduino Primo documentation still references "features"

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939391#comment-15939391
 ] 

Aditi Hilbert commented on MYNEWT-675:
--

Marko, can you please create the binaries of your specially patched openocd for 
64-bit Linux and Mac OS?

We will host them on runtimeco and point a link to it in the documentation.

> Arduino Primo documentation still references "features"
> ---
>
> Key: MYNEWT-675
> URL: https://issues.apache.org/jira/browse/MYNEWT-675
> Project: Mynewt
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: v1_0_0_rel
>Reporter: Sterling Hughes
>Assignee: Marko Kiiskila
> Fix For: v1_0_0_rel
>
>
> http://mynewt.apache.org/latest/os/tutorials/blinky_primo/
> In order to use openocd, it says to have the following line:
> $ newt target set primo_boot features=openocd_debug
> $ newt target set primoblinky features=openocd_debug
> Instead, this is now "syscfg=OPENOCD_DEBUG" in order to have the same effect. 
>  
> Also, install of custom openocd is painful, as it requires autotools - it 
> would be great if we already compiled the openocd binary for mac, linux 
> platforms.  This is more of an openocd thing, but still. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (MYNEWT-658) Build failure when following the tutorial on setting up NimBLE application

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-658.
--
Resolution: Fixed

Changes made.

"@apache-mynewt-core/libc/baselibc" not required as it is part of the 
dependency tree for kernel.

> Build failure when following the tutorial on setting up NimBLE application
> --
>
> Key: MYNEWT-658
> URL: https://issues.apache.org/jira/browse/MYNEWT-658
> Project: Mynewt
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: v1_0_0_beta2
> Environment: Linux, Native
>Reporter: Kumar Amit Mehta
>Assignee: Aditi Hilbert
>Priority: Minor
>  Labels: documentation
>
> There are two problems with the NimBLE application tutorial [1]
> i)  newt build ble_tgt fails.
> 
> $ newt build ble_tgt
> Building target targets/ble_tgt
> Error: Could not resolve package dependency: 
> @apache-mynewt-core/libs/baselibc; depender: apps/ble_app
> 
> ii) After fixing the package dependency problem (see below) build fails as 
> os_init() expects an argument.
> 
> Error: apps/ble_app/src/main.c: In function 'main':
> apps/ble_app/src/main.c:6:5: error: too few arguments to function 'os_init'
>  os_init();
> 
> Proposed solution:
> i) Fix apps/ble_app/pkg.yml
>  
> pkg.deps:
> - "@apache-mynewt-core/kernel/os"
> - "@apache-mynewt-core/hw/hal"
> - "@apache-mynewt-core/libc/baselibc"
> - "@apache-mynewt-core/sys/log/full"
> - "@apache-mynewt-core/sys/stats/full"
> - "@apache-mynewt-core/sys/console/full"
> - "@apache-mynewt-core/net/nimble/transport/ram"
> - "@apache-mynewt-core/net/nimble/controller"
> - "@apache-mynewt-core/net/nimble/host"
> 
> ii) Replace os_init() with os_init(NULL)
>  
> [1] http://mynewt.apache.org/latest/network/ble/nimble_setup/ (version: 
> latest*)
> * Both latest and v0.9.0 seem to be same.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MYNEWT-649) "newt target set" allows random variable to be set; should allow only valid variable settings.

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert reassigned MYNEWT-649:


Assignee: Wanda Chiu

> "newt target set" allows random variable to be set; should allow only valid 
> variable settings.
> --
>
> Key: MYNEWT-649
> URL: https://issues.apache.org/jira/browse/MYNEWT-649
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>Assignee: Wanda Chiu
> Fix For: v1_1_0_rel
>
>
> The "newt target set" command should have a check for allowed settings.
> For example, I can set the variable "bogus" with a value and  target.bogus 
> will be added to the target.yml file.   Do we have a list of all the valid 
> variables so we can add the validation to the command?  What I have listed as 
> valid variables in the `newt target set" command documentation are: app, bsp, 
> loader, build_profile, cflags, aflags, lflags, syscfg. 
> We should make sure the "newt vals" command also covers this set of valid 
> target variables to make things consistent.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MYNEWT-649) "newt target set" allows random variable to be set; should allow only valid variable settings.

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-649:


 Summary: "newt target set" allows random variable to be set; 
should allow only valid variable settings.
 Key: MYNEWT-649
 URL: https://issues.apache.org/jira/browse/MYNEWT-649
 Project: Mynewt
  Issue Type: Bug
Reporter: Aditi Hilbert
 Fix For: v1_1_0_rel


The "newt target set" command should have a check for allowed settings.

For example, I can set the variable "bogus" with a value and  target.bogus will 
be added to the target.yml file.   Do we have a list of all the valid variables 
so we can add the validation to the command?  What I have listed as valid 
variables in the `newt target set" command documentation are: app, bsp, loader, 
build_profile, cflags, aflags, lflags, syscfg. 

We should make sure the "newt vals" command also covers this set of valid 
target variables to make things consistent.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MYNEWT-648) "newt test net/oic" fails when compiling with clang

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-648:
-
Summary: "newt test net/oic" fails when compiling with clang  (was: "newt 
test net/oic)

> "newt test net/oic" fails when compiling with clang
> ---
>
> Key: MYNEWT-648
> URL: https://issues.apache.org/jira/browse/MYNEWT-648
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>
> $ newt test net/oic
> Testing package net/oic/test
> Compiling encoding/cborattr/src/cborattr.c
> Compiling encoding/tinycbor/src/cborerrorstrings.c
> 
> Compiling net/oic/src/api/oc_server_api.c
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:38:
> In file included from net/oic/src/messaging/coap/observe.h:45:
> net/oic/include/oic/oc_ri.h:126:3: error: redefinition of typedef 
> 'oc_resource_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_resource_t;
>   ^
> net/oic/include/oic/oc_ri.h:98:28: note: previous definition is here
> typedef struct oc_resource oc_resource_t;
>^
> net/oic/include/oic/oc_ri.h:152:28: error: redefinition of typedef 
> 'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> typedef struct coap_packet coap_packet_t;
>^
> net/oic/src/messaging/coap/coap.h:227:3: note: previous definition is here
> } coap_packet_t;
>   ^
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:39:
> In file included from net/oic/src/messaging/coap/separate.h:46:
> net/oic/src/messaging/coap/oc_coap.h:30:3: error: redefinition of typedef 
> 'oc_separate_response_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_separate_response_t;
>   ^
> net/oic/include/oic/oc_ri.h:64:37: note: previous definition is here
> typedef struct oc_separate_response oc_separate_response_t;
> ^
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:39:
> In file included from net/oic/src/messaging/coap/separate.h:46:
> net/oic/src/messaging/coap/oc_coap.h:37:3: error: redefinition of typedef 
> 'oc_response_buffer_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_response_buffer_t;
>   ^
> net/oic/include/oic/oc_ri.h:66:35: note: previous definition is here
> typedef struct oc_response_buffer oc_response_buffer_t;
>   ^
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:39:
> net/oic/src/messaging/coap/separate.h:67:28: error: redefinition of typedef 
> 'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> typedef struct coap_packet coap_packet_t;
>^
> net/oic/include/oic/oc_ri.h:152:28: note: previous definition is here
> typedef struct coap_packet coap_packet_t;
>^
> 5 errors generated.
> Error: Test failure(s):
> Passed tests: []
> Failed tests: [net/oic/test]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MYNEWT-648) "newt test net/oic" fails when compiling with clang

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891146#comment-15891146
 ] 

Aditi Hilbert commented on MYNEWT-648:
--

$ gcc -v
Configured with: --prefix=/Library/Developer/CommandLineTools/usr 
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 8.0.0 (clang-800.0.42.1)
Target: x86_64-apple-darwin16.0.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin


> "newt test net/oic" fails when compiling with clang
> ---
>
> Key: MYNEWT-648
> URL: https://issues.apache.org/jira/browse/MYNEWT-648
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>
> $ newt test net/oic
> Testing package net/oic/test
> Compiling encoding/cborattr/src/cborattr.c
> Compiling encoding/tinycbor/src/cborerrorstrings.c
> 
> Compiling net/oic/src/api/oc_server_api.c
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:38:
> In file included from net/oic/src/messaging/coap/observe.h:45:
> net/oic/include/oic/oc_ri.h:126:3: error: redefinition of typedef 
> 'oc_resource_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_resource_t;
>   ^
> net/oic/include/oic/oc_ri.h:98:28: note: previous definition is here
> typedef struct oc_resource oc_resource_t;
>^
> net/oic/include/oic/oc_ri.h:152:28: error: redefinition of typedef 
> 'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> typedef struct coap_packet coap_packet_t;
>^
> net/oic/src/messaging/coap/coap.h:227:3: note: previous definition is here
> } coap_packet_t;
>   ^
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:39:
> In file included from net/oic/src/messaging/coap/separate.h:46:
> net/oic/src/messaging/coap/oc_coap.h:30:3: error: redefinition of typedef 
> 'oc_separate_response_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_separate_response_t;
>   ^
> net/oic/include/oic/oc_ri.h:64:37: note: previous definition is here
> typedef struct oc_separate_response oc_separate_response_t;
> ^
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:39:
> In file included from net/oic/src/messaging/coap/separate.h:46:
> net/oic/src/messaging/coap/oc_coap.h:37:3: error: redefinition of typedef 
> 'oc_response_buffer_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_response_buffer_t;
>   ^
> net/oic/include/oic/oc_ri.h:66:35: note: previous definition is here
> typedef struct oc_response_buffer oc_response_buffer_t;
>   ^
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:39:
> net/oic/src/messaging/coap/separate.h:67:28: error: redefinition of typedef 
> 'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> typedef struct coap_packet coap_packet_t;
>^
> net/oic/include/oic/oc_ri.h:152:28: note: previous definition is here
> typedef struct coap_packet coap_packet_t;
>^
> 5 errors generated.
> Error: Test failure(s):
> Passed tests: []
> Failed tests: [net/oic/test]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MYNEWT-648) "newt test net/oic

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-648:
-
Description: 
$ newt test net/oic
Testing package net/oic/test
Compiling encoding/cborattr/src/cborattr.c
Compiling encoding/tinycbor/src/cborerrorstrings.c

Compiling net/oic/src/api/oc_server_api.c
In file included from net/oic/src/api/oc_buffer.c:23:
In file included from net/oic/src/messaging/coap/engine.h:38:
In file included from net/oic/src/messaging/coap/observe.h:45:
net/oic/include/oic/oc_ri.h:126:3: error: redefinition of typedef 
'oc_resource_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
} oc_resource_t;
  ^
net/oic/include/oic/oc_ri.h:98:28: note: previous definition is here
typedef struct oc_resource oc_resource_t;
   ^
net/oic/include/oic/oc_ri.h:152:28: error: redefinition of typedef 
'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
typedef struct coap_packet coap_packet_t;
   ^
net/oic/src/messaging/coap/coap.h:227:3: note: previous definition is here
} coap_packet_t;
  ^
In file included from net/oic/src/api/oc_buffer.c:23:
In file included from net/oic/src/messaging/coap/engine.h:39:
In file included from net/oic/src/messaging/coap/separate.h:46:
net/oic/src/messaging/coap/oc_coap.h:30:3: error: redefinition of typedef 
'oc_separate_response_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
} oc_separate_response_t;
  ^
net/oic/include/oic/oc_ri.h:64:37: note: previous definition is here
typedef struct oc_separate_response oc_separate_response_t;
^
In file included from net/oic/src/api/oc_buffer.c:23:
In file included from net/oic/src/messaging/coap/engine.h:39:
In file included from net/oic/src/messaging/coap/separate.h:46:
net/oic/src/messaging/coap/oc_coap.h:37:3: error: redefinition of typedef 
'oc_response_buffer_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
} oc_response_buffer_t;
  ^
net/oic/include/oic/oc_ri.h:66:35: note: previous definition is here
typedef struct oc_response_buffer oc_response_buffer_t;
  ^
In file included from net/oic/src/api/oc_buffer.c:23:
In file included from net/oic/src/messaging/coap/engine.h:39:
net/oic/src/messaging/coap/separate.h:67:28: error: redefinition of typedef 
'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
typedef struct coap_packet coap_packet_t;
   ^
net/oic/include/oic/oc_ri.h:152:28: note: previous definition is here
typedef struct coap_packet coap_packet_t;
   ^
5 errors generated.
Error: Test failure(s):
Passed tests: []
Failed tests: [net/oic/test]


> "newt test net/oic
> --
>
> Key: MYNEWT-648
> URL: https://issues.apache.org/jira/browse/MYNEWT-648
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>
> $ newt test net/oic
> Testing package net/oic/test
> Compiling encoding/cborattr/src/cborattr.c
> Compiling encoding/tinycbor/src/cborerrorstrings.c
> 
> Compiling net/oic/src/api/oc_server_api.c
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:38:
> In file included from net/oic/src/messaging/coap/observe.h:45:
> net/oic/include/oic/oc_ri.h:126:3: error: redefinition of typedef 
> 'oc_resource_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_resource_t;
>   ^
> net/oic/include/oic/oc_ri.h:98:28: note: previous definition is here
> typedef struct oc_resource oc_resource_t;
>^
> net/oic/include/oic/oc_ri.h:152:28: error: redefinition of typedef 
> 'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> typedef struct coap_packet coap_packet_t;
>^
> net/oic/src/messaging/coap/coap.h:227:3: note: previous definition is here
> } coap_packet_t;
>   ^
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:39:
> In file included from net/oic/src/messaging/coap/separate.h:46:
> net/oic/src/messaging/coap/oc_coap.h:30:3: error: redefinition of typedef 
> 'oc_separate_response_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_separate_response_t;
>   ^
> net/oic/include/oic/oc_ri.h:64:37: note: previous definition is here
> typedef struct oc_separate_response oc_separate_response_t;
> ^
> In file included from net/oic/src/api/oc_buffer.c:23:
> In file included from net/oic/src/messaging/coap/engine.h:39:
> In file included from net/oic/src/messaging/coap/separate.h:46:
> net/oic/src/messaging/coap/oc_coap.h:37:3: error: redefinition of typedef 
> 'oc_response_buffer_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } oc_response_buffer_t;
>   ^
> net/oic/include/oic/oc_ri.h:66:35: note: previo

[jira] [Created] (MYNEWT-648) "newt test net/oic

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-648:


 Summary: "newt test net/oic
 Key: MYNEWT-648
 URL: https://issues.apache.org/jira/browse/MYNEWT-648
 Project: Mynewt
  Issue Type: Bug
Reporter: Aditi Hilbert






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (MYNEWT-548) The blinky.elf created by the Create Your First Mynewt Project tutorial runs only on linux

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-548.
--
Resolution: Fixed

docs updated

> The blinky.elf created by the Create Your First Mynewt Project tutorial runs 
> only on linux
> --
>
> Key: MYNEWT-548
> URL: https://issues.apache.org/jira/browse/MYNEWT-548
> Project: Mynewt
>  Issue Type: Bug
>Affects Versions: v1_0_0_beta1
> Environment: macOS, Docker
>Reporter: Liviu Ionescu
>Assignee: Aditi Hilbert
> Fix For: v1_0_0_rel
>
>
> I followed your basic setup instructions and installed the Docker version of 
> `newt`.
> Then I followed 
> https://mynewt.apache.org/latest/os/get_started/project_create/ to create and 
> build the `my_blinky_sim` application.
> When trying to run the binary, not only the path is incorrect 
> (`./bin/my_blinky_sim/apps/blinky/blinky.elf`), but the file is a Linux 
> binary:
> ```
> file ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf
> ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf: ELF 32-bit LSB 
> executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter 
> /lib/ld-linux.so.2, for GNU/Linux 2.6.32, 
> BuildID[sha1]=d66139b97ed3cd7d9c9e41a03137d91002c706b2, not stripped
> ```
> I do not know if it is possible to create macOS applications, if not, the 
> documentation should clearly state that the simulated applications run only 
> on Linux; if it is possible, the documentation should explain how to do it. 
> does installing `newt` natively allow to generate macOS applications?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MYNEWT-622) newtmgr crashes when trying to download core without filename

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert reassigned MYNEWT-622:


Assignee: Aditi Hilbert

> newtmgr crashes when trying to download core without filename
> -
>
> Key: MYNEWT-622
> URL: https://issues.apache.org/jira/browse/MYNEWT-622
> Project: Mynewt
>  Issue Type: Bug
>Affects Versions: v1_0_0_beta2
>Reporter: Marko Kiiskila
>Assignee: Aditi Hilbert
>
> [marko@IsMyLaptop:~/src8/incubator-mynewt-blinky/repos/apache-mynewt-core]$ 
> newtmgr -c AL01QIP7 image coredownload
> panic: interface conversion: error is *errors.errorString, not *util.NewtError
> goroutine 1 [running]:
> panic(0x4539fc0, 0xc4200102c0)
>   /usr/local/go/src/runtime/panic.go:500 +0x1a1
> mynewt.apache.org/newt/newtmgr/cli.nmUsage(0xc420178900, 0x4844fa0, 
> 0xc42004fc60)
>   /Users/marko/newt/src/mynewt.apache.org/newt/newtmgr/cli/usage.go:34 
> +0x2ce
> mynewt.apache.org/newt/newtmgr/cli.coreDownloadCmd(0xc420178900, 
> 0xc420012960, 0x0, 0x2)
>   /Users/marko/newt/src/mynewt.apache.org/newt/newtmgr/cli/image.go:393 
> +0xb0
> mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra.(*Command).execute(0xc420178900,
>  0xc420012700, 0x2, 0x2, 0xc420178900, 0xc420012700)
>   
> /Users/marko/newt/src/mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra/command.go:636
>  +0x443
> mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc420176000,
>  0xc420176480, 0xc420176240, 0xc42016f000)
>   
> /Users/marko/newt/src/mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra/command.go:722
>  +0x367
> mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra.(*Command).Execute(0xc420176000,
>  0x40d711c, 0xc421a0)
>   
> /Users/marko/newt/src/mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra/command.go:681
>  +0x2b
> main.main()
>   /Users/marko/newt/src/mynewt.apache.org/newt/newtmgr/newtmgr.go:25 +0x2f
> exit status 2



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MYNEWT-557) Newt build command does not print out a warning when overriding an undefined configuration setting

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-557:
-
 Assignee: Wanda Chiu
Fix Version/s: v1_0_0_rel

> Newt build command does not print out a warning when overriding an undefined 
> configuration setting
> --
>
> Key: MYNEWT-557
> URL: https://issues.apache.org/jira/browse/MYNEWT-557
> Project: Mynewt
>  Issue Type: Bug
>  Components: Newt
>Affects Versions: v1_0_0_beta1
>Reporter: Wanda Chiu
>Assignee: Wanda Chiu
> Fix For: v1_0_0_rel
>
>
> The newt build command ignores overriding an undefined configuration setting. 
> There should be a warning message to let the user know because the error may 
> be caused by typo with the configuration setting name. This can create 
> unexpected behavior because the user thinks the override was successful. Note 
> that the newt target config command does output a warning message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-557) Newt build command does not print out a warning when overriding an undefined configuration setting

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-557:
-
Affects Version/s: (was: v1_0_0_rel)
   v1_0_0_beta1

> Newt build command does not print out a warning when overriding an undefined 
> configuration setting
> --
>
> Key: MYNEWT-557
> URL: https://issues.apache.org/jira/browse/MYNEWT-557
> Project: Mynewt
>  Issue Type: Bug
>  Components: Newt
>Affects Versions: v1_0_0_beta1
>Reporter: Wanda Chiu
>
> The newt build command ignores overriding an undefined configuration setting. 
> There should be a warning message to let the user know because the error may 
> be caused by typo with the configuration setting name. This can create 
> unexpected behavior because the user thinks the override was successful. Note 
> that the newt target config command does output a warning message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-553) Option in newt to print only executed commands during build.

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-553:


 Summary: Option in newt to print only executed commands during 
build.
 Key: MYNEWT-553
 URL: https://issues.apache.org/jira/browse/MYNEWT-553
 Project: Mynewt
  Issue Type: Improvement
Reporter: Aditi Hilbert


This could be then used instead of '-l debug' which
produces huge amount of logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-496) Update www.apache.org/licenses/exports/ with tinycrypt and polarssl info

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706104#comment-15706104
 ] 

Aditi Hilbert commented on MYNEWT-496:
--

Justin, can you please help us out? I believe you have SVN access to the site. 
Can you submit the changes for us? I have also emailed infrastructure to grant 
me some karma but haven't heard back yet.

> Update  www.apache.org/licenses/exports/ with tinycrypt and polarssl info
> -
>
> Key: MYNEWT-496
> URL: https://issues.apache.org/jira/browse/MYNEWT-496
> Project: Mynewt
>  Issue Type: Task
>Affects Versions: v1_0_0_beta1
>Reporter: Aditi Hilbert
>Assignee: Justin Mclean
> Fix For: v1_0_0_beta1
>
>
> 1. Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info
> (we have added polarssl and tinycrypt.
> 2. Send email to US govt. notifying our crypto code cryptography qualifies 
> for the TSU exception
> (the repo link has changed since last filing)
> 3. We also have to place the notice below in each distribution's README file:
> ` This distribution includes cryptographic software. The country in which you 
> currently reside may have restrictions on the import, possession, use, and/or 
> re-export to another country, of encryption software. BEFORE using any 
> encryption software, please check your country's laws, regulations and 
> policies concerning the import, possession, or use, and re-export of 
> encryption software, to see if this is permitted. See 
>  for more information.
> The U.S. Government Department of Commerce, Bureau of Industry and Security 
> (BIS), has classified this software as Export Commodity Control Number (ECCN) 
> 5D002.C.1, which includes information security software using or performing 
> cryptographic functions with asymmetric algorithms. The form and manner of 
> this Apache Software Foundation distribution makes it eligible for export 
> under the License Exception ENC Technology Software Unrestricted (TSU) 
> exception (see the BIS Export Administration Regulations, Section 740.13) for 
> both object code and source code.
> The following provides more details on the included cryptographic software: 
> ... `  components of the release including cryptography.>
> needs to be fixed before release candidate is put to vote.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-496) Update www.apache.org/licenses/exports/ with tinycrypt and polarssl info

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-496:
-
Assignee: Justin Mclean  (was: Aditi Hilbert)

> Update  www.apache.org/licenses/exports/ with tinycrypt and polarssl info
> -
>
> Key: MYNEWT-496
> URL: https://issues.apache.org/jira/browse/MYNEWT-496
> Project: Mynewt
>  Issue Type: Task
>Affects Versions: v1_0_0_beta1
>Reporter: Aditi Hilbert
>Assignee: Justin Mclean
> Fix For: v1_0_0_beta1
>
>
> 1. Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info
> (we have added polarssl and tinycrypt.
> 2. Send email to US govt. notifying our crypto code cryptography qualifies 
> for the TSU exception
> (the repo link has changed since last filing)
> 3. We also have to place the notice below in each distribution's README file:
> ` This distribution includes cryptographic software. The country in which you 
> currently reside may have restrictions on the import, possession, use, and/or 
> re-export to another country, of encryption software. BEFORE using any 
> encryption software, please check your country's laws, regulations and 
> policies concerning the import, possession, or use, and re-export of 
> encryption software, to see if this is permitted. See 
>  for more information.
> The U.S. Government Department of Commerce, Bureau of Industry and Security 
> (BIS), has classified this software as Export Commodity Control Number (ECCN) 
> 5D002.C.1, which includes information security software using or performing 
> cryptographic functions with asymmetric algorithms. The form and manner of 
> this Apache Software Foundation distribution makes it eligible for export 
> under the License Exception ENC Technology Software Unrestricted (TSU) 
> exception (see the BIS Export Administration Regulations, Section 740.13) for 
> both object code and source code.
> The following provides more details on the included cryptographic software: 
> ... `  components of the release including cryptography.>
> needs to be fixed before release candidate is put to vote.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-496) Update www.apache.org/licenses/exports/ with tinycrypt and polarssl info

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704558#comment-15704558
 ] 

Aditi Hilbert commented on MYNEWT-496:
--

www.apache.org/licenses/exports/ needs to be updated with the following info:

Apache Mynewt Incubator Project
Product Name: Apache Mynewt
Version: 1.0.0-b1-incubating and later
ECCN: 5D002
Controlled Source: ASF
Link: 
(mbedtls)
https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;a=tree;f=crypto/mbedtls;h=d5f6a7013f36a68d25b9232769a273e990278477;hb=HEAD
 
(tinycrypt)
https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;a=tree;f=crypto/tinycrypt;h=13294d0db5cdf2b0e882839f8c204d7d2ddd3bd1;hb=HEAD
(polarssl)
https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;a=tree;f=net/ip/lwip_base/src/netif/ppp/polarssl;h=47a41b927b1faff57e562b0dac21c82c040e8025;hb=HEAD

--
To update the page: The source XML page contains a list of XML trees under 
eccnmatrix that can be edited by anyone with site-dev karma (which includes all 
of the PMC chairs). Note that the exports web page is generated from the XML.


> Update  www.apache.org/licenses/exports/ with tinycrypt and polarssl info
> -
>
> Key: MYNEWT-496
> URL: https://issues.apache.org/jira/browse/MYNEWT-496
> Project: Mynewt
>  Issue Type: Task
>Affects Versions: v1_0_0_beta1
>Reporter: Aditi Hilbert
>Assignee: Aditi Hilbert
> Fix For: v1_0_0_beta1
>
>
> 1. Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info
> (we have added polarssl and tinycrypt.
> 2. Send email to US govt. notifying our crypto code cryptography qualifies 
> for the TSU exception
> (the repo link has changed since last filing)
> 3. We also have to place the notice below in each distribution's README file:
> ` This distribution includes cryptographic software. The country in which you 
> currently reside may have restrictions on the import, possession, use, and/or 
> re-export to another country, of encryption software. BEFORE using any 
> encryption software, please check your country's laws, regulations and 
> policies concerning the import, possession, or use, and re-export of 
> encryption software, to see if this is permitted. See 
>  for more information.
> The U.S. Government Department of Commerce, Bureau of Industry and Security 
> (BIS), has classified this software as Export Commodity Control Number (ECCN) 
> 5D002.C.1, which includes information security software using or performing 
> cryptographic functions with asymmetric algorithms. The form and manner of 
> this Apache Software Foundation distribution makes it eligible for export 
> under the License Exception ENC Technology Software Unrestricted (TSU) 
> exception (see the BIS Export Administration Regulations, Section 740.13) for 
> both object code and source code.
> The following provides more details on the included cryptographic software: 
> ... `  components of the release including cryptography.>
> needs to be fixed before release candidate is put to vote.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-496) Update www.apache.org/licenses/exports/ with tinycrypt and polarssl info

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-496:


 Summary: Update  www.apache.org/licenses/exports/ with tinycrypt 
and polarssl info
 Key: MYNEWT-496
 URL: https://issues.apache.org/jira/browse/MYNEWT-496
 Project: Mynewt
  Issue Type: Task
Affects Versions: v1_0_0_beta1
Reporter: Aditi Hilbert
Assignee: Aditi Hilbert
 Fix For: v1_0_0_beta1


1. Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info
(we have added polarssl and tinycrypt.

2. Send email to US govt. notifying our crypto code cryptography qualifies for 
the TSU exception

(the repo link has changed since last filing)

3. We also have to place the notice below in each distribution's README file:

` This distribution includes cryptographic software. The country in which you 
currently reside may have restrictions on the import, possession, use, and/or 
re-export to another country, of encryption software. BEFORE using any 
encryption software, please check your country's laws, regulations and policies 
concerning the import, possession, or use, and re-export of encryption 
software, to see if this is permitted. See  for more 
information.
The U.S. Government Department of Commerce, Bureau of Industry and Security 
(BIS), has classified this software as Export Commodity Control Number (ECCN) 
5D002.C.1, which includes information security software using or performing 
cryptographic functions with asymmetric algorithms. The form and manner of this 
Apache Software Foundation distribution makes it eligible for export under the 
License Exception ENC Technology Software Unrestricted (TSU) exception (see the 
BIS Export Administration Regulations, Section 740.13) for both object code and 
source code.

The following provides more details on the included cryptographic software: ... 
` 

needs to be fixed before release candidate is put to vote.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-445) Option to erase stats counter

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-445:


 Summary: Option to erase stats counter
 Key: MYNEWT-445
 URL: https://issues.apache.org/jira/browse/MYNEWT-445
 Project: Mynewt
  Issue Type: Improvement
Reporter: Aditi Hilbert


A runtime option to clear the stats counter would be useful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-444) The log level should be configurable module by module. Log recording should be according to the level

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-444:


 Summary: The log level should be configurable module by module. 
Log recording should be according to the level
 Key: MYNEWT-444
 URL: https://issues.apache.org/jira/browse/MYNEWT-444
 Project: Mynewt
  Issue Type: Improvement
Reporter: Aditi Hilbert


It would be useful to be able to set different log levels for different 
packages e.g. ERROR for LOG_MODULE_OS and DEBUG for LOG_MODULE_NIMBLE_CTLR 
Should be more efficient use of memory to log according to the level instead of 
logging everything and only displaying according to the level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-436) "newt target" should spit out an error message when it encounters unexpected files while resolving targets

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-436:


 Summary: "newt target" should spit out an error message when it 
encounters unexpected files while resolving targets
 Key: MYNEWT-436
 URL: https://issues.apache.org/jira/browse/MYNEWT-436
 Project: Mynewt
  Issue Type: Improvement
  Components: Newt
Reporter: Aditi Hilbert
Assignee: Sterling Hughes


If an app is nested inside another app by mistake, newt does not complain but 
does not show any targets either. It should complain that something is amiss, 
something to the effect of "found unexpected files in apps".  

For example, I had blinky inside blinky by mistake (because of the current 
situation of having to manually clone the develop blinky repo):
aditihilbert@~/dev/myproj/apps/blinky$ ls
blinky  pkg.yml src

aditihilbert@~/dev/myproj$ newt target show
aditihilbert@~/dev/myproj$

I remove blinky and newt target works ok.

aditihilbert@~/dev/myproj$ newt target show
targets/arduino_boot
app=@apache-mynewt-core/apps/boot
bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero
build_profile=optimized
targets/blinky_zero
app=apps/blinky
bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero
build_profile=debug
targets/my_blinky_sim
app=apps/blinky
bsp=@apache-mynewt-core/hw/bsp/native
build_profile=debug







--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-375) Make image slots consistent for split image case

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-375:


 Summary: Make image slots consistent for split image case
 Key: MYNEWT-375
 URL: https://issues.apache.org/jira/browse/MYNEWT-375
 Project: Mynewt
  Issue Type: Improvement
Reporter: Aditi Hilbert
Assignee: Paul Dietrich
Priority: Minor


Currently the slot numbers for the various image pieces are not clear.

For example, the following defines are in split.c 
#define LOADER_IMAGE_SLOT0
#define SPLIT_IMAGE_SLOT1

However, "newtmgr image list2" lists split images in slot 1 and slot 2. The 
usage of the slot numbers should be made consistent across the split image 
implementation such as:

The bootloader resides in slot 0.
The "loader" resides in slot 1
The "split app" resides in slot 2.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-361) Consecutive commands not run in terminal

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-361.
--
Resolution: Fixed

> Consecutive commands not run in terminal
> 
>
> Key: MYNEWT-361
> URL: https://issues.apache.org/jira/browse/MYNEWT-361
> Project: Mynewt
>  Issue Type: Bug
>  Components: Newt
>Affects Versions: v0_9_0
> Environment: Ubuntu 14.10 using the Docker version of newt
>Reporter: Tim
>Assignee: Christopher Collins
>Priority: Minor
> Fix For: v1_0_0_beta1
>
>
> Basically, paste a few newt commands into a terminal, like this:
> newt target create nrf52_boot
> newt target set nrf52_boot app=@apache-mynewt-core/apps/boot
> newt target set nrf52_boot bsp=@apache-mynewt-core/hw/bsp/nrf52dk
> newt target set nrf52_boot build_profile=optimized
> My expected behaviour is that each one executes after the previous one has 
> finished. What actually happens is that  only the first commands execute. The 
> others don't do anything (not even an error).
> You can actually see this easier like this:
> newt target show
> newt target show
> vs
> newt target show && newt target show
> If I paste this it works as expected, so I'm not sure what newt does 
> differently (does it fork and run in the background or something weird?)
> sleep 1
> ls



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MYNEWT-158) The current level of navigation menu being viewed should be visible in the viewable area of the TOC

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert closed MYNEWT-158.

Resolution: Won't Fix

> The current level of navigation menu being viewed should be visible in the 
> viewable area of the TOC
> ---
>
> Key: MYNEWT-158
> URL: https://issues.apache.org/jira/browse/MYNEWT-158
> Project: Mynewt
>  Issue Type: Improvement
>Reporter: Aditi Hilbert
>Assignee: Todd Mitton
> Attachments: pic1.png, pic2.png
>
>
> What it is now is shown in pic1
> How it should be is shown in pic2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-158) The current level of navigation menu being viewed should be visible in the viewable area of the TOC

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435487#comment-15435487
 ] 

Aditi Hilbert commented on MYNEWT-158:
--

This is not worth the work required. We have a nice big scroll bar that can be 
easily used to get to the current topic. And there are next and previous 
buttons to move to nearby topics as well.

> The current level of navigation menu being viewed should be visible in the 
> viewable area of the TOC
> ---
>
> Key: MYNEWT-158
> URL: https://issues.apache.org/jira/browse/MYNEWT-158
> Project: Mynewt
>  Issue Type: Improvement
>Reporter: Aditi Hilbert
>Assignee: Todd Mitton
> Attachments: pic1.png, pic2.png
>
>
> What it is now is shown in pic1
> How it should be is shown in pic2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-118) GSoC - Android or iOS application to interact with devices/boards powered by Mynewt OS and BLE stack (Nimble)

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434158#comment-15434158
 ] 

Aditi Hilbert commented on MYNEWT-118:
--

We did this outside GSoC. We wrote an Android app to turn LED on/off and query 
status. 
It is available in the Android app store. A hackster.io project provides the 
instructions: 
https://www.hackster.io/22275/bluetooth-le-gpio-controller-603d1b?ref=user&ref_id=93046&offset=0


> GSoC - Android or iOS application to interact with devices/boards powered by 
> Mynewt OS and BLE stack (Nimble)
> -
>
> Key: MYNEWT-118
> URL: https://issues.apache.org/jira/browse/MYNEWT-118
> Project: Mynewt
>  Issue Type: New Feature
>Reporter: Aditi Hilbert
>Assignee: Aditi Hilbert
>  Labels: gsoc2016
>
> Mentor: Will San Filippo, Marko Kiiskila, Aditi Hilbert
> Difficulty: Medium-Hard
> Skills: C, Java or Objective-C or Swift, basic knowledge of Bluetooth Low 
> Energy
> Description: Android and iOS have built-in platform support for Bluetooth Low 
> Energy in the central role and provide APIs that apps can use to discover 
> devices, query for services, and read/write characteristics. Utilize these 
> available APIs to build your own application that interacts with a device 
> running Mynewt. An example of an application is one that graphically displays 
> all the available LEDs on a board and allows the user to make them blink in 
> any desired pattern.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-236) Need a simple newt tutorial blink for SIM

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433895#comment-15433895
 ] 

Aditi Hilbert commented on MYNEWT-236:
--

This is done - https://mynewt.apache.org/latest/os/get_started/project_create/

The first project is doing blinky in simulator. Maybe I should rename it as 
"First Project - Blinky in Simulator"?

> Need a simple newt tutorial blink for SIM 
> --
>
> Key: MYNEWT-236
> URL: https://issues.apache.org/jira/browse/MYNEWT-236
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Paul Dietrich
>Assignee: Aditi Hilbert
>
> folks won't have hardware and we need a universal demo that is interesting  
> Consider printing out LED ON or using a beep or something.
> The "first" tutorial with STM32 seems pretty limiting as not many people have 
> access to that board.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-99) Implement LL encryption procedure.

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-99.
-
Resolution: Fixed

> Implement LL encryption procedure.
> --
>
> Key: MYNEWT-99
> URL: https://issues.apache.org/jira/browse/MYNEWT-99
> Project: Mynewt
>  Issue Type: New Feature
>  Components: Nimble
>Affects Versions: v0_8_0_beta1
>Reporter: William San Filippo
>Assignee: Aditi Hilbert
>  Labels: controller, security
> Fix For: v0_8_0_rel
>
>
> We need to implement the LL encryption procedure for security.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MYNEWT-356) BLE Host - Secure Connections Only Mode

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert closed MYNEWT-356.

Resolution: Not A Problem

> BLE Host - Secure Connections Only Mode 
> 
>
> Key: MYNEWT-356
> URL: https://issues.apache.org/jira/browse/MYNEWT-356
> Project: Mynewt
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
> Fix For: v1_0_0_beta1
>
>
> BLE certification requires Central security to support Secure Connections 
> Only mode. Right now if we turn on Secure Connection, all other security 
> modes are also turned on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MYNEWT-357) BLE Host: Central Address Resolution support is needed for certification

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert closed MYNEWT-357.

Resolution: Not A Problem

> BLE Host: Central Address Resolution support is needed for certification
> 
>
> Key: MYNEWT-357
> URL: https://issues.apache.org/jira/browse/MYNEWT-357
> Project: Mynewt
>  Issue Type: Task
>Reporter: Aditi Hilbert
> Fix For: v1_0_0_beta1
>
>
> System Spec reference:[8] 12.4  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MYNEWT-355) Check whether RTX support is implemented in the BLE host controller

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert closed MYNEWT-355.

Resolution: Not A Problem

> Check whether RTX support is implemented in the BLE host controller
> ---
>
> Key: MYNEWT-355
> URL: https://issues.apache.org/jira/browse/MYNEWT-355
> Project: Mynewt
>  Issue Type: Task
>  Components: ble
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
> Fix For: v1_0_0_beta1
>
>
> According to the Test Plan Generator on the Bluetooth SIG site, the L2CAP 
> layer requires Support of RTX timer (L2CAP, 6.2.1) for host controller 
> subsystem certification. Chris will check whether it's in there already.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-357) BLE Host: Central Address Resolution support is needed for certification

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-357:


 Summary: BLE Host: Central Address Resolution support is needed 
for certification
 Key: MYNEWT-357
 URL: https://issues.apache.org/jira/browse/MYNEWT-357
 Project: Mynewt
  Issue Type: Task
Reporter: Aditi Hilbert
 Fix For: v1_0_0_beta1


System Spec reference:  [8] 12.4  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-356) BLE Host - Secure Connections Only Mode

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-356:


 Summary: BLE Host - Secure Connections Only Mode 
 Key: MYNEWT-356
 URL: https://issues.apache.org/jira/browse/MYNEWT-356
 Project: Mynewt
  Issue Type: Task
Reporter: Aditi Hilbert
Assignee: Christopher Collins
 Fix For: v1_0_0_beta1


BLE certification requires Central security to support Secure Connections Only 
mode. Right now if we turn on Secure Connection, all other security modes are 
also turned on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-355) Check whether RTX support is implemented in the BLE host controller

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-355:
-
Assignee: Christopher Collins

> Check whether RTX support is implemented in the BLE host controller
> ---
>
> Key: MYNEWT-355
> URL: https://issues.apache.org/jira/browse/MYNEWT-355
> Project: Mynewt
>  Issue Type: Task
>  Components: ble
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
> Fix For: v1_0_0_beta1
>
>
> According to the Test Plan Generator on the Bluetooth SIG site, the L2CAP 
> layer requires Support of RTX timer (L2CAP, 6.2.1) for host controller 
> subsystem certification. Chris will check whether it's in there already.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-355) Check whether RTX support is implemented in the BLE host controller

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-355:


 Summary: Check whether RTX support is implemented in the BLE host 
controller
 Key: MYNEWT-355
 URL: https://issues.apache.org/jira/browse/MYNEWT-355
 Project: Mynewt
  Issue Type: Task
  Components: ble
Reporter: Aditi Hilbert
 Fix For: v1_0_0_beta1


According to the Test Plan Generator on the Bluetooth SIG site, the L2CAP layer 
requires Support of RTX timer (L2CAP, 6.2.1) for host controller subsystem 
certification. Chris will check whether it's in there already.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-352) Use Go's vendoring support for newtmgr

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384842#comment-15384842
 ] 

Aditi Hilbert commented on MYNEWT-352:
--

INFRA-12307 opened for separating into two repos.

> Use Go's vendoring support for newtmgr
> --
>
> Key: MYNEWT-352
> URL: https://issues.apache.org/jira/browse/MYNEWT-352
> Project: Mynewt
>  Issue Type: Improvement
>Reporter: Aditi Hilbert
> Fix For: v0_10_0
>
>
> Without using the vendoring feature of go, installation errors are seen if 
> the underlying libraries (e.g. Cobra) get updated and are not backwards 
> compatible.
> We first need to separate the newt and newtmgr repos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-352) Use Go's vendoring support for newtmgr

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-352:


 Summary: Use Go's vendoring support for newtmgr
 Key: MYNEWT-352
 URL: https://issues.apache.org/jira/browse/MYNEWT-352
 Project: Mynewt
  Issue Type: Improvement
Reporter: Aditi Hilbert
 Fix For: v0_10_0


Without using the vendoring feature of go, installation errors are seen if the 
underlying libraries (e.g. Cobra) get updated and are not backwards compatible.

We first need to separate the newt and newtmgr repos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-328) Docker container instructions should say to add user to group docker

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-328.
--
Resolution: Fixed

> Docker container instructions should say to add user to group docker
> 
>
> Key: MYNEWT-328
> URL: https://issues.apache.org/jira/browse/MYNEWT-328
> Project: Mynewt
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: WISHLIST
> Environment: Ubuntu 16.04, mynewt 0.9
>Reporter: lloyd konneker
>Assignee: Aditi Hilbert
>Priority: Trivial
>
> If you follow the documented example for installing Docker and the mynewt 
> container, it fails with "Failed to connect to Docker daemon", UNLESS you 
> follow the instructions given at docker.com for adding your user to the group 
> docker.
> I think the documentation could say "Be sure to follow the Docker 
> installation instructions related to group docker.  You must be able to run 
> the docker command from a terminal without prefacing it with sudo."  (An 
> alternative fix is to add "sudo" to the newt script?)
> The instructions at docker.com for Linux installation using Ubuntu have 
> "Optional Configuration" steps.  The step of adding your user to the docker 
> group seems necessary to use newt as described.  Some of the other steps such 
> as "Configure Docker daemon to start on boot" don't seem to be necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-328) Docker container instructions should say to add user to group docker

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345107#comment-15345107
 ] 

Aditi Hilbert commented on MYNEWT-328:
--

These are separate issues. The first one is for the docker daemon. By adding 
your user in the group docker you are making sure you can run any docker 
container as that user. We will make a note of it in the documentation as you 
suggest.

The second one is related to the docker client and container-specific. We are 
aware of this second issue and are working on it. Our container assigns 
ownership to root when it creates the files in the container. It needs to be 
able to detect who issued the docker command for that container and assign 
ownership to that user instead. 

> Docker container instructions should say to add user to group docker
> 
>
> Key: MYNEWT-328
> URL: https://issues.apache.org/jira/browse/MYNEWT-328
> Project: Mynewt
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: WISHLIST
> Environment: Ubuntu 16.04, mynewt 0.9
>Reporter: lloyd konneker
>Assignee: Aditi Hilbert
>Priority: Trivial
>
> If you follow the documented example for installing Docker and the mynewt 
> container, it fails with "Failed to connect to Docker daemon", UNLESS you 
> follow the instructions given at docker.com for adding your user to the group 
> docker.
> I think the documentation could say "Be sure to follow the Docker 
> installation instructions related to group docker.  You must be able to run 
> the docker command from a terminal without prefacing it with sudo."  (An 
> alternative fix is to add "sudo" to the newt script?)
> The instructions at docker.com for Linux installation using Ubuntu have 
> "Optional Configuration" steps.  The step of adding your user to the docker 
> group seems necessary to use newt as described.  Some of the other steps such 
> as "Configure Docker daemon to start on boot" don't seem to be necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MYNEWT-328) Docker container instructions should say to add user to group docker

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345107#comment-15345107
 ] 

Aditi Hilbert edited comment on MYNEWT-328 at 6/22/16 8:31 PM:
---

These are separate issues. The first one is for the docker daemon. By adding 
your user in the group docker you are making sure you can run any docker 
container as that user. We will make a note of it in the documentation as you 
suggest.

The second one is related to the docker client and is container-specific. We 
are aware of this second issue and are working on it. Our container assigns 
ownership to root when it creates the files in the container. It needs to be 
able to detect who issued the docker command for that container and assign 
ownership to that user instead. 


was (Author: aditihilbert):
These are separate issues. The first one is for the docker daemon. By adding 
your user in the group docker you are making sure you can run any docker 
container as that user. We will make a note of it in the documentation as you 
suggest.

The second one is related to the docker client and container-specific. We are 
aware of this second issue and are working on it. Our container assigns 
ownership to root when it creates the files in the container. It needs to be 
able to detect who issued the docker command for that container and assign 
ownership to that user instead. 

> Docker container instructions should say to add user to group docker
> 
>
> Key: MYNEWT-328
> URL: https://issues.apache.org/jira/browse/MYNEWT-328
> Project: Mynewt
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: WISHLIST
> Environment: Ubuntu 16.04, mynewt 0.9
>Reporter: lloyd konneker
>Assignee: Aditi Hilbert
>Priority: Trivial
>
> If you follow the documented example for installing Docker and the mynewt 
> container, it fails with "Failed to connect to Docker daemon", UNLESS you 
> follow the instructions given at docker.com for adding your user to the group 
> docker.
> I think the documentation could say "Be sure to follow the Docker 
> installation instructions related to group docker.  You must be able to run 
> the docker command from a terminal without prefacing it with sudo."  (An 
> alternative fix is to add "sudo" to the newt script?)
> The instructions at docker.com for Linux installation using Ubuntu have 
> "Optional Configuration" steps.  The step of adding your user to the docker 
> group seems necessary to use newt as described.  Some of the other steps such 
> as "Configure Docker daemon to start on boot" don't seem to be necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-321) newt should check existence of repository.yml before trying to parse it

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334591#comment-15334591
 ] 

Aditi Hilbert commented on MYNEWT-321:
--

Install log from a user spews out a barrage of go messages which can be traced 
to the issue of missing repository.yml:

mynewt_arduino_zero
Downloading repository description for mynewt_arduino_zero... success!
mynewt_sodaq_autonomo
Downloading repository description for mynewt_sodaq_autonomo... success!
panic: interface conversion: interface is int, not int64

goroutine 1 [running]:
panic(0x8f7ac0, 0xc820308680)
/usr/local/go/src/runtime/panic.go:481 +0x3e6
mynewt.apache.org/newt/newt/vendor/mynewt.apache.org/newt/yaml.stringValue(0x81e180,
 0xc820201640, 0x0, 0x0)

/home/kees/src/mynewt/dev/go/src/mynewt.apache.org/newt/newt/vendor/mynewt.apache.org/newt/yaml/decode.go:113
 +0x17c
mynewt.apache.org/newt/newt/vendor/mynewt.apache.org/newt/yaml.decodeMappingStart(0xc820292d80,
 0xc8201dedc0, 0xc8202bae80, 0x0, 0x0, 0x0, 0x0, 0x0)

/home/kees/src/mynewt/dev/go/src/mynewt.apache.org/newt/newt/vendor/mynewt.apache.org/newt/yaml/decode.go:214
 +0x138
 



> newt should check existence of repository.yml before trying to parse it
> ---
>
> Key: MYNEWT-321
> URL: https://issues.apache.org/jira/browse/MYNEWT-321
> Project: Mynewt
>  Issue Type: Bug
>  Components: Newt
>Reporter: Marko Kiiskila
>Assignee: Sterling Hughes
>
> If remote repository is missing repository.yml, error message from 'newt 
> install' does not point user to right direction.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-113) Support random private resolvable address in BLE

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-113.
--
Resolution: Implemented

This is completed...being tested at UnPlugFest in HKG

> Support random private resolvable address in BLE
> 
>
> Key: MYNEWT-113
> URL: https://issues.apache.org/jira/browse/MYNEWT-113
> Project: Mynewt
>  Issue Type: Sub-task
>  Components: Nimble
>Reporter: Aditi Hilbert
> Fix For: v0_9_0
>
>
> Random Private Resolvable– Used in bonded devices and requires the Identity 
> Resolving Key (IRK) be shared during Phase 3 of the pairing procedure. This 
> changes periodically based on a timer or other method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-112) Support random non-resolvable private address

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-112.
--
Resolution: Implemented

> Support random non-resolvable private address
> -
>
> Key: MYNEWT-112
> URL: https://issues.apache.org/jira/browse/MYNEWT-112
> Project: Mynewt
>  Issue Type: Sub-task
>  Components: Nimble
>Reporter: Aditi Hilbert
> Fix For: v0_10_0
>
>
> Random Private Non-Resolvable– Shared between bonded devices for use during 
> reconnection. This changes with each connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-305) Newt does not display possible values for target attributes "features", "cflags", "lflags", and "build_profile"

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-305:
-
Affects Version/s: 0.9.0
   0.8.0
  Description: 
Newt is supposed to display all the existing values for a target variable 
(attribute) when the user hits return after that variable. For example, for my 
target named "primoble" it displays the following possible bsp's.

$ newt target set primoble bsp
Valid values for target variable "target.bsp":
@apache-mynewt-core/hw/bsp/bmd300eval
@apache-mynewt-core/hw/bsp/nrf51dk
@apache-mynewt-core/hw/bsp/nrf52pdk
@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
@apache-mynewt-core/hw/bsp/nrf51-arduino_101
@apache-mynewt-core/hw/bsp/native
@apache-mynewt-core/hw/bsp/nrf51dk-16kbram
@apache-mynewt-core/hw/bsp/arduino_primo_nrf52
@apache-mynewt-core/hw/bsp/nrf52dk

However, features available for the target are not displayed:
$ newt target set primoble features
Valid values for target variable "target.features":
Error: Unknown target variable: "target.features"

For "features", valid values for the defined bsp should be displayed. If the 
bsp is not defined for the target, all possible values (such as 
"openocd_debug", "arduino_zero_pro" etc.) should be displayed with a statement 
"Set the bsp for the target to see valid features for the bsp").

The possible values should be displayed for cflags (-DSTATS_NAME_ENABLE, 
-DLOG_LEVEL, -DBLETEST, ...), lflags (don't know the values), and build_profile 
('optimized', 'debug') as well instead of the following error.

$ newt target set primoble cflags
Valid values for target variable "target.cflags":
Error: Unknown target variable: "target.cflags"




  Component/s: Newt
  Summary: Newt does not display possible values for target 
attributes "features", "cflags", "lflags", and "build_profile"   (was: List of 
all possible values for target attribute not displayed for "feature)

> Newt does not display possible values for target attributes "features", 
> "cflags", "lflags", and "build_profile" 
> 
>
> Key: MYNEWT-305
> URL: https://issues.apache.org/jira/browse/MYNEWT-305
> Project: Mynewt
>  Issue Type: Bug
>  Components: Newt
>Affects Versions: 0.8.0, 0.9.0
>Reporter: Aditi Hilbert
>
> Newt is supposed to display all the existing values for a target variable 
> (attribute) when the user hits return after that variable. For example, for 
> my target named "primoble" it displays the following possible bsp's.
> $ newt target set primoble bsp
> Valid values for target variable "target.bsp":
> @apache-mynewt-core/hw/bsp/bmd300eval
> @apache-mynewt-core/hw/bsp/nrf51dk
> @apache-mynewt-core/hw/bsp/nrf52pdk
> @apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
> @apache-mynewt-core/hw/bsp/nrf51-arduino_101
> @apache-mynewt-core/hw/bsp/native
> @apache-mynewt-core/hw/bsp/nrf51dk-16kbram
> @apache-mynewt-core/hw/bsp/arduino_primo_nrf52
> @apache-mynewt-core/hw/bsp/nrf52dk
> However, features available for the target are not displayed:
> $ newt target set primoble features
> Valid values for target variable "target.features":
> Error: Unknown target variable: "target.features"
> For "features", valid values for the defined bsp should be displayed. If the 
> bsp is not defined for the target, all possible values (such as 
> "openocd_debug", "arduino_zero_pro" etc.) should be displayed with a 
> statement "Set the bsp for the target to see valid features for the bsp").
> The possible values should be displayed for cflags (-DSTATS_NAME_ENABLE, 
> -DLOG_LEVEL, -DBLETEST, ...), lflags (don't know the values), and 
> build_profile ('optimized', 'debug') as well instead of the following error.
> $ newt target set primoble cflags
> Valid values for target variable "target.cflags":
> Error: Unknown target variable: "target.cflags"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-305) List of all possible values for target attribute not displayed for "feature

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-305:


 Summary: List of all possible values for target attribute not 
displayed for "feature
 Key: MYNEWT-305
 URL: https://issues.apache.org/jira/browse/MYNEWT-305
 Project: Mynewt
  Issue Type: Bug
Reporter: Aditi Hilbert






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-267) BLE - make TX power configurable

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-267:
-
Fix Version/s: (was: v0_8_0_rel)
   v0_9_0_rel

> BLE - make TX power configurable
> 
>
> Key: MYNEWT-267
> URL: https://issues.apache.org/jira/browse/MYNEWT-267
> Project: Mynewt
>  Issue Type: New Feature
>Reporter: Aditi Hilbert
>Assignee: William San Filippo
> Fix For: v0_9_0_rel
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-61) BLE Host - Security Manager - Just Works

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-61.
-
Resolution: Fixed

> BLE Host - Security Manager - Just Works
> 
>
> Key: MYNEWT-61
> URL: https://issues.apache.org/jira/browse/MYNEWT-61
> Project: Mynewt
>  Issue Type: New Feature
>  Components: Nimble
>Reporter: Christopher Collins
>Assignee: Aditi Hilbert
> Fix For: v0_8_0_rel
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-265) BLE - advertise iBeacon

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-265.
--
Resolution: Fixed

> BLE - advertise iBeacon
> ---
>
> Key: MYNEWT-265
> URL: https://issues.apache.org/jira/browse/MYNEWT-265
> Project: Mynewt
>  Issue Type: New Feature
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
> Fix For: v0_8_0_rel
>
>
> Uses only the advertisement channel. 
> 9 bytes of constant preamble, then the Proximity UUID (16 bytes), Major (2 
> bytes) and Minor values (2 bytes). 
> The final byte in the packet is the RSSI measured at 1 meter from the device 
> - used to calculate distance from the iBeacon.
> Also covers adjusting the advertisement rate (which is already available)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-265) BLE - advertise iBeacon

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262680#comment-15262680
 ] 

Aditi Hilbert commented on MYNEWT-265:
--

Chris has implemented it. Tutorial being added.

> BLE - advertise iBeacon
> ---
>
> Key: MYNEWT-265
> URL: https://issues.apache.org/jira/browse/MYNEWT-265
> Project: Mynewt
>  Issue Type: New Feature
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
> Fix For: v0_8_0_rel
>
>
> Uses only the advertisement channel. 
> 9 bytes of constant preamble, then the Proximity UUID (16 bytes), Major (2 
> bytes) and Minor values (2 bytes). 
> The final byte in the packet is the RSSI measured at 1 meter from the device 
> - used to calculate distance from the iBeacon.
> Also covers adjusting the advertisement rate (which is already available)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MYNEWT-286) nRF51 crashes when receiving large(ish) ACL packet

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert reassigned MYNEWT-286:


Assignee: William San Filippo

> nRF51 crashes when receiving large(ish) ACL packet
> --
>
> Key: MYNEWT-286
> URL: https://issues.apache.org/jira/browse/MYNEWT-286
> Project: Mynewt
>  Issue Type: Bug
>  Components: Nimble
> Environment: nRF51 USB dongle or devkit
>Reporter: Johan Hedberg
>Assignee: William San Filippo
>
> The default L2CAP MTUs of ATT and legacy SMP fixed channels is 23. This works 
> fine. As soon as LE Secure Connections SMP is attempted (MTU of 65) and the 
> public key sent the controller stops responding (gdb doesn't work. needs a 
> hard power cycle).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-123) Send email to US govt. notifying our crypto code cryptography qualifies for the TSU exception

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-123.
--
Resolution: Fixed

email sent

> Send email to US govt. notifying our crypto code cryptography qualifies for 
> the TSU exception
> -
>
> Key: MYNEWT-123
> URL: https://issues.apache.org/jira/browse/MYNEWT-123
> Project: Mynewt
>  Issue Type: Sub-task
>  Components: Image Mgmt
>Reporter: Aditi Hilbert
>Assignee: Aditi Hilbert
> Fix For: v0_8_0_rel
>
>
> Once the applicable source code is linked from the ASF-wide export page, we 
> have to send the following email to
> TO: cr...@bis.doc.gov
>e...@nsa.gov
>CC: d...@mynewt.incubator.apache.org 
>   legal-arch...@apache.org
> 
> SUBMISSION TYPE:  TSU
> SUBMITTED BY: {PMC member sending email}
> SUBMITTED FOR:Apache Software Foundation
> POINT OF CONTACT: Secretary, Apache Software Foundation
> FAX:  +1-919-573-9199
> MANUFACTURER(S)   "Apache Software Foundation.”
> PRODUCT NAME/MODEL #: Apache Mynewt Larva 
>   Code found at: 
> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git (currently 
> in branch named “develop” under  libs/mbedtls) 
> ECCN: 5D002
> NOTIFICATION: http://www.apache.org/licenses/exports/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-280) DAC HAL for Arduino Zero

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-280:


 Summary: DAC HAL for Arduino Zero
 Key: MYNEWT-280
 URL: https://issues.apache.org/jira/browse/MYNEWT-280
 Project: Mynewt
  Issue Type: Task
Reporter: Aditi Hilbert
Assignee: Paul Dietrich
 Fix For: v0_8_0_rel






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-107) HAL for RTC

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-107:
-
Fix Version/s: (was: v0_8_0_rel)
   v0_9_0_beta1

> HAL for RTC
> ---
>
> Key: MYNEWT-107
> URL: https://issues.apache.org/jira/browse/MYNEWT-107
> Project: Mynewt
>  Issue Type: Sub-task
>  Components: HAL, OS
>Reporter: Aditi Hilbert
>Assignee: Marko Kiiskila
>Priority: Minor
> Fix For: v0_9_0_beta1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-62) BLE Host - Security Manager - IO Capabilities

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-62:

Fix Version/s: (was: v0_8_0_rel)
   v0_9_0_rel

> BLE Host - Security Manager - IO Capabilities
> -
>
> Key: MYNEWT-62
> URL: https://issues.apache.org/jira/browse/MYNEWT-62
> Project: Mynewt
>  Issue Type: New Feature
>  Components: Nimble
>Reporter: Christopher Collins
>Assignee: Christopher Collins
> Fix For: v0_9_0_rel
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-13) NFFS does not work on STM32F3

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-13:

Fix Version/s: (was: v0_8_0_rel)
   v0_9_0_beta1

> NFFS does not work on STM32F3
> -
>
> Key: MYNEWT-13
> URL: https://issues.apache.org/jira/browse/MYNEWT-13
> Project: Mynewt
>  Issue Type: Bug
>  Components: NFFS
>Reporter: Marko Kiiskila
>Assignee: Christopher Collins
>Priority: Minor
> Fix For: v0_9_0_beta1
>
>
> STM32F3 flash writes are done 2 bytes at a time. NFFS should take into 
> account alignment restrictions underlying storage has.
> E.g. add alignment requirement in struct hal_flash. Add an HAL flash API call 
> to query this. NFFS would then use this when writing/reading blocks of data 
> from flash.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-278) "newt test" hangs when executing unit tests for apps/blinky

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220847#comment-15220847
 ] 

Aditi Hilbert commented on MYNEWT-278:
--

Unit tests were not available. Now it responds with the correct message.

> "newt test" hangs when executing unit tests for apps/blinky
> ---
>
> Key: MYNEWT-278
> URL: https://issues.apache.org/jira/browse/MYNEWT-278
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>
> Tried testing apps/blinky which is a pkg.
> $ newt test apps/blinky
> Testing package apps/blinky
> Warning: API conflict: console (libs/console/full <-> libs/console/stub)
> Compiling hal_cputime.c
> Compiling hal_flash.c
> ...
> Archiving util.a
> Linking test_blinky
> Executing test: 
> /Users/aditihilbert/dev/aditi/bin/unittest/apps/blinky/test_blinky
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MYNEWT-278) "newt test" hangs when executing unit tests for apps/blinky

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert closed MYNEWT-278.


> "newt test" hangs when executing unit tests for apps/blinky
> ---
>
> Key: MYNEWT-278
> URL: https://issues.apache.org/jira/browse/MYNEWT-278
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
>
> Tried testing apps/blinky which is a pkg.
> $ newt test apps/blinky
> Testing package apps/blinky
> Warning: API conflict: console (libs/console/full <-> libs/console/stub)
> Compiling hal_cputime.c
> Compiling hal_flash.c
> ...
> Archiving util.a
> Linking test_blinky
> Executing test: 
> /Users/aditihilbert/dev/aditi/bin/unittest/apps/blinky/test_blinky
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-278) "newt test" hangs when executing unit tests for apps/blinky

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-278.
--
Resolution: Fixed
  Assignee: Christopher Collins

> "newt test" hangs when executing unit tests for apps/blinky
> ---
>
> Key: MYNEWT-278
> URL: https://issues.apache.org/jira/browse/MYNEWT-278
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
>
> Tried testing apps/blinky which is a pkg.
> $ newt test apps/blinky
> Testing package apps/blinky
> Warning: API conflict: console (libs/console/full <-> libs/console/stub)
> Compiling hal_cputime.c
> Compiling hal_flash.c
> ...
> Archiving util.a
> Linking test_blinky
> Executing test: 
> /Users/aditihilbert/dev/aditi/bin/unittest/apps/blinky/test_blinky
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-279) "newt test" unclear error message for unavailable unit test

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert resolved MYNEWT-279.
--
Resolution: Fixed

> "newt test" unclear error message for unavailable unit test
> ---
>
> Key: MYNEWT-279
> URL: https://issues.apache.org/jira/browse/MYNEWT-279
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>
> $ newt test targets/myble2
> Testing package targets/myble2
> Linking test_myble2
> Undefined symbols for architecture i386:
>   "_main", referenced from:
>  implicit entry/start for main executable
> ld: symbol(s) not found for architecture i386
> collect2: error: ld returned 1 exit status
> Error: Test failure(s):
> Passed tests: []
> Failed tests: [targets/myble2]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MYNEWT-279) "newt test" unclear error message for unavailable unit test

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert closed MYNEWT-279.

Assignee: Christopher Collins

> "newt test" unclear error message for unavailable unit test
> ---
>
> Key: MYNEWT-279
> URL: https://issues.apache.org/jira/browse/MYNEWT-279
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
>
> $ newt test targets/myble2
> Testing package targets/myble2
> Linking test_myble2
> Undefined symbols for architecture i386:
>   "_main", referenced from:
>  implicit entry/start for main executable
> ld: symbol(s) not found for architecture i386
> collect2: error: ld returned 1 exit status
> Error: Test failure(s):
> Passed tests: []
> Failed tests: [targets/myble2]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-279) "newt test" unclear error message for unavailable unit test

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220841#comment-15220841
 ] 

Aditi Hilbert commented on MYNEWT-279:
--

The message is clear now. For example:

$ newt test apps/blinky
Error: Package apps/blinky contains no unit tests


> "newt test" unclear error message for unavailable unit test
> ---
>
> Key: MYNEWT-279
> URL: https://issues.apache.org/jira/browse/MYNEWT-279
> Project: Mynewt
>  Issue Type: Bug
>Reporter: Aditi Hilbert
>
> $ newt test targets/myble2
> Testing package targets/myble2
> Linking test_myble2
> Undefined symbols for architecture i386:
>   "_main", referenced from:
>  implicit entry/start for main executable
> ld: symbol(s) not found for architecture i386
> collect2: error: ld returned 1 exit status
> Error: Test failure(s):
> Passed tests: []
> Failed tests: [targets/myble2]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-279) "newt test" unclear error message for unavailable unit test

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-279:


 Summary: "newt test" unclear error message for unavailable unit 
test
 Key: MYNEWT-279
 URL: https://issues.apache.org/jira/browse/MYNEWT-279
 Project: Mynewt
  Issue Type: Bug
Reporter: Aditi Hilbert


$ newt test targets/myble2
Testing package targets/myble2
Linking test_myble2
Undefined symbols for architecture i386:
  "_main", referenced from:
 implicit entry/start for main executable
ld: symbol(s) not found for architecture i386
collect2: error: ld returned 1 exit status
Error: Test failure(s):
Passed tests: []
Failed tests: [targets/myble2]




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-278) "newt test" hangs when executing unit tests for apps/blinky

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-278:


 Summary: "newt test" hangs when executing unit tests for 
apps/blinky
 Key: MYNEWT-278
 URL: https://issues.apache.org/jira/browse/MYNEWT-278
 Project: Mynewt
  Issue Type: Bug
Reporter: Aditi Hilbert


Tried testing apps/blinky which is a pkg.

$ newt test apps/blinky
Testing package apps/blinky
Warning: API conflict: console (libs/console/full <-> libs/console/stub)
Compiling hal_cputime.c
Compiling hal_flash.c
...
Archiving util.a
Linking test_blinky
Executing test: 
/Users/aditihilbert/dev/aditi/bin/unittest/apps/blinky/test_blinky
...




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWTDOC-72) Describe bootloader overview and functions

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWTDOC-72:
--

 Summary: Describe bootloader overview and functions
 Key: MYNEWTDOC-72
 URL: https://issues.apache.org/jira/browse/MYNEWTDOC-72
 Project: MyNewt Docs
  Issue Type: Task
Reporter: Aditi Hilbert






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MYNEWT-150) Describe bootloader overview and functions

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert closed MYNEWT-150.

Resolution: Duplicate

new ticket opened under MYNEWTDOC

> Describe bootloader overview and functions
> --
>
> Key: MYNEWT-150
> URL: https://issues.apache.org/jira/browse/MYNEWT-150
> Project: Mynewt
>  Issue Type: Sub-task
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
>  Labels: docs
> Fix For: v0_8_0_rel
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-65) BLE tutorial: Nimble configuration and initialization

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-253 to MYNEWTDOC-65:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-65  (was: MYNEWT-253)
  Project: MyNewt Docs  (was: Mynewt)

> BLE tutorial: Nimble configuration and initialization
> -
>
> Key: MYNEWTDOC-65
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-65
> Project: MyNewt Docs
>  Issue Type: Improvement
>Reporter: Aditi Hilbert
>Assignee: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-16) Documentation of OS Tutorials: How to use memory pools and heap, and how to layout memory on embedded systems

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-197 to MYNEWTDOC-16:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-16  (was: MYNEWT-197)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation of OS Tutorials: How to use memory pools and heap, and how to 
> layout memory on embedded systems
> -
>
> Key: MYNEWTDOC-16
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-16
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-62) Doc review: Blinky on Olimex

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-250 to MYNEWTDOC-62:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-62  (was: MYNEWT-250)
  Project: MyNewt Docs  (was: Mynewt)

> Doc review: Blinky on Olimex
> 
>
> Key: MYNEWTDOC-62
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-62
> Project: MyNewt Docs
>  Issue Type: Improvement
>Reporter: Aditi Hilbert
>Assignee: Paul Dietrich
>  Labels: docs
>
> Focus is on completeness and accuracy of content (esp. wrt newt)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-12) Tutorial on creating a shell command

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-179 to MYNEWTDOC-12:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-12  (was: MYNEWT-179)
  Project: MyNewt Docs  (was: Mynewt)

> Tutorial on creating a shell command
> 
>
> Key: MYNEWTDOC-12
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-12
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Sterling Hughes
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-67) OS task minor cleanup

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-187 to MYNEWTDOC-67:
---

Fix Version/s: (was: v0_8_0_beta2)
Affects Version/s: (was: v0_8_0_beta1)
  Key: MYNEWTDOC-67  (was: MYNEWT-187)
  Project: MyNewt Docs  (was: Mynewt)

> OS task minor cleanup
> -
>
> Key: MYNEWTDOC-67
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-67
> Project: MyNewt Docs
>  Issue Type: Improvement
>Reporter: William San Filippo
>Assignee: William San Filippo
>Priority: Trivial
>  Labels: docs
>
> While writing the OS documentation I noticed a few minor things with 
> os_task.h.
> 1) The padding for struct os_task_info is slightly off and the structure can 
> be made slightly smaller by making the flags 8 bits.
> 2) We no longer use OS_TASK_NAME_SIZE.
> For #1, all we need to do is mke t_flags in struct os_task 8 bits. We can 
> then remove the padding from os_task_info.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-9) Documentation for Newtmgr tutorials: Clean up Slinky

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-214 to MYNEWTDOC-9:
--

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-9  (was: MYNEWT-214)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for Newtmgr tutorials: Clean up Slinky
> 
>
> Key: MYNEWTDOC-9
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-9
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Paul Dietrich
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-26) Documentation: HAL CPU Timer

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-194 to MYNEWTDOC-26:
---

Fix Version/s: (was: v0_8_0_beta2)
  Key: MYNEWTDOC-26  (was: MYNEWT-194)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation: HAL CPU Timer
> 
>
> Key: MYNEWTDOC-26
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-26
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-1) Need Mynewt Wiki setup, and page per-BSP on Mynewt Wiki

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-51 to MYNEWTDOC-1:
-

Fix Version/s: (was: v0_8_0_beta2)
  Component/s: (was: Documentation)
   (was: Site)
  Key: MYNEWTDOC-1  (was: MYNEWT-51)
  Project: MyNewt Docs  (was: Mynewt)

> Need Mynewt Wiki setup, and page per-BSP on Mynewt Wiki
> ---
>
> Key: MYNEWTDOC-1
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-1
> Project: MyNewt Docs
>  Issue Type: New Feature
>Reporter: Sterling Hughes
>Assignee: Aditi Hilbert
>  Labels: docs
>
> We should setup a Mynewt Wiki for subjects that are not suitable for the 
> standard documentation, but useful as developers modify things.
> The first thing we need to put into this is a page per-BSP, that gives 
> instructions on: 
> - Toolchain setup & installation 
> - BSP definitions and flash layout
> - Errata and notes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-69) Document supported versions of tool chain for each supported devboard in documentation

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-19 to MYNEWTDOC-69:
--

Fix Version/s: (was: v0_8_0_beta2)
  Component/s: (was: Documentation)
  Key: MYNEWTDOC-69  (was: MYNEWT-19)
  Project: MyNewt Docs  (was: Mynewt)

> Document supported versions of tool chain for each supported devboard in 
> documentation
> --
>
> Key: MYNEWTDOC-69
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-69
> Project: MyNewt Docs
>  Issue Type: Improvement
>Reporter: Sterling Hughes
>Assignee: Aditi Hilbert
>  Labels: docs
>
> Right now toolchain support is documented in Blinky, the first project 
> (http://mynewt.incubator.apache.org/get_started/project1/).  
> This document has instructions on how to download the toolchain using either 
> apt-get or homebrew (Mac OS X.)  Which are useful in a getting started guide, 
> however, for every board we support, I think we need one page that lists: 
> - What are the required versions of:
>   - Compiler (e.g. arm-none-eabi-gcc v4.1-4.3) 
>   - Debugger
> - Both the JTAG / ICE and GDB versions
>   - Newt 
> - An example target that can create a binary for that board 
> - Optional Additional Information:
>   - Picture of how to connect JTAG header
>   - Links and installation guide for the necessary toolchain support



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-32) Documentation HAL Overview

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-191 to MYNEWTDOC-32:
---

 Assignee: (was: Paul Dietrich)
Fix Version/s: (was: v0_8_0_beta2)
  Key: MYNEWTDOC-32  (was: MYNEWT-191)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation HAL Overview
> --
>
> Key: MYNEWTDOC-32
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-32
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-58) Always anchor the ASF footer (language + icons) to the bottom of documentation page

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-157 to MYNEWTDOC-58:
---

 Assignee: (was: Todd Mitton)
Fix Version/s: (was: v0_8_0_beta2)
  Key: MYNEWTDOC-58  (was: MYNEWT-157)
  Project: MyNewt Docs  (was: Mynewt)

> Always anchor the ASF footer (language + icons) to the bottom of 
> documentation page
> ---
>
> Key: MYNEWTDOC-58
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-58
> Project: MyNewt Docs
>  Issue Type: Improvement
>Reporter: Aditi Hilbert
>  Labels: docs
>
> No matter what the size of the browser window, the ASF footer should always 
> be anchored to the bottom of the page. The lengthier of the two items above 
> it - the navigation bar on the left and the content on the right - determines 
> the size of the boxes and scroll bar. There should be only a single scroll 
> bar down the page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-35) Documentation for OS Tutorials: How to write a test utility for a pkg

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-210 to MYNEWTDOC-35:
---

 Assignee: (was: Paul Dietrich)
Fix Version/s: (was: v0_8_0_beta2)
  Key: MYNEWTDOC-35  (was: MYNEWT-210)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for OS Tutorials: How to write a test utility for a pkg
> -
>
> Key: MYNEWTDOC-35
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-35
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-29) Documentation for BLE Tutorials: Connect to a remote device, and read attributes using the Bluetooth stack

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-200 to MYNEWTDOC-29:
---

Affects Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-29  (was: MYNEWT-200)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for BLE Tutorials: Connect to a remote device, and read 
> attributes using the Bluetooth stack
> --
>
> Key: MYNEWTDOC-29
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-29
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-31) Documentation for Newtmgr tutorials: Access a device using Newtmgr over Serial

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-207 to MYNEWTDOC-31:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-31  (was: MYNEWT-207)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for Newtmgr tutorials: Access a device using Newtmgr over Serial
> --
>
> Key: MYNEWTDOC-31
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-31
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-30) Documentation for OS Tutorials: Quiz buzzer

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-212 to MYNEWTDOC-30:
---

Fix Version/s: (was: v0_9_0_beta1)
  Key: MYNEWTDOC-30  (was: MYNEWT-212)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for OS Tutorials: Quiz buzzer
> ---
>
> Key: MYNEWTDOC-30
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-30
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>
> Scan the push button input and display the corresponding number on a display



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-25) Documentation for OS Tutorials: Connect a digital sensor to a board

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-211 to MYNEWTDOC-25:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-25  (was: MYNEWT-211)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for OS Tutorials: Connect a digital sensor to a board
> ---
>
> Key: MYNEWTDOC-25
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-25
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>
> Suggested board: Arduino zero
> via GPIO or UART
> Detect and log level changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-27) Documentation for Newtmgr tutorials: Add a custom Newtmgr command

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-209 to MYNEWTDOC-27:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-27  (was: MYNEWT-209)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for Newtmgr tutorials: Add a custom Newtmgr command
> -
>
> Key: MYNEWTDOC-27
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-27
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Paul Dietrich
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-2) In "Community" section need to have a sub-page that describes how to submit patches

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-52 to MYNEWTDOC-2:
-

Fix Version/s: (was: v0_8_0_beta2)
  Component/s: (was: Site)
  Key: MYNEWTDOC-2  (was: MYNEWT-52)
  Project: MyNewt Docs  (was: Mynewt)

> In "Community" section need to have a sub-page that describes how to submit 
> patches
> ---
>
> Key: MYNEWTDOC-2
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-2
> Project: MyNewt Docs
>  Issue Type: New Feature
>Reporter: Sterling Hughes
>Assignee: Sterling Hughes
>  Labels: docs
>
> We need to have a document on submitting patches and features back to Mynewt, 
> either using patches to dev@ mailing list or Github (if we support this 
> option.) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-33) Documentation for Newtmgr tutorials: Access a device using Newtmgr over BLE

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-206 to MYNEWTDOC-33:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-33  (was: MYNEWT-206)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for Newtmgr tutorials: Access a device using Newtmgr over BLE
> ---
>
> Key: MYNEWTDOC-33
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-33
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-61) Doc review: Blinky on STM32F303

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-251 to MYNEWTDOC-61:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-61  (was: MYNEWT-251)
  Project: MyNewt Docs  (was: Mynewt)

> Doc review: Blinky on STM32F303
> ---
>
> Key: MYNEWTDOC-61
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-61
> Project: MyNewt Docs
>  Issue Type: Improvement
>Reporter: Aditi Hilbert
>Assignee: Paul Dietrich
>  Labels: docs
>
> Focus is on completeness and accuracy of content (esp. wrt newt)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-18) Create BLE sections in docs

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-221 to MYNEWTDOC-18:
---

Fix Version/s: (was: v0_8_0_beta2)
  Key: MYNEWTDOC-18  (was: MYNEWT-221)
  Project: MyNewt Docs  (was: Mynewt)

> Create BLE sections in docs
> ---
>
> Key: MYNEWTDOC-18
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-18
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-11) Newt introduction

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-235 to MYNEWTDOC-11:
---

 Assignee: (was: Jules S. Damji)
Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-11  (was: MYNEWT-235)
  Project: MyNewt Docs  (was: Mynewt)

> Newt introduction
> -
>
> Key: MYNEWTDOC-11
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-11
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-14) Tutorial: How to define new OS stat and turn collection on

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-256 to MYNEWTDOC-14:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-14  (was: MYNEWT-256)
  Project: MyNewt Docs  (was: Mynewt)

> Tutorial: How to define new OS stat and turn collection on
> --
>
> Key: MYNEWTDOC-14
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-14
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-39) OS Tutorial: How to link to and use third-party packages from an external source

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-260 to MYNEWTDOC-39:
---

 Assignee: (was: Paul Dietrich)
Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-39  (was: MYNEWT-260)
  Project: MyNewt Docs  (was: Mynewt)

> OS Tutorial: How to link to and use third-party packages from an external 
> source
> 
>
> Key: MYNEWTDOC-39
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-39
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-28) Tutorials: Trigger an LED on an Arduino board by using a high sensitivity moisture sensor to detect changes

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-220 to MYNEWTDOC-28:
---

Fix Version/s: (was: v1_0_0_beta1)
  Key: MYNEWTDOC-28  (was: MYNEWT-220)
  Project: MyNewt Docs  (was: Mynewt)

> Tutorials: Trigger an LED on an Arduino board by using a high sensitivity 
> moisture sensor to detect changes
> ---
>
> Key: MYNEWTDOC-28
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-28
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-4) Documentation of OS Tutorials: Initialize the console and shell, and log messages to the console

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-204 to MYNEWTDOC-4:
--

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-4  (was: MYNEWT-204)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation of OS Tutorials: Initialize the console and shell, and log 
> messages to the console
> 
>
> Key: MYNEWTDOC-4
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-4
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Marko Kiiskila
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-5) Documentation for Newt tutorials: Defining a target

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-234 to MYNEWTDOC-5:
--

Key: MYNEWTDOC-5  (was: MYNEWT-234)
Project: MyNewt Docs  (was: Mynewt)

> Documentation for Newt tutorials: Defining a target
> ---
>
> Key: MYNEWTDOC-5
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-5
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-63) Building and contributing to newt should really be an Appendix

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-50 to MYNEWTDOC-63:
--

Fix Version/s: (was: v0_8_0_beta2)
  Component/s: (was: Documentation)
  Key: MYNEWTDOC-63  (was: MYNEWT-50)
  Project: MyNewt Docs  (was: Mynewt)

> Building and contributing to newt should really be an Appendix
> --
>
> Key: MYNEWTDOC-63
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-63
> Project: MyNewt Docs
>  Issue Type: Improvement
>Reporter: Sterling Hughes
>Assignee: Aditi Hilbert
>  Labels: docs
>
> Right now the documentation on the newt tool starts with instructions on how 
> to download and build newt from go source.
> During release, newt will be pre-built from source for all major platforms 
> and distributed (primarily) as a binary.  This documentation should be moved 
> into an Appendix. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-37) Add content to core OS documentation

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-142 to MYNEWTDOC-37:
---

Fix Version/s: (was: v0_8_0_beta2)
  Key: MYNEWTDOC-37  (was: MYNEWT-142)
  Project: MyNewt Docs  (was: Mynewt)

> Add content to core OS documentation
> 
>
> Key: MYNEWTDOC-37
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-37
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-36) Documentation: BLE stats and logs

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-258 to MYNEWTDOC-36:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-36  (was: MYNEWT-258)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation: BLE stats and logs
> -
>
> Key: MYNEWTDOC-36
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-36
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>
> list of stats - what, why (use)
> config options



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-40) Documentation: logs and stats module

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-255 to MYNEWTDOC-40:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-40  (was: MYNEWT-255)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation: logs and stats module
> 
>
> Key: MYNEWTDOC-40
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-40
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>
> enabling them
> cflags
> how they work



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-66) Doc review: Get Started

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-249 to MYNEWTDOC-66:
---

Fix Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-66  (was: MYNEWT-249)
  Project: MyNewt Docs  (was: Mynewt)

> Doc review: Get Started
> ---
>
> Key: MYNEWTDOC-66
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-66
> Project: MyNewt Docs
>  Issue Type: Improvement
>Reporter: Aditi Hilbert
>Assignee: Christopher Collins
>  Labels: docs
>
> All four tutorials under it:
>  - Installing Native tools
>  - Creating your first project
>  - Installing Cross tools for ARM
>  - Blinky, the first HW in simulation
> I may reorganize the material to make it more appealing/less daunting to new 
> comers. So this ticket is mainly about the completeness and accuracy of the 
> content.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-17) Documentation for OS Tutorials: Adding an air quality sensor

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-237 to MYNEWTDOC-17:
---

Fix Version/s: (was: v0_8_0_beta2)
  Key: MYNEWTDOC-17  (was: MYNEWT-237)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for OS Tutorials: Adding an air quality sensor
> 
>
> Key: MYNEWTDOC-17
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-17
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>Assignee: Marko Kiiskila
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Moved] (MYNEWTDOC-24) Documentation for OS Tutorials: Read & write files with the FS APIs

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWTDOC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert moved MYNEWT-203 to MYNEWTDOC-24:
---

Affects Version/s: (was: v0_8_0_rel)
  Key: MYNEWTDOC-24  (was: MYNEWT-203)
  Project: MyNewt Docs  (was: Mynewt)

> Documentation for OS Tutorials:  Read & write files with the FS APIs
> 
>
> Key: MYNEWTDOC-24
> URL: https://issues.apache.org/jira/browse/MYNEWTDOC-24
> Project: MyNewt Docs
>  Issue Type: Task
>Reporter: Aditi Hilbert
>  Labels: docs
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)