1. devel@lists.zephyrproject.org
  2. Messages
   Date   
Re: about BLE Rx test

Stephanos Io <assembler@...>
 

Hi,

 

I suppose you are performing RX sensitivity test.

 

> If RF equipment send a dbm above -86 (ex: -85 , -84 , -83 …..), the error message will disappear.

 

Assuming you are testing with BLE 2Mbps PHY, I think this behaviour is only to be expected given that the max. sensitivity is specified at -85 dBm at 2Mbps for nRF51824 (refer to the datasheet).

 

Stephanos

 

From: devel@... <devel@...> On Behalf Of Cufi, Carles
Sent: Tuesday, November 12, 2019 10:38 PM
To: Tommy.Lin@...; zephyr-devel@...
Cc: devel@...; Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...>
Subject: Re: [Zephyr-devel] about BLE Rx test

 

Adding Vinayak.

 

If this depends on the dBm setting it might be a bug actually. I’ll let Vinayak weigh in.

 

Carles

 

 

From: devel@... <devel@...> On Behalf Of Tommy Lin (???) via Lists.Zephyrproject.Org
Sent: 12 November 2019 13:01
To: zephyr-devel@...
Cc: devel@...
Subject: Re: [Zephyr-devel] about BLE Rx test

 

+ jimmy

 

From: Tommy Lin (林志聰)
Sent: Tuesday, November 12, 2019 7:18 PM
To: 'zephyr-devel@...' <zephyr-devel@...>
Cc: Isaac Chen (陳尚航) <Isaac_Chen@...>; Ryan Hsu (徐振鋒) <Ryan.Hsu@...>; Brent Tsai (蔡旻其) <Brent.Tsai@...>; 'Hanyu.Hsu@...' <Hanyu.Hsu@...>
Subject: RE: about BLE Rx test

 

Hi ,

Sorry , correction.

 

We have a product using nRF51824 with Zephyr v1.13.0.

Our DUT connect with RF equipment.

 

[Test sequence]

Step1: DUT enter Rx mode with HCI command.

Step2: RF equipment send 1500 bytes with -86dbm.

Step3: DUT end Rx mode

After then , DUT will show “tx time out “ error message.

 

 

PS:

  1. If RF equipment send a dbm above -86 (ex: -85 , -84 , -83 …..), the error message will disappear.
  2. We use Zephyr v1.13.0 and v1.14.0 , and the result is the same.

 

Could you give us some suggestions?

 

Thank You,

Tommy

 
Re: about BLE Rx test

Carles Cufi
 

Adding Vinayak.

 

If this depends on the dBm setting it might be a bug actually. I’ll let Vinayak weigh in.

 

Carles

 

 

From: devel@... <devel@...> On Behalf Of Tommy Lin (???) via Lists.Zephyrproject.Org
Sent: 12 November 2019 13:01
To: zephyr-devel@...
Cc: devel@...
Subject: Re: [Zephyr-devel] about BLE Rx test

 

+ jimmy

 

From: Tommy Lin (林志聰)
Sent: Tuesday, November 12, 2019 7:18 PM
To: 'zephyr-devel@...' <zephyr-devel@...>
Cc: Isaac Chen (陳尚航) <Isaac_Chen@...>; Ryan Hsu (徐振鋒) <Ryan.Hsu@...>; Brent Tsai (蔡旻其) <Brent.Tsai@...>; 'Hanyu.Hsu@...' <Hanyu.Hsu@...>
Subject: RE: about BLE Rx test

 

Hi ,

Sorry , correction.

 

We have a product using nRF51824 with Zephyr v1.13.0.

Our DUT connect with RF equipment.

 

[Test sequence]

Step1: DUT enter Rx mode with HCI command.

Step2: RF equipment send 1500 bytes with -86dbm.

Step3: DUT end Rx mode

After then , DUT will show “tx time out “ error message.

 

 

PS:

  1. If RF equipment send a dbm above -86 (ex: -85 , -84 , -83 …..), the error message will disappear.
  2. We use Zephyr v1.13.0 and v1.14.0 , and the result is the same.

 

