[jira] [Commented] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050020#comment-16050020 ] ASF subversion and git services commented on MYNEWT-768: Commit 4ce6e7c3c1340add8ceea46b477e4301b8762d6c in incubator-mynewt-newtmgr's branch refs/heads/master from [~cwanda] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newtmgr.git;h=4ce6e7c ] MYNEWT-768 help text for newtmgr image erase command. Added more help text to explain when an image can be erased and matches documentation. > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050021#comment-16050021 ] ASF subversion and git services commented on MYNEWT-768: Commit 041577f608f74abf9f4b6580c0b1692d1fa3ca94 in incubator-mynewt-newtmgr's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newtmgr.git;h=041577f ] Merge pull request #2 from cwanda/image_erase_help MYNEWT-768 help text for newtmgr image erase command. > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wanda Chiu resolved MYNEWT-768. --- Resolution: Fixed > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-768) Document newtmgr image erase subcommand
[ https://issues.apache.org/jira/browse/MYNEWT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049955#comment-16049955 ] Wanda Chiu commented on MYNEWT-768: --- Updated doc in this pr: https://github.com/apache/incubator-mynewt-site/pull/202 Also added more help text for the the newtmgr image erase command in this PR:https://github.com/apache/incubator-mynewt-newtmgr/pull/2 > Document newtmgr image erase subcommand > --- > > Key: MYNEWT-768 > URL: https://issues.apache.org/jira/browse/MYNEWT-768 > Project: Mynewt > Issue Type: Task > Security Level: Public(Viewable by anyone) > Components: Documentation >Affects Versions: v1_1_0_rel >Reporter: Wanda Chiu >Assignee: Wanda Chiu >Priority: Minor > Fix For: v1_1_0_rel > > > Need to document *newtmgr image erase* subcommand for 1.1. See PR > https://github.com/apache/incubator-mynewt-newt/pull/60. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-755) newtmgr panic: runtime error: cgo argument has Go pointer to Go pointer
[
https://issues.apache.org/jira/browse/MYNEWT-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049819#comment-16049819
]
Jacob commented on MYNEWT-755:
--
Heh. duh. Yeah I actually know that. I was probably using serial transport and
then switched to ble not thinking.
EXCEPT, it turns out ble does work on ios when I use the GODEBUG=cgocheck=0
flag :)
Jacobs-MacBook-Air:newt jacobrosenthal$ GODEBUG=cgocheck=0 newtmgr image
coredownload core.dump -cnimble_bleprph
2017/06/14 19:43:34 Unhandled event: xpc.Dict{"kCBMsgId":53,
"kCBMsgArgs":xpc.Dict{"kCBMsgArgDeviceUUID":xpc.UUID{0x2f, 0xd, 0xcb, 0x60,
0xf, 0x3e, 0x47, 0x52, 0xb7, 0x74, 0x13, 0x29, 0x3a, 0x3, 0xd4, 0xd0},
"kCBMsgArgATTMTU":104}}
Got response: 6 bytes
No corefile present
Jacobs-MacBook-Air:newt jacobrosenthal$
> newtmgr panic: runtime error: cgo argument has Go pointer to Go pointer
> ---
>
> Key: MYNEWT-755
> URL: https://issues.apache.org/jira/browse/MYNEWT-755
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: Newtmgr
>Reporter: Jacob
>Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> Googling seems to indicate maybe it needs refactoring?
> https://github.com/ry/v8worker/issues/31
> Ive tried back to mynewt_1_0_0_b2_tag and it still happens so I think its
> tied to again either xcode update or maybe a go point release?
> Jacobs-MacBook-Air:newtmgr jacobrosenthal$ go version
> go version go1.7.5 darwin/amd64
> My xcode is 8.3.2
> But I can confirm the listed workaround is to use GODEBUG=cgocheck=0 works
> but I get (possibly unrelated?) unhandled xpc events as well
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (MYNEWT-755) newtmgr panic: runtime error: cgo argument has Go pointer to Go pointer
[ https://issues.apache.org/jira/browse/MYNEWT-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins resolved MYNEWT-755. Resolution: Won't Fix Ah, I see. Sorry... somehow I missed that you were using a BLE connection profile. The gatt library (what newtmgr uses for BLE connectivity) doesn't work in Mac OS. That is why you're seeing that ugly crash dump. We could add a proper error message instead of the crash, but I don't think it matters too much in this case because we'll be replacing that version of newtmgr with one that actually does work in Mac OS: https://github.com/apache/incubator-mynewt-newtmgr > newtmgr panic: runtime error: cgo argument has Go pointer to Go pointer > --- > > Key: MYNEWT-755 > URL: https://issues.apache.org/jira/browse/MYNEWT-755 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Newtmgr >Reporter: Jacob >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > Googling seems to indicate maybe it needs refactoring? > https://github.com/ry/v8worker/issues/31 > Ive tried back to mynewt_1_0_0_b2_tag and it still happens so I think its > tied to again either xcode update or maybe a go point release? > Jacobs-MacBook-Air:newtmgr jacobrosenthal$ go version > go version go1.7.5 darwin/amd64 > My xcode is 8.3.2 > But I can confirm the listed workaround is to use GODEBUG=cgocheck=0 works > but I get (possibly unrelated?) unhandled xpc events as well -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-310) newt should globally namespace remote repositories
[ https://issues.apache.org/jira/browse/MYNEWT-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-310: --- Fix Version/s: (was: v1_1_0_rel) > newt should globally namespace remote repositories > -- > > Key: MYNEWT-310 > URL: https://issues.apache.org/jira/browse/MYNEWT-310 > Project: Mynewt > Issue Type: New Feature > Security Level: Public(Viewable by anyone) >Reporter: Sterling Hughes >Assignee: Christopher Collins > > Right now remote repositories can have conflicting names (e.g. somebody else > could reserve apache-mynewt-core, and newt wouldn't have a way of resolving > the conflict.) > Need some form of global namespacing on repository descriptors, whether using > the DNS name (ala go), or some other sort of registry. > This will become important once inter-repository dependencies and mirroring > come into play. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MYNEWT-190) Support automatically sending failure logs for newt
[ https://issues.apache.org/jira/browse/MYNEWT-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins reassigned MYNEWT-190: -- Assignee: (was: Christopher Collins) Fix Version/s: (was: v1_1_0_rel) > Support automatically sending failure logs for newt > > > Key: MYNEWT-190 > URL: https://issues.apache.org/jira/browse/MYNEWT-190 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Newt >Reporter: Sterling Hughes > > When newt fails to build, or users experience newt failures. There should be > an option to create a log bundle that can be sent to Mynewt, or automatically > posted and create JIRA ticket in the Mynewt ASF system. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MYNEWT-120) Add generation of IDE project files into newt
[ https://issues.apache.org/jira/browse/MYNEWT-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins reassigned MYNEWT-120: -- Assignee: (was: Christopher Collins) Fix Version/s: (was: v1_1_0_rel) > Add generation of IDE project files into newt > - > > Key: MYNEWT-120 > URL: https://issues.apache.org/jira/browse/MYNEWT-120 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Newt >Reporter: Sterling Hughes >Priority: Minor > > Add support for generating IDE project files from the newt tool: > - Eclipse > - Sublime > - Makefile -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-325) BLE Host - Allow ECC to be delegated to the controller
[ https://issues.apache.org/jira/browse/MYNEWT-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-325: --- Fix Version/s: (was: v1_1_0_rel) > BLE Host - Allow ECC to be delegated to the controller > -- > > Key: MYNEWT-325 > URL: https://issues.apache.org/jira/browse/MYNEWT-325 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins >Priority: Minor > > The host currently does all ECC operations in software using the tinycrypt > library. We need to: > * Implement the ECC HCI commands in the host and controller. > * Create a build option which: > ** Enables ECC functionality in the controller. > ** Disables ECC functionality in the host. > ** Makes the host use the HCI commands rather than call into tinycrypt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-38) Implement ECC correction in NFFS
[ https://issues.apache.org/jira/browse/MYNEWT-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-38: -- Fix Version/s: (was: v1_1_0_rel) > Implement ECC correction in NFFS > > > Key: MYNEWT-38 > URL: https://issues.apache.org/jira/browse/MYNEWT-38 > Project: Mynewt > Issue Type: New Feature > Security Level: Public(Viewable by anyone) > Components: NFFS >Reporter: Sterling Hughes >Assignee: Christopher Collins > > Data stored in NFFS files should optionally have ECC coding applied to them > to correct for data corruption. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-301) nffs corrupt
[ https://issues.apache.org/jira/browse/MYNEWT-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-301: --- Fix Version/s: (was: v1_1_0_rel) > nffs corrupt > > > Key: MYNEWT-301 > URL: https://issues.apache.org/jira/browse/MYNEWT-301 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: NFFS >Affects Versions: v1_0_0_beta2 >Reporter: Marko Kiiskila >Assignee: Christopher Collins > Attachments: bad_arduino_nffs.bin, bad_arduino_nffs.bin2 > > > happened on arduino, bootloader does not come up as NFFS is asserting. > (gdb) bt > #0 __assert_func (file=0x742a "nffs_restore.c", line=229, func=0x0 > <_sfixed>, > e=0x0 <_sfixed>) at os_fault.c:113 > #1 0x22ac in nffs_restore_find_file_ends () at nffs_restore.c:285 > #2 nffs_restore_full (area_descs=area_descs@entry=0x2000736c) > at nffs_restore.c:1160 > #3 0x04ca in nffs_detect (area_descs=area_descs@entry=0x2000736c) > at nffs.c:605 > #4 0x01e8 in setup_for_nffs () at boot.c:80 > #5 main () at boot.c:160 > (gdb) up -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-37) Implement FS compression in NFFS
[ https://issues.apache.org/jira/browse/MYNEWT-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-37: -- Fix Version/s: (was: v1_1_0_rel) > Implement FS compression in NFFS > > > Key: MYNEWT-37 > URL: https://issues.apache.org/jira/browse/MYNEWT-37 > Project: Mynewt > Issue Type: New Feature > Security Level: Public(Viewable by anyone) > Components: NFFS >Reporter: Sterling Hughes >Assignee: Christopher Collins > > Compression should be supported in NFFS. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-13) NFFS does not work on STM32F3 or NXP MK64F12
[ https://issues.apache.org/jira/browse/MYNEWT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-13: -- Fix Version/s: (was: v1_1_0_rel) > NFFS does not work on STM32F3 or NXP MK64F12 > > > Key: MYNEWT-13 > URL: https://issues.apache.org/jira/browse/MYNEWT-13 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: NFFS >Reporter: Marko Kiiskila >Assignee: Christopher Collins >Priority: Minor > > STM32F3 flash writes are done 2 bytes at a time. MK64F12 flash alignment is > 8. 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.4.14#64029)
[jira] [Updated] (MYNEWT-338) NFFS - Can't delete from a completely full file system
[ https://issues.apache.org/jira/browse/MYNEWT-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-338: --- Fix Version/s: (was: v1_1_0_rel) > NFFS - Can't delete from a completely full file system > -- > > Key: MYNEWT-338 > URL: https://issues.apache.org/jira/browse/MYNEWT-338 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: NFFS >Reporter: Christopher Collins >Assignee: Christopher Collins > > Deleting a file or directory requires writing an inode to the disk. If the > disk is completely full, there is not room for the deletion record, and the > delete attempt will fail with an FS_EFULL error. > It should be sufficient to always ensure that at least one area has room for > a deletion record. All deletion records are the same size. Once a deletion > record is written, the previous inode entry and all children inodes or > constituent data blocks can be removed during garbage collection. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-343) nffs crash at bootloader
[
https://issues.apache.org/jira/browse/MYNEWT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Collins updated MYNEWT-343:
---
Fix Version/s: (was: v1_1_0_rel)
> nffs crash at bootloader
>
>
> Key: MYNEWT-343
> URL: https://issues.apache.org/jira/browse/MYNEWT-343
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: NFFS
> Environment: Arduino Zero with NFFS
>Reporter: Marko Kiiskila
>Assignee: Christopher Collins
> Attachments: arduino_nffs.bin, nffs-inode-invalid-id.bin
>
>
> System asserts. I was switching between images.
> Program received signal SIGTRAP, Trace/breakpoint trap.
> __assert_func (file=, line=,
> func=, e=) at os_fault.c:124
> 124 asm("bkpt");
> (gdb) bt
> #0 __assert_func (file=, line=,
> func=, e=) at os_fault.c:124
> #1 0x105e in nffs_hash_remove (entry=entry@entry=0x20001ad8)
> at nffs_hash.c:179
> #2 0x2ff2 in nffs_block_delete_from_ram (
> block_entry=block_entry@entry=0x20001ad8) at nffs_block.c:266
> #3 0x26f2 in nffs_restore_sweep () at nffs_restore.c:353
> #4 0x283e in nffs_restore_full (area_descs=area_descs@entry=0x2000736c)
> at nffs_restore.c:1400
> #5 0x04ca in nffs_detect (area_descs=area_descs@entry=0x2000736c)
> at nffs.c:606
> #6 0x01e8 in setup_for_nffs () at boot.c:93
> #7 main () at boot.c:173
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (MYNEWT-747) Impossible to newtmgr upload firmware to nrf51 devices
[ https://issues.apache.org/jira/browse/MYNEWT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob closed MYNEWT-747. Resolution: Fixed > Impossible to newtmgr upload firmware to nrf51 devices > -- > > Key: MYNEWT-747 > URL: https://issues.apache.org/jira/browse/MYNEWT-747 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Image Mgmt, Newtmgr > Environment: All >Reporter: Jacob >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > It is currently not possible to upload firmware to a nrf51 device. > Mailing list discussion: > https://lists.apache.org/thread.html/bc99b1c75790198685d40a12e8e49de12f0b9e8891f93f2fd9a95f0d@%3Cdev.mynewt.apache.org%3E > Logs show: > 832:[ts=6499968ssb, mod=4 level=0] Disconnection Complete: status=0 handle=1 > reason=8 > Appears to be related to the flash erase > https://github.com/apache/incubator-mynewt-core/blob/cb23f34e9b55de68078c0c2200b268cf536d003b/mgmt/imgmgr/src/imgmgr.c#L324 > Flash erase is blocking and takes a while, so traditionally on nordic > softdevic schedule to work outside of radio events as much as possible. > newtmgr isnt and probably shouldn't be coupled down to the radio abstraction. > Nordic forum also talks about altering intervals and latencies, > https://devzone.nordicsemi.com/question/24290/slow-flash-erase-performance-with-sd_flash_page_erase/?answer=24361#post-id-24361 > but discussion on the list also found that a lacking solution > One possible solution discussed solution was to separate erase from upload > commands -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-755) newtmgr panic: runtime error: cgo argument has Go pointer to Go pointer
[ https://issues.apache.org/jira/browse/MYNEWT-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049631#comment-16049631 ] Jacob commented on MYNEWT-755: -- Last login: Sun Jun 11 16:22:02 on ttys007 Jacobs-MacBook-Air:~ jacobrosenthal$ cd $GOPATH Jacobs-MacBook-Air:go jacobrosenthal$ cd src/mynewt.apache.org/newt/ Jacobs-MacBook-Air:newt jacobrosenthal$ git branch image_erase * master newtmgr-erase Jacobs-MacBook-Air:newt jacobrosenthal$ git pull origin master remote: Counting objects: 29, done. remote: Compressing objects: 100% (12/12), done. remote: Total 29 (delta 20), reused 23 (delta 14), pack-reused 0 Unpacking objects: 100% (29/29), done. >From https://github.com/apache/incubator-mynewt-newt * branch master -> FETCH_HEAD 97bb88d6..cd248f80 master -> origin/master Updating 97bb88d6..cd248f80 Fast-forward newt/cli/image_cmds.go | 60 newt/cli/run_cmds.go | 9 +++ newt/image/image.go| 67 ++ 3 files changed, 131 insertions(+), 5 deletions(-) Jacobs-MacBook-Air:newt jacobrosenthal$ cd newt Jacobs-MacBook-Air:newt jacobrosenthal$ go install Jacobs-MacBook-Air:newt jacobrosenthal$ cd ../newtmgr/ Jacobs-MacBook-Air:newtmgr jacobrosenthal$ go install Jacobs-MacBook-Air:newtmgr jacobrosenthal$ pwd /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr Jacobs-MacBook-Air:newtmgr jacobrosenthal$ newtmgr Newtmgr helps you manage remote devices running the Mynewt OS Usage: newtmgr [flags] newtmgr [command] Available Commands: config Read or write a config value on a device connManage newtmgr connection profiles crash Send a crash command to a device datetimeManage datetime on a device echoSend data to a device and display the echoed back data fs Access files on a device image Manage images on a device log Manage logs on a device mpstats Read memory pool statistics from a device reset Send reset request to a device run Run test procedures on a device statRead statistics from a device taskstats Read task statistics from a device Flags: -c, --conn string connection profile to use -h, --help Help for newtmgr commands -l, --loglevel string log level to use (default "info") -t, --trace print all bytes transmitted and received Use "newtmgr [command] --help" for more information about a command. Jacobs-MacBook-Air:newtmgr jacobrosenthal$ newtmgr image list -cnimble_bleprph panic: runtime error: cgo argument has Go pointer to Go pointer goroutine 1 [running]: mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt/xpc.XpcConnect.func2(0x4b00120, 0xc420149290, 0x4b00120) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt/xpc/xpc_darwin.go:169 +0xaf mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt/xpc.XpcConnect(0x4627b26, 0xf, 0x48973c0, 0xc420144300, 0x0) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt/xpc/xpc_darwin.go:169 +0xc2 mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt.NewDevice(0x48f1580, 0x0, 0x0, 0x1, 0x1, 0x0, 0x48d3240) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/vendor/github.com/runtimeco/gatt/device_darwin.go:67 +0x239 mynewt.apache.org/newt/newtmgr/transport.(*ConnBLE).Open(0xc42012e660, 0x489dec0, 0xc42013c230, 0x0, 0x7fff5fbffbad, 0xe) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/transport/connble.go:169 +0x1ce mynewt.apache.org/newt/newtmgr/transport.newConn(0x489dec0, 0xc42013c230, 0x0, 0x0, 0x0, 0xc42012e420, 0xc420132050) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/transport/conn.go:110 +0x230 mynewt.apache.org/newt/newtmgr/transport.NewConn(0x489dec0, 0xc42013c230, 0xe, 0xc42013c230, 0x0, 0x0) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/transport/conn.go:75 +0x3e mynewt.apache.org/newt/newtmgr/cli.getTargetCmdRunner(0x0, 0x0, 0xc42010dd18) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/cli/common.go:39 +0x8b mynewt.apache.org/newt/newtmgr/cli.imageStateListCmd(0xc420151d40, 0xc420149120, 0x0, 0x1) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/cli/image.go:86 +0x26 mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra.(*Command).execute(0xc420151d40, 0xc420149110, 0x1, 0x1, 0xc420151d40, 0xc420149110) /Users/jacobrosenthal/dev/go/src/mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra/command.go:636 +0x231 mynewt.apache.org/newt/newtmgr/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc42015, 0xc4201518c0, 0xc420151200, 0xc420148e80)
[jira] [Commented] (MYNEWT-747) Impossible to newtmgr upload firmware to nrf51 devices
[ https://issues.apache.org/jira/browse/MYNEWT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049632#comment-16049632 ] Jacob commented on MYNEWT-747: -- Resolved in https://issues.apache.org/jira/browse/MYNEWT-733 > Impossible to newtmgr upload firmware to nrf51 devices > -- > > Key: MYNEWT-747 > URL: https://issues.apache.org/jira/browse/MYNEWT-747 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Image Mgmt, Newtmgr > Environment: All >Reporter: Jacob >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > It is currently not possible to upload firmware to a nrf51 device. > Mailing list discussion: > https://lists.apache.org/thread.html/bc99b1c75790198685d40a12e8e49de12f0b9e8891f93f2fd9a95f0d@%3Cdev.mynewt.apache.org%3E > Logs show: > 832:[ts=6499968ssb, mod=4 level=0] Disconnection Complete: status=0 handle=1 > reason=8 > Appears to be related to the flash erase > https://github.com/apache/incubator-mynewt-core/blob/cb23f34e9b55de68078c0c2200b268cf536d003b/mgmt/imgmgr/src/imgmgr.c#L324 > Flash erase is blocking and takes a while, so traditionally on nordic > softdevic schedule to work outside of radio events as much as possible. > newtmgr isnt and probably shouldn't be coupled down to the radio abstraction. > Nordic forum also talks about altering intervals and latencies, > https://devzone.nordicsemi.com/question/24290/slow-flash-erase-performance-with-sd_flash_page_erase/?answer=24361#post-id-24361 > but discussion on the list also found that a lacking solution > One possible solution discussed solution was to separate erase from upload > commands -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-759) Change BLE-over-CoAP UUID from 128-bit to 16-bit
[ https://issues.apache.org/jira/browse/MYNEWT-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins resolved MYNEWT-759. Resolution: Won't Fix This will be part of the cloud connector package, not the 1.1.0 release. > Change BLE-over-CoAP UUID from 128-bit to 16-bit > > > Key: MYNEWT-759 > URL: https://issues.apache.org/jira/browse/MYNEWT-759 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > The plan is to reserve a 16-bit UUID with the Bluetooth SIG. In the > meantime, we will use the (arbitrarilly chosen) UUID 0x9923. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MYNEWT-782) Atmel SAMD21 i2c probing
[ https://issues.apache.org/jira/browse/MYNEWT-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048613#comment-16048613 ] Vipul Rahane edited comment on MYNEWT-782 at 6/14/17 6:12 AM: -- This might be a case of clock stretching as I encountered the same with BNO055. I have a ticket open for it: https://issues.apache.org/jira/browse/MYNEWT-631. Linking it to this ticket to give more context. There is also a capture attached to the ticket. was (Author: vrahane): This might be case of clock stretching as I encountered the same with BNO055. I have a tickets opened for it: https://issues.apache.org/jira/browse/MYNEWT-631. Linking it to this ticket to give more context. There is also a capture attached to the ticket. > Atmel SAMD21 i2c probing > > > Key: MYNEWT-782 > URL: https://issues.apache.org/jira/browse/MYNEWT-782 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila > > I have 2 test i2c devices. I can do 'i2c_scan' on either, but will discover > the device only once. > On subsequent runs the device does not report being present. Should > investigate if this is because a) the device itself refuses to respond or b) > hal i2c driver on SAMD21 is faulty. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
