Date   

Updated Event: Zephyr Project: APIs #cal-invite

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

Zephyr Project: APIs

When:
Tuesday, 26 May 2020
4:00pm to 5:00pm
(UTC+00:00) UTC
Repeats: Weekly on Tuesday

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:

Meeting decisions/discussions in their respective PRs, tracked here: https://github.com/zephyrproject-rtos/zephyr/projects/18


________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Zephyr 2.3.0-rc2 tagged

Carles Cufi
 

Hi all,

The second release candidate for Zephyr 2.3.0 has now been tagged (v2.3.0-rc2).

The current issue counts are:

- 1 high-priority bug
- 16 medium-priority bugs

The high-priority bug (#23364) has a PR (#25954), but a waiver to release without a fix for this particular issue has been requested, due to the invasiveness of the Pull Request and the risk of merging it this late in the release cycle. A note would be added to the release notes and a subsequent 2.3.1 would be released to address this issue.

During the days left until the release, I would encourage everybody to test thoroughly and file any issues found so that they can be fixed as quickly as possible. Additionally, there are still sections in the release notes that need filling, those can be tracked here:
https://github.com/zephyrproject-rtos/zephyr/issues/25869

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

More details about Zephyr releases can found on the pages below:
https://docs.zephyrproject.org/latest/development_process/release_process.html
https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

The final release remains scheduled for June 5th.

Thank you to everybody who contributed to this release so far!

Carles


Running LWM2M client on nucleo_wb55rg

Brenton Chetty <brent7984@...>
 

Hi, I am new to Zephyr.
I managed to get the LWM2M client working using qemu.
How do I get lwm2m working on the nucleo_wb55rg?
On RIOT OS, I had to make use of a border router and tap interface to get the board communicating with the leshan server on my pc.

With thanks
Brenton


Updated Event: Zephyr Project: APIs #cal-invite

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

Zephyr Project: APIs

When:
Tuesday, 26 May 2020
4:00pm to 5:00pm
(UTC+00:00) UTC
Repeats: Weekly on Tuesday

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:


________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Upcoming Event: Zephyr Project: APIs - Tue, 06/02/2020 4:00pm-5:00pm, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: APIs

When: Tuesday, 2 June 2020, 4:00pm to 5:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join Microsoft Teams Meeting:
https://teams.microsoft.com/l/meetup-join/19%3ameeting_YzYzZTAzNGItOWFiMS00MDBkLTkyYmMtNzljZjkwNDVlMThm%40thread.v2/0?context=%7b%22Tid%22%3a%22686ea1d3-bc2b-4c6f-a92c-d99c5c301635%22%2c%22Oid%22%3a%2262b63b80-05d3-4465-b5a0-f04e4e156f10%22%7d

+1 213-437-3346 United States, Los Angeles (Toll)

Conference ID: 262 362 129#

Local numbers: 
https://dialin.teams.microsoft.com/488d1b50-0dd2-4ca1-aee4-92bb50a48081?id=262362129


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


Re: [Zephyr-users] Support for Atmel SAMG55

Kumar Gala
 

On Jun 1, 2020, at 8:25 AM, Michael Hope <michaelh@...> wrote:

Hi Adam. I just so happen to be adding support for the Adafruit
ItsyBitsy M4 board ATM. It's SAMD51 based which seems to be basically
the same as the SAMG55.

I've checked the UART, GPIO, SPI, and watchdog drivers so far. I'm
adding a PWM and QSPI driver, and will check the USB driver.

You'll need to create your own board definition and to create the
device tree files.

-- Michael
Just an FYI, working on moving pinmux for SAM0 over to DTS like I did for atmel SAM.

Also, we’re under some discussions on QSPI so good to know that you are looking at support for that as well on SAM0.

- k


API meeting: agenda

Carles Cufi
 

Hi all,

*************************************************
We will be using Teams instead of Zoom:
https://teams.microsoft.com/l/meetup-join/19%3ameeting_YzYzZTAzNGItOWFiMS00MDBkLTkyYmMtNzljZjkwNDVlMThm%40thread.v2/0?context=%7b%22Tid%22%3a%22686ea1d3-bc2b-4c6f-a92c-d99c5c301635%22%2c%22Oid%22%3a%2262b63b80-05d3-4465-b5a0-f04e4e156f10%22%7d
*************************************************

Today's topics:

- QSPI flash drivers:
- Should we revisit the common QSPI API? https://github.com/zephyrproject-rtos/zephyr/pull/20069
- Should it be part of the current SPI API? https://github.com/zephyrproject-rtos/zephyr/issues/17902
- If not, should we try to unify the common functionality in the multiple QSPI flash drivers?
- https://github.com/zephyrproject-rtos/zephyr/pull/25806
- https://github.com/zephyrproject-rtos/zephyr/pull/25669

- SPI JEDEC runtime support
- PR https://github.com/zephyrproject-rtos/zephyr/pull/23658

- RTC API follow-up (if the relevant people are present and there is material for discussion)
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/23526

Pending additional investigation:
- Documenting API behavior in Doxygen:
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/18970
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/21061

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


Re: [Zephyr-users] Support for Atmel SAMG55

Michael Hope
 

Yip, looks like I jumped the gun. Sorry about that!

On Mon, 1 Jun 2020 at 18:10, Adam Podogrocki <a.podogrocki@...> wrote:

Hi Michael,

I'm afraid it won't be as easy as using definition for SAMD51. I've compared memory mapping. It is enough to see that Internal Flash has different address, there is Internal ROM in G55. G55 has a single AHB-APB Brigde, wheres D51 has 4 Bridges. In D51 there are Serial Communication Interfaces (SERCOM) which can be configured in I2C, SPI, or USART mode. In G55 similar role is played by FLEXCOM, but memory addresses are different.

In short words it looks like G55 needs its own HAL files.

BR,
Adam

On Mon, 1 Jun 2020 at 15:25, Michael Hope <michaelh@...> wrote:

Hi Adam. I just so happen to be adding support for the Adafruit
ItsyBitsy M4 board ATM. It's SAMD51 based which seems to be basically
the same as the SAMG55.

I've checked the UART, GPIO, SPI, and watchdog drivers so far. I'm
adding a PWM and QSPI driver, and will check the USB driver.

You'll need to create your own board definition and to create the
device tree files.

-- Michael

On Mon, 1 Jun 2020 at 14:32, Adam Podogrocki <a.podogrocki@...> wrote:

Hi,

are there any activities ongoing to add support for SAMG55 MCU to Zephyr?

Regards,
Adam


Re: [Zephyr-users] Support for Atmel SAMG55

Adam Podogrocki
 

Hi Michael,

I'm afraid it won't be as easy as using definition for SAMD51. I've compared memory mapping. It is enough to see that Internal Flash has different address, there is Internal ROM in G55. G55 has a single AHB-APB Brigde, wheres D51 has 4 Bridges. In D51 there are Serial Communication Interfaces (SERCOM) which can be configured in I2C, SPI, or USART mode. In G55 similar role is played by FLEXCOM, but memory addresses are different.

In short words it looks like G55 needs its own HAL files.

BR,
Adam

On Mon, 1 Jun 2020 at 15:25, Michael Hope <michaelh@...> wrote:
Hi Adam.  I just so happen to be adding support for the Adafruit
ItsyBitsy M4 board ATM.  It's SAMD51 based which seems to be basically
the same as the SAMG55.

I've checked the UART, GPIO, SPI, and watchdog drivers so far.  I'm
adding a PWM and QSPI driver, and will check the USB driver.

You'll need to create your own board definition and to create the
device tree files.

-- Michael

On Mon, 1 Jun 2020 at 14:32, Adam Podogrocki <a.podogrocki@...> wrote:
>
> Hi,
>
> are there any activities ongoing to add support for SAMG55 MCU to Zephyr?
>
> Regards,
> Adam


Re: [Zephyr-users] Support for Atmel SAMG55

Michael Hope
 

Hi Adam. I just so happen to be adding support for the Adafruit
ItsyBitsy M4 board ATM. It's SAMD51 based which seems to be basically
the same as the SAMG55.

I've checked the UART, GPIO, SPI, and watchdog drivers so far. I'm
adding a PWM and QSPI driver, and will check the USB driver.

You'll need to create your own board definition and to create the
device tree files.

-- Michael

On Mon, 1 Jun 2020 at 14:32, Adam Podogrocki <a.podogrocki@...> wrote:

Hi,

are there any activities ongoing to add support for SAMG55 MCU to Zephyr?

Regards,
Adam


Support for Atmel SAMG55

Adam Podogrocki
 

Hi,

are there any activities ongoing to add support for SAMG55 MCU to Zephyr?

Regards,
Adam 


Zephyr 2.2.1 released

Johan Hedberg
 

Hi,

We are excited to announce the release of Zephyr 2.2.1, the first maintenance release of Zephyr 2.2.

This is primarily a bug fix release, concentrating on security vulnerabilities and issues affecting Bluetooth qualification.

The following security vulnerabilities (CVEs) have been addressed:

- CVE-2020-10028
- CVE-2020-10060
- CVE-2020-10063
- CVE-2020-10066

More details on these can be found in https://docs.zephyrproject.org/latest/security/vulnerabilities.html

A list of all issues fixed or addressed can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.2.1

Thank you to everyone who contributed to this release!

Johan


Upcoming Event: Zephyr Project: Dev Meeting - Thu, 05/28/2020 3:00pm-4:00pm, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 28 May 2020, 3:00pm to 4:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join Microsoft Teams Meeting: https://teams.microsoft.com/l/meetup-join/19%3ameeting_M2Q2ZDk4OWItMWE2MS00MTExLTkyYTQtNmUwOTA4MzgwOGYw%40thread.v2/0?context=%7b%22Tid%22%3a%22686ea1d3-bc2b-4c6f-a92c-d99c5c301635%22%2c%22Oid%22%3a%2262b63b80-05d3-4465-b5a0-f04e4e156f10%22%7d

+1 213-437-3346 United States, Los Angeles (Toll)
Conference ID: 750 623 026#


Local numbers: 
https://dialin.teams.microsoft.com/488d1b50-0dd2-4ca1-aee4-92bb50a48081?id=750623026


Re: Zephyr Toolchain Working Group Meeting – 28 May 2020

Rasmussen, Torsten
 

Today’s meeting minutes:

https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/

Notes/Minutes

Status updates

  • Metaware Debugger support: PR available here:
    https://github.com/zephyrproject-rtos/zephyr/pull/#24806
  • IAR: Nothing new
  • Torsten: Toolchain abstraction: Issue:#16031, Draft PR: https://github.com/zephyrproject-rtos/zephyr/pull/24851
    Nothing new, hopefully the release of 2.3 will free up some time.
    Following where commented regarding #24851.
    • Promising direction
    • Needs documentation, especially on the properties and what they are used for.
    • Not all toolchains support multiple `imacros` flags,
      Consider to have a possibility for simple concatenation of all headers into a single.

Best regards

 

Torsten T. Rasmussen

 

 

From: Rasmussen, Torsten
Sent: 28 May, 2020 14:14
To: devel@...
Subject: Zephyr Toolchain Working Group Meeting – 28 May 2020

 

Probably not much has happened since last meeting, due to 2.3 release in the making, but letøs get an update on statuses.


Agenda

  • Updates:
  • Short term goals, way forward
    • Dedicated toolchain test cases.
    • Label PR for automatic execution of CI Toolchain test cases

 

 

Feel free to send a mail, if you would like additional topics to be discussed.

 

Best regards

 

Torsten T. Rasmussen           

 

Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________

 

Join Microsoft Teams Meeting

+1 213-437-3346   United States, Los Angeles (Toll)

Conference ID: 570 955 823#

Local numbers | Reset PIN | Learn more about Teams | Meeting options

________________________________________________________________________________

 

 


Zephyr Toolchain Working Group - Thu, 05/28/2020 #cal-notice

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

Zephyr Toolchain Working Group

When:
Thursday, 28 May 2020
2:00pm to 3:00pm
(GMT+00:00) UTC

Where:
Microsoft Teams Meeting

Description:
Topic:  Zephyr Toolchain Working Group

Time: Mar 19, 2020 07:00 AM Pacific Time (US and Canada)

        Every 2 weeks on Thu, until Jul 23, 2020, 10 occurrence(s)

        Mar 19, 2020 07:00 AM

        Apr 2, 2020 07:00 AM

        Apr 16, 2020 07:00 AM

        Apr 30, 2020 07:00 AM

        May 14, 2020 07:00 AM

        May 28, 2020 07:00 AM

        Jun 11, 2020 07:00 AM

        Jun 25, 2020 07:00 AM

        Jul 9, 2020 07:00 AM

        Jul 23, 2020 07:00 AM

Join Microsoft Teams Meeting: https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZGRjNzNjMjEtOWJmMi00ODUxLWE2MjEtODM0M2FiMzQxMjE5%40thread.v2/0?context=%7b%22Tid%22%3a%22686ea1d3-bc2b-4c6f-a92c-d99c5c301635%22%2c%22Oid%22%3a%2262b63b80-05d3-4465-b5a0-f04e4e156f10%22%7d

+1 213-437-3346 United States, Los Angeles (Toll)

Conference ID: 570 955 823#

Local numbers: 
https://dialin.teams.microsoft.com/488d1b50-0dd2-4ca1-aee4-92bb50a48081?id=570955823

 


Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r


Upcoming Event: Zephyr Toolchain Working Group - Thu, 05/28/2020 2:00pm-3:00pm #cal-reminder

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

Reminder: Zephyr Toolchain Working Group

When: Thursday, 28 May 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

View Event

Organizer: Maureen Helm

Description: Topic:  Zephyr Toolchain Working Group

Time: Mar 19, 2020 07:00 AM Pacific Time (US and Canada)

        Every 2 weeks on Thu, until Jul 23, 2020, 10 occurrence(s)

        Mar 19, 2020 07:00 AM

        Apr 2, 2020 07:00 AM

        Apr 16, 2020 07:00 AM

        Apr 30, 2020 07:00 AM

        May 14, 2020 07:00 AM

        May 28, 2020 07:00 AM

        Jun 11, 2020 07:00 AM

        Jun 25, 2020 07:00 AM

        Jul 9, 2020 07:00 AM

        Jul 23, 2020 07:00 AM

Join Microsoft Teams Meeting: https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZGRjNzNjMjEtOWJmMi00ODUxLWE2MjEtODM0M2FiMzQxMjE5%40thread.v2/0?context=%7b%22Tid%22%3a%22686ea1d3-bc2b-4c6f-a92c-d99c5c301635%22%2c%22Oid%22%3a%2262b63b80-05d3-4465-b5a0-f04e4e156f10%22%7d

+1 213-437-3346 United States, Los Angeles (Toll)

Conference ID: 570 955 823#

Local numbers: 
https://dialin.teams.microsoft.com/488d1b50-0dd2-4ca1-aee4-92bb50a48081?id=570955823

 


Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r


Zephyr Toolchain Working Group Meeting – 28 May 2020

Rasmussen, Torsten
 

Probably not much has happened since last meeting, due to 2.3 release in the making, but letøs get an update on statuses.


Agenda

  • Updates:
  • Short term goals, way forward
    • Dedicated toolchain test cases.
    • Label PR for automatic execution of CI Toolchain test cases

 

 

Feel free to send a mail, if you would like additional topics to be discussed.

 

Best regards

 

Torsten T. Rasmussen           

 

Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________

 

Join Microsoft Teams Meeting

+1 213-437-3346   United States, Los Angeles (Toll)

Conference ID: 570 955 823#

Local numbers | Reset PIN | Learn more about Teams | Meeting options

________________________________________________________________________________

 

 


Re: Mesh Example

Carles Cufi
 

Hi Muhammad,

 

I have just copied Trond and Johan who might be able to help you with the provisioning issue.

 

Carles

 

From: Muhammad Muh <muhammad.muh83@...>
Sent: 27 May 2020 04:46
To: devel@...; Cufi, Carles <Carles.Cufi@...>
Subject: Mesh Example

 

Dear Respectable Group Members,

 

Good Morning,

 

I hope you all will be doing well in this COVID 19 situation.

 

Regarding Zephyr, I am facing a problem in running the nrf mesh example. I will be grateful if you can help me in this regard.

 

Example: /home/muhammad/zephyrproject/zephyr/samples/boards/nrf/mesh/onoff-app.

 

During Provisioning I am getting the following error please guide me. I will be grateful.

 

[meshctl]# discover-unprovisioned on

SetDiscoveryFilter success

Discovery started

Adapter property changed

[CHG] Controller CC:B0:DA:AA:73:AC Discovering: yes

Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)