Could you give us some suggestions?

 

Thank You,

Tommy

 
Re: Add support Optiga Trust X

Carles Cufi
 

Hi Pawel,

 

Copying a couple of people from Infineon that might be interested in your work.

 

About your questions.

 

  1. You are expected to provide the board files in a single Pull Request. If you are not able to do so maybe you can provide as much as you can using a Draft Pull Request and then ask for help in the mailing list
  2. Looking at the optiga-trust-x source code, it’s licensed under the MIT license, and it’s also a cross-platform project that is not maintained as part of Zephyr. This means that the proper way to integrate it into Zephyr is to use a separate repository with a Zephyr module. See here for more details: https://docs.zephyrproject.org/latest/guides/modules.html#submitting-a-new-module
  3. All code that goes into the main Zephyr repository should be Apache 2.0 licensed. The MIT license is fine for a module, which is a repository hosted under the zephyrproject-rtos GitHub organization but not the main repo itself. I recommend that you place all code under the MIT license in the external module, and the rest licensed as Apache 2.0 in the zephyr repo itself.

 

Carles

 

 

From: devel@... <devel@...> On Behalf Of Pawel Zarembski via Lists.Zephyrproject.Org
Sent: 12 November 2019 13:35
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] Add support Optiga Trust X

 

Hello,

I am currently working on project based on EFM32PG board and Optiga Trust X (security chip). I already did some work on implementing their framework and I run it with success with sample demo.

I want to ask about process of adding support for that board for Zephyr.

  1. Do I need to do everything by my own and then do the Pull Request for that?
  2. Should the framework/library be implemented as external Module or for example as external library ( /ext/lib )?
  3. Is there a problem with licensing? Because this framework is build on MIT license copyrighted by Infineon Technologies and some part with MIT copyrighted by Arrow Electronics.

 

Helpful links:

Repo: https://github.com/Infineon/optiga-trust-x

Implemented Platform Abstraction Layer with Zephyr support: https://github.com/Infineon/optiga-trust-x/tree/master/pal/efm32pg_zephyr

 

Best regards

Paweł Zarembski

Arrow Electronics

 
Add support Optiga Trust X

Paweł Zarembski
 

Hello,

I am currently working on project based on EFM32PG board and Optiga Trust X (security chip). I already did some work on implementing their framework and I run it with success with sample demo.

I want to ask about process of adding support for that board for Zephyr.

  1. Do I need to do everything by my own and then do the Pull Request for that?
  2. Should the framework/library be implemented as external Module or for example as external library ( /ext/lib )?
  3. Is there a problem with licensing? Because this framework is build on MIT license copyrighted by Infineon Technologies and some part with MIT copyrighted by Arrow Electronics.

 

Helpful links:

Repo: https://github.com/Infineon/optiga-trust-x

Implemented Platform Abstraction Layer with Zephyr support: https://github.com/Infineon/optiga-trust-x/tree/master/pal/efm32pg_zephyr

 

Best regards

Paweł Zarembski

Arrow Electronics
Re: about BLE Rx test

Tommy Lin (林志聰) <Tommy.Lin@...>
 

+ jimmy

 

From: Tommy Lin (林志聰)
Sent: Tuesday, November 12, 2019 7:18 PM
To: 'zephyr-devel@...' <zephyr-devel@...>
Cc: Isaac Chen (陳尚航) <Isaac_Chen@...>; Ryan Hsu (徐振鋒) <Ryan.Hsu@...>; Brent Tsai (蔡旻其) <Brent.Tsai@...>; 'Hanyu.Hsu@...' <Hanyu.Hsu@...>
Subject: RE: about BLE Rx test

 

Hi ,

Sorry , correction.

 

We have a product using nRF51824 with Zephyr v1.13.0.

Our DUT connect with RF equipment.

 

[Test sequence]

Step1: DUT enter Rx mode with HCI command.

Step2: RF equipment send 1500 bytes with -86dbm.

Step3: DUT end Rx mode

After then , DUT will show “tx time out “ error message.

 

 

PS:

1.     If RF equipment send a dbm above -86 (ex: -85 , -84 , -83 …..), the error message will disappear.

