Date   

Re: [Zephyr-devel] #BluetoothMesh URI provisioning #bluetoothmesh

Johan Hedberg
 

Hi Vikrant,

On Fri, Mar 30, 2018, Vikrant More wrote:
Is Zephyr going to introduce feature so that beacon will broadcast URI for
unprovisioned #BluetoothMesh DEVICEs ?
This is already supported using the "const char *uri" member of struct
bt_mesh_prov.

Johan


#BluetoothMesh URI provisioning #bluetoothmesh

Vikrant More <vikrant8051@...>
 

Hi, 

Is Zephyr going to introduce feature so that beacon will broadcast URI for unprovisioned #BluetoothMesh DEVICEs ?

Or it is simply replacing DEVICE_NAME (means Zephyr ) to something like mentioned in #BluetoothMesh specification at 8.4.2 ( Beacon : 0070cf7c9732a345b691494810d2e9cbf44020d97478b3 ) ?

-------------------------------------------------------------------------------------------------------------
As per my understanding,

URI beacon = DEVICE's UUID + some part of Hash which is generated from "URI data" which is stored at URL 

URI data = ECDH public key of DEVICE ( which is common to all DEVICEs under particular category)

Am I right ?

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

Please throw some light on URI beacon based secure provisioning.

Thank You !!


NXP MCUX RTC implementation

Franco Saworski <franco.saworski@...>
 

Hi,

we at blik are working with Zephyr on one of our hardware units, and would like to use a lowpower mechanism along with an RTC wakeup.

Unfortunately RTC implementations are sparse, with only one implementation present. Is there a technical limitation or reason for this?
As far as I understand, SoC lowpower implementations are omitted in Zephyr, because they are usually usecase specific. I can't imagine the same for RTC.

Furthermore, we are looking for someone to develop the RTC driver and ultimately upstream it, as a small paid project. Please feel free to message me, if you're interested.

Kind regards,
Franco Saworski


--

Embedded Engineer

blik GmbH
transparent real-time data

Leonrodstraße 68 | 80636 München
HRB: 233881 | Amtsgericht München
Geschäftsführer: Bastian Burger, Philip Eller, Victoria Hauzeneder

Information in this email - including any attachments - may be privileged, confidential and is intended exclusively for the addressee(s). If you are not the intended recipient, please notify the sender and delete all copies from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone.


Re: USB HID sample

Johannes Hutter
 

Hey Yannis,

thanks for the answer. I think, I just figured it out now. I forgot to set the pinmux for USB OTG in my custom board file. Now the endpoint gets registered and seems to work.

Best regards,

Joe



On 27.03.2018 09:49, Yannis Damigos wrote:

I tried to run the USB HID sample on a STM-based device and ran into some problems. I get a usage fault caused by a division by zero. This actually happens in the ST HAL, where a division by the MPS of the USB enpoint is done. The MPS is actually 0 when the sample does the USB write. Is there something missing in the sample? When turning the logging in the USB subsystem on, I can also see, that the Enpoints 0x00 and 0x80 are configured, but not the HID endpoint (on 0x83). the set_callback function is however called in the stm driver.

Would be great if someone could point me in the right direction.

Hi Joe,

I will try to test the sample on my boards in the next days. The default HID endpoint is 0x81. Is it configured?

Best regards,
Yannis 

--

Johannes Hutter | Embedded Software Engineer
Mail: johannes@...


Workaround GmbH (ProGlove)
Friedenstr. 4 | 81671 München

Managing Director: Thomas Kirchner
HRB: 216605 | AG München
USt.-IdNr.: DE298859320


Re: USB HID sample

Yannis Damigos
 

I tried to run the USB HID sample on a STM-based device and ran into some problems. I get a usage fault caused by a division by zero. This actually happens in the ST HAL, where a division by the MPS of the USB enpoint is done. The MPS is actually 0 when the sample does the USB write. Is there something missing in the sample? When turning the logging in the USB subsystem on, I can also see, that the Enpoints 0x00 and 0x80 are configured, but not the HID endpoint (on 0x83). the set_callback function is however called in the stm driver.

Would be great if someone could point me in the right direction.

Hi Joe,

I will try to test the sample on my boards in the next days. The default HID endpoint is 0x81. Is it configured?

Best regards,
Yannis 


Re: USB HID sample

Michael Hope
 

Hi Johannes.  I don't know if this is helpful, but I'm successfully using the HID code on the SAMD21.  Doesn't mean there's not a bug though :)