Device UUID: c98f1f844cd300000000000000000000

OOB: 0000

[meshctl]# provision c98f1f844cd300000000000000000000

Trying to connect Device D3:4C:84:1F:8F:C9 Zephyr

Adapter property changed

[CHG] Controller CC:B0:DA:AA:73:AC Discovering: no

Failed to connect: org.bluez.Error.Failed

[meshctl]# provision c98f1f844cd300000000000000000000

Could not find device proxy

[meshctl]# discover-unprovisioned on

SetDiscoveryFilter success

Discovery started

Adapter property changed

[CHG] Controller CC:B0:DA:AA:73:AC Discovering: yes

Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)

Device UUID: c98f1f844cd300000000000000000000

OOB: 0000

[NEW] Device D3:4C:84:1F:8F:C9 Zephyr

[meshctl]# provision c98f1f844cd300000000000000000000

Trying to connect Device D3:4C:84:1F:8F:C9 Zephyr

Adapter property changed

[CHG] Controller CC:B0:DA:AA:73:AC Discovering: no

Connection successful

Services resolved yes

Found matching char: path /org/bluez/hci0/dev_D3_4C_84_1F_8F_C9/service0010/char0011, uuid 00002adb-0000-1000-8000-00805f9b34fb

Found matching char: path /org/bluez/hci0/dev_D3_4C_84_1F_8F_C9/service0010/char0013, uuid 00002adc-0000-1000-8000-00805f9b34fb