2.     We use Zephyr v1.13.0 and v1.14.0 , and the result is the same.

 

Could you give us some suggestions?

 

Thank You,

Tommy

 
Re: about BLE Rx test

Tommy Lin (林志聰) <Tommy.Lin@...>
 

Hi ,

Sorry , correction.

 

We have a product using nRF51824 with Zephyr v1.13.0.

Our DUT connect with RF equipment.

 

[Test sequence]

Step1: DUT enter Rx mode with HCI command.

Step2: RF equipment send 1500 bytes with -86dbm.

Step3: DUT end Rx mode

After then , DUT will show “tx time out “ error message.

 

 

PS:

1.     If RF equipment send a dbm above -86 (ex: -85 , -84 , -83 …..), the error message will disappear.

2.     We use Zephyr v1.13.0 and v1.14.0 , and the result is the same.

 

Could you give us some suggestions?

 

Thank You,

Tommy

 
about BLE Rx test

Tommy Lin (林志聰) <Tommy.Lin@...>
 

Hi ,

We have a product using nRF51824 with Zephyr v1.13.0.

Our DUT connect with RF equipment.

 

[Test sequence]

Step1: DUT enter Rx mode with HCI command.

Step2: RF equipment send 1500 bytes with -86dbm.

Step3: DUT end Rx mode

After then , DUT will show “tx time out “ error message.

 

 

PS:

1.     If RF equipment send a dbm below -86 , the error message will disappear.

2.     We use Zephyr v1.13.0 and v1.14.0 , and the result is the same.

 

Could you give us some suggestions?

 

Thank You,

Tommy

 
Re: Issue in OTA of zephyr OS over UART on Nordic nrf52840_pca10056 chip #ble #bluetoothmesh #nrf52840 #uart

Mayank <mayank7117@...>
 

Thanks Adam, 
I have upgraded zephyr to latest version (2.1.0) using west update.
Now with the configuration of my application as well as mcuboot, i reached at the stage where i can upload the signed application image using mcumgr cli.

Note: I am not running mcuboot in serial recovery mode.

PFA for hci_uart application.

Regards,
Mayank Patel


On Tue, Nov 12, 2019 at 3:50 PM Adam Podogrocki <a.podogrocki@...> wrote:
Hi Mayank,

could you please attach your 'zephyr/.config' file? Maybe I will find some inaccuracy there.

Cheers,
Adam

On Fri, 8 Nov 2019 at 06:00, Mayank <mayank7117@...> wrote:
Thanks Adam, I have disabled BT and Shell, Only UART is there.
Now, when i run the command with debug mode --> mcumgr -ldebug --conntype=serial --connstring='dev=/dev/ttymxc0,baud=115200' echo hello

I'm getting following response with timeout.

DEBU[2019-11-07 15:24:57.671] Using connection profile: name=unnamed type=serial connstring=dev=/dev/ttymxc0,baud=115200 
DEBU[2019-11-07 15:24:57.678] {add-nmp-listener} [serial_sesn.go:213] seq=66 
DEBU[2019-11-07 15:24:57.68] Encoded &{NmpBase:{hdr:{Op:2 Flags:0 Len:0 Group:0 Seq:66 Id:0}} Payload:hello} to:
00000000  a1 61 64 65 68 65 6c 6c  6f                       |.adehello| 
DEBU[2019-11-07 15:24:57.681] Encoded:
00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.705] Tx NMP request: 00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.706] Base64 encoding request:
00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.707] Tx serial
00000000  06 09                                             |..| 
DEBU[2019-11-07 15:24:57.708] Tx serial
00000000  41 42 4d 43 41 41 41 4a  41 41 42 43 41 4b 46 68  |ABMCAAAJAABCAKFh|
00000010  5a 47 56 6f 5a 57 78 73  62 38 45 4a              |ZGVoZWxsb8EJ| 
DEBU[2019-11-07 15:24:57.709] Tx serial
00000000  0a                                                |.| 
DEBU[2019-11-07 15:25:07.713] {remove-nmp-listener} [serial_sesn.go:213] seq=66 
DEBU[2019-11-07 15:25:07.726] goroutine 1 [running]:
github.com/spf13/cobra.(*Command).execute(0x2ce1400, 0x2ca72e0, 0x4, 0x4, 0x2ce1400, 0x2ca72e0)
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:830 +0x1f4
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:914 +0x230
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:864
main.main()
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:94 +0xe0
 
