Date   

Re: [Zephyr-devel] Zephyr Based Bluetooth Mesh implementation on nRF52840-PDK boards

Vikrant More <vikrant8051@...>
 

It is working now !!
I run hcitool lescan on another terminal & { discover-unprovisioned on , provision dddd0000000000000000000000000000 } on messhctl terminal.

Output -->
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[meshctl]# discover-unprovisioned on
set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
SetDiscoveryFilter success
Discovery started
Adapter property changed 
[CHG] Controller F0:03:8C:B7:5A:18 Discovering: yes
Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
Device UUID: dddd0000000000000000000000000000
OOB: 0000
[NEW] Device EA:E8:05:9B:16:1D Zephyr
[meshctl]# provision dddd0000000000000000000000000000
Trying to connect Device EA:E8:05:9B:16:1D Zephyr
Adapter property changed 
[CHG] Controller F0:03:8C:B7:5A:18 Discovering: no
[Zephyr]# Connection successful
[Zephyr]# Service added /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service0006
Service added /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a
Char added /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000b:
Char added /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000d:
Services resolved yes
Found matching char: path /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000b, uuid 00002adb-0000-1000-8000-00805f9b34fb
Found matching char: path /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000d, uuid 00002adc-0000-1000-8000-00805f9b34fb
Start notification on /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000d
Characteristic property changed /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000d
Notify started
Notify for Mesh Provisioning Out Data started
Open-Node: 0x1444640
Open-Prov: 0x1446380
Open-Prov: proxy 0x144a150
GATT-TX:  03 00 10 
Attempting to write /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000b
Initiated provisioning
Characteristic property changed /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000d
GATT-RX: 03 01 01 00 01 00 00 04 00 08 00 00 00 
Got provisioning data (12 bytes)
01 01 00 01 00 00 04 00 08 00 00 00 
GATT-TX:  03 02 00 00 02 03 04 
Attempting to write /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000b
GATT-TX:  03 03 a8 09 93 50 18 6f 0d 3a cb af 39 40 28 60 
GATT-TX:  9b fa 15 c9 
Attempting to write /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000b
Characteristic property changed /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000d
GATT-RX: 03 03 3a bd 0b 6e 8a d8 dd a9 92 22 a9 3c e4 c7 
GATT-RX: fe c3 f1 08 d9 5b ef ff 56 49 87 aa 64 ca 74 af 
GATT-RX: ed 3d 89 b9 60 9c b8 19 a3 54 16 a4 dd 12 8d 3c 
GATT-RX: f3 79 1c 18 15 2e 64 3a 4a e2 c1 34 19 c7 39 ab 
GATT-RX: 9f e3 
Got provisioning data (65 bytes)
03 3a bd 0b 6e 8a d8 dd a9 92 22 a9 3c e4 c7 fe 
c3 f1 08 d9 5b ef ff 56 49 87 aa 64 ca 74 af ed 
3d 89 b9 60 9c b8 19 a3 54 16 a4 dd 12 8d 3c f3 
79 1c 18 15 2e 64 3a 4a e2 c1 34 19 c7 39 ab 9f 
e3 
Request decimal key (0 - 9999)
[mesh] Enter Numeric key: 1234
GATT-TX:  03 05 79 75 31 d9 3c ce a3 27 2c d7 1b 5d 90 f3 
GATT-TX:  30 27 
Attempting to write /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000b
Characteristic property changed /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000d
GATT-RX: 03 05 eb 68 f7 99 be 18 ef 71 6e 51 10 f6 f5 05 
GATT-RX: d2 40 
Got provisioning data (17 bytes)
05 eb 68 f7 99 be 18 ef 71 6e 51 10 f6 f5 05 d2 
40 
GATT-TX:  03 06 af 78 37 46 88 64 92 8f f1 f4 9c c1 18 95 
GATT-TX:  a7 8d 
Attempting to write /org/bluez/hci0/dev_EA_E8_05_9B_16_1D/service000a/char000b
[Zephyr]#

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Now what to do next ??
I've repeat this procedure on all three board.

How to control LEDs on these board using meshctl or any android APP ??

Thank You!!



On Thu, Nov 16, 2017 at 10:10 AM, Vikrant More <vikrant8051@...> wrote:
Now I'm able to run "discover-unprovisioned on" this command & o/p is