Start notification on /org/bluez/hci0/dev_D3_4C_84_1F_8F_C9/service0010/char0013

Characteristic property changed /org/bluez/hci0/dev_D3_4C_84_1F_8F_C9/service0010/char0013

AcquireNotify success: fd 7 MTU 69

Notify for Mesh Provisioning Out Data started

Open-Node: 0x55af8f71fef0

Open-Prov: 0x55af8f71eb60

Open-Prov: proxy 0x55af8f7228a0

Initiated provisioning

Characteristic property changed /org/bluez/hci0/dev_D3_4C_84_1F_8F_C9/service0010/char0011

AcquireWrite success: fd 8 MTU 69

GATT-TX: 03 00 10

GATT-RX: 03 01 04 00 01 00 00 06 00 18 00 00 00

Got provisioning data (12 bytes)

01 04 00 01 00 00 06 00 18 00 00 00

GATT-TX: 03 02 00 00 02 04 06

GATT-TX: 03 03 62 b6 6f 0d 10 8e 62 d9 0b b9 5e c5 68 fe

GATT-TX: dd cd 0f ee 2c d1 c9 87 b7 76 9f 51 0d d5 fd 09

GATT-TX: e7 bc e4 9a a3 96 e8 36 f6 1e 53 72 54 78 f1 d2

