Date   

Summer 2019 Zephyr Project Newsletter

Zephyr Project
 

Welcome to the Zephyr Project Newsletter! As the Zephyr community continues to grow and innovate we've added this update to the list of resources and tools available to our ecosystem to stay connected. In this edition, we are excited to bring you updates on what's in store for ZephyrOS this summer and fall, provide a glimpse into some of the work currently underway in the community and share ways you can get involved in the Zephyr Project. 

 

About the Zephyr Project

Zephyr Project Welcomes it's 500th Contributor!

Community is core to a successful open source project. In addition to improving and expanding the code base, a vibrant and diverse community brings new perspectives, energy and opportunity. Over the last year the Zephyr community has grown dramatically and the project is stronger because of these new voices. This month, the Zephyr Project is thrilled to welcome it's 500th contributor. On behalf of the entire community, we would like to welcome each and every one of the new contributors. 

If you are interested in joining the Zephyr Project as a member or contributor please reach out. We are here to help.
How to Contribute
Become a Member

The Zephyr Project Announces Major Technical Milestone with Release of Zephyr OS 1.14 LTS. 

Earlier this spring, Zephyr Project introduced the first long term support (LTS) release of Zephyr OS, Zephyr 1.14.0 LTS. This release is an important technical milestone for the community and is intended to be a more stable, certifiable option for product makers and developers. Major enhancements include:
  • Support for over 160 different board configurations spanning 8 architecture configurations. 
  • Enhancement of the native POSIX port by adding UART, USB, and display drivers. Based on this port, we added a simulated NRF52832 SoC which enables running full system, multi-node simulations, without the need of real hardware.
  • Application of MISRA-C code guideline on the kernel and core components of Zephyr. 
  • Addition of an experimental BLE split software Controller with Upper Link Layer and Lower Link Layer for supporting multiple BLE radio hardware architectures.
  • Introduction of the west tool for management of multiple repositories and enhanced support for flashing and debugging.
  • Support for the x86_64 architecture. It is currently implemented only for QEMU targets, supports arbitrary numbers of CPUs, and runs in SMP mode by default, our first platform to do so.
  • Added support for application user mode, application memory partitions, and hardware stack protection in ARMv8m
This release marks the culmination of one of the largest and most ambitious efforts undertaken by the Zephyr Project to date. This release would not have been possible without the hard work and skill of the 250 developers who contributed code over the last 6 months. Read more here.
Get Zephyr OS

Winners of Zephyr OS 1.14 LTS Bug Fixing Contest Announced

As part of the celebration of the ZephyrOS 1.14 LTS release the TSC hosted their first ever bug fixing contest. Sponsored by Zephyr Project member NXP, this contest awarded an i.MX RT1050 to eligible developers who helped close bugs and issues in this release. We are thrilled to announce the winners of the contest: Jukka Rissanen, Vikrant More, Aaron Tsui and Tavish Naruka. We thank you for your contributions to the Zephyr Project! Enjoy the boards and happy hacking!

Products Powered by ZephyrOS

The Zephyr Project is proud to promote the incredible products and services created by our community of product makers, innovators and entrepreneurs. If you would like to have your product featured in the Zephyr Quarterly newsletter please contact us.
 

The HiFive1 Rev B is Here

HiFive1 Rev B is an upgrade to SiFive's low-cost development board featuring the Freedom E310. It’s the best way to start prototyping and developing your RISC‑V applications. Order yours today.


Laird Connectivity Pinnacle 100

Laird Connectivity has a new multi-wireless modem that combines the advantages of low-power cellular LTE connectivity and Bluetooth 5 technology into an integrated solution. This unique combination allows new use cases employing low-cost, long-range Bluetooth sensors all attached to the next generation LTE network in simpler and less costly solution architecture.

 

hereO CORE

hereO Core is the world's first plug and play IoT platform developed from the ground up for companies looking to smarten up their consumer product offerings and mobile assets.

 

Ruuvi Node

