devel@lists.zephyrproject.org

Tagging Pull Requests for 1.11

Hi all, I want to remind everybody that we're nearing the 1.11 release date, and as part of this we will only merge Pull Requests that address an issue and are clearly tagged as "1.11". To tag a Pull

By Carles Cufi · #1844 ·

EasyDMA for nordic soc, 52832

Hi! I'm trying to understand how to use EasyDMA, provided by Nordic, in the Zephyr platform. As I can not find any generic configuration option for it, I suppose I need to hack it some how! I've seen

By Timo Kolthoff <Timo.Kolthoff@...> · #1843 ·

Re: Zephyr v1.11.0-rc2 tagged

Hi Henrik, I believe you are right. I will make a note of this since it was not documented. I'll make sure to update this for the next -rc. Thanks for pointing it out. Regards, Carles

By Carles Cufi · #1842 ·

Re: Zephyr v1.11.0-rc2 tagged

Hi, Shouldn't the VERSION file be updated with each -rc release as was done for the v1.10.0-rcX tags? A little late now, I know. Regards, Brix -- Henrik Brix Andersen

By Henrik Brix Andersen · #1841 ·

Zephyr v1.11.0-rc2 tagged

Hi all, We are a couple of days late, but we have just tagged Zephyr 1.11.0-rc2. The stabilization phase seems to be progressing stably, and so we will continue to allow issue and regression fixes

By Carles Cufi · #1840 ·

Re: Securing BLE device communication without OOB pairing (multiple devices)

Awesome, thanks! >>If he/she clicks on "yes" then only process go ahead. >>[ Here APP will only connect to Devices which are in vicinity by >>checking their signal strength (RSSI) ] >>So I think,

By Vikrant More <vikrant8051@...> · #1839 ·

Re: Securing BLE device communication without OOB pairing (multiple devices)

Hi Vikrant, Zephyr's Bluetooth stack exposes ECC as standard HCI commands & events through subsys/bluetooth/host/hci_ecc.c. And you're right that it's the FIPS P-256 curve that both LE Secure

By Johan Hedberg · #1838 ·

Re: Securing BLE device communication without OOB pairing (multiple devices)

Hi Johan, https://github.com/kmackay/micro-ecc has support for 5 standard curves: secp160r1, secp192r1, secp224r1, secp256r1, and secp256k1. Out of secp256r1 and secp256k1, which one is used by Zephyr

By Vikrant More <vikrant8051@...> · #1837 ·

Re: Securing BLE device communication without OOB pairing (multiple devices)

Hi Johan, Thanks for reply !! Ok, but I don't know how to integrate & use it in my current project since there is no any documentation available about it. So I chose alternate way but will figure out

By Vikrant More <vikrant8051@...> · #1836 ·

Re: Securing BLE device communication without OOB pairing (multiple devices)

Hi Vikrant, micro-ecc is what the Zephyr TinyCrypt uses, and it is also what the Zephyr Bluetooth Security Manager (LE pairing) and mesh implementations use, so no need to start installing micro-ecc

By Johan Hedberg · #1835 ·

Re: Securing BLE device communication without OOB pairing (multiple devices)

Hello World !! I found solution as micro-ecc library -> https://github.com/kmackay/micro-ecc to generate #AdminKey or Master key on both sides without transferring it on insecure Bluetooth Link. Thank

By Vikrant More <vikrant8051@...> · #1834 ·

Re: Securing BLE device communication without OOB pairing (multiple devices)

Hello, How to use ECDH mechanism to establish common #AdminKey or Master Key, using functions defined in $zephyr_base/subsys/bluetooth/host/ecc.h for normal BLE devices ? We uses this concept, in

By Vikrant More <vikrant8051@...> · #1833 ·

Securing BLE device communication without OOB pairing (multiple devices)

Hello, If I enabled encryption or authentication to access BLE device characteristic, we have to do OOB pairing. But in some cases, it is not possible like budget LED lights. In this case, how to make

By Vikrant More <vikrant8051@...> · #1832 ·

Re: CMSIS Support in zephyr

We don’t currently have CMSIS driver support. We haven’t had an SoC vendor who’s utilized it and we’ve typically used the SoC vendor’s HAL/SDK and have shim drivers. - k

By Kumar Gala · #1831 ·

Re: CMSIS Support in zephyr

Hi Vinayak , By CMSIS compliant drivers i mean the drivers that follow the CMSIS API convention. Please refer to: http://www2.keil.com/mdk5/cmsis/driver and

By Nachiketa Kumar · #1830 ·

Re: CMSIS Support in zephyr

Hi Nachiketa, Could you ellaborate on CMSIS compliance? One of the drivers I am aware that uses extensively the CMSIS interfaces defined for NRF5 series is

By Chettimada, Vinayak Kariappa · #1829 ·

CMSIS Support in zephyr

Hi , Does zephyr support CMSIS compliant drivers ? I see it as one of the supported HAL models but there aren't any drivers currently using the CMSIS model. Thanks, Nachiketa

By Nachiketa Kumar · #1828 ·

duplicate symbol error Silabs EFM32 happy gecko build

Hi all, I am trying to port Silabs EFM32 happy gecko to Zephyr project. After running ninja I got the following errors: offsets.c:26: ../../../../ext/hal/cmsis/Include/arm_math.h:667:23: error:

By Marcio Montenegro · #1827 ·

[SOLVED] porting zephyr to Silabs EFM32 happy gecko

Hi all, 1. I add: CONFIG_NEWLIB_LIBC=y on efm32hg_slstk_3400a_defconfig file 2. Silabs Happy gecko is cortex_m0+ armv6 so the correct efm32hg.dts configuration is: #include <arm/armv6-m.dtsi> #include

By Marcio Montenegro · #1826 ·

Re: Info on what is allowed from IRQ context

Hi, I believe the general rule is that calling functions with a timeout of K_NO_WAIT is allowed from ISRs. Regards, Brix -- Henrik Brix Andersen <henrik@...>

By Henrik Brix Andersen · #1825 ·

Messages