set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
SetDiscoveryFilter success
Discovery started
Adapter property changed 
[CHG] Controller F0:03:8C:B7:5A:18 Discovering: ye


But "provision dddd0000000000000000000000000000" is still giving me this o/p-

Device with UUID dddd0000000000000000000000000000 not found.
Stale services? Remove device and re-discover

I'm able to discover & connect nRF52840-PDK board via nRF connect android app.


On Wed, Nov 15, 2017 at 10:01 PM, Steve Brown <sbrown@...> wrote:
More.

If I run the old bluetoothd, I get

[NEW] Controller B8:27:EB:06:2E:57 raspberrypi [default]
[meshctl]# discover-unprovisioned on
set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
SetDiscoveryFilter failed: org.bluez.Error.InvalidArguments
Discovery started
Adapter property changed
[CHG] Controller B8:27:EB:06:2E:57 Discovering: yes

The same as you.

I'm pretty sure that's your problem.

Steve


On Wed, 2017-11-15 at 21:17 +0530, Vikrant More wrote:
>
> [meshctl]# discover-unprovisioned on
> set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
> SetDiscoveryFilter failed: org.bluez.Error.InvalidArguments
> Discovery started
> Adapter property changed
> [CHG] Controller F0:03:8C:B7:5A:18 Discovering: yes
>
> I built BlueZ 5.47 as per your style but I am getting same error
> which is mentioned above.
>
> On Nov 15, 2017 5:47 PM, "Steve Brown" <sbrown@...> wrote:
> > I don't recognize that repository. The one I'm using is
> >
> > https://git.kernel.org/pub/scm/bluetooth/bluez.git
> >
> > The json files are in that repository.
> >
> > I run ./bootstrap-configure, then make and sudo make install.
> >
> > You might want to remove your distribution's bluez from your system
> > so
> > there's no confusion over version.
> >
> > Lastly, are you sure that the bluetooth hardware on your computer
> > does
> > ble? If in doubt, try
> > sudo btmgmt info
> >
> > Steve
> >
> > On Wed, 2017-11-15 at 17:12 +0530, Vikrant More wrote:
> > > could you please help how to build https://github.com/hadess/blue
> > z ??
> > >
> > > since here I am not getting configure file to execute -->
> > > ./configure --prefix=/usr  --sysconfdir=/etc  --
> > localstatedir=/var
> > > --enable-library  --disable-systemd  && make
> > >
> > > On Wed, Nov 15, 2017 at 4:52 PM, Steve Brown <sbrown@...
> > >
> > > wrote:
> > > > It looks like you have some kind of problem on the bluez end.
> > > >
> > > > I get the following on the same board.
> > > >
> > > > [meshctl]# discover-unprovisioned on
> > > > set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
> > > > SetDiscoveryFilter success
> > > > Discovery started
> > > > Adapter property changed
> > > > [CHG] Controller B8:27:EB:06:2E:57 Discovering: yes
> > > >                 Mesh Provisioning Service (00001827-0000-1000-
> > 8000-
> > > > 00805f9b34fb)
> > > >                         Device UUID:
> > > > dddd0000000000000000000000000000
> > > >                         OOB: 0000
> > > >
> > > >
> > > > Are you sure you have a 5.47 bluetoothd running?
> > > >
> > > > Steve
> > > >
> > > >
> > > > On Wed, 2017-11-15 at 16:29 +0530, Vikrant More wrote:
> > > > > Thank very much !!
> > > > >
> > > > > I used your suggested commands. And I got following response
> > -
> > > > >
> > > > > [meshctl]# discover-unprovisioned on
> > > > > set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
> > > > > SetDiscoveryFilter failed: org.bluez.Error.InvalidArguments
> > > > > Discovery started
> > > > > Adapter property changed
> > > > > [CHG] Controller F0:03:8C:B7:5A:18 Discovering: yes
> > > > >
> > > > >
> > > > >
> > > > > meshctl]# provision dddd0000000000000000000000000000
> > > > > Device with UUID dddd0000000000000000000000000000 not found.
> > > > > Stale services? Remove device and re-discover
> > > > >
> > > > >
> > > > > On Wed, Nov 15, 2017 at 2:32 PM, Steve Brown <sbrown@cortland
> > .com
> > > > >
> > > > > wrote:
> > > > > > Hi Vikrant,
> > > > > >
> > > > > > On Wed, 2017-11-15 at 13:58 +0530, Vikrant More wrote:
> > > > > > > Hello,
> > > > > > > I to want build Zephyr based lighting system & for
> > testing I
> > > > have
> > > > > > 3
> > > > > > > nRF52840-PDK boards.
> > > > > > >
> > > > > > > I've flashed  zephyr/samples/bluetooth/mesh firmware on
> > all
> > > > three
> > > > > > > board.
> > > > > > > They are advertising themselves as any other GATT
> > peripheral
> > > > > > devices.
> > > > > > >
> > > > > > > As per my understanding they are in unprovisioned state.
> > > > > > >
> > > > > > > Using "NRF connect" Android app I can send data to
> > service
> > > > (Mesh
> > > > > > > Provisioning Service) running on it.
> > > > > > >
> > > > > > > I think this service is for provisioning purpose. Am I
> > right
> > > > ?
> > > > > > >
> > > > > > > How to do provisioning using meshctl utility (BlueZ 5.47)
> > ?
> > > > > > >
> > > > > > > When I execute meshctl on my ubuntu laptop it gives me
> > > > following
> > > > > > > error -
> > > > > > >
> > > > > > >        Local config directory not provided.
> > > > > > >    Failed to parse local node configuration file
> > > > local_node.json
> > > > > > >
> > > > > > >
> > > > > > I assume you built the bluez 5.47 from source.
> > > > > >
> > > > > > The json files live in bluez/mesh. You either have to run
> > > > meshctl
> > > > > > in
> > > > > > that directory or point to it with the "-c" option.
> > > > > >
> > > > > > Once in meshctl, the commands:
> > > > > > discover-unprovisioned on
> > > > > > provision <Device UUID>
> > > > > >
> > > > > > should get you going.
> > > > > >
> > > > > > In the mesh sample the UUID is hardwired to
> > > > > > "dddd0000000000000000000000000000"
> > > > > >
> > > > > > Steve
> > > > > >
> > > > >
> > > > >
> > >
> > >