goroutine 6 [syscall]:
os/signal.signal_recv(0x0)
        /snap/go/4668/src/runtime/sigqueue.go:147 +0x130
os/signal.loop()
        /snap/go/4668/src/os/signal/signal_unix.go:23 +0x14
created by os/signal.init.0
        /snap/go/4668/src/os/signal/signal_unix.go:29 +0x30
 
goroutine 9 [chan receive]:
main.main.func1(0x2c42800)
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:82 +0x34
created by main.main
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:80 +0xd8
 
goroutine 10 [runnable]:
bufio.(*Scanner).Scan(0x2f9be80, 0x2f9be80)
        /snap/go/4668/src/bufio/scan.go:203 +0x230
 
goroutine 11 [select]:
Error: NMP timeout


--> Can anyone has came across such issue.
Regards,
Mayank

?
config_hci_uart

Re: Issue in OTA of zephyr OS over UART on Nordic nrf52840_pca10056 chip #ble #bluetoothmesh #nrf52840 #uart

Adam Podogrocki
 

Hi Mayank,

could you please attach your 'zephyr/.config' file? Maybe I will find some inaccuracy there.

Cheers,
Adam

On Fri, 8 Nov 2019 at 06:00, Mayank <mayank7117@...> wrote:
Thanks Adam, I have disabled BT and Shell, Only UART is there.
Now, when i run the command with debug mode --> mcumgr -ldebug --conntype=serial --connstring='dev=/dev/ttymxc0,baud=115200' echo hello

I'm getting following response with timeout.

DEBU[2019-11-07 15:24:57.671] Using connection profile: name=unnamed type=serial connstring=dev=/dev/ttymxc0,baud=115200 
DEBU[2019-11-07 15:24:57.678] {add-nmp-listener} [serial_sesn.go:213] seq=66 
DEBU[2019-11-07 15:24:57.68] Encoded &{NmpBase:{hdr:{Op:2 Flags:0 Len:0 Group:0 Seq:66 Id:0}} Payload:hello} to:
00000000  a1 61 64 65 68 65 6c 6c  6f                       |.adehello| 
DEBU[2019-11-07 15:24:57.681] Encoded:
00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.705] Tx NMP request: 00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.706] Base64 encoding request:
00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.707] Tx serial
00000000  06 09                                             |..| 
DEBU[2019-11-07 15:24:57.708] Tx serial
00000000  41 42 4d 43 41 41 41 4a  41 41 42 43 41 4b 46 68  |ABMCAAAJAABCAKFh|
00000010  5a 47 56 6f 5a 57 78 73  62 38 45 4a              |ZGVoZWxsb8EJ| 
DEBU[2019-11-07 15:24:57.709] Tx serial
00000000  0a                                                |.| 
DEBU[2019-11-07 15:25:07.713] {remove-nmp-listener} [serial_sesn.go:213] seq=66 
DEBU[2019-11-07 15:25:07.726] goroutine 1 [running]:
github.com/spf13/cobra.(*Command).execute(0x2ce1400, 0x2ca72e0, 0x4, 0x4, 0x2ce1400, 0x2ca72e0)
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:830 +0x1f4
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:914 +0x230
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:864
main.main()
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:94 +0xe0
 
goroutine 6 [syscall]:
os/signal.signal_recv(0x0)
        /snap/go/4668/src/runtime/sigqueue.go:147 +0x130
os/signal.loop()
        /snap/go/4668/src/os/signal/signal_unix.go:23 +0x14
created by os/signal.init.0
        /snap/go/4668/src/os/signal/signal_unix.go:29 +0x30
 
goroutine 9 [chan receive]:
main.main.func1(0x2c42800)
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:82 +0x34
created by main.main
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:80 +0xd8
 
