Ah, no microbit is logging an exception
Jacobs-MacBook-Air:chippd3 jacobrosenthal$ newtmgr image test
d030287bbf70c662fb6e1331fea8e91aab5e161fc82e42020f38d1fd3d700697 -c1412
-ldebug -t
2017/03/04 14:30:19 [DEBUG] Writing newtmgr request &{Op:2 Flags:0 Len:49
Group:1 Seq:0 Id:0 Data:[162 103 99
I checked out the microbit target in upstream which is probably damn near
identical to my tinyble target, and it similarly hangs.
They share the same programmer, mbed firmware with cmsisdap hid endpoint,
so I wonder if its a transport issue not a dep issue.
On Wed, Feb 22, 2017 at 4:50 PM,
I can shell to both boards and send and receive characters, so I know uart
is ok.
And the target syscfg are identical, as are the targets I believe, heres a
recursive target diff, looks like just names
Jacobs-MacBook-Air:mynewt-button-example jacobrosenthal$ diff -r
targets/split-tinyble/
Hi Jacob,
On Tue, Feb 21, 2017 at 09:10:08PM -0700, Jacob Rosenthal wrote:
[...]
> I get two distinct hangs to make things more weird.
>
> Jacobs-MacBook-Air:~ jacobrosenthal$ newtmgr image list -cserial1 -t -ldebug
> 2017/02/21 20:36:03 [DEBUG] Writing newtmgr request &{Op:0 Flags:0 Len:0
>