Re: IPSP sample with KW41Z-BLE controller gives error: No route to host (on Linux kernel 4.4.0-98)

Luiz Augusto von Dentz
 

Hi Priyanka,

On Tue, Nov 14, 2017 at 2:47 PM, Priyanka Rawat <priyanka.rawat@nxp.com> wrote:
Hello


I test KW41Z-BLE controller with Zepyhr sample IPSP running in QEMU on Linux
Kernel 4.4.0-98


I load 6lowpan module and enable bluetooth_6lowpan module


# modprobe bluetooth_6lowpan
# modprobe 6lowpan

# echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable


However, while connecting the device it gives error "no route to host"


# echo "connect 00:60:37:00:00:16 1" >
/sys/kernel/debug/bluetooth/6lowpan_control
bash: echo: write error: No route to host
I guess your adapter is not powered, try bluetoothctl> power on

Any idea what is missing here?


$ sudo hcitool -i hci1 lecc 00:60:37:00:00:16
Connection handle 32

Whereas this works fine when I test zephyr IPSP sample (BLE host) with
virtual BLE controller connected to QEMU serial line.


ifconfig shows bt0 up after connecting the virtual device


# echo "connect 00:aa:01:00:00:23 1" >
/sys/kernel/debug/bluetooth/6lowpan_control


# cat /sys/kernel/debug/bluetooth/6lowpan_enable
1

# cat /sys/kernel/debug/bluetooth/6lowpan_control
00:aa:01:00:00:23 (type 1)
Note, this is all being deprecated by:

https://www.spinics.net/lists/linux-bluetooth/msg72592.html

--
Luiz Augusto von Dentz


Increasing serial buffer size for HCI commands

Priyanka
 

Hi

 

How can I increase serial buffer size over which HCI commands are sent / received, for example, on KW41Z side ?

Is there a software managed UART or Hardware?

 

For example, for Arduino, there is / was a way to change UART buffer size e.g.,

define SERIAL_TX_BUFFER_SIZE 256

define SERIAL_RX_BUFFER_SIZE 256

 

Thanks

Priyanka


Re: [Zephyr-devel] Zephyr Based Bluetooth Mesh implementation on nRF52840-PDK boards

Steve Brown
 

It looks like you have some kind of problem on the bluez end.

I get the following on the same board.

[meshctl]# discover-unprovisioned on
set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
SetDiscoveryFilter success
Discovery started
Adapter property changed
[CHG] Controller B8:27:EB:06:2E:57 Discovering: yes
Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
Device UUID: dddd0000000000000000000000000000
OOB: 0000