Developed by Finnish open-source electronics specialist, Ruuvi Innovations, the Ruuvi Node is a highly robust, maintenance-free, 100 per cent open-source node solution that combines a Nordic Semiconductor nRF9160 System-in-Package (SiP) cellular IoT module and an ultra-low power Nordic nRF52840 multi-protocol Bluetooth System-on-Chip (SoC).

Phantom ELDA

Phantom's End-device Level Distributed Automation (ELDA) is a Bluetooth LE home automation system which allows wall switches to wirelessly control lights in mesh network. The system uses two devices employing Nordic’s nRF52832 SoC for mesh networking between wall switch and LED drivers. Learn more here.

Zephyr Project Face to Face Meeting Brings Together Community for Strategic Planning

With the successful release of ZephyrOS 1.14 LTS complete it is now time for the community to begin looking ahead to what's next for Zephyr Project. In addition to safety certifications, the Zephyr Project is currently working towards:

  • Improving our processes and transparency
  • Revamping our website and online presence
  • The release of Zephyr 2.0 and Zephyr 1.14.1
  • Enabling product makers and users through guides and training materials

Thank you to the team at Intel for hosting this incredible, intensive 3 day workshop. You can read the full recap of the event in this blog by Zephyr Project Board Chairperson Amy Occhialino (Intel).

A Message From Linux Foundation Strategic Programs Director Kate Stewart: Welcome New Zephyr Project Leadership

The Zephyr Project would like to extend a warm welcome to the following contributors who have taken leadership roles within the community.  
  • Maureen Helm (NXP) TSC Chairperson
  • Mark Merizan (Intel) Marketing Committee Chairperson
  • David Brown (Linaro) Security Architect
  • Flávio Ceolin (Intel) Security Chair
  • Amber Hibberd (Intel) Interim Safety Chair
We would like to thank Anas Nashif (Intel) for his service to the community as TSC Chairperson from 2016 - 2019, Andy Gross (Linaro) for his work as the Security Chairperson and Ebba Simpson (Linaro) for her leadership as the Chairperson of the Marketing Committee. Thank you! 

New Developer Guides and Resources

RISC-V Getting Started Guide

The RISC-V Getting Started Guide shows users how to get started developing for the free and open RISC-V ISA. The Guide focuses on running Zephyr and Linux – on popular RISC-V platforms with minimum effort. Learn more here.
 
The Bluetooth LE Developer Study Guide is the perfect way to learn about Bluetooth LE, GATT and GAP and Zephyr with hands-on experience. Download the Bluetooth LE Developer Study Guide today and get coding with Zephyr and Bluetooth! Learn more here.
 
Thank you to our friends at Fit IoT-Lab for sharing a fantastic guide with the community that shows users how to quickly setup a Zephyr development environment and how to compile a Zephyr firmware.
 
Antmicro has recently released Renode 1.7 and 1.7.1, one of the largest updates yet of the open source multi-node simulation framework that has been gaining popularity in both the RISC-V ecosystem and Zephyr Project.
 

The Zephyr Project Technical Newsletter

Back by popular demand, we are thrilled to share the latest changes and ongoing initiatives within the Zephyr repos in this monthly recap published by Marti Bolivar (Nordic Semiconductors). View the May and June updates.
 

Upcoming Events 

For the full listing of events, workshops and speaking engagements, please visit our event page.

Get Involved


Zephyr Project is a diverse and inclusive community dedicated to building a vendor neutral ecosystem around Zephyr OS. We welcome contributions of all types as we build a truly open source RTOS to meet the needs of developers and users inventing, building and connecting the Internet of Things. Join us.
Join the Slack Channel
Contribute to Zephyr OS
Contact Us
LinkedIn
Twitter
Website
YouTube
GitHub
Copyright © 2019 Zephyr Project, All rights reserved.

Our mailing address is:
1 Letterman Drive
Building D, Suite D4700
San Francisco, CA 94129
Phone/Fax: +1 415 723 9709
https://www.linuxfoundation.org/

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

 






This email was sent to devel@...
why did I get this?    unsubscribe from this list    update subscription preferences
Zephyr Project · 1702 Bauerle Ave · Austin, TX 78704-3304 · USA

