[jira] [Commented] (MYNEWT-677) NMP: Include next_index in log show response
[
https://issues.apache.org/jira/browse/MYNEWT-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930605#comment-15930605
]
ASF subversion and git services commented on MYNEWT-677:
Commit d7a9e96a9f17270d371ce421697c4407b1647bf4 in incubator-mynewt-core's
branch refs/heads/develop from [~ccollins476]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=d7a9e96
]
MYNEWT-677 NMP: Include next_index in log show rsp
The next_index value (index of next log entry to be written) is useful
for determining if a device's flash has been wiped since the last time
logs were scoured.
The new value is at the top-level of the log show response with the
following name: next_index.
> NMP: Include next_index in log show response
>
>
> Key: MYNEWT-677
> URL: https://issues.apache.org/jira/browse/MYNEWT-677
> Project: Mynewt
> Issue Type: Bug
> Components: Newtmgr
>Reporter: Christopher Collins
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> The next_index value (index of next log entry to be written) is useful for
> determining if a device's flash has been wiped since the last time logs were
> scoured.
> The new value is at the top-level of the log show response with the following
> name: {{next_index}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MYNEWT-676) Reboot counter value inconsistent
[ https://issues.apache.org/jira/browse/MYNEWT-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930603#comment-15930603 ] ASF subversion and git services commented on MYNEWT-676: Commit f23fbe77dabe3226359c7790bbdd3d7847ee9a0a in incubator-mynewt-core's branch refs/heads/develop from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=f23fbe7 ] MYNEWT-676 - Oops, fix broken apps. > Reboot counter value inconsistent > - > > Key: MYNEWT-676 > URL: https://issues.apache.org/jira/browse/MYNEWT-676 > Project: Mynewt > Issue Type: Bug >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The value that gets logged to the reboot log is one greater than the actual > reboot counter (the value retrieved via "newtmgr config reboot/reboot_cnt"). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MYNEWT-677) NMP: Include next_index in log show response
[
https://issues.apache.org/jira/browse/MYNEWT-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Collins updated MYNEWT-677:
---
Description:
The next_index value (index of next log entry to be written) is useful for
determining if a device's flash has been wiped since the last time logs were
scoured.
The new value is at the top-level of the log show response with the following
name: {{next_index}}.
was:The next_index value (index of next log entry to be written) is useful
for determining if a device's flash has been wiped since the last time logs
were scoured.
> NMP: Include next_index in log show response
>
>
> Key: MYNEWT-677
> URL: https://issues.apache.org/jira/browse/MYNEWT-677
> Project: Mynewt
> Issue Type: Bug
> Components: Newtmgr
>Reporter: Christopher Collins
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> The next_index value (index of next log entry to be written) is useful for
> determining if a device's flash has been wiped since the last time logs were
> scoured.
> The new value is at the top-level of the log show response with the following
> name: {{next_index}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MYNEWT-677) NMP: Include next_index in log show response
Christopher Collins created MYNEWT-677: -- Summary: NMP: Include next_index in log show response Key: MYNEWT-677 URL: https://issues.apache.org/jira/browse/MYNEWT-677 Project: Mynewt Issue Type: Bug Components: Newtmgr Reporter: Christopher Collins Assignee: Christopher Collins Fix For: v1_1_0_rel The next_index value (index of next log entry to be written) is useful for determining if a device's flash has been wiped since the last time logs were scoured. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYNEWT-676) Reboot counter value inconsistent
[ https://issues.apache.org/jira/browse/MYNEWT-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930559#comment-15930559 ] ASF subversion and git services commented on MYNEWT-676: Commit d1f00e95a6d4187d4227782fd97b055473137a0e in incubator-mynewt-core's branch refs/heads/develop from [~ccollins476] [ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=d1f00e9 ] MYNEWT-676 Reboot counter value inconsistent The value that gets logged to the reboot log is one greater than the actual reboot counter (the value retrieved via "newtmgr config reboot/reboot_cnt"). > Reboot counter value inconsistent > - > > Key: MYNEWT-676 > URL: https://issues.apache.org/jira/browse/MYNEWT-676 > Project: Mynewt > Issue Type: Bug >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The value that gets logged to the reboot log is one greater than the actual > reboot counter (the value retrieved via "newtmgr config reboot/reboot_cnt"). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYNEWT-676) Reboot counter value inconsistent
Christopher Collins created MYNEWT-676: -- Summary: Reboot counter value inconsistent Key: MYNEWT-676 URL: https://issues.apache.org/jira/browse/MYNEWT-676 Project: Mynewt Issue Type: Bug Reporter: Christopher Collins Assignee: Christopher Collins Fix For: v1_1_0_rel The value that gets logged to the reboot log is one greater than the actual reboot counter (the value retrieved via "newtmgr config reboot/reboot_cnt"). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYNEWT-675) Arduino Primo documentation still references "features"
Sterling Hughes created MYNEWT-675: -- Summary: 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)
