|
Bluez' mesh-cfgclient fails to retrieve composition data from onoff-app sample
Hi Trond, On further testing, it now works. I must have not properly flashed my board. Sorry for the noise and thanks for the fix. Steve
Hi Trond, On further testing, it now works. I must have not properly flashed my board. Sorry for the noise and thanks for the fix. Steve
|
By
Steve Brown
· #7438
·
|
|
Bluez' mesh-cfgclient fails to retrieve composition data from onoff-app sample
Hi Trond, The patch didn't fix the problem. I've attached the meshd and zephyr debug output. Steve MESHD Nov 3 03:55:38 mesh0 bluetooth-meshd[21346]: mesh/node.c:dev_key_send_call() DevKeySend Nov 3 0
Hi Trond, The patch didn't fix the problem. I've attached the meshd and zephyr debug output. Steve MESHD Nov 3 03:55:38 mesh0 bluetooth-meshd[21346]: mesh/node.c:dev_key_send_call() DevKeySend Nov 3 0
|
By
Steve Brown
· #7437
·
|
|
Bluez' mesh-cfgclient fails to retrieve composition data from onoff-app sample
I bisected this to eca014115 Bluetooth: Mesh: Isolate cryptographic material I suspect segmented messages. The successful sequence number starts at 2 whereas the failing one starts at 1. I'm not famil
I bisected this to eca014115 Bluetooth: Mesh: Isolate cryptographic material I suspect segmented messages. The successful sequence number starts at 2 whereas the failing one starts at 1. I'm not famil
|
By
Steve Brown
· #7435
·
|
|
USB fails to enumerate on nrf52840_pca10056 board
Hi Emil, Thanks for the files. Neither work on my boards. I suspect my silicon may be too old. I've had the boards for a couple of years. The build/date codes on both boards are: QIAAAA/1716AK. The la
Hi Emil, Thanks for the files. Neither work on my boards. I suspect my silicon may be too old. I've had the boards for a couple of years. The build/date codes on both boards are: QIAAAA/1716AK. The la
|
By
Steve Brown
· #6530
·
|
|
USB fails to enumerate on nrf52840_pca10056 board
Hi Johann, Could you email me a zephyr.hex of a USB app that enumerates? With it I can eliminate my nrf52 boards as the problem. Thanks, Steve
Hi Johann, Could you email me a zephyr.hex of a USB app that enumerates? With it I can eliminate my nrf52 boards as the problem. Thanks, Steve
|
By
Steve Brown
· #6523
·
|
|
USB fails to enumerate on nrf52840_pca10056 board
Hi Carles, This is the first time I've tried the nrf usb so I have no "working version" to compare. West version: v0.6.3 zephyr-sdk-0.10.3 The desc_section test was build with: west build -b nrf52840_
Hi Carles, This is the first time I've tried the nrf usb so I have no "working version" to compare. West version: v0.6.3 zephyr-sdk-0.10.3 The desc_section test was build with: west build -b nrf52840_
|
By
Steve Brown
· #6522
·
|
|
USB fails to enumerate on nrf52840_pca10056 board
All the USB samples and tests fail to enumerate. git HEAD 77006e896 Output from the desc_sections test is below: Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB disconnect, device number 65
All the USB samples and tests fail to enumerate. git HEAD 77006e896 Output from the desc_sections test is below: Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB disconnect, device number 65
|
By
Steve Brown
· #6519
·
|
|
[Zephyr-users] [Zephyr-devel] not able to complete #BluetoothMesh provisioning & configuration process using #meshctl (5.49)
#meshctl
#bluetoothmesh
Hi Johan, Works for me. Provisioning completes on samples/bluetooth/mesh and connects for configuration. The identity connection had previously failed. It's curious that the SILabs provisioner reporte
Hi Johan, Works for me. Provisioning completes on samples/bluetooth/mesh and connects for configuration. The identity connection had previously failed. It's curious that the SILabs provisioner reporte
|
By
Steve Brown
· #2108
·
|
|
[Zephyr-users] [Zephyr-devel] not able to complete #BluetoothMesh provisioning & configuration process using #meshctl (5.49)
#meshctl
#bluetoothmesh
Hi, I had a chance to look at this further. More at the bottom. It doesn't appear that bt_mesh_proxy_identity_enable() gets called in prov.c:proxy_data(). The earlier call to bt_mesh_provision() close
Hi, I had a chance to look at this further. More at the bottom. It doesn't appear that bt_mesh_proxy_identity_enable() gets called in prov.c:proxy_data(). The earlier call to bt_mesh_provision() close
|
By
Steve Brown
· #2104
·
|
|
tests/subsys/fs/nffs_fs_api fails after commit ff7dfc4fb44b5c987e42afc847dce33f43d520ba
Hi Carles, The test now builds and runs successfully. Thanks, Steve
Hi Carles, The test now builds and runs successfully. Thanks, Steve
|
By
Steve Brown
· #1660
·
|
|
tests/subsys/fs/nffs_fs_api fails after commit ff7dfc4fb44b5c987e42afc847dce33f43d520ba
From bisect dts: bindings: add support for the flash driver name ***** BOOTING ZEPHYR OS v1.10.99 - BUILD: Jan 27 2018 10:01:12 ***** Running test suite nffs_fs_basic_test ============================
From bisect dts: bindings: add support for the flash driver name ***** BOOTING ZEPHYR OS v1.10.99 - BUILD: Jan 27 2018 10:01:12 ***** Running test suite nffs_fs_basic_test ============================
|
By
Steve Brown
· #1652
·
|
|
[Zephyr-users] Subscribing to heartbeat messages in a mesh network
Hi Ashish Steve
By
Steve Brown
· #1548
·
|
|
[Zephyr-users] Subscribing to heartbeat messages in a mesh network
Hi Ashish, If the target of heartbeat publish is 0077 (meshctl's unicast address), it will display the returned status. Steve
Hi Ashish, If the target of heartbeat publish is 0077 (meshctl's unicast address), it will display the returned status. Steve
|
By
Steve Brown
· #1540
·
|
|
[Zephyr-users] I2C and adc support for nRF5
Hi Ashish, The board name is nrf52840_pca10056 That works on my boards. Steve
Hi Ashish, The board name is nrf52840_pca10056 That works on my boards. Steve
|
By
Steve Brown
· #1473
·
|
|
Replay protection
I agree. Just a few nodes with relay enabled and a nominal TTL of 7 would create a lot of traffic. The retransmit count and period are hardwired to 2 and 200 ms (4 * 50ms) respectively in meshctl. I'l
I agree. Just a few nodes with relay enabled and a nominal TTL of 7 would create a lot of traffic. The retransmit count and period are hardwired to 2 and 200 ms (4 * 50ms) respectively in meshctl. I'l
|
By
Steve Brown
· #1455
·
|
|
Replay protection
Hi Johan, Yes, I've conflated sequence number and transaction id. It's clear now. Thanks for the clarification, Steve
Hi Johan, Yes, I've conflated sequence number and transaction id. It's clear now. Thanks for the clarification, Steve
|
By
Steve Brown
· #1453
·
|
|
Replay protection
Hi Johan, These are publish retransmits. However, the transaction ID's in the received messages are all the same. It's the "trans_id" field in the log in my earlier post. An upper layer, like my serve
Hi Johan, These are publish retransmits. However, the transaction ID's in the received messages are all the same. It's the "trans_id" field in the log in my earlier post. An upper layer, like my serve
|
By
Steve Brown
· #1451
·
|
|
Replay protection
Is replay protection implemented? The reason for the question is that my server is receiving both the initial publish transmit as well as the subsequent retransmits. The server is at 0x0100 and is sub
Is replay protection implemented? The reason for the question is that my server is receiving both the initial publish transmit as well as the subsequent retransmits. The server is at 0x0100 and is sub
|
By
Steve Brown
· #1449
·
|
|
BLE Nitrogen
Hi Charles, I started with 2 Nitrogens and attempted to connect to them with a CSR dongle. I received no unprovisioned beacons. I fired up the ubertooth sniffer and didn't see any traffic either. My c
Hi Charles, I started with 2 Nitrogens and attempted to connect to them with a CSR dongle. I received no unprovisioned beacons. I fired up the ubertooth sniffer and didn't see any traffic either. My c
|
By
Steve Brown
· #1438
·
|
|
BLE Nitrogen
Hi Gene, You can program it with drag/drop CMSIS bootloader's disk, pyocd or openocd over USB. The "make flash" uses pyocd and worked fine for me. The softdevice is only the Nordic SDK. Zephyr's Bluet
Hi Gene, You can program it with drag/drop CMSIS bootloader's disk, pyocd or openocd over USB. The "make flash" uses pyocd and worked fine for me. The softdevice is only the Nordic SDK. Zephyr's Bluet
|
By
Steve Brown
· #1429
·
|