Email Marketing Powered by Mailchimp


Re: Zephyr kernel compatibility with POSIX standard

Nashif, Anas
 

Gabrielle,

Right now Zephyr only supports a subset of the POSIX embedded profile (PSE52). It will depend on your application needs and the level of POSIX support your application depends on.

 

Anas

 

From: <devel@...> on behalf of Gabriele Morgante <gabriele.morgante@...>
Date: Wednesday, 10 July 2019 at 06:49
To: "devel@..." <devel@...>
Subject: [Zephyr-devel] Zephyr kernel compatibility with POSIX standard

 

Hi,

we are interested to know the compatibility degree of Zephyr kernel with the POSIX standard.

For instance, could we execute a C program POSIX compliant, written for an x86 linux kernel, on a Zephyr board as a Zephyr Application?

Thanks, regards!


Zephyr kernel compatibility with POSIX standard

Gabriele Morgante <gabriele.morgante@...>
 

Hi,

we are interested to know the compatibility degree of Zephyr kernel with the POSIX standard.

For instance, could we execute a C program POSIX compliant, written for an x86 linux kernel, on a Zephyr board as a Zephyr Application?

Thanks, regards!


Name of new Driver API

Tom Burdick
 

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



Upcoming Event: Zephyr Project: APIs - Tue, 07/09/2019 9:00am-10:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: APIs

When: Tuesday, 9 July 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

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

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878

Or iPhone one-tap :
    US: +16465588656,,177647878# or +16699006833,,177647878# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 177 647 878
    International numbers available: https://zoom.us/zoomconference?m=ioAR9GK1OE5LkN1ojt-heTCl7yPcJrhY


 Live meeting minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing


API meeting agenda for 9 Jul 2019

Maureen Helm
 

API meeting agenda for 9 Jul 2019:

  • Sensors (Maureen/Kevin/Tom)

 

Discussion is postponed on the following. Please review and submit feedback in GitHub before next week:

  • GPIO #15611 (Piotr M)
  • Driver-specific functions #17072 (Peter B)

 

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/projects/18

 


Upcoming Event: Zephyr Project: APIs - Tue, 07/02/2019 9:00am-10:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: APIs

When: Tuesday, 2 July 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

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

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878

Or iPhone one-tap :
    US: +16465588656,,177647878# or +16699006833,,177647878# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 177 647 878
    International numbers available: https://zoom.us/zoomconference?m=ioAR9GK1OE5LkN1ojt-heTCl7yPcJrhY


 Live meeting minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing


DTS deprecated defines

Kumar Gala
 

All,

We’ve made some recent changes to DTS generated defines to make this more consistent:

* _GPIO_ and _PWM_ defines are now _GPIOS_ and _PWMS_ (to match the property in dts)
* LED/SW defines used in samples are now DT_ALIAS_ prefixed

As such we are marking the old defines as deprecated. Its possible that some driver or sample got missed, so please let me know or submit a PR to fixup any such cases.

Here’s the PR that will mark the old style defines as deprecated:

https://github.com/zephyrproject-rtos/zephyr/pull/17254

Thanks

- k


Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 4 July 2019 #cal-cancelled

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

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, 4 July 2019
8:00am to 9:00am
(UTC-07:00) America/Los Angeles

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

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: nrf52 hw pwm 1 enabled and compile failed on sample code #builds #ninja

lairdjm
 

Hi Jeremy

The reason is that hardware is static and defined as part of the device tree, so for the nRF52840 this will be in the boards\arm\nrf52840_pca10056 directory and is nrf52840_pca10056.dts, if you open this file in a text editor and search for PWM you will find this code:

&pwm0 {

                status = "ok";

                ch0-pin = <13>;

                ch0-inverted;

};

There is no pwm1 section, so to utilise a second PWM channel you would need to create another section for it named &pwm1.

Thanks,
Jamie


nrf52 hw pwm 1 enabled and compile failed on sample code #builds #ninja

hotkernel@...
 