Are you sure you have a 5.47 bluetoothd running?

Steve

On Wed, 2017-11-15 at 16:29 +0530, Vikrant More wrote:
Thank very much !!

I used your suggested commands. And I got following response -

[meshctl]# discover-unprovisioned on
set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
SetDiscoveryFilter failed: org.bluez.Error.InvalidArguments
Discovery started
Adapter property changed
[CHG] Controller F0:03:8C:B7:5A:18 Discovering: yes



meshctl]# provision dddd0000000000000000000000000000
Device with UUID dddd0000000000000000000000000000 not found.
Stale services? Remove device and re-discover


On Wed, Nov 15, 2017 at 2:32 PM, Steve Brown <sbrown@cortland.com>
wrote:
Hi Vikrant,

On Wed, 2017-11-15 at 13:58 +0530, Vikrant More wrote:
Hello,
I to want build Zephyr based lighting system & for testing I have
3
nRF52840-PDK boards.

I've flashed zephyr/samples/bluetooth/mesh firmware on all three
board.
They are advertising themselves as any other GATT peripheral
devices.

As per my understanding they are in unprovisioned state.

Using "NRF connect" Android app I can send data to service (Mesh
Provisioning Service) running on it.

I think this service is for provisioning purpose. Am I right ?

How to do provisioning using meshctl utility (BlueZ 5.47) ?

When I execute meshctl on my ubuntu laptop it gives me following
error -

Local config directory not provided.
Failed to parse local node configuration file local_node.json

I assume you built the bluez 5.47 from source.

The json files live in bluez/mesh. You either have to run meshctl
in
that directory or point to it with the "-c" option.

Once in meshctl, the commands:
discover-unprovisioned on
provision <Device UUID>

should get you going.

In the mesh sample the UUID is hardwired to
"dddd0000000000000000000000000000"

Steve


Re: [Zephyr-devel] Zephyr Based Bluetooth Mesh implementation on nRF52840-PDK boards

Vikrant More <vikrant8051@...>
 

Thank very much !!

I used your suggested commands. And I got following response - 

[meshctl]# discover-unprovisioned on
set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
SetDiscoveryFilter failed: org.bluez.Error.InvalidArguments
Discovery started
Adapter property changed 
[CHG] Controller F0:03:8C:B7:5A:18 Discovering: yes



meshctl]# provision dddd0000000000000000000000000000
Device with UUID dddd0000000000000000000000000000 not found.
Stale services? Remove device and re-discover


On Wed, Nov 15, 2017 at 2:32 PM, Steve Brown <sbrown@...> wrote:
Hi Vikrant,

On Wed, 2017-11-15 at 13:58 +0530, Vikrant More wrote:
> Hello,
> I to want build Zephyr based lighting system & for testing I have 3
> nRF52840-PDK boards.
>
> I've flashed  zephyr/samples/bluetooth/mesh firmware on all three
> board.
> They are advertising themselves as any other GATT peripheral devices.
>
> As per my understanding they are in unprovisioned state.
>
> Using "NRF connect" Android app I can send data to service (Mesh
> Provisioning Service) running on it.
>
> I think this service is for provisioning purpose. Am I right ?
>
> How to do provisioning using meshctl utility (BlueZ 5.47) ?
>
> When I execute meshctl on my ubuntu laptop it gives me following
> error -
>
>        Local config directory not provided.
>    Failed to parse local node configuration file local_node.json
>
>
I assume you built the bluez 5.47 from source.

The json files live in bluez/mesh. You either have to run meshctl in
that directory or point to it with the "-c" option.

Once in meshctl, the commands:
discover-unprovisioned on
provision <Device UUID>

should get you going.

In the mesh sample the UUID is hardwired to
"dddd0000000000000000000000000000"

Steve



Re: [Zephyr-devel] Zephyr Based Bluetooth Mesh implementation on nRF52840-PDK boards

Steve Brown
 

Hi Vikrant,

On Wed, 2017-11-15 at 13:58 +0530, Vikrant More wrote:
Hello,
I to want build Zephyr based lighting system & for testing I have 3
nRF52840-PDK boards.

I've flashed zephyr/samples/bluetooth/mesh firmware on all three
board.
They are advertising themselves as any other GATT peripheral devices.

