You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Marko Kiiskila (JIRA)" <ji...@apache.org> on 2017/06/05 17:47:04 UTC

[jira] [Commented] (MYNEWT-733) newtmgr image upload crashes on nrf51 devices

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

Marko Kiiskila commented on MYNEWT-733:
---------------------------------------

Jacob, is this issue still pending, or were you able to figure this one out?

> newtmgr image upload crashes on nrf51 devices
> ---------------------------------------------
>
>                 Key: MYNEWT-733
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-733
>             Project: Mynewt
>          Issue Type: Bug
>      Security Level: Public(Viewable by anyone) 
>          Components: Newtmgr
>            Reporter: Jacob
>            Assignee: Christopher Collins
>         Attachments: upload crash.txt
>
>
> Jacobs-MacBook-Air:chippd3 jacobrosenthal$ newt target show split-nrf51dk 
> targets/split-nrf51dk
>     app=@apache-mynewt-core/apps/blesplit
>     bsp=@apache-mynewt-core/hw/bsp/nrf51dk
>     build_profile=optimized
>     loader=@apache-mynewt-core/apps/bleprph
>     syscfg=BLE_ACL_BUF_SIZE=128:BLE_LL_CFG_FEAT_LE_ENCRYPTION=0:BLE_SM_LEGACY=0:LOG_LEVEL=0
> [jacobrosenthal@localhost Downloads]$ sudo "$(which newtmgr)" -c ble image upload  blesplit.img -t -ldebug
> 2017/04/14 15:02:08 [DEBUG] BLE Connection devaddr:[]
> 2017/04/14 15:02:08 dev: hci0 up
> 2017/04/14 15:02:08 dev: hci0 down
> 2017/04/14 15:02:08 dev: hci0 opened
> 2017/04/14 15:02:08 [DEBUG] State:PoweredOn
> 2017/04/14 15:02:08 [DEBUG] scanning...
> 2017/04/14 15:02:08 [DEBUG] Peripheral Discovered: nimble-bleprph, Address:[10 10 10 10 10 10] Address Type:0
> 2017/04/14 15:02:08 [DEBUG] Peripheral Connected
> 2017/04/14 15:02:08 [DEBUG] Newtmgr Service Found 
> 2017/04/14 15:02:08 [DEBUG] Newtmgr Characteristic Found
> 2017/04/14 15:02:08 [DEBUG] Writing newtmgr request &{Op:2 Flags:0 Len:99 Group:1 Seq:0 Id:1 Data:[163 100 100 97 116 97 88 79 60 184 243 150 36 0 0 0 32 0 0 0 72 16 0 0 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 64 0 32 41 56 2 0 0 26 128 243 20 136 128 243 16 136 3 33 24 72 2 104 10 67 2 96 23 72 2 104 10 67 2 96 0 26 22 74 22 75 154 66 1 210 1 99 108 101 110 25 16 140 99 111 102 102 0]}
> 2017/04/14 15:02:08 [DEBUG] Serializing request &{Op:2 Flags:0 Len:99 Group:1 Seq:0 Id:1 Data:[163 100 100 97 116 97 88 79 60 184 243 150 36 0 0 0 32 0 0 0 72 16 0 0 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 64 0 32 41 56 2 0 0 26 128 243 20 136 128 243 16 136 3 33 24 72 2 104 10 67 2 96 23 72 2 104 10 67 2 96 0 26 22 74 22 75 154 66 1 210 1 99 108 101 110 25 16 140 99 111 102 102 0]} into buffer [2 0 0 99 0 1 0 1 163 100 100 97 116 97 88 79 60 184 243 150 36 0 0 0 32 0 0 0 72 16 0 0 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 64 0 32 41 56 2 0 0 26 128 243 20 136 128 243 16 136 3 33 24 72 2 104 10 67 2 96 23 72 2 104 10 67 2 96 0 26 22 74 22 75 154 66 1 210 1 99 108 101 110 25 16 140 99 111 102 102 0]
> 2017/04/14 15:02:08 [DEBUG] Tx packet dump:
> 00000000  02 00 00 63 00 01 00 01  a3 64 64 61 74 61 58 4f  |...c.....ddataXO|
> 00000010  3c b8 f3 96 24 00 00 00  20 00 00 00 48 10 00 00  |<...$... ...H...|
> 00000020  12 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 00000030  00 40 00 20 29 38 02 00  00 1a 80 f3 14 88 80 f3  |.@. )8..........|
> 00000040  10 88 03 21 18 48 02 68  0a 43 02 60 17 48 02 68  |...!.H.h.C.`.H.h|
> 00000050  0a 43 02 60 00 1a 16 4a  16 4b 9a 42 01 d2 01 63  |.C.`...J.K.B...c|
> 00000060  6c 65 6e 19 10 8c 63 6f  66 66 00                 |len...coff.|
> 2017/04/14 15:02:08 [DEBUG] Write BLE Packet:buf:: c �ddataXO<���$ H @ )8 �� ��� � ! H h
> C ` H h
> C ` J K�B � clen �coff len::107
> 2017/04/14 15:02:12 [DEBUG] Disconnected%!(EXTRA <nil>)
> Ive seen a disconnection with 520
> 832:[ts=6499968ssb, mod=4 level=0] Disconnection Complete: status=0 handle=1 reason=8
> 834:[ts=6515592ssb, mod=64 level=1] connection updated; status=520 handle=1 our_ota_addr_type=0 our_ota_addr=0a:0a:0a:0a:0a:0a our_id_addr_type=0 our_id_addr=0a:0a:0a:0a:0a:0a peer_ota_addr_type=0 peer_ota_addr=b8:e8:56:03:d3:ed peer_id_addr_type=0 peer_id_addr=b8:e8:56:03:d3:ed conn_itvl=12 conn_latency=0 supervision_timeout=200 encrypted=0 authenticated=0 bonded=0
> but more recently I just get a crash in the scheduler
> 1345:[ts=10507780ssb, mod=4 level=0] Number of ComUnhandled interrupt (3), exception sp 0x20000998
> 1345: r0:0x200004c0  r1:0x00000001  r2:0x20002ff0  r3:0x00000001
> 1345: r4:0x200004c0  r5:0x00000001  r6:0x0000002b  r7:0x20000a99
> 1345: r8:0xffffffff  r9:0xffffffff r10:0xffffffff r11:0xffffffff
> 1345:r12:0x00000000  lr:0x00009279  pc:0x00008eda psr:0x21000000
> 1345:ICSR:0x00421003
> b * 0x00008eda 
> Breakpoint 1 at 0x8eda: file repos/apache-mynewt-core/kernel/os/src/os_sched.c, line 166.



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