GATT-TX: 14 fd 88 86 b2 bb ec 05 3f 38 df b0 09 f5 57 47

GATT-TX: e1 c5

[Zephyr]# menu config

Menu config:

Available commands:

-------------------

target <unicast>                                  Set target node to configure

composition-get [page_num]                        Get composition data

netkey-add <net_idx>                              Add network key

netkey-del <net_idx>                              Delete network key

appkey-add <app_idx>                              Add application key

appkey-del <app_idx>                              Delete application key

bind <ele_idx> <app_idx> <mod_id> [cid]           Bind app key to a model

mod-appidx-get <ele_addr> <model id>              Get model app_idx

ttl-set <ttl>                                     Set default TTL

ttl-get                                           Get default TTL

pub-set <ele_addr> <pub_addr> <app_idx> <per (step|res)> <re-xmt (cnt|per)> <mod id> [cid]

 Set publication

pub-get <ele_addr> <model>                        Get publication

proxy-set <proxy>                                 Set proxy state

proxy-get                                         Get proxy state

ident-set <net_idx> <state>                       Set node identity state

ident-get <net_idx>                               Get node identity state

beacon-set <state>                                Set node identity state

beacon-get                                        Get node beacon state

relay-set <relay> <rexmt count> <rexmt steps>     Set relay