As per my understanding they are in unprovisioned state.

Using "NRF connect" Android app I can send data to service (Mesh
Provisioning Service) running on it.

I think this service is for provisioning purpose. Am I right ?

How to do provisioning using meshctl utility (BlueZ 5.47) ?

When I execute meshctl on my ubuntu laptop it gives me following
error -

Local config directory not provided.
Failed to parse local node configuration file local_node.json

I assume you built the bluez 5.47 from source.

The json files live in bluez/mesh. You either have to run meshctl in
that directory or point to it with the "-c" option.

Once in meshctl, the commands:
discover-unprovisioned on
provision <Device UUID>

should get you going.

In the mesh sample the UUID is hardwired to
"dddd0000000000000000000000000000"

Steve


Zephyr Based Bluetooth Mesh implementation on nRF52840-PDK boards

Vikrant More <vikrant8051@...>
 

Hello,
I to want build Zephyr based lighting system & for testing I have 3 nRF52840-PDK boards.

I've flashed  zephyr/samples/bluetooth/mesh firmware on all three board.
They are advertising themselves as any other GATT peripheral devices.

As per my understanding they are in unprovisioned state. 

Using "NRF connect" Android app I can send data to service (Mesh Provisioning Service) running on it.

I think this service is for provisioning purpose. Am I right ?

How to do provisioning using meshctl utility (BlueZ 5.47) ?

When I execute meshctl on my ubuntu laptop it gives me following error - 

       Local config directory not provided.
   Failed to parse local node configuration file local_node.json

From where I can get this local_node.json which is compatible for nRF52840-PDK ?

I've also posted same Question of Nordic Semi. devzone forum:


Bluetooth Mesh

Vikrant More <vikrant8051@...>
 

I want build Zephyr based lighting system & for testing I have 3 nRF52840-PDK boards.

I've flashed  zephyr/samples/bluetooth/mesh firmware on all three board.
They are advertising themselves as any other GATT peripheral devices.

As per my understanding they are in unprovisioned state. 

Using "NRF connect" Android app I can send data to service (Mesh Provisioning Service) running on it.

I think this service is for provisioning purpose. Am I right ?

How to do provisioning using meshctl utility (BlueZ 5.47) ?

When I execute meshctl on my ubuntu laptop it gives me following error - 

       Local config directory not provided.
   Failed to parse local node configuration file local_node.json

From where I can get this local_node.json which is compatible for nRF52840-PDK ?

I've also posted same Question of Nordic Semi. devzone forum:


IPSP sample with KW41Z-BLE controller gives error: No route to host (on Linux kernel 4.4.0-98)

Priyanka
 

Hello


I test KW41Z-BLE controller with Zepyhr sample IPSP running in QEMU on Linux Kernel 4.4.0-98


I load 6lowpan module and enable bluetooth_6lowpan module 


# modprobe bluetooth_6lowpan
# modprobe 6lowpan

# echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable


However, while connecting the device it gives error "no route to host"


# echo "connect 00:60:37:00:00:16 1" > /sys/kernel/debug/bluetooth/6lowpan_control
bash: echo: write error: No route to host

Any idea what is missing here?


$ sudo hcitool -i hci1 lecc 00:60:37:00:00:16
Connection handle 32

Whereas this works fine when I test zephyr IPSP sample (BLE host) with virtual BLE controller connected to QEMU serial line.


ifconfig shows bt0 up after connecting the virtual device


# echo "connect 00:aa:01:00:00:23 1" > /sys/kernel/debug/bluetooth/6lowpan_control


# cat /sys/kernel/debug/bluetooth/6lowpan_enable
1

# cat /sys/kernel/debug/bluetooth/6lowpan_control
00:aa:01:00:00:23 (type 1)


Thanks

Priyanka



Re: Odp.: 6loWPAN IPSP devices fail to communicate (bluetooth-next 4.14.0-rc7 )

Luiz Augusto von Dentz
 

Hi Dogiel,

On Tue, Nov 14, 2017 at 1:27 PM, Dogiel Pawel <Pawel.Dogiel@tieto.com> wrote:
Hi Luiz,

Thank You for Your response, fix for multi-link setup worked fine for Me.
If you can please then respond to the patch since that seems to be
ignored for now, though it might not be useful in the future.

Now I'm trying to use userspace way with patches for kernel and BlueZ:

https://marc.info/?l=linux-wpan&m=150832838029474&w=4
and
https://www.spinics.net/lists/linux-bluetooth/msg72592.html

After that managed to connect to the devices and can see the bt0 interface but for now I can not ping any device.
Neither if there is one or multiple of them.
Looks like that was not the latest version, let me send a v3 of that.

Regards,
Pawel

________________________________________
Od: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Wysłane: 10 listopada 2017 13:03:55
Do: Dogiel Pawel
DW: Zephyr-users@lists.zephyrproject.org
Temat: Re: [Zephyr-users] 6loWPAN IPSP devices fail to communicate (bluetooth-next 4.14.0-rc7 )

Hi Dogiel,

We will be removing the debugfs in the future, there are actually
patches on the BlueZ mailing to implement it in userspace using the
TUN/TAP driver through the kernel part is still not settle:

https://www.spinics.net/lists/linux-bluetooth/msg72592.html

In the meantime you may try this:

https://www.spinics.net/lists/linux-bluetooth/msg72040.html

On Thu, Nov 9, 2017 at 3:54 PM, Dogiel Pawel <Pawel.Dogiel@tieto.com> wrote:
Hello,

I have issue with IPSP devices over 6loWPAN on kernel 4.14.0-rc7.

The thing is that when I connect My Linux machine to one IPSP device using 'debugfs' interface the communication is OK. Pings are working.
But when second IPSP device is connected no pings are received from IPSP devices ('resource unreachable').

Regards,
Pawel
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users


--
Luiz Augusto von Dentz


--
Luiz Augusto von Dentz


Odp.: 6loWPAN IPSP devices fail to communicate (bluetooth-next 4.14.0-rc7 )

Dogiel Pawel <Pawel.Dogiel@...>
 

Hi Luiz,

Thank You for Your response, fix for multi-link setup worked fine for Me.

Now I'm trying to use userspace way with patches for kernel and BlueZ:

https://marc.info/?l=linux-wpan&m=150832838029474&w=4
and
https://www.spinics.net/lists/linux-bluetooth/msg72592.html

After that managed to connect to the devices and can see the bt0 interface but for now I can not ping any device.
Neither if there is one or multiple of them.

Regards,
Pawel

________________________________________
Od: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Wysłane: 10 listopada 2017 13:03:55
Do: Dogiel Pawel
DW: Zephyr-users@lists.zephyrproject.org
Temat: Re: [Zephyr-users] 6loWPAN IPSP devices fail to communicate (bluetooth-next 4.14.0-rc7 )

Hi Dogiel,

We will be removing the debugfs in the future, there are actually
patches on the BlueZ mailing to implement it in userspace using the
TUN/TAP driver through the kernel part is still not settle:

https://www.spinics.net/lists/linux-bluetooth/msg72592.html

In the meantime you may try this:

https://www.spinics.net/lists/linux-bluetooth/msg72040.html

On Thu, Nov 9, 2017 at 3:54 PM, Dogiel Pawel <Pawel.Dogiel@tieto.com> wrote:
Hello,

I have issue with IPSP devices over 6loWPAN on kernel 4.14.0-rc7.

The thing is that when I connect My Linux machine to one IPSP device using 'debugfs' interface the communication is OK. Pings are working.
But when second IPSP device is connected no pings are received from IPSP devices ('resource unreachable').

Regards,
Pawel
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users


--
Luiz Augusto von Dentz


Re: I2C on nucleo L476RG

Yannis Damigos
 

Hi Nicolas,

did you also update dts.fixup file in boards directory?

Best regards,
Yannis

On Sun, Nov 12, 2017 at 4:31 PM, Nicolas Gonzalez <nicolas@ngonzalez.fr> wrote:
Hello,

I am new to Zephyr and i try to use I2C on my nucleo L476RG.

dev = device_get_binding(CONFIG_I2C_1_NAME);
^ This always return NULL.

I saw in the pinmux.c that I2C_1 could be used :
#ifdef CONFIG_I2C_1
{STM32_PIN_PB6, STM32L4X_PINMUX_FUNC_PB6_I2C1_SCL},
{STM32_PIN_PB7, STM32L4X_PINMUX_FUNC_PB7_I2C1_SDA},
#endif /* CONFIG_I2C_1 */

I decided to add these lines to my prf.conf :
CONFIG_I2C=y
CONFIG_I2C_1=y
CONFIG_I2C_1_IRQ_PRI=1

