devel@lists.zephyrproject.org

Re: Extracting iBeacon Advertisement Packets

Martin <ma@...>

#5446

Sorry, I was copying the wrong code..

int i;

//print adv. packet
for(i=0;i<buf->len;i++) {
printk("%d %02X\n",i, buf->data[i]);
}

//print major
printk("maj: %d\n",((buf->data[25] & 0xff) * 0x100 + (buf->data[26] & 0xff) ));
Am Mi., 21. Nov. 2018 um 18:12 Uhr schrieb Martin <ma@jgs-wg.de>:

Show quoted text

Well, simple enough.

int i;

for(i=0; i<5; i++) {
printf("i%d\n", i+1);
}

prints the advertisement packet's bytes in decimals and includes the
UUID acc. to the kontakt.io article. Hope this helps anyone...

Martin
Am Mi., 21. Nov. 2018 um 17:56 Uhr schrieb Martin <ma@jgs-wg.de>:

Hi,
I am quite new to Zephyr and want to extract iBeacon Advertisement
Packets. I already have access to them as a net_buf_simple structure,
but I want to read the major and minor for example. I realize that I
have to probably read some certain bytes out of net_buf_simple
(according to https://support.kontakt.io/hc/en-gb/articles/201492492-Advertising-packet-structure).
Can someone point me to a direction (function) to do this?

Thanks,
Martin

Re: Extracting iBeacon Advertisement Packets

Martin <ma@...>

#5445

Well, simple enough.

int i;

for(i=0; i<5; i++) {
printf("i%d\n", i+1);
}

prints the advertisement packet's bytes in decimals and includes the
UUID acc. to the kontakt.io article. Hope this helps anyone...

Martin
Am Mi., 21. Nov. 2018 um 17:56 Uhr schrieb Martin <ma@jgs-wg.de>:

Show quoted text

Hi,
I am quite new to Zephyr and want to extract iBeacon Advertisement
Packets. I already have access to them as a net_buf_simple structure,
but I want to read the major and minor for example. I realize that I
have to probably read some certain bytes out of net_buf_simple
(according to https://support.kontakt.io/hc/en-gb/articles/201492492-Advertising-packet-structure).
Can someone point me to a direction (function) to do this?

Thanks,
Martin

Extracting iBeacon Advertisement Packets

Martin <ma@...>

#5444

Hi,
I am quite new to Zephyr and want to extract iBeacon Advertisement
Packets. I already have access to them as a net_buf_simple structure,
but I want to read the major and minor for example. I realize that I
have to probably read some certain bytes out of net_buf_simple
(according to https://support.kontakt.io/hc/en-gb/articles/201492492-Advertising-packet-structure).
Can someone point me to a direction (function) to do this?

Thanks,
Martin

Re: Zephyr BLE Controller Nordic - BLE qualification process

frv

#5443

Hi Luiz Augusto von Dentz,

Thank you very much for your reply. This should give me sufficient direction to go further.

The idea for our BLE central oriented platform (two boards solution) is to run on the BLE Host board Linux and thus depending on BlueZ. The BLE controller runs on a Nordic board Zephyr (HCI_UART).
Both boards will be bridged via a HCI uart(h4) transport layer.

Our BLE peripheral oriented platform might be a pure single board Nordic BLE Host Controller approach depending on Nordic's SoftDevice for the BLE stack.

Best regards,
Frank

Re: Zephyr BLE Controller Nordic - BLE qualification process

Luiz Augusto von Dentz

#5442

Hi,
On Wed, Nov 21, 2018 at 10:39 AM frv <F.Vieren@televic.com> wrote:

[Edited Message Follows]

Hi Carles,

Probably all is here for the qualification process, correct? : https://www.bluetooth.com/develop-with-bluetooth/qualification-listingThere is a listing for the Host Stack as well:

https://launchstudio.bluetooth.com/ListingDetails/70189

Just wondering do we have extra concerns should we rely on the BlueZ stack at Host side except for the GPL licensing.
Probably when relying on QT which is LGPL and wraps the BlueZ stack we don't have issues around strict GPL licensing?Is your system going to run Zephyr or Linux/BlueZ as host stack? BlueZ
daemon is GPL but that exposes APIs over D-Bus so you are not really
linking to it, that said the qualification for BlueZ  also depends on
the Kernel. There is quite a few listings of BlueZ:

https://launchstudio.bluetooth.com/ListingDetails/65535
https://launchstudio.bluetooth.com/ListingDetails/48333
https://launchstudio.bluetooth.com/ListingDetails/507
https://launchstudio.bluetooth.com/ListingDetails/12555
https://launchstudio.bluetooth.com/ListingDetails/7341
https://launchstudio.bluetooth.com/ListingDetails/17086
https://launchstudio.bluetooth.com/ListingDetails/7319

From looks of them the latest BlueZ listing is for version 5.48,
though depending on the product they may have only some layers
qualified not the entire stack.

Update 9h38 21/11/2018 :
Our company has a SIG account, so I have registered for a user account, to be able to fetch documentation and ask questions.

Best regards,
Frank


-- 
Luiz Augusto von Dentz

Re: Zephyr BLE Controller Nordic - BLE qualification process

frv

#5441
Edited

Hi Carles,

Probably all is here for the qualification process, correct? : https://www.bluetooth.com/develop-with-bluetooth/qualification-listing

Just wondering do we have extra concerns should we rely on the BlueZ stack at Host side except for the GPL licensing.
Probably when relying on QT which is LGPL and wraps the BlueZ stack we don't have issues around strict GPL licensing?

Update 9h38 21/11/2018 :
Our company has a SIG account, so I have registered for a user account, to be able to fetch documentation and ask questions.

Best regards,
Frank

Zephyr BLE Controller Nordic - BLE qualification process

frv

#5440

Hi Carles,

In the document: https://www.zephyrproject.org/building-a-qualified-ble-controller-with-zephyr-os-1-9/

at the end this is mentioned:

“Note that Nordic’s qualification will only cover the BLE Controller, which means that whichever Host is used for a particular design will have to be qualified independently.”

What does this really imply for us? Is there an official procedure from the SIG or some other authority that must be followed. Is this documented somewhere?

Thanks in advance.

Best regards,

Frank

Re: Zephyr BLE Controller Nordic HW no longer related to SoftDevice?

frv

#5439

Hi Carles,

Great! Thanks for your confirmation on my observations regarding the Nordic SoftDevice and the Zephyr implementation.

I think for a BLE host (central role) implementation we will forward for the 2 boards solutions, running on the BLE host board a Linux OS that uses a BLE SW framework (e.g. QT BLE) that is BlueZ based and using the Nordic HW board as connectivity chip, the BLE controller based on Zephyr.

Nevertheless if Nordic's PC BLE driver SW stack becomes more mature and stable it might also be a solution.
However my experience with running Zephyr on the Nordic nRF52 is so far great, so it will be hard to move back to the "serialization solution" of Nordic that is also nice.

Best regards,
Frank

Re: Zephyr BLE Controller Nordic HW no longer related to SoftDevice?

Carles Cufi

#5438

Hi Frank,

The SoftDevice is Nordic’s proprietary BLE protocol stack. It consists of a binary blob that is flashed at the beginning of the flash memory and can be accessed through SV calls, and it is designed to be the arbitrator to control access to certain hardware on the chip. This is incompatible with Zephyr, which already includes a completely different BLE stack which is open source and located in subsys/bluetooth/.

So the answer to your first question is that the SoftDevice cannot be combined with Zephyr, and you should not need to do so since Zephyr already has its own BLE stack.

The answer to the second question is also “yes”. The SoftDevice doesn’t expose an HCI interface, making it unsuitable for use as a BLE Controller, which is what BlueZ requires. Zephyr on the other hand can be built to expose an HCI interface (hci_uart) to work with BlueZ.

Carles

Show quoted text

From: devel@... <devel@...> On Behalf Of frv
Sent: 20 November 2018 10:53
To: devel@...
Subject: [Zephyr-devel] Zephyr BLE Controller Nordic HW no longer related to SoftDevice?

Hi Community, Carles,

Without having looking into the details for the HCI_UART implementation when using Zephyr RTOS as SW platform for implementing the BLE controller on Nordic HW, the SoftDevice is no longer present in the SW stack. Correct?

Is it further correct to say that the SoftDevice SW which is Nordic specific replaces the standard HCI way on which BlueZ is based.

I base my understandings on this nice written document:

https://www.zephyrproject.org/building-a-qualified-ble-controller-with-zephyr-os-1-9/

Thanks in advance,

Best regards,

Frank

Zephyr BLE Controller Nordic HW no longer related to SoftDevice?

frv

#5437

Hi Community, Carles,

Without having looking into the details for the HCI_UART implementation when using Zephyr RTOS as SW platform for implementing the BLE controller on Nordic HW, the SoftDevice is no longer present in the SW stack. Correct?

Is it further correct to say that the SoftDevice SW which is Nordic specific replaces the standard HCI way on which BlueZ is based.

I base my understandings on this nice written document:

https://www.zephyrproject.org/building-a-qualified-ble-controller-with-zephyr-os-1-9/

Thanks in advance,

Best regards,

Frank

Bluetooth: Mesh: APP key & Mesh initialisation delay related issue

vikrant8051 <vikrant8051@...>

#5436

Hi,

1) If we, (provision -> unprovision -> provision) the Bluetooth Mesh Node which is based on onoff_level_lighting_vnd_app then in case of some arbitrary available Model APP key not get save on SoC persistent storage during "any" reprovision event.

After reboot we have to reassign APP key to things get work.

2) Still facing Mesh initialisation delay. This is because of some recent commits.

There could be problem in commits which are merged after

46386522142e546c6e028db0f560c6db25a02d06

Thank You !!

Re: Can't use ninja flash for Nucleo board at macos

cstyle

#5435

The problem has been solved by

The problem has already been solved by export OPENOCD_DEFAULT_PATH

Re: Looking for help with SAMD2x

Sean Nyekjær <sean@...>

#5434

On Sun, 18 Nov 2018 at 10.24, Henrik Brix Andersen <henrik@...> wrote:

Hi,

> On 16 Nov 2018, at 18.28, Kumar Gala <kumar.gala@...> wrote:
>
> Guys,
>
> I’m looking to see if someone (or group) can help with maintenance of the Atmel SAMD2x SoC family. We have a few things that need updating (like the watchdog driver). And need someone I can check in w/from time to time if there are questions or we need testing on a board.
>
> Let me know if you can help in the short term with converting drivers/watchdog/wdt_sam0.c to use the new watchdog API.

I am working on converting the SAM0 WDT implementation to the new API (https://github.com/zephyrproject-rtos/zephyr/issues/10914).

Regards,
Brix
--
Henrik Brix Andersen

I’m also available if needed :-)

For the sam0 it’s only in my spare time...

/Sean

Re: Looking for help with SAMD2x

Henrik Brix Andersen

#5433

Hi,

On 16 Nov 2018, at 18.28, Kumar Gala <kumar.gala@linaro.org> wrote:

Guys,

I’m looking to see if someone (or group) can help with maintenance of the Atmel SAMD2x SoC family.  We have a few things that need updating (like the watchdog driver).  And need someone I can check in w/from time to time if there are questions or we need testing on a board.

Let me know if you can help in the short term with converting drivers/watchdog/wdt_sam0.c to use the new watchdog API.I am working on converting the SAM0 WDT implementation to the new API (https://github.com/zephyrproject-rtos/zephyr/issues/10914).

Regards,
Brix
--  
Henrik Brix Andersen

Can't use ninja flash for Nucleo board at macos

cstyle

#5432

After install open-ocd and  gcc-arm-none-eabi-7-2018-q2-update-mac I can build zephyr seccess,but can’t use ninja flash to flash to my hw board on macOS.

Is there any file missing (board/st_nucleo_l4.cfg),how to fix this bug? Thanks.

Error message like this:

azhuodeMacBook-Pro:build azhuo$ ninja flash
[0/1] Flashing nucleo_l476rg
Using runner: openocd
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
/Users/azhuo/zephyr/zephyr/boards/arm/nucleo_l476rg/support/openocd.cfg:1: Error: Can't find board/st_nucleo_l4.cfg
in procedure 'script' 
at file "embedded:startup.tcl", line 60
at file "/Users/azhuo/zephyr/zephyr/boards/arm/nucleo_l476rg/support/openocd.cfg", line 1

ERROR: command exited with status 1: /usr/local/bin/openocd -f /Users/azhuo/zephyr/zephyr/boards/arm/nucleo_l476rg/support/openocd.cfg -c init -c targets -c 'reset halt' -c 'flash write_image
 erase /Users/azhuo/zephyr/zephyr/samples/hello_world/build/zephyr/zephyr.bin 0x8000000' -c 'reset halt' -c 'verify_image /Users/azhuo/zephyr/zephyr/samples/hello_world/build/zephyr/zephyr.bin 0x8000000' -c 'reset run' -c shutdown
run as "west -v ... flash ..." for a stack trace

Re: Looking for help with SAMD2x

Vincent - VLoTech

#5431

Hi Kumar,

We work mostly with sam4s series but also used samd21 before. 
I can help you with the maintenance and also align the atmel SoC series. 

Please let me know if you are interested in my help and what is needed. 

Kind regards

Vincent

Show quoted text

Op 16 nov. 2018 om 18:28 heeft Kumar Gala <kumar.gala@linaro.org> het volgende geschreven:

Guys,

I’m looking to see if someone (or group) can help with maintenance of the Atmel SAMD2x SoC family.  We have a few things that need updating (like the watchdog driver).  And need someone I can check in w/from time to time if there are questions or we need testing on a board.

Let me know if you can help in the short term with converting drivers/watchdog/wdt_sam0.c to use the new watchdog API.

[ I also have a question about testing flash support ]

thanks

- k

Not able to build any project

vikrant8051 <vikrant8051@...>

#5430

Hello,

After latest sync with master branch not able to build any project ....

For details this is log for building hello_world app ...

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

root@computer:/home/vikrant/zephyr/samples/hello_world/build# cmake -GNinja -DBOARD=nrf52840_pca10056 ..
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.6", minimum required is "3.4")
-- Selected BOARD nrf52840_pca10056
Zephyr version: 1.13.99
Parsing Kconfig tree in /home/vikrant/zephyr/Kconfig
Loading /home/vikrant/zephyr/boards/arm/nrf52840_pca10056/nrf52840_pca10056_defconfig as base
Merging /home/vikrant/zephyr/samples/hello_world/prj.conf
-- Generating zephyr/include/generated/generated_dts_board.h
nrf52840_pca10056.dts_compiled: Warning (unique_unit_address): /soc/i2c@40003000: duplicate unit-address (also used in node /soc/spi@40003000)
nrf52840_pca10056.dts_compiled: Warning (unique_unit_address): /soc/i2c@40004000: duplicate unit-address (also used in node /soc/spi@40004000)
-- Cache files will be written to: /root/.cache/zephyr
-- The C compiler identification is GNU 6.2.0
-- The CXX compiler identification is GNU 6.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-gcc
-- Performing Test toolchain_is_ok
-- Performing Test toolchain_is_ok - Success
-- Configuring done
CMake Error at ../../CMakeLists.txt:1226 (target_link_libraries):
Error evaluating generator expression:

    $<TARGET_OBJECTS:offsets>

The evaluation of the TARGET_OBJECTS generator expression is only suitable
for consumption by CMake. It is not suitable for writing out elsewhere.

CMake Error at ../../CMakeLists.txt:1191 (target_link_libraries):
Error evaluating generator expression:

    $<TARGET_OBJECTS:offsets>

The evaluation of the TARGET_OBJECTS generator expression is only suitable
for consumption by CMake. It is not suitable for writing out elsewhere.

CMake Error at ../../CMakeLists.txt:570 (add_custom_command):
Error evaluating generator expression:

    $<TARGET_OBJECTS:offsets>

The evaluation of the TARGET_OBJECTS generator expression is only suitable
for consumption by CMake. It is not suitable for writing out elsewhere.

CMake Error at ../../CMakeLists.txt:570 (add_custom_command):
Error evaluating generator expression:

    $<TARGET_OBJECTS:offsets>

The evaluation of the TARGET_OBJECTS generator expression is only suitable
for consumption by CMake. It is not suitable for writing out elsewhere.

CMake Error at ../../CMakeLists.txt:570 (add_custom_command):
Error evaluating generator expression:

    $<TARGET_OBJECTS:offsets>

The evaluation of the TARGET_OBJECTS generator expression is only suitable
for consumption by CMake. It is not suitable for writing out elsewhere.

-- Generating done
-- Build files have been written to: /home/vikrant/zephyr/samples/hello_world/build

Thank You !!

Looking for help with SAMD2x

Kumar Gala

#5429

Guys,

I’m looking to see if someone (or group) can help with maintenance of the Atmel SAMD2x SoC family.  We have a few things that need updating (like the watchdog driver).  And need someone I can check in w/from time to time if there are questions or we need testing on a board.

Let me know if you can help in the short term with converting drivers/watchdog/wdt_sam0.c to use the new watchdog API.

[ I also have a question about testing flash support ]

thanks

- k

Re: Getting started with ARM GNU Compiler | errors | #gettingstartedguide

Balasubramanyam

#5428

Hi Sebastian,

I tried deleting build folder and created again.

Compilation successful without any issues. Issue not seen anymore

Thanks,

Balasubramanyam Rangineni

Show quoted text

On Fri, Nov 16, 2018 at 9:23 PM Bøe, Sebastian <Sebastian.Boe@...> wrote:

I can't think of any reason why blinky would work, whilst hello_world
would produce that error.

Could you try again after deleting the build directories?

It is not necessary to add --specs=nosys.specs when the variant is set to gnuarmemb.

________________________________________
From: devel@... <devel@...> on behalf of Balasubramanyam <rangineni.balu@...>
Sent: Friday, November 16, 2018 4:48:20 PM
To: marti@...
Cc: devel@...
Subject: Re: [Zephyr-devel] Getting started with ARM GNU Compiler | errors | #gettingstartedguide

Hi Marti,

I tried compiling zephyr\samples\hello_world\ project.
I used camke command to compile
cmake -GNinja -DBOARD=nrf52832_mdk ..

Failure seen after this command itself. But when I tried compiling blinky project I did not see any issue.

On Fri, Nov 16, 2018 at 9:10 PM Marti Bolivar <marti@...<mailto:marti@...>> wrote:
Hi,

Is this an upstream sample project? What command lines did you use for
cmake and building the project itself?

Thanks,
Marti
On Thu, Nov 15, 2018 at 9:55 PM <rangineni.balu@...<mailto:rangineni.balu@...>> wrote:
>
> Hi Team,
>
> I am just getting started with Zephyr and trying to setup development environment. I followed all the steps described to setup ARM GNU GCC toolchain and compilation ENV.
> After setting up everything required, I got the following error after trying to compile a sample project.
>
> "
> CMake Error at ../../cmake/extensions.cmake:1086 (message):
> Assertion failed: The toolchain is unable to build a dummy C file. See
> CMakeError.log.
> Call Stack (most recent call first):
> ../../CMakeLists.txt:28 (assert)
>
>
> -- Configuring incomplete, errors occurred!
> See also "../zephyr/samples/hello_world/build/CMakeFiles/CMakeOutput.log".
> See also "../zephyr/samples/hello_world/build/CMakeFiles/CMakeError.log".
> ""
>
> I went through the log files and it seems build failed at following
>
> ""
> The output was:
> 1
> c:/gnu_arm_embedded/bin/../lib/gcc/arm-none-eabi/7.3.1/../../../../arm-none-eabi/lib\libc.a(lib_a-exit.o): In function `exit':
> exit.c:(.text.exit+0x2c): undefined reference to `_exit'
> collect2.exe: error: ld returned 1 exit status""
>
> Seems ARM compiler issue, after bit of google found out that these options "--specs=nosys.specs" needs to be passed as command line params to run gcc.
> I am not able to figure out where i can exactly instruct build environment to use these command line options for GCC.
>
> I have attached both error and output log.
> Any help will be appreciated to be able to compile a project successfully.
>
> Thanks,
> Balasubramanyam Rangineni

--
Thanks & Regards,
Rangineni Balasubramanyam

--

Thanks & Regards,

Rangineni Balasubramanyam

Re: Getting started with ARM GNU Compiler | errors | #gettingstartedguide

Sebastian Boe

#5427

I can't think of any reason why blinky would work, whilst hello_world
would produce that error.

Could you try again after deleting the build directories?

It is not necessary to add --specs=nosys.specs when the variant is set to gnuarmemb.

________________________________________
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> on behalf of Balasubramanyam <rangineni.balu@gmail.com>
Sent: Friday, November 16, 2018 4:48:20 PM
To: marti@foundries.io
Cc: devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] Getting started with ARM GNU Compiler | errors | #gettingstartedguide

Hi Marti,

I tried compiling zephyr\samples\hello_world\ project.
I used camke command to compile
    cmake -GNinja -DBOARD=nrf52832_mdk ..

Failure seen after this command itself. But when I tried compiling blinky project I did not see any issue.

On Fri, Nov 16, 2018 at 9:10 PM Marti Bolivar <marti@foundries.io<mailto:marti@foundries.io>> wrote:
Hi,

Is this an upstream sample project? What command lines did you use for
cmake and building the project itself?

Thanks,
Marti
On Thu, Nov 15, 2018 at 9:55 PM <rangineni.balu@gmail.com<mailto:rangineni.balu@gmail.com>> wrote:

Hi Team,

I am just getting started with Zephyr and trying to setup development environment. I followed all the steps described to setup ARM GNU GCC toolchain and compilation ENV.
After setting up everything required, I got the following error after trying to compile a sample project.

"
CMake Error at ../../cmake/extensions.cmake:1086 (message):
  Assertion failed: The toolchain is unable to build a dummy C file.  See
  CMakeError.log.
Call Stack (most recent call first):
  ../../CMakeLists.txt:28 (assert)


-- Configuring incomplete, errors occurred!
See also "../zephyr/samples/hello_world/build/CMakeFiles/CMakeOutput.log".
See also "../zephyr/samples/hello_world/build/CMakeFiles/CMakeError.log".
""

I went through the log files  and it seems build failed at following

""
The output was:
1
c:/gnu_arm_embedded/bin/../lib/gcc/arm-none-eabi/7.3.1/../../../../arm-none-eabi/lib\libc.a(lib_a-exit.o): In function `exit':
exit.c:(.text.exit+0x2c): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status""

Seems ARM compiler issue, after bit of google found out that these options "--specs=nosys.specs" needs to be passed as command line params to run gcc.
I am not able to figure out where i can exactly instruct build environment to use these command line options for GCC.

I have attached both error and output log.
Any help will be appreciated to be able to compile a project successfully.

Thanks,
Balasubramanyam Rangineni
--
Thanks & Regards,
Rangineni Balasubramanyam