relay-get                                         Get relay

hb-pub-set <pub_addr> <count> <period> <ttl> <features> <net_idx> Set heartbeat publish

hb-pub-get                                        Get heartbeat publish

hb-sub-set <src_addr> <dst_addr> <period>         Set heartbeat subscribe

hb-sub-get                                        Get heartbeat subscribe

sub-add <ele_addr> <sub_addr> <model id>          Add subscription

sub-get <ele_addr> <model id>                     Get subscription

node-reset                                        Reset a node and remove it from network

back                                              Return to main menu

version                                           Display version

quit                                              Quit program

exit                                              Quit program

help                                              Display help about this program

export                                            Print environment variables

[Zephyr]#    target 0100

Configuring node 0100

[config: Target = 0100]#    appkey-add 1

Node 0100

 not found[config: Target = 0100]#

 

Regards

 

 

 


Switching to utilize C99 types in Zephyr 2.4

Kumar Gala
 

All,

Wanted to raise that there is an GH Issue for discussion on switching to C99 integer types and deprecating the zephyr types defined in include/zephyr/types.h

The issue is:

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

PR is:

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

Please comment on the issue if there are concerns on this change as it will be discussed amongst the Zephyr TSC. The idea is approved that we’d make this change in between the 2.3 release being finalized and the 2.4 merge window being opened.

thanks

- k


Dev-Review Meeting Agenda May 27

Kumar Gala
 

Here’s the agenda topics for this week:

* Review PR/issues’s tagged with dev-review:

- subsys: power: initialize states as disabled
https://github.com/zephyrproject-rtos/zephyr/pull/21118

- QSPI Flash support:
(Related to support for QSPI on i.mx-RT and remembering what we decide in API meeting as well as question if one can utilize spi-nor.c??)
https://github.com/zephyrproject-rtos/zephyr/pull/25669

* Any 2.3 issues that need discussion

* Any 2.4 topics / initial plans of activity.
- C99 types / what to do with {u}int64_t
https://github.com/zephyrproject-rtos/zephyr/pull/25679

* Any topics anyone else has.

- k