Hello guys,
I have got a compile error after enable the PWM channel 1 on nrf52_pca10040 board with sample code.
If I only use PWM0, there is no problem to pass the compile, but if I enable the PWM1, the issue happened.
I have searched all the source code, and did not find any difference between PWM0 and PWM1.
board: nrf52_pca10040
sample code: samples/bluetooth/peripheral_hr
ninja guiconfig:
 

the error info shows as below:
jeremy@jeremy:~/zephyr/source2/samples/bluetooth/peripheral_hr/build$ ninja
[0/1] Re-running CMake...
Zephyr version: 1.14.99
-- Selected BOARD nrf52_pca10040
-- Found west: /home/jeremy/.local/bin/west (found suitable version "0.5.7", minimum required is "0.5.6")
-- Loading /home/jeremy/zephyr/source2/boards/arm/nrf52_pca10040/nrf52_pca10040.dts as base
-- Overlaying /home/jeremy/zephyr/source2/dts/common/common.dts
Parsing Kconfig tree in /home/jeremy/zephyr/source2/Kconfig
Loaded configuration '/home/jeremy/zephyr/source2/samples/bluetooth/peripheral_hr/build/zephyr/.config'
No change to '/home/jeremy/zephyr/source2/samples/bluetooth/peripheral_hr/build/zephyr/.config'
-- Cache files will be written to: /home/jeremy/.cache/zephyr
-- Configuring done
-- Generating done
-- Build files have been written to: /home/jeremy/zephyr/source2/samples/bluetooth/peripheral_hr/build
[150/162] Building C object zephyr/drivers/pwm/CMakeFiles/drivers__pwm.dir/pwm_nrfx.c.obj
FAILED: zephyr/drivers/pwm/CMakeFiles/drivers__pwm.dir/pwm_nrfx.c.obj
ccache /home/jeremy/zephyr/sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DBUILD_VERSION=zephyr-v1.14.0-1479-gd3977996088a -DKERNEL -DNRF52832_XXAA -D_FORTIFY_SOURCE=2 -D__ZEPHYR_SUPERVISOR__ -D__ZEPHYR__=1 -I../../../../kernel/include -I../../../../arch/arm/include -I../../../../include -I../../../../include/drivers -Izephyr/include/generated -I../../../../soc/arm/nordic_nrf/nrf52 -I../../../../soc/arm/nordic_nrf/include -I../../../../lib/libc/minimal/include -I../../../../ext/lib/crypto/tinycrypt/include -I../../../../ext/hal/cmsis/Include -I../../../../ext/hal/nordic/nrfx -I../../../../ext/hal/nordic/nrfx/drivers/include -I../../../../ext/hal/nordic/nrfx/hal -I../../../../ext/hal/nordic/nrfx/mdk -I../../../../ext/hal/nordic/. -I../../../../subsys/bluetooth -isystem /home/jeremy/zephyr/sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/8.3.0/include -isystem /home/jeremy/zephyr/sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/8.3.0/include-fixed -Os -nostdinc -imacros /home/jeremy/zephyr/source2/samples/bluetooth/peripheral_hr/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mthumb -mcpu=cortex-m4 -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/home/jeremy/zephyr/source2=. -ffunction-sections -fdata-sections -mabi=aapcs -march=armv7e-m -std=c99 -MD -MT zephyr/drivers/pwm/CMakeFiles/drivers__pwm.dir/pwm_nrfx.c.obj -MF zephyr/drivers/pwm/CMakeFiles/drivers__pwm.dir/pwm_nrfx.c.obj.d -o zephyr/drivers/pwm/CMakeFiles/drivers__pwm.dir/pwm_nrfx.c.obj   -c /home/jeremy/zephyr/source2/drivers/pwm/pwm_nrfx.c
In file included from ../../../../include/pwm.h:32,
                 from /home/jeremy/zephyr/source2/drivers/pwm/pwm_nrfx.c:7:
/home/jeremy/zephyr/source2/drivers/pwm/pwm_nrfx.c:384:9: error: 'DT_NORDIC_NRF_PWM_PWM_1_LABEL' undeclared here (not in a function); did you mean 'DT_NORDIC_NRF_PWM_PWM_0_LABEL'?
         DT_NORDIC_NRF_PWM_PWM_##idx##_LABEL,        \
         ^~~~~~~~~~~~~~~~~~~~~~
../../../../include/device.h:107:11: note: in definition of macro 'DEVICE_AND_API_INIT'
   .name = drv_name, .init = (init_fn),     \
           ^~~~~~~~
/home/jeremy/zephyr/source2/drivers/pwm/pwm_nrfx.c:383:2: note: in expansion of macro 'DEVICE_DEFINE'
  DEVICE_DEFINE(pwm_nrfx_##idx,           \
  ^~~~~~~~~~~~~
/home/jeremy/zephyr/source2/drivers/pwm/pwm_nrfx.c:444:1: note: in expansion of macro 'PWM_NRFX_DEVICE'
 PWM_NRFX_DEVICE(1);
 ^~~~~~~~~~~~~~~
[154/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/poll.c.obj
ninja: build stopped: subcommand failed.
 
Thanks in advance!
Jeremy


API meeting agenda for 2 Jul 2019

Maureen Helm
 

API meeting agenda for 2 Jul 2019:

  • Counter (Krzysztof C)
  • GPIO (Piotr M)
  • Sensors (Maureen/Kevin/Tom)
  • Driver-specific functions (Peter B)

 

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/projects/18


Re: Is "CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC = 32768" correct for nRF52840?

Wang, Steven L
 

Hi Carles:

   Thanks for help on it.

-Steven

On 6/28/2019 9:50 PM, Cufi, Carles wrote:
Hi Steven,

Yes, it's correct but there's an inaccuracy problem that Andy has fixed in this PR:

https://github.com/zephyrproject-rtos/zephyr/pull/16782

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On
Behalf Of Wang, Steven L via Lists.Zephyrproject.Org
Sent: 28 June 2019 10:03
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] Is "CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC = 32768"
correct for nRF52840?

Hi:

   Does anyone know if "CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC = 32768" is
correct for nRF52840? I call test_kernel_systick() with reel_board and
it always fails. I tried to print "start_time" and "stop_time"

and found that "stop_time - start_time" was around "32670". However, it
is supposed to be a number bigger than "32768". So, I'm wondering if
"32768" is correct setting.


#define WAIT_TIME_US 1000000

void test_kernel_systick(void)
{
        u32_t start_time, stop_time, diff;

        start_time = osKernelSysTick();
        k_busy_wait(WAIT_TIME_US);
        stop_time = osKernelSysTick();

        diff = SYS_CLOCK_HW_CYCLES_TO_NS(stop_time -
                                         start_time) / NSEC_PER_USEC;

        zassert_true(diff >= WAIT_TIME_US, NULL); }

Thanks,

-Steven



Opened on mac st_nucleo_l476

cstyle
 

Anyone use openocd for Mac? thanks.

Show error message like this ,After install  opened 0.10.0 by homebrew for st_nucleo_l476rg.


logs :

azhuodeMacBook-Pro:zephyr azhuo$ west flash
ninja: no work to do.
Using runner: openocd
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
Warn : ignoring extra IDs in hl_vid_pid (maximum is 1 pair)
hla_vid_pid (vid pid)* 

ERROR: command exited with status 1: /usr/local/bin/openocd -f /Users/azhuo/zephyr14git/zephyrproject/zephyr/boards/arm/nucleo_l476rg/support/openocd.cfg -c init -c targets -c 'reset halt' -c 'flash write_image erase /Users/azhuo/zephyr14git/zephyrproject/zephyr/build/zephyr/zephyr.elf' -c 'reset halt' -c 'verify_image /Users/azhuo/zephyr14git/zephyrproject/zephyr/build/zephyr/zephyr.elf' -c 'reset run' -c shutdown
run as "west -v flash" for a stack trace
azhuodeMacBook-Pro:zephyr azhuo$ west -v flash
ZEPHYR_BASE=/Users/azhuo/zephyr14git/zephyrproject/zephyr (origin: env)
ninja: no work to do.
Using runner: openocd
/usr/local/bin/openocd -f /Users/azhuo/zephyr14git/zephyrproject/zephyr/boards/arm/nucleo_l476rg/support/openocd.cfg -c init -c targets -c 'reset halt' -c 'flash write_image erase /Users/azhuo/zephyr14git/zephyrproject/zephyr/build/zephyr/zephyr.elf' -c 'reset halt' -c 'verify_image /Users/azhuo/zephyr14git/zephyrproject/zephyr/build/zephyr/zephyr.elf' -c 'reset run' -c shutdown
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
Warn : ignoring extra IDs in hl_vid_pid (maximum is 1 pair)
hla_vid_pid (vid pid)* 

ERROR: command exited with status 1: /usr/local/bin/openocd -f /Users/azhuo/zephyr14git/zephyrproject/zephyr/boards/arm/nucleo_l476rg/support/openocd.cfg -c init -c targets -c 'reset halt' -c 'flash write_image erase /Users/azhuo/zephyr14git/zephyrproject/zephyr/build/zephyr/zephyr.elf' -c 'reset halt' -c 'verify_image /Users/azhuo/zephyr14git/zephyrproject/zephyr/build/zephyr/zephyr.elf' -c 'reset run' -c shutdown
Traceback (most recent call last):
  File "/Users/azhuo/zephyr14git/zephyrproject/.west/west/src/west/main.py", line 580, in main
    args.handler(args, unknown)
  File "/Users/azhuo/zephyr14git/zephyrproject/.west/west/src/west/main.py", line 332, in ext_command_handler
    command.run(*west_parser.parse_known_args(argv))
  File "/Users/azhuo/zephyr14git/zephyrproject/.west/west/src/west/commands/command.py", line 90, in run
    self.do_run(args, unknown)
  File "/Users/azhuo/zephyr14git/zephyrproject/zephyr/scripts/west_commands/flash.py", line 32, in do_run
    'ZEPHYR_BOARD_FLASH_RUNNER')
  File "/Users/azhuo/zephyr14git/zephyrproject/zephyr/scripts/west_commands/run_common.py", line 228, in do_run_common
    runner.run(command_name)
  File "/Users/azhuo/zephyr14git/zephyrproject/zephyr/scripts/west_commands/runners/core.py", line 407, in run
    self.do_run(command, **kwargs)
  File "/Users/azhuo/zephyr14git/zephyrproject/zephyr/scripts/west_commands/runners/openocd.py", line 84, in do_run
    self.do_flash(**kwargs)
  File "/Users/azhuo/zephyr14git/zephyrproject/zephyr/scripts/west_commands/runners/openocd.py", line 116, in do_flash
    self.check_call(cmd)
  File "/Users/azhuo/zephyr14git/zephyrproject/zephyr/scripts/west_commands/runners/core.py", line 466, in check_call
    subprocess.check_call(cmd)
  File "/usr/local/Cellar/python/3.7.1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 341, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/local/bin/openocd', '-f', '/Users/azhuo/zephyr14git/zephyrproject/zephyr/boards/arm/nucleo_l476rg/support/openocd.cfg', '-c', 'init', '-c', 'targets', '-c', 'reset halt', '-c', 'flash write_image erase /Users/azhuo/zephyr14git/zephyrproject/zephyr/build/zephyr/zephyr.elf', '-c', 'reset halt', '-c', 'verify_image /Users/azhuo/zephyr14git/zephyrproject/zephyr/build/zephyr/zephyr.elf', '-c', 'reset run', '-c', 'shutdown']' returned non-zero exit status 1.
