Date   

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


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


Issue in OTA of zephyr OS over BLE on Nordic nrf52840_pca10056 chip #nrf52840 #ble #bluetoothmesh

Mayank <mayank7117@...>
 

Hi,

I'm trying to do an OTA of zephyr hci_uart application and i have done following things.
Referred https://docs.zephyrproject.org/1.14.0/samples/subsys/mgmt/mcumgr/smp_svr/README.html?highlight=build%20smp_svr
By following this document,
1) Build & flashed MCUBOOT bootloader. Addr range(0x0 to 0x8000)
2) Build, signed hex file & flashed smp_svr. Addr range(0xC000 to 0x27000)

Now, when I run below command it should respond with 'hello', but that is not the case.
Command --> sudo mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' echo hello

Instead, i'm getting 'Can not up hci0 interface'.
According to my understanding hci0 will be up only when i will build & flash the zephyr's hci_uart application(But it's not mentioned anywhere in above zephyr's doc).
So am i missing something and if not why it is not working as mentioned in the above zephyr's link.

Thanks,
Mayank


Dev-Review Meeting Agenda (Nov 7)

Kumar Gala
 

Here’s the agenda topics for this week:

New, orthogonal and complete time conversion API
https://github.com/zephyrproject-rtos/zephyr/pull/19591

DTS: Remove parsing of DT generated Kconfig symbols [galak, SebastianBoe]
https://github.com/zephyrproject-rtos/zephyr/pull/20335

scripts: dts: Accept 'status = "ok"
https://github.com/zephyrproject-rtos/zephyr/pull/19408

PinMux:
[WIP] NXP Kinetis DTS Pinmux rework -
https://github.com/zephyrproject-rtos/zephyr/pull/20398
dts: stm32: Introduce linux like pinctrl bindings
https://github.com/zephyrproject-rtos/zephyr/pull/20386

If there’s anything else to add please let me know.

Thanks

- k


Re: ELC-E Zephyr Multiimage BoF - Bob Build Tool

Bolivar, Marti
 

Hi,

"Jan Kloetzke via Lists.Zephyrproject.Org"
<jan=kloetzke.net@lists.zephyrproject.org> writes:

On Mon, Nov 04, 2019 at 10:34:37PM +0000, Bolivar, Marti wrote:
I made a quick hack west extension to convert the upstream zephyr
manifest into the format used there, in case it's useful:

https://github.com/mbolivar/tree/bob-the-builder

Example:

$ west gen-bob-checkout
checkoutSCM:
- commit: 07380358424edecdefeb28ed7cb43e27b530014d
dir: zephyr
scm: git
url: https://github.com/zephyrproject-rtos/zephyr
- commit: 04ff67a0826a51041e51034faf8fc4d3eeacd846
dir: modules/hal/atmel
scm: git
url: https://github.com/zephyrproject-rtos/hal_atmel
- commit: e01f3bce2a94847253369efb9a081f5c0e9ec882
dir: tools/ci-tools
scm: git
url: https://github.com/zephyrproject-rtos/ci-tools
- commit: 99129c5efc907ea613c4b73ccff07581feb58a7a
dir: modules/lib/civetweb
scm: git
url: https://github.com/zephyrproject-rtos/civetweb
[...]

Just in case it's useful to anyone who wants all the projects but
doesn't want to do the paperwork themselves.
That looks indeed useful.

I was wondering if there is a way to select only the needed
repositories? West seems to always clone all known projects up-front.
Plain "west update" updates all the repositories. You can say "west
update project-1 project-2 ..." to just work on a subset of them.

OTOH Bob's approach is normally to checkout the sources individually for
each project and then build these individually. AFAICT this won't work
for Zephyr because all repositories must be present to be gathered in
one large CMake project. So the structure ends up with a single large
source package. Are there any plans to make this more modular in the
future?
If you have cloned all the modules your application needs to build,
you're fine. You don't need to download all of them.

Indeed, you don't need west at all if you manually set ZEPHYR_MODULES
before building:

https://docs.zephyrproject.org/latest/guides/west/without-west.html#specifying-modules

But west doesn't manage dependencies between repositories. That would
take it into package manager territory. We are staying away from that
as a design decision.

It's up to the user to either manage their application's dependencies
explicitly, or just fetch the kitchen sink. Either way, Kconfig
ultimately controls what gets built into the final firmware image.

Marti


Re: ELC-E Zephyr Multiimage BoF - Bob Build Tool

Jan Kloetzke <jan@...>
 

On Mon, Nov 04, 2019 at 10:34:37PM +0000, Bolivar, Marti wrote:
"Jan Kloetzke via Lists.Zephyrproject.Org"
<jan=kloetzke.net@lists.zephyrproject.org> writes:

On Fri, Nov 01, 2019 at 09:24:59AM +0000, Bolivar, Marti wrote:
"Jan Kloetzke via Lists.Zephyrproject.Org"
<jan=kloetzke.net@lists.zephyrproject.org> writes:

Hi Kumar,

On Wed, Oct 30, 2019 at 02:05:36AM -0500, Kumar Gala wrote:

On Oct 29, 2019, at 5:08 AM, jan@kloetzke.net wrote:

Hi,

I think the https://github.com/BobBuildTool/bob-example-embedded
example is the most interesting one to the Zephyr community (even
though it's using FreeRTOS+Linux at the moment).

If you guys have a particular example that already builds multiple
dependent Zephyr images then we can try to setup some Bob recipes
that builds the same thing...

/Jan
You can take a look at the open-amp sample, it creates 2 zephyr images:

https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/subsys/ipc/openamp
I'm currently preparing some recipes. It will post them with some
instructions how to build in the next days once I got it working...
Ok, here it is: https://github.com/jkloetzke/zephyr-example-recipes

There is a README.md with a short overview. Basically you just have to
clone the recipes and build it:

$ git clone https://github.com/jkloetzke/zephyr-example-recipes.git \
--recurse-submodules
$ cd zephyr-example-recipes
$ bob dev demo::zephyr -j

Make sure that you have the latest version of Bob. The demo recipes use
the "layers" feature that has not been released yet. It's best to
install Bob via:

$ pip3 install [--user] git+https://github.com/BobBuildTool/bob

Otherwise have a look at

https://bob-build-tool.readthedocs.io/en/latest/installation.html

for further options.

Note that the recipes do not use west but clone the involved
repositories directly and calls cmake itself. This has the advantage
that there is only one tool that fetches/updates sources.
Seems like zephyr.yaml is the file controlling this in a map called
checkoutSCM. (I haven't read the bob docs, but I'm sure that's covered
there.)
Yes, that's correct. It's covered here:

https://bob-build-tool.readthedocs.io/en/latest/manual/configuration.html#checkoutscm


I made a quick hack west extension to convert the upstream zephyr
manifest into the format used there, in case it's useful:

https://github.com/mbolivar/tree/bob-the-builder

Example:

$ west gen-bob-checkout
checkoutSCM:
- commit: 07380358424edecdefeb28ed7cb43e27b530014d
dir: zephyr
scm: git
url: https://github.com/zephyrproject-rtos/zephyr
- commit: 04ff67a0826a51041e51034faf8fc4d3eeacd846
dir: modules/hal/atmel
scm: git
url: https://github.com/zephyrproject-rtos/hal_atmel
- commit: e01f3bce2a94847253369efb9a081f5c0e9ec882
dir: tools/ci-tools
scm: git
url: https://github.com/zephyrproject-rtos/ci-tools
- commit: 99129c5efc907ea613c4b73ccff07581feb58a7a
dir: modules/lib/civetweb
scm: git
url: https://github.com/zephyrproject-rtos/civetweb
[...]

Just in case it's useful to anyone who wants all the projects but
doesn't want to do the paperwork themselves.
That looks indeed useful.

I was wondering if there is a way to select only the needed
repositories? West seems to always clone all known projects up-front.
OTOH Bob's approach is normally to checkout the sources individually for
each project and then build these individually. AFAICT this won't work
for Zephyr because all repositories must be present to be gathered in
one large CMake project. So the structure ends up with a single large
source package. Are there any plans to make this more modular in the
future?

Additionally
the OpenAMP sample was put into a dedicated repository because some
refactoring was needed, namely removing the "ExternalProject" link
between the images.

The recipes also show how a toolchain is defined in the recipes. There
is no need for the user to install a toolchain but the right one is
brought in by the recipes automatically. Usually this is done with all
involved tools to maximize reproducibility but this would have just made
the example more complicated.

Sounds great!

Please be aware of this in that case:

https://github.com/zephyrproject-rtos/zephyr/issues/19918

It would be good to see a solution that doesn't have this issue.
This is handled well by Bob. The explicit goal of Bob is to feel like
"make" even though Bob controls the build of whole packages.

Have fun.

/Jan


Re: Event-driven architecture in Zephyr

pawel.dunaj@...
 

Hi Jeff,

As far as I know Zephyr does not have any such mechanism. This is why we have created the Event Manger. The aim was to keep it universal but since it was done to satisfy needs of a certain project it has its limitations. We tried to keep overhead low and remove concurrency issues. Anyway I am glad that people try to use it.

In nrf_desktop we use separate low-priority thread for long running operations. We were also thinking about splitting long operations into sub-tasks each triggered separately (you can have a look in the optical sensor drivers).

I would like to hear what people find missing in the Event Manager as there is a plan to improve it in the future. I would like to move towards creating an application framework but that is a much bigger task and first we need to see what is really needed.

Thanks,
Pawel


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

Adam Podogrocki
 

Hi Mayank,

If you are using UART as a connection type, then please disable other communication channels like BT and shell - at least in my case with STM32 it helped.

I assume that flash partition layout corresponds to what you've wrote: "I have flashed MCUBOOT (0x0 to 0x8000) and smp_svr (0xC000 to 0x27000)." 
I assume that you have signed the 'smp_svr' binary.
Regards,
Adam

On Wed, 6 Nov 2019 at 07:36, Mayank Patel <mayank7117@...> wrote:
Hi Adam,

Thanks for the quick reply.
I have flashed MCUBOOT (0x0 to 0x8000) and smp_svr (0xC000 to 0x27000).
The flag CONFIG_UART_MCUMGR_ON_DEV_NAME is defaults to 'UART_0'.

My DTS file has following configuration right now.
        chosen {
                zephyr,console = &uart0;
                zephyr,shell-uart = &uart0;
                zephyr,uart-mcumgr = &uart0;
                zephyr,bt-mon-uart = &uart0;
                zephyr,sram = &sram0;
                zephyr,flash = &flash0;
                zephyr,code-partition = &slot0_partition;
        };

&uart0 {
        compatible = "nordic,nrf-uart";
        current-speed = <115200>;
        status = "ok";
        //For i.MX DCE configuration
        tx-pin = <8>;
        rx-pin = <4>;
        rts-pin = <26>;
        cts-pin = <6>;
};

Command used from imx6ul board running on yocto linux:
sudo mcumgr --conntype serial --connstring='dev=/dev/ttymxc0,baud=115200' echo hello

So, am i missing some configuration or do you see any other issue?




Regards,
Mayank Patel
(M.Tech VLSI & Embedded system)
Ganpat University
+91-9722260070


On Tue, Nov 5, 2019 at 8:43 PM Adam Podogrocki <a.podogrocki@...> wrote:
Hi Mayank,

If you are sure the partition layout of flash memory is correct and you flashed MCUboot and SMP_SVR sample respectively, then please check if the CONFIG_UART_MCUMGR_ON_DEV_NAME is set correctly.

Regards,
Adam



On Tue, 5 Nov 2019 at 15:15, Mayank <mayank7117@...> wrote:

Hi,
I have nrf52840 on my custom board (Based on IMX6, Running Yocto linux) which is connected over UART.
I want to do an OTA of zephyr OS on that chip over serial/ble and for that i had already tried following things.
1) I have build smp_svr and flashed it to nrf52840 so that i can use 'mcumgr' command line tool for the flashing.
Referred https://docs.zephyrproject.org/1.14.0/samples/subsys/mgmt/mcumgr/smp_svr/README.html?highlight=build%20smp_svr to know how to use 'mcumgr'.