It doesn't work at all ...
I tried to modify the device tree of the board but unsuccessful too :)

Thank you for your help,
ngonzalez
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users


I2C on nucleo L476RG

Nicolas Gonzalez <nicolas@...>
 

Hello,

I am new to Zephyr and i try to use I2C on my nucleo L476RG.

dev = device_get_binding(CONFIG_I2C_1_NAME);
^ This always return NULL.

I saw in the pinmux.c that I2C_1 could be used :
#ifdef CONFIG_I2C_1
{STM32_PIN_PB6, STM32L4X_PINMUX_FUNC_PB6_I2C1_SCL},
{STM32_PIN_PB7, STM32L4X_PINMUX_FUNC_PB7_I2C1_SDA},
#endif /* CONFIG_I2C_1 */

I decided to add these lines to my prf.conf :
CONFIG_I2C=y
CONFIG_I2C_1=y
CONFIG_I2C_1_IRQ_PRI=1

It doesn't work at all ...
I tried to modify the device tree of the board but unsuccessful too :)

Thank you for your help,
ngonzalez


Re: 6loWPAN IPSP devices fail to communicate (bluetooth-next 4.14.0-rc7 )

Luiz Augusto von Dentz
 

Hi Dogiel,

We will be removing the debugfs in the future, there are actually
patches on the BlueZ mailing to implement it in userspace using the
TUN/TAP driver through the kernel part is still not settle:

https://www.spinics.net/lists/linux-bluetooth/msg72592.html

In the meantime you may try this:

https://www.spinics.net/lists/linux-bluetooth/msg72040.html

On Thu, Nov 9, 2017 at 3:54 PM, Dogiel Pawel <Pawel.Dogiel@tieto.com> wrote:
Hello,

I have issue with IPSP devices over 6loWPAN on kernel 4.14.0-rc7.

The thing is that when I connect My Linux machine to one IPSP device using 'debugfs' interface the communication is OK. Pings are working.
But when second IPSP device is connected no pings are received from IPSP devices ('resource unreachable').

Regards,
Pawel
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users
--
Luiz Augusto von Dentz


Re: [Zephyr-devel] CMake migration complete

Carles Cufi
 

Hi Kumar, Anas,

Yes, conf is now part of the SDK on Linux. That said, and since bundling an SDK for macOS and Windows is tricky, our current plan is to switch to Python for Kconfig.

Regards,

Carles

-----Original Message-----
From: Nashif, Anas [mailto:anas.nashif@intel.com]
Sent: 09 November 2017 15:12
To: Kumar Gala <kumar.gala@linaro.org>; Cufi, Carles
<Carles.Cufi@nordicsemi.no>
Cc: zephyr-users@lists.zephyrproject.org; zephyr-
devel@lists.zephyrproject.org
Subject: RE: [Zephyr-devel] CMake migration complete

Conf is coming from SDK now (on Linux)

-----Original Message-----
From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-
bounces@lists.zephyrproject.org] On Behalf Of Kumar Gala
Sent: Thursday, November 9, 2017 9:09 AM
To: Cufi, Carles <Carles.Cufi@nordicsemi.no>
Cc: zephyr-users@lists.zephyrproject.org; zephyr-
devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] CMake migration complete

Curious why on OS-X we need conf build before hand instead of doing what
we do on linux?

Or are we getting conf from the SDK on linux?

- k
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel


Re: [Zephyr-devel] CMake migration complete

Nashif, Anas
 

Conf is coming from SDK now (on Linux)

-----Original Message-----
From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-bounces@lists.zephyrproject.org] On Behalf Of Kumar Gala
Sent: Thursday, November 9, 2017 9:09 AM
To: Cufi, Carles <Carles.Cufi@nordicsemi.no>
Cc: zephyr-users@lists.zephyrproject.org; zephyr-devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] CMake migration complete

Curious why on OS-X we need conf build before hand instead of doing what we do on linux?

Or are we getting conf from the SDK on linux?

- k
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel


Re: [Zephyr-devel] CMake migration complete

Kumar Gala
 

Curious why on OS-X we need conf build before hand instead of doing what we do on linux?

Or are we getting conf from the SDK on linux?

- k


6loWPAN IPSP devices fail to communicate (bluetooth-next 4.14.0-rc7 )

Dogiel Pawel <Pawel.Dogiel@...>
 

Hello,