azhuodeMacBook-Pro:zephyr azhuo$ 


Re: Is "CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC = 32768" correct for nRF52840?

Carles Cufi
 

Hi Steven,

Yes, it's correct but there's an inaccuracy problem that Andy has fixed in this PR:

https://github.com/zephyrproject-rtos/zephyr/pull/16782

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On
Behalf Of Wang, Steven L via Lists.Zephyrproject.Org
Sent: 28 June 2019 10:03
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] Is "CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC = 32768"
correct for nRF52840?

Hi:

   Does anyone know if "CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC = 32768" is
correct for nRF52840? I call test_kernel_systick() with reel_board and
it always fails. I tried to print "start_time" and "stop_time"

and found that "stop_time - start_time" was around "32670". However, it
is supposed to be a number bigger than "32768". So, I'm wondering if
"32768" is correct setting.


#define WAIT_TIME_US 1000000

void test_kernel_systick(void)
{
        u32_t start_time, stop_time, diff;

        start_time = osKernelSysTick();
        k_busy_wait(WAIT_TIME_US);
        stop_time = osKernelSysTick();

        diff = SYS_CLOCK_HW_CYCLES_TO_NS(stop_time -
                                         start_time) / NSEC_PER_USEC;

        zassert_true(diff >= WAIT_TIME_US, NULL); }