goroutine 10 [runnable]:
bufio.(*Scanner).Scan(0x2f9be80, 0x2f9be80)
        /snap/go/4668/src/bufio/scan.go:203 +0x230
 
goroutine 11 [select]:
Error: NMP timeout


--> Can anyone has came across such issue.
Regards,
Mayank
Re: Error building hello world #samples

Carles Cufi
 

Hi there,

 

It looks like some of the modules are missing.

 

Can you make sure you have run “west update” in the working tree?

 

Carles

 

From: devel@... <devel@...> On Behalf Of mdecandia via Lists.Zephyrproject.Org
Sent: 11 November 2019 22:58
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] Error building hello world #samples

 

Hi all,
I'm trying to build hello_world sample on Ubuntu 19.10 with west buld command. I'm having the following issue:

west build -b qemu_x86 $PWD/samples/hello_world

-- west build: build configuration:

       source directory: /home/michele/devel/zephyr/samples/hello_world

       build directory: /home/michele/devel/zephyr/build

       BOARD: qemu_x86 (origin: command line)

-- west build: generating a build system

Zephyr version: 2.1.0

-- Selected BOARD qemu_x86

-- Found west: /home/michele/.local/bin/west (found suitable version "0.6.3", minimum required is "0.6.0")

CMake Error at /home/michele/devel/zephyr/cmake/zephyr_module.cmake:45 (message):

  Traceback (most recent call last):

 

    File "/home/michele/devel/zephyr/scripts/zephyr_module.py", line 167, in <module>

      main()

    File "/home/michele/devel/zephyr/scripts/zephyr_module.py", line 158, in main

      process_module(project, cmake_out_file, kconfig_out_file)

    File "/home/michele/devel/zephyr/scripts/zephyr_module.py", line 68, in process_module

      pykwalify.core.Core(source_data=meta, schema_data=schema)\

    File "/home/michele/.local/lib/python3.7/site-packages/pykwalify/core.py", line 114, in __init__

      raise CoreError(u"No source file/data was loaded")

 

  pykwalify.errors.CoreError: <CoreError: error code 3: No source file/data

  was loaded: Path: '/'>

 

Call Stack (most recent call first):

  /home/michele/devel/zephyr/cmake/app/boilerplate.cmake:458 (include)

  CMakeLists.txt:5 (include)

 

 

-- Configuring incomplete, errors occurred!

ERROR: command exited with status 1: /usr/bin/cmake -B/home/michele/devel/zephyr/build -S/home/michele/devel/zephyr/samples/hello_world -GNinja -DBOARD=qemu_x86



Any idea?

Thanks
Error building hello world #samples

mdecandia@...
 

Hi all,
I'm trying to build hello_world sample on Ubuntu 19.10 with west buld command. I'm having the following issue:

west build -b qemu_x86 $PWD/samples/hello_world
-- west build: build configuration:
       source directory: /home/michele/devel/zephyr/samples/hello_world
       build directory: /home/michele/devel/zephyr/build
       BOARD: qemu_x86 (origin: command line)
-- west build: generating a build system
Zephyr version: 2.1.0
-- Selected BOARD qemu_x86
-- Found west: /home/michele/.local/bin/west (found suitable version "0.6.3", minimum required is "0.6.0")
CMake Error at /home/michele/devel/zephyr/cmake/zephyr_module.cmake:45 (message):
  Traceback (most recent call last):
 
    File "/home/michele/devel/zephyr/scripts/zephyr_module.py", line 167, in <module>
      main()
    File "/home/michele/devel/zephyr/scripts/zephyr_module.py", line 158, in main
      process_module(project, cmake_out_file, kconfig_out_file)
    File "/home/michele/devel/zephyr/scripts/zephyr_module.py", line 68, in process_module
      pykwalify.core.Core(source_data=meta, schema_data=schema)\
    File "/home/michele/.local/lib/python3.7/site-packages/pykwalify/core.py", line 114, in __init__
      raise CoreError(u"No source file/data was loaded")
 
  pykwalify.errors.CoreError: <CoreError: error code 3: No source file/data
  was loaded: Path: '/'>
 
