Hi Lichun
On 29 March 2018 at 12:28, Li-Chun Ko <[email protected]> wrote:
> Hi Łukasz,
>
> I am using the ADV bearer.
>
> I don't have the log at hand but you should get all the information from
> the picture I attached in my previous email. It was captured by a low cost
> Nordic sniffer.
Could you resend picture you mentioned? It looks like it is missing in
your first email (at least I did not get it)
>
> I used bascally the same steps that were mentioned in the BLE mesh tutroial
> except I changed the UUID and I also built the bootloader at the same time
> (I don't know why without compiling the bootloader the serial interface of
> the mesh node doesn't seem to work; I haven't got a chance to take a
> further look so now I always compile them together).
> Below are the detailed steps. I will share the configuration with you once
> I can reach my computer.
>
> Cheers,
> Lichun
> __
> newt new my_mesh
> cd my_mesh/
> newt install -v
> newt target create blemesh
> newt target set blemesh app=@apache-mynewt-core/apps/blemesh
> newt target set blemesh bsp=@apache-mynewt-core/hw/bsp/nrf52dk
> newt target set blemesh build_profile=optimized
> newt target set blemesh syscfg=BLE_MESH_PB_GATT=1:BLE_
> MESH_DEV_UUID='(uint8_t[16]){0x33, 0x19, 0}'
> newt target create nrf52_boot
> newt target set nrf52_boot app=@apache-mynewt-core/apps/boot
> newt target set nrf52_boot bsp=@apache-mynewt-core/hw/bsp/nrf52dk
> newt target set nrf52_boot build_profile=optimized
> newt build nrf52_boot
> newt build blemesh
> newt create-image blemesh 1.0.0
> newt load blemesh
>
> Łukasz Rymanowski <[email protected]> 於 2018年3月29日 週四 下午5:02 寫道：
>
>> Hi Lichun,
>>
>> On 29 March 2018 at 10:42, Li-Chun Ko <[email protected]> wrote:
>> > Hi all,
>> >
>> > I am running blemesh with mynewt 1.3.0 on Nordics pca 10040. Here are
>> two
>> > questions I have:
>> >
>> > 1. Is it correct that the current mynewt release doesn't support the
>> > Provisioner's role? I wasn't able to find a way to do so.
>> >
>>
>> This is correct. Provisioner is not supported in Mynewt. However if
>> you want to test mesh wit two Mynewt devices, I suggest to use
>> blemesh_shell application which gives you a way to hardcode mesh
>> credentians by using "provision" command.
>>
>> > 2. I tried to use the mesh stack from Noridc to play the Provisioner's
>> role
>> > but it seems the device cannot decode the unprovisioning beacon
>> generated by
>> > mynewt's mesh stack correctly. I captured the beacon with wireshark 2.5.1
>> > and noticed that the tool cannot parse the beacon correctly either. The
>> > AdvData can be recognized as mesh beacon but the content is showed as
>> > "unknown data". I am thinking there might be some PDU format issues (I
>> > suspect the length field of the mesh beacon which is 24 bytes is
>> incorrect)
>> > but I am not sure. I have attached a photo as the reference and hopefully
>> > someone can help check.
>> >
>>
>> That is interesting. I did not test against Nordic stack but was
>> testing against PTS tool and some other implementation and have not
>> seen such issue.
>> Could you share your target configuration ("newt target show <target
>> name>") and wireshark logs?
>>
>> BTW What bearer uses Nordic stack?
>>
>> > Br,
>> > Lichun
>>
>> Thanks
>> Łukasz
>>
Best
Łukasz
