Hello All,

I have one question regarding the ability of zephyr's hci_uart sample app.
I am using this application on nrf52840_pca10056 for scanning the ble beacons.

Scenario is i can see "hci0" interface UP RUNNING. and my custom application starts scanning beacons continuously (Here I'm using bluez's api).
Here, as i am in continuous scanning/receiving mode, I can see that when I'm using "hciconfig" command to show hci interface, there Rx bytes keep on increasing.

*******************************

NOTE: We will be using Webex for this meeting instead of zoom. The link is here:

https://meetingsamer4.webex.com/meetingsamer4/j.php?MTID=m43ef84def3356ff1725609f8000d3854

*******************************

Here’s the agenda topics for this week:

* Review PR’s tagged with dev-review:

* Zephyr sdk improvement [@tejlmand)
https://github.com/zephyrproject-rtos/zephyr/pull/24143

* usb: USB Audio class implementation [@carles]:
https://github.com/zephyrproject-rtos/zephyr/pull/21526

* Zephyr Bluetooth Authentication - ZEBRA [@carles]
https://github.com/zephyrproject-rtos/zephyr/issues/23465

* Any topics anyone else has.

- k

Reminder: Zephyr Project: APIs

When: Tuesday, 14 April 2020, 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

Two additional items:

- DAC API proposal
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/21805

- Auth API location
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/23465

Hi all,

Tomorrow's topics:

- Proposal to unify the "forever" timeout constant across subsystems that take milliseconds as an input parameter
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/24267

- RTC API proposal review after comments from the author
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/23526/

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

Hi,
    I found the following problem in hal nxp spi, and there is a corresponding solution, how should I submit these codes to hal_nxp, it seems that zephyr hal_nxp does not accpet the modiftion of the driver code.
Issue 1: LPSPI_MasterSetDelayTimes nt32_t realDelay is used, subsequent calculations may cause realDelay to overflow and produce incorrect delay data

Issue 2: LPSPI_MasterTransferComplete did not clear kLPSPI_TransferCompleteFlag, the other interrupts that followed may be treated as Transfer Complete, resulting in an abnormal reception status of zephyr spi

I am currently putting the modification method in the following PR, can someone please tell me the correct submission path. Thanks!
https://github.com/zephyrproject-rtos/hal_nxp/pull/36

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 9 April 2020, 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

Here’s the agenda topics for this week:

* Review PR’s tagged with dev-review

* Use of DTS Alias v Chosen for device selection:

We have a number of DT_ defines like:
DT_ADC_{0..n}_NAME
DT_RTC_{0..n}_NAME
DT_ENTROPY_NAME
DT_I2C_{0..n}_NAME
DT_FLASH_DEV_NAME

Do we replace these with chosen properties:
zephyr,adc-{0..n}
zephyr,rtc-{0..n}
zephyr,entropy
zephyr,i2c-{0..n}
zephyr,display /* new */

* zephyr,flash meaning and usage / DT_FLASH_DEV_NAME and flash controller.
- look at deprecating zephyr,flash (which was mostly a means to get CONFIG_FLASH_BASE_ADDR/SIZE vals). Replace with zephyr,flash-ctrl which would get us DT_FLASH_DEV_NAME.

* DT SAM Atmel Pinmux / NXP pinmux
https://github.com/zephyrproject-rtos/zephyr/pull/24164
https://github.com/zephyrproject-rtos/zephyr/pull/20398/files

* Any topics anyone else has

- k

Hello,

On Mon, 6 Apr 2020 21:44:27 +0300
"Paul Sokolovsky via lists.zephyrproject.org"
<paul.sokolovsky=linaro.org@lists.zephyrproject.org> wrote:

[]

If there is time, I'd like to share some progress on setting up CI
for network testing with real hardware, on which I've been working
last time.

I appreciate being able to present my work quickly and the discussion
of testing matters which followed. As it was just a quick spoken
presentation, I'd like to share a few links showing more details, with
the idea to keep wider community in loop of testing efforts around
Zephyr.

So, in this work Linaro LITE team uses the LAVA system (Linaro
Automation and Validation Architecture), which is an open source
project at https://www.lavasoftware.org/ (we run a particular
deployment at https://lite.validation.linaro.org/).

How it works is that we build Zephyr tests/samples in Jenkins (using
the standard Zephyr "sanitycheck" tool), then submit binaries to LAVA,
accompanied by a "test job definition", which is a YAML file like
https://lite.validation.linaro.org/scheduler/job/960800/multinode_definition#defline1 .

The job is then being run, with log of interaction recorded and
analyzed for success/failure. In this case it's a networking test which
involves 2 "nodes": a DUT (device under test) per se (FRDM-K64F board):
https://lite.validation.linaro.org/scheduler/job/960800.0 and a docker
container representing "a host":
https://lite.validation.linaro.org/scheduler/job/960800.1#L56 . Here,
the actual test interaction happens on the host, which starts with
easy-pinging a device, then pings more with full Ethernet frames, then
does a "poorman's flood ping" of pinging 1000 times with full packets
and 10ms interval. All these actions are encoded in the YAML definition
and are easily reconfigurable.

LAVA checks that individual actions outcome satisfies success criteria
and records overall results, e.g.
https://lite.validation.linaro.org/results/960801/0_ping .

The biggest value of such a system would come from early notifications
of failures, and ability to compare results over time. The best ways to
achieve that is so far under investigation (the whole work is largely a
prototype at this stage).

As discussed yesterday, we all by now should be aware that "Zephyr
testing" bastion is being stormed by multiple stakeholders in different
ways, and I just wanted to share Linaro's approach and progress with
wider community. While the primary drivers for this works are
requirements of our members interested in Zephyr, who already adopted
the LAVA system, the work itself is open-source, results are public, and
hopefully useful for a wider Zephyr community. (And different teams
working on testing definitely should reuse results of each other's work,
and further the best practices for making Zephyr more testable and
quality-assured).


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

Hi Narendar,

On Tue, Apr 7, 2020 at 9:26 AM Narendar Malepu
<narendarm@semiconsoul.com> wrote:

Previously worked on zephyr branch(2.1.0) but now i want to move to master branch(2.2.99).
When I trying to compile application getting below warning for all gpio functions
warning: 'gpio_pin_write' is deprecated [-Wdeprecated-declarations]

I recently encountered the same issue. It was a relatively painless
fix (thanks btw to the Zephyr devs who made the transition so easy).

Write:
gpio_pin_write(dev, pin, val) => gpio_pin_set(dev, pin, val)

Read:
u32_t state;
gpio_pin_read(dev, pin, &state) => state = gpio_pin_get(dev, pin)

Configure:
gpio_pin_configure(dev, pin, GPIO_DIR_OUT) => gpio_pin_configure(dev,
pin, GPIO_OUTPUT)

Cheers,

C

Hi,

Previously worked on zephyr branch(2.1.0) but now i want to move to master branch(2.2.99).
When I trying to compile application getting below warning for all gpio functions
warning: 'gpio_pin_write' is deprecated [-Wdeprecated-declarations]


Thanks,
Narendhar

Hi all,

Due to several people being away and needing a bit more time to discuss some of the items offline I am cancelling this week's API meeting.
Next week the meeting will take place as usual.

Thanks,

Carles

Cancelled: Zephyr Project: APIs

This event has been cancelled.

When:
Tuesday, 7 April 2020
9:00am to 10:00am
(UTC-07:00) America/Los Angeles

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

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