Call Stack (most recent call first):
  /home/michele/devel/zephyr/cmake/app/boilerplate.cmake:458 (include)
  CMakeLists.txt:5 (include)
 
 
-- Configuring incomplete, errors occurred!
ERROR: command exited with status 1: /usr/bin/cmake -B/home/michele/devel/zephyr/build -S/home/michele/devel/zephyr/samples/hello_world -GNinja -DBOARD=qemu_x86


Any idea?

Thanks
Tomorrow's API meeting: Agenda

Carles Cufi
 

Hi all,

This week we will look at:

- QSPI/jedec API proposal vs SPI API extension:
- https://github.com/zephyrproject-rtos/zephyr/pull/20069
vs
- https://github.com/zephyrproject-rtos/zephyr/pull/20564

- GPIO: Update on progress
- Look at the PRs with driver conversion (https://github.com/zephyrproject-rtos/zephyr/issues/18530)
- Check users of GPIO APIs: https://github.com/zephyrproject-rtos/zephyr/issues/20017
- Tips for converting users can be found here: https://github.com/zephyrproject-rtos/zephyr/issues/20017#issuecomment-549315497 (thanks Peter!)
- Any additional outstanding PRs to topic-gpio

Additional items in the "Triage" column in the GitHub project may be discussed if time permits.
If you want an item included in the meeting, please add it to the GitHub project.

https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion
https://github.com/zephyrproject-rtos/zephyr/projects/18
https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles
New topic branch created: topic-ble-llcp

Carles Cufi
 

Hi all,

We have just created a new topic branch to work on refactoring the BLE Link Layer control procedures.
If you are interested in this work feel free to follow that branch and the Pull Requests that will be posted against it.

Regards,

Carles
Zephyr 2.1.0-rc1 tagged

David Leach
 

Hi Zephyr developers,

 

Zephyr 2.1.0-rc1 release candidate has been tagged.

 

All required features scheduled for 2.1 release are now merged into master. As of now we are in the stabilization phase for 2.1 release; the merge window is closed for new features and enhancements, and will remain closed until the release date. We will also start working on filling in the existing skeleton for the release notes.

 

During the stabilization period only bug-fix, documentation, and stabilization-related patches may be merged to master. Additional features or enhancements for 2.1 release will require approval by TSC.

 

As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers.

 

Testing Zephyr release candidate branches is also requested; please, test the code base and file bug reports so they can be addressed before the release deadline.

 

The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.1.0-rc1

 

More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

 

The final release is tentatively scheduled for November 29th.

 

Thank you to everybody who contributed to this release!

 

David Leach

 

 

David Leach

 

NXP Semiconductors

phone: +1.210.241.6761

Email: david.leach@...

 

 

** PROPRIETARY & COMPANY-CONFIDENTIAL **

 
Re: Issue in OTA of zephyr OS over UART on Nordic nrf52840_pca10056 chip #ble #bluetoothmesh #nrf52840 #uart

Mayank <mayank7117@...>
 

Thanks Adam, I have disabled BT and Shell, Only UART is there.
Now, when i run the command with debug mode --> mcumgr -ldebug --conntype=serial --connstring='dev=/dev/ttymxc0,baud=115200' echo hello

I'm getting following response with timeout.

DEBU[2019-11-07 15:24:57.671] Using connection profile: name=unnamed type=serial connstring=dev=/dev/ttymxc0,baud=115200 
DEBU[2019-11-07 15:24:57.678] {add-nmp-listener} [serial_sesn.go:213] seq=66 
DEBU[2019-11-07 15:24:57.68] Encoded &{NmpBase:{hdr:{Op:2 Flags:0 Len:0 Group:0 Seq:66 Id:0}} Payload:hello} to:
00000000  a1 61 64 65 68 65 6c 6c  6f                       |.adehello| 
DEBU[2019-11-07 15:24:57.681] Encoded:
00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.705] Tx NMP request: 00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.706] Base64 encoding request:
00000000  02 00 00 09 00 00 42 00  a1 61 64 65 68 65 6c 6c  |......B..adehell|
00000010  6f                                                |o| 
DEBU[2019-11-07 15:24:57.707] Tx serial
00000000  06 09                                             |..| 
DEBU[2019-11-07 15:24:57.708] Tx serial
00000000  41 42 4d 43 41 41 41 4a  41 41 42 43 41 4b 46 68  |ABMCAAAJAABCAKFh|
00000010  5a 47 56 6f 5a 57 78 73  62 38 45 4a              |ZGVoZWxsb8EJ| 
DEBU[2019-11-07 15:24:57.709] Tx serial
00000000  0a                                                |.| 
DEBU[2019-11-07 15:25:07.713] {remove-nmp-listener} [serial_sesn.go:213] seq=66 
DEBU[2019-11-07 15:25:07.726] goroutine 1 [running]:
mynewt.apache.org/newt/util.NewNewtError(0x5b35ca, 0xb, 0xb)
        /home/mayank/go/bin/pkg/mod/mynewt.apache.org/newt@....0-20190805215728-4e771ee138aa/util/util.go:77 +0xa4