I have issue with IPSP devices over 6loWPAN on kernel 4.14.0-rc7.

The thing is that when I connect My Linux machine to one IPSP device using 'debugfs' interface the communication is OK. Pings are working.
But when second IPSP device is connected no pings are received from IPSP devices ('resource unreachable').

Regards,
Pawel


Re: [Zephyr-devel] CMake migration complete

Carles Cufi
 

Hi Erwin,

-----Original Message-----
From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-
bounces@lists.zephyrproject.org] On Behalf Of Erwin Rol
Sent: 09 November 2017 10:56
To: Bøe, Sebastian <Sebastian.Boe@nordicsemi.no>; zephyr-
devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] CMake migration complete

Well that kind of sucks, cause the on Redhat 7.X the newest cmake is
3.6.x.

Will the needed cmake be part of the toolchain ?
No, but it's quite simple to install a recent version of CMake manually:

http://docs.zephyrproject.org/getting_started/installation_linux.html#installing-requirements-and-dependencies

$ mkdir $HOME/work_dir && cd $HOME/work_dir
$ wget https://cmake.org/files/v3.8/cmake-3.8.2-Linux-x86_64.sh
$ yes | sh cmake-3.8.2-Linux-x86_64.sh | cat
$ echo "export PATH=$PWD/cmake-3.8.2-Linux-x86_64/bin:\$PATH" >> $HOME/.zephyrrc
$ bash
$ cmake --version

Regards,

Carles



- Erwin


On Thu, 2017-11-09 at 08:57 +0000, Bøe, Sebastian wrote:
PS: Correction; install cmake 3.8.2 or later.
From: Bøe, Sebastian
Sent: Thursday, 9 November 2017 9:42:27 AM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrpr
oject.org
Subject: CMake migration complete

Hi all,

Zephyr has finally migrated to CMake.

This migration is an important step in a larger effort to make Zephyr
easy to use for application developers working on different platforms
with different development environment needs.

Simplified, this change retains Kconfig as-is, and replaces all
Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild
offers is replaced by a set of CMake extentions. These extentions have
either provided simple one-to-one translations of KBuild features or
introduced new concepts that replace KBuild concepts.

This is a breaking change for existing test infrastructure and build
scripts that are maintained out-of-tree. But for FW itself, no porting
should be necessary.

For users that just want to continue their work with minimal
disruption the following should suffice:

Install CMake 3.8.2 exactly

Port any out-of-tree Makefiles to CMake.

Learn the absolute minimum about the new command line interface:

# To do a clean build;

$ cd samples/hello_world
$ mkdir build && cd build
$ cmake -DBOARD=nrf52_pca10040 ..

# For incremental builds;

$ cd build
$ make

PR: https://github.com/zephyrproject-rtos/zephyr/pull/4692
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel


Re: [Zephyr-devel] CMake migration complete

Erwin Rol <mailinglists@...>
 

Well that kind of sucks, cause the on Redhat 7.X the newest cmake is
3.6.x.

Will the needed cmake be part of the toolchain ?

- Erwin

On Thu, 2017-11-09 at 08:57 +0000, Bøe, Sebastian wrote:
PS: Correction; install cmake 3.8.2 or later.
From: Bøe, Sebastian
Sent: Thursday, 9 November 2017 9:42:27 AM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrpr
oject.org
Subject: CMake migration complete
 
Hi all,

Zephyr has finally migrated to CMake.

This migration is an important step in a larger effort to make Zephyr
easy to use for application developers working on different platforms
with different development environment needs.

Simplified, this change retains Kconfig as-is, and replaces all
Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild
offers is replaced by a set of CMake extentions. These extentions
have
either provided simple one-to-one translations of KBuild features or
introduced new concepts that replace KBuild concepts.

This is a breaking change for existing test infrastructure and build
scripts that are maintained out-of-tree. But for FW itself, no
porting
should be necessary.

For users that just want to continue their work with minimal
disruption the following should suffice:

Install CMake 3.8.2 exactly

Port any out-of-tree Makefiles to CMake.

Learn the absolute minimum about the new command line interface:

# To do a clean build;

$ cd samples/hello_world
$ mkdir build && cd build
$ cmake -DBOARD=nrf52_pca10040 ..

# For incremental builds;

$ cd build
$ make

PR: https://github.com/zephyrproject-rtos/zephyr/pull/4692
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel

2341 - 2360 of 2599