Now, when i use mcumgr to communicate 'hello' message over serial/UART, It shows error of connection timed out. (Also tried with -t switch, but no luck).
Command used are :
sudo mcumgr --conntype serial --connstring='dev=/dev/ttymxc0,baud=115200' echo hello
--> So it's not able to open the connection using mcumgr and not getting any reply (Getting timeout).


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

Mayank <mayank7117@...>
 

Hi Adam,

Thanks for the quick reply.
I have flashed MCUBOOT (0x0 to 0x8000) and smp_svr (0xC000 to 0x27000).
The flag CONFIG_UART_MCUMGR_ON_DEV_NAME is defaults to 'UART_0'.

My DTS file has following configuration right now.
        chosen {
                zephyr,console = &uart0;
                zephyr,shell-uart = &uart0;
                zephyr,uart-mcumgr = &uart0;
                zephyr,bt-mon-uart = &uart0;
                zephyr,sram = &sram0;
                zephyr,flash = &flash0;
                zephyr,code-partition = &slot0_partition;
        };

&uart0 {
        compatible = "nordic,nrf-uart";
        current-speed = <115200>;
        status = "ok";
        //For i.MX DCE configuration
        tx-pin = <8>;
        rx-pin = <4>;
        rts-pin = <26>;
        cts-pin = <6>;
};

Command used from imx6ul board running on yocto linux:
sudo mcumgr --conntype serial --connstring='dev=/dev/ttymxc0,baud=115200' echo hello

So, am i missing some configuration or do you see any other issue?




Regards,
Mayank Patel
(M.Tech VLSI & Embedded system)
Ganpat University
+91-9722260070


On Tue, Nov 5, 2019 at 8:43 PM Adam Podogrocki <a.podogrocki@...> wrote:
Hi Mayank,

If you are sure the partition layout of flash memory is correct and you flashed MCUboot and SMP_SVR sample respectively, then please check if the CONFIG_UART_MCUMGR_ON_DEV_NAME is set correctly.

Regards,
Adam



On Tue, 5 Nov 2019 at 15:15, Mayank <mayank7117@...> wrote:

Hi,
I have nrf52840 on my custom board (Based on IMX6, Running Yocto linux) which is connected over UART.
I want to do an OTA of zephyr OS on that chip over serial/ble and for that i had already tried following things.
1) I have build smp_svr and flashed it to nrf52840 so that i can use 'mcumgr' command line tool for the flashing.
Referred https://docs.zephyrproject.org/1.14.0/samples/subsys/mgmt/mcumgr/smp_svr/README.html?highlight=build%20smp_svr to know how to use 'mcumgr'.

Now, when i use mcumgr to communicate 'hello' message over serial/UART, It shows error of connection timed out. (Also tried with -t switch, but no luck).
Command used are :
sudo mcumgr --conntype serial --connstring='dev=/dev/ttymxc0,baud=115200' echo hello
--> So it's not able to open the connection using mcumgr and not getting any reply (Getting timeout).

1741 - 1760 of 8196