mynewt.apache.org/newt/util.ChildNewtError(0x68d080, 0x2c0e010, 0x2c5cbd0)
        /home/mayank/go/bin/pkg/mod/mynewt.apache.org/newt@....0-20190805215728-4e771ee138aa/util/util.go:103 +0x78
mynewt.apache.org/newtmgr/newtmgr/cli.echoRunCmd(0x2ce1400, 0x2ca73e0, 0x1, 0x4)
        /home/mayank/go/bin/pkg/mod/mynewt.apache.org/newtmgr@....0-20190909210301-5029f07bf173/newtmgr/cli/echo.go:48 +0x1dc
github.com/spf13/cobra.(*Command).execute(0x2ce1400, 0x2ca72e0, 0x4, 0x4, 0x2ce1400, 0x2ca72e0)
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:830 +0x1f4
github.com/spf13/cobra.(*Command).ExecuteC(0x2c82640, 0x5dc824, 0x2c42800, 0x0)
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:914 +0x230
github.com/spf13/cobra.(*Command).Execute(...)
        /home/mayank/go/bin/pkg/mod/github.com/spf13/cobra@....5/command.go:864
main.main()
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:94 +0xe0
 
goroutine 6 [syscall]:
os/signal.signal_recv(0x0)
        /snap/go/4668/src/runtime/sigqueue.go:147 +0x130
os/signal.loop()
        /snap/go/4668/src/os/signal/signal_unix.go:23 +0x14
created by os/signal.init.0
        /snap/go/4668/src/os/signal/signal_unix.go:29 +0x30
 
goroutine 9 [chan receive]:
main.main.func1(0x2c42800)
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:82 +0x34
created by main.main
        /home/mayank/go/src/github.com/apache/mynewt-mcumgr-cli/mcumgr/mcumgr.go:80 +0xd8
 
goroutine 10 [runnable]:
bufio.(*Scanner).Scan(0x2f9be80, 0x2f9be80)
        /snap/go/4668/src/bufio/scan.go:203 +0x230
mynewt.apache.org/newtmgr/nmxact/nmserial.(*SerialXport).Rx(0x2c42cc0, 0x2c2dfd0, 0x0, 0x0, 0x68cb58, 0x2c0f4f0)
        /home/mayank/go/bin/pkg/mod/mynewt.apache.org/newtmgr@....0-20190909210301-5029f07bf173/nmxact/nmserial/serial_xport.go:304 +0xec
mynewt.apache.org/newtmgr/nmxact/nmserial.(*SerialXport).Start.func1(0x2c42cc0)
        /home/mayank/go/bin/pkg/mod/mynewt.apache.org/newtmgr@....0-20190909210301-5029f07bf173/nmxact/nmserial/serial_xport.go:135 +0xd8
created by mynewt.apache.org/newtmgr/nmxact/nmserial.(*SerialXport).Start
        /home/mayank/go/bin/pkg/mod/mynewt.apache.org/newtmgr@....0-20190909210301-5029f07bf173/nmxact/nmserial/serial_xport.go:127 +0xf8
 