Thanks,

-Steven



Is "CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC = 32768" correct for nRF52840?

Wang, Steven L
 

Hi:

   Does anyone know if "CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC = 32768" is correct for nRF52840? I call test_kernel_systick() with reel_board and it always fails. I tried to print "start_time" and "stop_time"

and found that "stop_time - start_time" was around "32670". However, it is supposed to be a number bigger than "32768". So, I'm wondering if "32768" is correct setting.


#define WAIT_TIME_US 1000000

void test_kernel_systick(void)
{
        u32_t start_time, stop_time, diff;

        start_time = osKernelSysTick();
        k_busy_wait(WAIT_TIME_US);
        stop_time = osKernelSysTick();

        diff = SYS_CLOCK_HW_CYCLES_TO_NS(stop_time -
                                         start_time) / NSEC_PER_USEC;

        zassert_true(diff >= WAIT_TIME_US, NULL);
}

Thanks,

-Steven


Re: New sample for the microbit Line follower robot #samples #microbit #robot

Marc Herbert
 

On Linux the script zephyrproject/tools/ci-tools/scripts/check_compliance.py -c commit_range checks all that for you.

 

I also got the script running on Windows too once with a couple hacks.

 

Marc

 

From: <devel@...> on behalf of "Wang, Steven L" <steven.l.wang@...>
Date: Thursday, 27 June 2019 at 18:56
To: "devel@..." <devel@...>
Subject: Re: [Zephyr-devel] New sample for the microbit Line follower robot #samples #microbit #robot

 

Hi Maksim:

    I think it is good idea. It is helpful for anyone, who uses the same board for development.

    For your PR, there are several failures of auto checking, such as checkpath, Shippable, etc.  I think you have to fix them first.

-Steven

On 6/27/2019 9:32 PM, Maksim Masalski wrote:

Hello,
I made a new sample for the microbit board, which can be used to program a small robotic car to follow the line. What community thinks about my idea? Will it be useful for some of the developers?
By the way, I created a PR https://github.com/zephyrproject-rtos/zephyr/pull/17125

Best regards, Maksim


Re: New sample for the microbit Line follower robot #samples #microbit #robot

Wang, Steven L
 

Hi Maksim:

    I think it is good idea. It is helpful for anyone, who uses the same board for development.

    For your PR, there are several failures of auto checking, such as checkpath, Shippable, etc.  I think you have to fix them first.

-Steven

On 6/27/2019 9:32 PM, Maksim Masalski wrote:
Hello,
I made a new sample for the microbit board, which can be used to program a small robotic car to follow the line. What community thinks about my idea? Will it be useful for some of the developers?
By the way, I created a PR https://github.com/zephyrproject-rtos/zephyr/pull/17125

Best regards, Maksim


Zephyr 2.0 Release - important information & dates

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


Upcoming Event: Zephyr Project: Dev Meeting - Thu, 06/27/2019 8:00am-9:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 27 June 2019, 8:00am to 9:00am, (GMT-07: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

1821 - 1840 of 7903