|
Re: Zephyr Sample Demo with nrf52840 Dongle
Carles Cufi
Hi there,
nrfutil does not support Python 3 for now. You will need to install Python 2 and then install nrfutil with its pip2.
Carles
From: devel@... <devel@...>
On Behalf Of via Lists.Zephyrproject.Org
Sent: 24 July 2019 09:15 To: devel@... Cc: devel@... Subject: Re: [Zephyr-devel] Zephyr Sample Demo with nrf52840 Dongle
Dear All,
In reference to the NRF52840 Dongle Example, yesterday i send you the problem with the first step i.e. west build -b nrf52840_pca10059 zephyr/samples/basic/blinky
Now this step is going smoothly.. The second step ( nrfutil pkg generate --hw-version 52 --sd-req=0x00 \
--application build/zephyr/zephyr.hex \
--application-version 1 blinky.zip)
is giving the error message which is as follows: ~/zephyrproject/zephyr/samples/basic/blinky$ nrfutil pkg generate --hw-version 52 --sd-req=0x00 \
Traceback (most recent call last):
File "/home/muhammad/.local/bin/nrfutil", line 11, in <module>
sys.exit(cli())
File "/home/muhammad/.local/lib/python3.6/site-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File "/home/muhammad/.local/lib/python3.6/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/home/muhammad/.local/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/home/muhammad/.local/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/home/muhammad/.local/lib/python3.6/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/muhammad/.local/lib/python3.6/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/home/muhammad/.local/lib/python3.6/site-packages/nordicsemi/__main__.py", line 867, in generate
package.generate_package(zipfile_path)
File "/home/muhammad/.local/lib/python3.6/site-packages/nordicsemi/dfu/package.py", line 403, in generate_package
for key, firmware_data in self.firmwares_data.iteritems():
AttributeError: 'dict' object has no attribute 'iteritems'
Thank you for your help.
Regards
From: Muhammad Muh
Dear,
I am totally new in Zephyr. I am new in the field of IoT programming. I have gone through the tutorial of zephyr. Learned some things. But now i want to go through the Sample examples of Blink LED and Mesh Demo so that i can have a start off. I have tried to run the sample as per the instructions given in the tutorial but not successful. I will be grateful if you can help me in this regards. Waiting for the kind reply. Thank you in advance.
Regards Muhammad.
|
|
|
|
Re: Zephyr Sample Demo with nrf52840 Dongle
Lars Knudsen
Hi Muhammad, it seems like you are depending on python 3.6 - I don't have my env on the machine I'm using right now, but seem to remember you need python 2 (I might be wrong) br Lars
On Wed, Jul 24, 2019 at 2:19 PM Muhammad Muh <muhammad.muh83@...> wrote:
|
|
|
|
Re: Zephyr Sample Demo with nrf52840 Dongle
Muhammad Muh <muhammad.muh83@...>
Dear All,
In reference to the NRF52840 Dongle Example, yesterday i send you the problem with the first step i.e.
west build -b nrf52840_pca10059 zephyr/samples/basic/blinky
Now this step is going smoothly..
The second step (
nrfutil pkg generate --hw-version 52 --sd-req=0x00 \ --application build/zephyr/zephyr.hex \ --application-version 1 blinky.zip)is giving the error message which is as follows:
From: Muhammad Muh
Sent: Wednesday, July 24, 2019 9:52 AM To: devel@... <devel@...> Subject: Zephyr Sample Demo with nrf52840 Dongle Dear,
I am totally new in Zephyr. I am new in the field of IoT programming. I have gone through the tutorial of zephyr. Learned some things. But now i want to go through the Sample examples of Blink LED and Mesh Demo so that
i can have a start off. I have tried to run the sample as per the instructions given in the tutorial but not successful. I will be grateful if you can help me in this regards. Waiting for the kind reply. Thank you in advance.
Regards Muhammad.
|
|
|
|
Re: [EXT] [Zephyr-devel] Help flashing nxp MIMXRT1050-EVKB
Andrei Gansari
Hello Flavio,
toggle quoted messageShow quoted text
From what you describe, most probably you have an old version of SEGGER JLink on your host machine. I have the following version on my machine: SEGGER J-Link Commander V6.46c (Compiled Jun 3 2019 18:32:22) DLL version V6.46c, compiled Jun 3 2019 18:31:31 Please check your host's version of JLink (e.g. JLinkExe - Linux/ JLink Commander - Windows) There maybe other issues such as: - debugger FW (looks like you use a generic firmware, there is a board and hyperflash specific version of the firmware) - dip switches on board Regards, Andrei Gansari
-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On Behalf Of Flavio Ceolin via Lists.Zephyrproject.Org Sent: Tuesday, July 23, 2019 6:54 PM To: zephyr-devel@lists.zephyrproject.org Cc: devel@lists.zephyrproject.org Subject: [EXT] [Zephyr-devel] Help flashing nxp MIMXRT1050-EVKB Caution: EXT Email I'm trying to flash this board following our documentation with no success. I've being installed the OpenSDA_V2_1.bin firmware but when I try to flash I get the following error: J-Link connection not established yet but required for command. Connecting to J-Link via USB...O.K. Firmware: J-Link OpenSDA 2 compiled May 27 2019 11:01:03 Hardware version: V1.00 S/N: 621000000 VTref=3.300V Target connection not established yet but required for command. The selected device "MCIMXRT1052" is unknown to this version of the J-Link software. --- I've tried both, stable and beta J-Link tools. Someone have seen or know how to fix problem ? Regards, Flavio Ceolin
|
|
|
|
TSC meeting agenda for 24 Jul 2019
Carles Cufi
Hi all,
Here is the agenda for today's meeting: * Vincent Lacroix from Systerel presentation on the OPC UA protocol * TSC / Marketing Committee coordination https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#technical-steering-committee-tsc https://docs.google.com/document/d/12p8Q4USdExsP3a8lIdhyqG-4vxb44kisccZ9TvlxWBA/edit#heading=h.x36xe8bnwr9r Thanks, Carles
|
|
|
|
Re: Zephyr Sample Demo with nrf52840 Dongle
Lars Knudsen
Hi Muhammad, I have an example project that needs a few changes to be compatible with the latest master (was using 1.14-rc) - but maybe it can be used for inspiration: br Lars
On Wed, Jul 24, 2019 at 9:17 AM Serafin <serafin@...> wrote:
|
|
|
|
Re: Zephyr Sample Demo with nrf52840 Dongle
Serafin
Hi Muhammad
I doubt anyone here can give you a better general write up then the documentation. So you need to provide information about the specific problem.
Best regards Serafin
On 24/07/2019 03:52, Muhammad Muh
wrote:
|
|
|
|
how to make zephyr as a ble mesh provisioner?
rahul tiwari
Hello,
what are the steps required to make zephyr OS as a provisioner. I flashed the sample board example of mesh over nordic pca10040 , and i cant provision it from BlueZ meshctl Kindly provide me the way to provision it Regards Rahul
|
|
|
|
Zephyr Sample Demo with nrf52840 Dongle
Muhammad Muh <muhammad.muh83@...>
Dear,
I am totally new in Zephyr. I am new in the field of IoT programming. I have gone through the tutorial of zephyr. Learned some things. But now i want to go through the Sample examples of Blink LED and Mesh Demo so that
i can have a start off. I have tried to run the sample as per the instructions given in the tutorial but not successful. I will be grateful if you can help me in this regards. Waiting for the kind reply. Thank you in advance.
Regards Muhammad.
|
|
|
|
Help flashing nxp MIMXRT1050-EVKB
Flavio Ceolin
I'm trying to flash this board following our documentation with no
success. I've being installed the OpenSDA_V2_1.bin firmware but when I try to flash I get the following error: J-Link connection not established yet but required for command. Connecting to J-Link via USB...O.K. Firmware: J-Link OpenSDA 2 compiled May 27 2019 11:01:03 Hardware version: V1.00 S/N: 621000000 VTref=3.300V Target connection not established yet but required for command. The selected device "MCIMXRT1052" is unknown to this version of the J-Link software. --- I've tried both, stable and beta J-Link tools. Someone have seen or know how to fix problem ? Regards, Flavio Ceolin
|
|
|
|
Fw: [Zephyr-devel] Development in Zephyr
Muhammad Muh <muhammad.muh83@...>
Dear Mr Aldrich,
Hope you will be fine and in best of health. I have gone through the links which you have referred me. I found them very very useful. Thank you for your kind support. Now i have purchased
the NRF52840 Dongles. In reference to our previous discussion, it is requested to kindly help me through the examples of LED Blink and Mesh Demo. During LED Blink i am getting different sort of errors. Following are lines.
ZEPHYR_BASE=/home/muhammad/zephyrproject/zephyr (origin: configfile)
args: Namespace(board='nrf52840_pca10059', build_dir='path/to/build2/directory', cmake=False, command='build', force=False, help=None, source_dir=None, target=None, verbose=1, version=False, zephyr_base=None) remainder: [] source_dir: None cmake_opts: None source directory: /home/muhammad/zephyrproject/zephyr build directory: /home/muhammad/zephyrproject/zephyr/path/to/build2/directory BOARD: nrf52840_pca10059 CMake Error at CMakeLists.txt:13 (message): A user error has occured. cmake was invoked with '/home/muhammad/zephyrproject/zephyr' specified as the source directory, but it must be invoked with an application source directory, such as '/home/muhammad/zephyrproject/zephyr/samples/hello_world'. Debug variables: CMAKE_CACHEFILE_DIR: /home/muhammad/zephyrproject/zephyr/path/to/build2/directory CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.13) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! ERROR: command exited with status 1: /home/muhammad/.local/bin/cmake -B/home/muhammad/zephyrproject/zephyr/path/to/build2/directory -H/home/muhammad/zephyrproject/zephyr -GNinja -DBOARD=nrf52840_pca10059 Traceback (most recent call last): File "/home/muhammad/zephyrproject/.west/west/src/west/main.py", line 580, in main args.handler(args, unknown) File "/home/muhammad/zephyrproject/.west/west/src/west/main.py", line 332, in ext_command_handler command.run(*west_parser.parse_known_args(argv)) File "/home/muhammad/zephyrproject/.west/west/src/west/commands/command.py", line 90, in run self.do_run(args, unknown) File "/home/muhammad/zephyrproject/zephyr/scripts/west_commands/build.py", line 153, in do_run self._run_cmake(self.args.cmake_opts) File "/home/muhammad/zephyrproject/zephyr/scripts/west_commands/build.py", line 317, in _run_cmake cmake.run_cmake(final_cmake_args) File "/home/muhammad/zephyrproject/.west/west/src/west/cmake.py", line 35, in run_cmake subprocess.check_call(cmd, **kwargs) File "/usr/lib/python3.6/subprocess.py", line 311, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/home/muhammad/.local/bin/cmake', '-B/home/muhammad/zephyrproject/zephyr/path/to/build2/directory', '-H/home/muhammad/zephyrproject/zephyr', '-GNinja', '-DBOARD=nrf52840_pca10059']' returned non-zero exit status 1
Thank you for your help. I will be grateful if you can help me out in these sample demo.
Regards
Muhammad
From: Muhammad Muh
Sent: Tuesday, June 25, 2019 4:08 PM To: Thea Aldrich <aldrich.thea@...>; Thea Aldrich <taldrich@...> Cc: devel@... <devel@...> Subject: Re: [Zephyr-devel] Development in Zephyr Mr. Aldrich thank you for your email. I am really thank full to you.
a) Regarding "Slack Channel" i did not know about this before. Now i will definitely join it.
b) In reference to "Bluetooth Section of the Documentation Guide" i did not go through all these links. I will follow these to get more know how. I will get back to you after studying
these documents.
Thank you once again.
Regards Muhammad
From: Thea Aldrich <aldrich.thea@...>
Sent: Tuesday, June 25, 2019 4:13 AM To: Muhammad Muh; Thea Aldrich Cc: devel@... Subject: Re: [Zephyr-devel] Development in Zephyr Hello Muhammad,
Welcome to the Zephyr Project! We're so happy to hear you are exploring ZephyrOS and Bluetooth Mesh. I'm happy to help you through the process of getting started with your first application. Have you joined the
Slack channel? Its a great place to ask questions and get to know the community better. A number of our experts in Bluetooth Mesh are on daily. Everyone is always happy to help.
My favorite place to get started is the
Bluetooth section of the documentation guide. I have also personally found the Bluetooth Mesh Study
Guide incredibly useful. Its produced by the Bluetooth SIG and is a great resource for getting a deeper understanding of the ins and outs of the technology. You may also find
this presentations useful.
If those guides do not answer your questions or if you already went through the guides and still have questions, please feel free to reach out to me at any time. I am always happy to help where I can.
Best,
Thea Aldrich
Zephyr Project Developer Advocate
On Mon, Jun 24, 2019 at 8:04 AM Muhammad Muh <muhammad.muh83@...> wrote:
|
|
|
|
[RFC] Proposed development plan for Zephyr's POSIX subsystem
Paul Sokolovsky
Hello,
The POSIX subsystem in Zephyr catches attention of more and more users, as a means to streamline porting of the software to Zephyr (just take existing code and build it for Zephyr - what could be simpler!). The POSIX subsystem is under active development during last half-year to achieve this (currently still fairly distant) ideal. Recently, there was some questioning of where exactly the POSIX subsystem goes, and by which ways. https://github.com/zephyrproject-rtos/zephyr/issues/17706 was created to capture answers to these questions and unblock further progress of this important direction. I would like to invite all interested parties to read and discuss it. If there won't be timely feedback, there's a chance that very important patches, waiting in the queue for months, won't make it into Zephyr 2.0, further putting away Zephyr's adoption for real-world projects (most of which aren't writing software from scratch, but reusing existing components). Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
|
|
|
|
API meeting cancelled this week
Carles Cufi
Hi all,
Due to holidays and celebrations we have had to cancel this week's API meeting. Next week we will resume holding the meetings as usual. Thanks, Carles
|
|
|
|
Cancelled Event: Zephyr Project: APIs - Tuesday, 23 July 2019
#cal-cancelled
devel@lists.zephyrproject.org Calendar <devel@...>
Cancelled: Zephyr Project: APIs This event has been cancelled. When: Where: Organizer: Description: Live meeting minutes: https://docs.google.com/
|
|
|
|
New default BLE Link Layer
Carles Cufi
Hi all,
With the merge of PR #15781, the new "split" Link Layer is now the default for BLE-enabled applications. Extensive development and testing effort has gone into this feature, but there might be regressions that have slipped through the testing procedures. Please open issues on GitHub if you come across any issues when testing your applications with it. You can revert back to using the previous Link Layer by enabling the CONFIG_BT_LL_SW_LEGACY Kconfig option. https://github.com/zephyrproject-rtos/zephyr/pull/15781 Thank you to everybody involved in this feature for making it happen. New features that were not possible to implement with the old architecture will now slowly start coming to the new Link Layer. Regards, Carles
|
|
|
|
Re: One Questions about ZephyrOS
Jennifer M Williams
Welcome to Zephyr, @"Explorer! Thanks for the question – others can provide their feedback and suggestions, too. Can you elaborate on the middleware support you found was lacking? It might help to know more about your requirements.
Re: new to Zephyr - Have you had a chance to check out the Getting Started Guide and Application Developers Guide? There are also many Samples and Demos for a variety of supported boards.
Cheers!
From: devel@... <devel@...>
On Behalf Of "Explorer
Sent: Friday, July 19, 2019 6:34 PM To: devel <devel@...> Subject: [Zephyr-devel] One Questions about ZephyrOS
Hi,
I am MCU development guy and I am new to Zephyr OS, do not know if a good place to mail here, pls just ignore it if this mail is not proper to be here.
I want to know if Zephyr can have a good way to seperate Driver & Kernel and Application development in an product development lifetime? Linux is a good example as it support elf-loader and standard Driver & Kernel model.
My reason: High performance MCU, not MPU (Cortex M7 and 64-bit RISC-V based , STM32F7, NXP i.MX RT1052 ) , they are are becoming popular, so there are much more software development work should be done on these MCU, while there is little elegant open source RTOS with mature middleware to support such kind of high-performance MCU development. eCos and uCLinux are maybe good but these projects are nearly dead , the popolar uCOS or FreeRTOS are just too light-weight (lack of middlerware supported). If application development and low-level driver can be seperated and standarized, maybe there will be lots of middleware can port from Linux ecosystem and ZephyrOS can benifit from it.
Do not know if i am right, correct me if i am wrong~
------- B.R. RockC
|
|
|
|
One Questions about ZephyrOS
"Explorer
Hi, I am MCU development guy and I am new to Zephyr OS, do not know if a good place to mail here, pls just ignore it if this mail is not proper to be here. I want to know if Zephyr can have a good way to seperate Driver & Kernel and Application development in an product development lifetime? Linux is a good example as it support elf-loader and standard Driver & Kernel model. My reason: High performance MCU, not MPU (Cortex M7 and 64-bit RISC-V based , STM32F7, NXP i.MX RT1052 ) , they are are becoming popular, so there are much more software development work should be done on these MCU, while there is little elegant open source RTOS with mature middleware to support such kind of high-performance MCU development. eCos and uCLinux are maybe good but these projects are nearly dead , the popolar uCOS or FreeRTOS are just too light-weight (lack of middlerware supported). If application development and low-level driver can be seperated and standarized, maybe there will be lots of middleware can port from Linux ecosystem and ZephyrOS can benifit from it. Do not know if i am right, correct me if i am wrong~ ------- B.R. RockC
|
|
|
|
VB: Zephyr 2.0 Release - important information & dates
Glaropoulos, Ioannis
Hi Zephyr developers! Polite reminder that the merge window for the Zephyr 2.0 release will remain open for three weeks more, until Friday August 9th. Any new features or enhancements to be included in the Zephyr 2.0 release must be pushed to master by the feature freeze deadline. If you are working on such features, please, submit your pull-requests in good time, to have them properly reviewed, revised and merged before August 9.
Thanks!
Ioannis Glaropoulos
Från: Glaropoulos, Ioannis
Hi Zephyr developers,
The next major Zephyr release, 2.0, is scheduled for Friday, 30 August 2019.
We are now in the development phase for 2.0; merge window is open for all features until feature freeze, which is scheduled for Friday 9 August, 2019. This is in 6 weeks from today. Major features should, ideally, be up for review by mid-July 2019.
Any new features / enhancements to be included in the Zephyr 2.0 release must be pushed to master by the feature freeze deadline. If you are working on such features / enhancements, please, submit your pull-requests in good time, to have them properly reviewed, revised and merged before August 9.
After feature freeze only bug-fixes, documentation and stabilization-related updates may be merged; the merge window will remain closed until the release date.
More details can be found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
Roadmap: https://github.com/zephyrproject-rtos/zephyr/projects/9
Thanks in advance for all your contributions!
Ioannis Glaropoulos
|
|
|
|
Re: Name of new Driver API
Carles Cufi
Hi Tom,
Thanks for asking here, we can also have a quick vote in the API call next week if you can attend.
RTIO, with an rtio_ prefix being used in the code, sounds sensible to me, +1 on the name.
Regards,
Carles
From: devel@... <devel@...>
On Behalf Of Tom Burdick via Lists.Zephyrproject.Org
Sent: 09 July 2019 19:07 To: devel@... Cc: devel@... Subject: [Zephyr-devel] Name of new Driver API
Hi Zephyr Devs,
I've been working on an updated driver API that intends to encompass a wide array of devices including sensors and some signal output devices. Very similar in nature to what Linux provides in its IIO driver API. The intention is create a way of efficiently moving and processing streams of data in a DMA friendly way on small devices.
I started off with the name ZIO as an abbreviation of Zephyr IO, quickly realizing that Linux had a similar in purpose driver API already written for it. I thought this was a large enough conflict in naming to warrant renaming things.
I've since been using the prefix of RTIO, short for Real-Time IO, which I think very much relates to what I'm doing. I've already gotten some positive feedback from a fellow zephyr developer on the name but I think its important the wider community has their say.
I don't think the name sensor really helps to encompass what this API does in its entirety, or its goals. I do think something along the lines of IO is appropriate. Real-Time IO does better encompass what it does in my opinion.
I'd like the communities opinion on this name, and if you are not thrilled with it, one good name suggestion.
Any new suggested names should be short, there's an 80 character line limit after all and much that needs to go to non-prefix stuff.
I'm happy to go with what the community feels is a good name. But again, I do not think sensor/sensor2/etc would really do what this is justice. It would pigeon hole the work.
Thanks!
Tom
|
|
|
|
Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 18 July 2019
#cal-cancelled
devel@lists.zephyrproject.org Calendar <devel@...>
Cancelled: Zephyr Project: Dev Meeting This event has been cancelled. When: Where: Organizer: Description:
|
|
|