goroutine 11 [select]:
mynewt.apache.org/newtmgr/nmxact/nmserial.(*SerialSesn).Open.func1(0x2c5cbd0)
        /home/mayank/go/bin/pkg/mod/mynewt.apache.org/newtmgr@....0-20190909210301-5029f07bf173/nmxact/nmserial/serial_sesn.go:101 +0xcc
created by mynewt.apache.org/newtmgr/nmxact/nmserial.(*SerialSesn).Open
        /home/mayank/go/bin/pkg/mod/mynewt.apache.org/newtmgr@....0-20190909210301-5029f07bf173/nmxact/nmserial/serial_sesn.go:97 +0x1b8 
Error: NMP timeout


--> Can anyone has came across such issue.
Regards,
Mayank
Upcoming Event: Zephyr Project: Dev Meeting - Thu, 11/07/2019 8:00am-9:00am, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>
 

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 7 November 2019, 8:00am to 9:00am, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/993312203

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join Zoom Meeting
https://zoom.us/j/993312203

One tap mobile
+16699006833,,993312203# US (San Jose)
+16465588656,,993312203# US (New York)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 558 8656 US (New York)
        +1 877 369 0926 US Toll-free
        +1 855 880 1246 US Toll-free
Meeting ID: 993 312 203
Find your local number: https://zoom.us/u/ankEMRagf
Re: Issue in OTA of zephyr OS over BLE on Nordic nrf52840_pca10056 chip #nrf52840 #ble #bluetoothmesh

Mayank <mayank7117@...>
 

Thanks Jamie,

Here, I would like to point out the exact setup that i'm trying DFU on.
I have One custom board which has imx6ul processor, I'm having one BLE controller on board which is connected to processor over uart.
Now from the boards serial console i would like to update the zephyr application to that BLE controller.

Regards,
Mayank


On Thu, Nov 7, 2019 at 1:14 PM lairdjm <jamie.mccrae@...> wrote:

Hi Mayank,

You are getting this error because the hci0 device could not be enabled on your host system, the echo command sends that to the remote device using Bluetooth. You need a Bluetooth dongle plugged into your PC which supports Bluetooth 4.0+ (and must have support for Bluetooth Low Energy). You can use the BlueZ commands to see what Bluetooth devices you have on your system and the corresponding LMP versions. You need a device with LMP version 6 or newer.

Thanks,

Jamie
Re: problem with command call

Carles Cufi
 

Hi there,

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On
Behalf Of FLIGIL Veneamin via Lists.Zephyrproject.Org
Sent: 07 November 2019 11:41
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] problem with command call

Hello. I am sorry for disturbing you.
When I call the command on linux vm: west init zephyrprohect I have the
response:
Command ‘west’ not found, did you mean:
command ’test’ from deb coreutils (8.30-1ubuntu1)
Try: sudo apt install <deb name>
Make sure that you have installed west with:

$ pip3 install --user west

and that then the location where your binary is installed is in your PATH:

https://docs.zephyrproject.org/latest/getting_started/index.html#python-and-pip


Carles
problem with command call

FLIGIL Veneamin <veneamin.fligil@...>
 

Hello. I am sorry for disturbing you.
When I call the command on linux vm: west init zephyrprohect
I have the response:
Command ‘west’ not found, did you mean:
command ’test’ from deb coreutils (8.30-1ubuntu1)
Try: sudo apt install <deb name>
Re: Issue in OTA of zephyr OS over BLE on Nordic nrf52840_pca10056 chip #nrf52840 #ble #bluetoothmesh

lairdjm
 

Hi Mayank,

You are getting this error because the hci0 device could not be enabled on your host system, the echo command sends that to the remote device using Bluetooth. You need a Bluetooth dongle plugged into your PC which supports Bluetooth 4.0+ (and must have support for Bluetooth Low Energy). You can use the BlueZ commands to see what Bluetooth devices you have on your system and the corresponding LMP versions. You need a device with LMP version 6 or newer.

Thanks,

Jamie
1721 - 1740 of 8183