-- Michael

On Mon, 26 Mar 2018 at 20:09 Johannes Hutter <johannes@...> wrote:

Hello guys,


I tried to run the USB HID sample on a STM-based device and ran into some problems. I get a usage fault caused by a division by zero. This actually happens in the ST HAL, where a division by the MPS of the USB enpoint is done. The MPS is actually 0 when the sample does the USB write. Is there something missing in the sample? When turning the logging in the USB subsystem on, I can also see, that the Enpoints 0x00 and 0x80 are configured, but not the HID endpoint (on 0x83). the set_callback function is however called in the stm driver.

Would be great if someone could point me in the right direction.


Thanks and Best Regards,

Joe

--

Johannes Hutter | Embedded Software Engineer
Mail: johannes@...


Workaround GmbH (ProGlove)
Friedenstr. 4 | 81671 München

Managing Director: Thomas Kirchner
HRB: 216605 | AG München
USt.-IdNr.: DE298859320

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


Re: Custom per project flash runner

Marti Bolivar
 



On Mon, Mar 26, 2018 at 2:10 PM, Roman Tataurov <diytronic@...> wrote:
Hello!
 
26.03.2018, 01:27, "Marti Bolivar" <marti@...>:
Hi Roman,
 
You can specify a flash and debug runner without touching any board files by setting BOARD_FLASH_RUNNER and/or BOARD_DEBUG_RUNNER in the CMake command line when generating a build system.
 
 
Damn ... of course. So easy. Feel stupid :(

Not at all! Thanks for asking. I'm sure others were wondering too. This area needs better documentation.
 
Thank you Marti! It is really a solution.

I'm glad.

Thanks,
Marti
 
 
Here is an example branch, in which I have created a "dummy" runner:
 
 
Here is the commit which adds the extra runner, which just prints the command instead of acting on hardware:
 
 
Here is an example shell session where the flash and debug runners are set at CMake time and then used later using "ninja flash", "ninja debug", and "ninja debugserver". I have used the nrf52_pca10040 board, but it should work with any board.
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ cmake -GNinja -DBOARD=nrf52_pca10040 -DBOARD_FLASH_RUNNER=dummy -DBOARD_DEBUG_RUNNER=dummy ..
CMake Deprecation Warning at /home/mbolivar/src/zephyr/cmake/app/boilerplate.cmake:38 (cmake_policy):
  The OLD behavior for policy CMP0000 will be removed from a future version
  of CMake.
 
  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
  CMakeLists.txt:2 (include)
 
 
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.3", minimum required is "3.4") 
-- Selected BOARD nrf52_pca10040
Zephyr version: 1.11.99
[snip]
-- Configuring done
-- Generating done
-- Build files have been written to: /home/mbolivar/src/zephyr/samples/hello_world/build
 
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja
[1/118] Generating always_rebuild
Building for board nrf52_pca10040
[113/118] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       44732 B       512 KB      8.53%
            SRAM:       11388 B        64 KB     17.38%
        IDT_LIST:         132 B         2 KB      6.45%
[118/118] Linking C executable zephyr/zephyr.elf
 
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja flash
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Flashing nrf52_pca10040
command: flash
 
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja debug
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Debugging nrf52_pca10040
command: debug
 
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja debugserver
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Debugging nrf52_pca10040
command: debugserver
 
 
Hope this helps. Please let me know if you still have problems.
 
Thanks,
Marti
 
On Sun, Mar 25, 2018, 3:48 PM Roman Tataurov <diytronic@...> wrote:
Hello!

I there some way to specify custom flash runner command instead of default one used for board.
For example I have a flasher what work with my board, but does not specified with board configuration.
Tried to play with set(BOARD_FLASH_RUNNER - it work if change it inside board config, but found no way to overwrite it in project files, not touching board files.

--
Roman Tataurov

_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users
 
 
-- 
Roman Tataurov
 


Re: Custom per project flash runner

Roman Tataurov
 

Hello!
 
26.03.2018, 01:27, "Marti Bolivar" <marti@...>:
Hi Roman,
 
You can specify a flash and debug runner without touching any board files by setting BOARD_FLASH_RUNNER and/or BOARD_DEBUG_RUNNER in the CMake command line when generating a build system.
 
 
Damn ... of course. So easy. Feel stupid :(
Thank you Marti! It is really a solution.
 
Here is an example branch, in which I have created a "dummy" runner:
 
 
Here is the commit which adds the extra runner, which just prints the command instead of acting on hardware:
 
 
Here is an example shell session where the flash and debug runners are set at CMake time and then used later using "ninja flash", "ninja debug", and "ninja debugserver". I have used the nrf52_pca10040 board, but it should work with any board.
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ cmake -GNinja -DBOARD=nrf52_pca10040 -DBOARD_FLASH_RUNNER=dummy -DBOARD_DEBUG_RUNNER=dummy ..
CMake Deprecation Warning at /home/mbolivar/src/zephyr/cmake/app/boilerplate.cmake:38 (cmake_policy):
  The OLD behavior for policy CMP0000 will be removed from a future version
  of CMake.
 
  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
  CMakeLists.txt:2 (include)
 
 
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.3", minimum required is "3.4") 
-- Selected BOARD nrf52_pca10040
Zephyr version: 1.11.99
[snip]
-- Configuring done
-- Generating done
-- Build files have been written to: /home/mbolivar/src/zephyr/samples/hello_world/build
 
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja
[1/118] Generating always_rebuild
Building for board nrf52_pca10040
[113/118] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       44732 B       512 KB      8.53%
            SRAM:       11388 B        64 KB     17.38%
        IDT_LIST:         132 B         2 KB      6.45%
[118/118] Linking C executable zephyr/zephyr.elf
 
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja flash
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Flashing nrf52_pca10040
command: flash
 
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja debug
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Debugging nrf52_pca10040
command: debug
 
 
plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja debugserver
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Debugging nrf52_pca10040
command: debugserver
 
 
Hope this helps. Please let me know if you still have problems.
 
Thanks,
Marti
 
On Sun, Mar 25, 2018, 3:48 PM Roman Tataurov <diytronic@...> wrote:
Hello!

I there some way to specify custom flash runner command instead of default one used for board.
For example I have a flasher what work with my board, but does not specified with board configuration.
Tried to play with set(BOARD_FLASH_RUNNER - it work if change it inside board config, but found no way to overwrite it in project files, not touching board files.

--
Roman Tataurov

_______________________________________________
Zephyr-users mailing list
Zephyr-users@...
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users
 
 
-- 
Roman Tataurov
 


USB HID sample

Johannes Hutter
 

Hello guys,


I tried to run the USB HID sample on a STM-based device and ran into some problems. I get a usage fault caused by a division by zero. This actually happens in the ST HAL, where a division by the MPS of the USB enpoint is done. The MPS is actually 0 when the sample does the USB write. Is there something missing in the sample? When turning the logging in the USB subsystem on, I can also see, that the Enpoints 0x00 and 0x80 are configured, but not the HID endpoint (on 0x83). the set_callback function is however called in the stm driver.

Would be great if someone could point me in the right direction.


Thanks and Best Regards,

Joe

--

Johannes Hutter | Embedded Software Engineer
Mail: johannes@...


Workaround GmbH (ProGlove)
Friedenstr. 4 | 81671 München

Managing Director: Thomas Kirchner
HRB: 216605 | AG München
USt.-IdNr.: DE298859320


Re: Custom per project flash runner

Marti Bolivar
 

Hi Roman,

You can specify a flash and debug runner without touching any board files by setting BOARD_FLASH_RUNNER and/or BOARD_DEBUG_RUNNER in the CMake command line when generating a build system.

Here is an example branch, in which I have created a "dummy" runner:


Here is the commit which adds the extra runner, which just prints the command instead of acting on hardware:


Here is an example shell session where the flash and debug runners are set at CMake time and then used later using "ninja flash", "ninja debug", and "ninja debugserver". I have used the nrf52_pca10040 board, but it should work with any board.

plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ cmake -GNinja -DBOARD=nrf52_pca10040 -DBOARD_FLASH_RUNNER=dummy -DBOARD_DEBUG_RUNNER=dummy ..
CMake Deprecation Warning at /home/mbolivar/src/zephyr/cmake/app/boilerplate.cmake:38 (cmake_policy):
  The OLD behavior for policy CMP0000 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
  CMakeLists.txt:2 (include)


-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.3", minimum required is "3.4") 
-- Selected BOARD nrf52_pca10040
Zephyr version: 1.11.99
[snip]
-- Configuring done
-- Generating done
-- Build files have been written to: /home/mbolivar/src/zephyr/samples/hello_world/build


plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja
[1/118] Generating always_rebuild
Building for board nrf52_pca10040
[113/118] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       44732 B       512 KB      8.53%
            SRAM:       11388 B        64 KB     17.38%
        IDT_LIST:         132 B         2 KB      6.45%
[118/118] Linking C executable zephyr/zephyr.elf


plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja flash
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Flashing nrf52_pca10040
command: flash


plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja debug
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Debugging nrf52_pca10040
command: debug


plop: ~/src/zephyr/samples/hello_world/build (set-runner) mbolivar
$ ninja debugserver
[1/89] Generating always_rebuild
Building for board nrf52_pca10040
[1/2] Debugging nrf52_pca10040
command: debugserver


Hope this helps. Please let me know if you still have problems.

Thanks,
Marti


On Sun, Mar 25, 2018, 3:48 PM Roman Tataurov <diytronic@...> wrote:
Hello!

I there some way to specify custom flash runner command instead of default one used for board.
For example I have a flasher what work with my board, but does not specified with board configuration.
Tried to play with set(BOARD_FLASH_RUNNER - it work if change it inside board config, but found no way to overwrite it in project files, not touching board files.

--
Roman Tataurov

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


Custom per project flash runner

Roman Tataurov
 

Hello!

I there some way to specify custom flash runner command instead of default one used for board.
For example I have a flasher what work with my board, but does not specified with board configuration.
Tried to play with set(BOARD_FLASH_RUNNER - it work if change it inside board config, but found no way to overwrite it in project files, not touching board files.

--
Roman Tataurov


What is need of addition authentication in case of #BluetoothMesh if ECDH public key exchanged over OOB ? #bluetoothmesh

Vikrant More <vikrant8051@...>
 

Hi, 

If #BluetoothMesh DEVICE ECDH-public key (oob public key) is exchanged over OOB channel then what is further need of authentication using input-OOB or output-OOB or static-OOB ?

Thanks,


Re: [Zephyr-devel] How hacker will hack/impact my BLE device, when ...??

Vikrant More <vikrant8051@...>
 

Hi,
I think we can do OOB pairing, even if Device doesn't have display to share Passkey with user App.

1. Create ECDH public-private key pair (only once in Device life)
2. Read ECDH-Public key via Device serial terminal. Create QR code from it & add it in Device packaging.

3. User will scan it with APP & APP will transfer own dynamically created public key over BLE link.
4. Shared secret will created on both side which can be used to encrypt further communication.

Thanks,
vikrant8051



On Wed, Mar 21, 2018 at 9:13 PM, Vikrant More <vikrant8051@...> wrote:
Hi,
https://eewiki.net/display/Wireless/A+Basic+Introduction+to+BLE+Security

MITM attacks are when a third device, which we will call the malicious device, impersonates the other two legitimate devices, in order to fool these devices into connecting to it. In this scenario, both the GAP Central and GAP Peripheral will connect to the malicious device which in turn routes the communication between the two other devices. This gives the legitimate devices the illusion that they are directly connected to each other when in fact their connection has been compromised. This setup not only allows the malicious device to intercept all the data being sent, but also allows it to inject false data into the communication or remove data before it reaches its intended recipient.

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

After reading this, I understand that without OOB Pairing everything is more or less insecure.


On Wed, Mar 21, 2018 at 7:04 PM, Marcio Montenegro <mtuxpe@...> wrote:
Google Secure beacons.No new hardware design :
https://developers.google.com/beacons/eddystone-eid

Regards,
Marcio


On Wed, Mar 21, 2018 at 10:15 AM, Vikrant More <vikrant8051@...> wrote:
Hi Marcio,
I'm not allowed to add anything extra in my current hardware design.

Besides this, is there any thing which is very serious ?
I'm still trying to understand various security risk behind my current implementation.

Thanks,
 

On Wed, Mar 21, 2018 at 5:35 PM, Marcio Montenegro <mtuxpe@...> wrote:
Hi all,
Maybe you can use crypto device on your product.


You also need to develop an application to configure  crypto device chip.
Then after configuration each device are unique.
For inspiration see:

Note that this devices has no Bluetooth.
Best,
Marcio


On Wed, Mar 21, 2018 at 2:08 AM, Vakul Garg <vakul.garg@...> wrote:

Hi Vikrant

 

I am curious to understand about your security implementation.

I work in area of TLS security and I am not bluetooth security expert.

 

In your case, does the app need to differentiate between a genuine or fake device?

Will it be able to create a shared secret with the device even if it is a clone of genuine device and purpose programmed to leak the common encryption key?

 

Regards

 

Vakul

 

From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-bounces@lists.zephyrproject.org] On Behalf Of Vikrant More
Sent: Tuesday, March 20, 2018 11:28 PM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] How hacker will hack/impact my BLE device, when ...??

 

Hi,

 

In my current project, I haven't implemented OOB pairing ( BLE based smart lights)

 

Using Zephyr built-in ECDH library, shared secret (using secp256r1 curve) get created on Device as well as on APP side which will act like encryption key for further communication.

 

On that encrypted link, APP send encryption key which is common for all devices associated with it.

 

All this happens when DEVICE is in factory reset mode.

 

There after communication link is encrypted using newly assign common key.

 

..................................................................................….........................................

 

This will create security risk, only if device is not authenticated by user & it could transfer security key ( which is common to many devices) to unauthorized device.

 

To solve this, APP will automatically trigger DEVICE's LEDs to blink & ask user "do you see blinking LED?" 

 

If user click on "YES" then & only then ECDH process will initiate & common key get share with new DEVICE.

 

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

 

Besides this I didn't found any security flaw in this implementation. So I need help from Bluetooth Security expert. Is there anyone who can help me to find out flaws & security risks in my current implementation ?

 

Thanks,

vikrant8051


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







Re: USB on STM32

Yannis Damigos
 

On Fri, Mar 23, 2018 at 11:15 AM Johannes Hutter <johannes@...> wrote:

Hey Yannis,

that makes of course sense, if the missing define is generated from the dts. Thanks a lot!

Best Regards,

Joe




Hi Joe,

please consider creating a PR to enable USB on nucleo_f411re.

Best Regards,

Yannis



Re: USB on STM32

Johannes Hutter
 

Hey Yannis,

that makes of course sense, if the missing define is generated from the dts. Thanks a lot!

Best Regards,

Joe


On 22.03.2018 19:56, Yannis Damigos wrote:
On 03/22/2018 08:09 PM, Johannes Hutter wrote:
Hello guys,


I have trouble getting the usb/cdc_acm sample running on the nucleo_f411re. During the build I get errors of a couple of undeclared macros. For example:

 error: ‘ST_STM32_OTGFS_50000000_NUM_BIDIR_ENDPOINTS’ undeclared here (not in a function)
#define CONFIG_USB_NUM_BIDIR_ENDPOINTS  ST_STM32_OTGFS_50000000_NUM_BIDIR_ENDPOINTS

Is it possible that there is part of the stm HAL needed for USB missing?


 
Hi Joe,

USB is not enabled on nucleo_f411re. It should be easy to enable it.
Check the following link https://github.com/zephyrproject-rtos/zephyr/pull/6535/files

Best regards,
Yannis


--

Johannes Hutter | Embedded Software Engineer
Mail: johannes@...


Workaround GmbH (ProGlove)
Friedenstr. 4 | 81671 München

Managing Director: Thomas Kirchner
HRB: 216605 | AG München
USt.-IdNr.: DE298859320


Re: USB on STM32

Yannis Damigos
 

On 03/22/2018 08:09 PM, Johannes Hutter wrote:
Hello guys,


I have trouble getting the usb/cdc_acm sample running on the nucleo_f411re. During the build I get errors of a couple of undeclared macros. For example:

 error: ‘ST_STM32_OTGFS_50000000_NUM_BIDIR_ENDPOINTS’ undeclared here (not in a function)
#define CONFIG_USB_NUM_BIDIR_ENDPOINTS  ST_STM32_OTGFS_50000000_NUM_BIDIR_ENDPOINTS

Is it possible that there is part of the stm HAL needed for USB missing?


Hi Joe,

USB is not enabled on nucleo_f411re. It should be easy to enable it.
Check the following link https://github.com/zephyrproject-rtos/zephyr/pull/6535/files

Best regards,
Yannis


USB on STM32

Johannes Hutter
 

Hello guys,


I have trouble getting the usb/cdc_acm sample running on the nucleo_f411re. During the build I get errors of a couple of undeclared macros. For example:

 error: ‘ST_STM32_OTGFS_50000000_NUM_BIDIR_ENDPOINTS’ undeclared here (not in a function)
#define CONFIG_USB_NUM_BIDIR_ENDPOINTS  ST_STM32_OTGFS_50000000_NUM_BIDIR_ENDPOINTS

Is it possible that there is part of the stm HAL needed for USB missing?


Best regards,

Joe

--

Johannes Hutter | Embedded Software Engineer
Mail: johannes@...


Workaround GmbH (ProGlove)
Friedenstr. 4 | 81671 München

Managing Director: Thomas Kirchner
HRB: 216605 | AG München
USt.-IdNr.: DE298859320


Re: BBC:microbit like pairing implementation on nRF52840-PDK

Vikrant More <vikrant8051@...>
 

Hi,
Suppose there is Admin Characteristic (which requires OOB pairing since I've enable BT_GATT_PERM_WRITE_AUTHEN | BT_GATT_PERM_WRITE_ENCRYPT | BT_GATT_PERM_READ_AUTHEN | BT_GATT_PERM_READ_ENCRYPT)
Can I send AES Key(common for all devices) after OOB pairing to Admin characteristic?

If Yes, then Device can save it on flash & future communication with all other characteristics
( where I've not enable BT_GATT_PERM_WRITE_AUTHEN | BT_GATT_PERM_WRITE_ENCRYPT | BT_GATT_PERM_READ_AUTHEN | BT_GATT_PERM_READ_ENCRYPT)
will be encrypted using it. That's it !!


Thanks,

On Thu, Mar 22, 2018 at 2:48 PM, Vikrant More <vikrant8051@...> wrote:
In this video, user directly enter PIN from BBC:microbit for pairing.


https://www.youtube.com/watch?v=L54Sp2DZibA
In this video, user add pattern first & then enter PIN to pair.

What is pros & cons in these two styles of pairing ?

----------------------------------------------------------------------------------------------------------------------------------------
In both cases. user transform microbit into pairing mode.

What is significance behind it ? Is it help to device enter into factory reset mode ?

As per current Zephyr implementation, we can do pairing without goes into pairing mode.
----------------------------------------------------------------------------------------------------------------------------------------

By using combination of,

 1. BT_GATT_PERM_WRITE_AUTHEN
 2. BT_GATT_PERM_WRITE_ENCRYPT
 3. BT_GATT_PERM_READ_AUTHEN
 4. BT_GATT_PERM_READ_ENCRYPT

we could block Guest users to access certain characteristics & allow only Admin to access them
(who has paired with the Device)

If I do OOB pairing using Device Serial Terminal, it works as expected but after Device reboot I have to do it again to access admin characteristic.

There should be some variable which I have to store on device flash after Pairing & have to reinitialize them on every reboot.
But there is no any demo examples or documentations which shows what to save on flash.
I think this is what I want but this much is not sufficient for noob like me to implementation it with actual products.
----------------------------------------------------------------------------------------------------------------------------------------

Thank You !!












BBC:microbit like pairing implementation on nRF52840-PDK

Vikrant More <vikrant8051@...>
 

In this video, user directly enter PIN from BBC:microbit for pairing.


https://www.youtube.com/watch?v=L54Sp2DZibA
In this video, user add pattern first & then enter PIN to pair.

What is pros & cons in these two styles of pairing ?

----------------------------------------------------------------------------------------------------------------------------------------
In both cases. user transform microbit into pairing mode.

What is significance behind it ? Is it help to device enter into factory reset mode ?

As per current Zephyr implementation, we can do pairing without goes into pairing mode.
----------------------------------------------------------------------------------------------------------------------------------------

By using combination of,

 1. BT_GATT_PERM_WRITE_AUTHEN
 2. BT_GATT_PERM_WRITE_ENCRYPT
 3. BT_GATT_PERM_READ_AUTHEN
 4. BT_GATT_PERM_READ_ENCRYPT

we could block Guest users to access certain characteristics & allow only Admin to access them
(who has paired with the Device)

If I do OOB pairing using Device Serial Terminal, it works as expected but after Device reboot I have to do it again to access admin characteristic.

There should be some variable which I have to store on device flash after Pairing & have to reinitialize them on every reboot.
But there is no any demo examples or documentations which shows what to save on flash.
I think this is what I want but this much is not sufficient for noob like me to implementation it with actual products.
----------------------------------------------------------------------------------------------------------------------------------------

Thank You !!











Sensor Subsystem FIFO-operation

Thomas Li Fredriksen
 

Good morning,

Have for some time looked in to the Sensor API. From what I can see, there does not appear to be any built-in way of handling FIFO-operation or buffering.

A lot of sensors support internal FIFO operations with interrupts triggered by some FIFO threshold. How would this commonly be handled in Zephyr?

Cheers.

2401 - 2420 of 3075