Re: Linkage Zephyr V1.13 versus V2.X
frv
Hi all,
Sorry replied the solution to myself and not to the group, but solution is to set the option "CONFIG_BT_GATT_DYNAMIC_DB=y" in the application prj.conf file, otherwise it is no longer possible to call the function bt_gatt_service_register when creating a GATT service (dynamically...). Best regards, Frank
|
|||||||||
|
|||||||||
Re: Linkage Zephyr V1.13 versus V2.X
Hi Lawrence,
Correct, but this one was quite easy to find as the compiler raised the issue as the function parameters no longer matched. Having to specify the option in the prj.conf to support dynamic BT GATT service creation was quite harder :). I had no glue the bt_gatt_service_register code was no longer linked in when the option "CONFIG_BT_GATT_DYNAMIC_DB=y" was not set in the prj.conf file. Thanks for the response, Frank
|
|||||||||
|
|||||||||
Re: Linkage Zephyr V1.13 versus V2.X
I had the same issue when moving forward kernel versions. The API for
At the top level get rid of the bt_gatt_ccc_cfg variables (my code has two characteristics) :
#ifndef NEW_BT_STACK static struct bt_gatt_ccc_cfg iks_atom_ccc_cfg[BT_GATT_CCC_MAX]; static struct bt_gatt_ccc_cfg iks_mtoa_ccc_cfg[BT_GATT_CCC_MAX]; #endif
And inside the bt_gatt_attr change the parameters to the BT_GATT_CCC macro, delete the first parameter it is no longer needed, and add a new 3rd parameter (same thing in two places for me):
#ifdef NEW_BT_STACK BT_GATT_CCC(iks_atom_ccc_cfg_changed,BT_GATT_PERM_WRITE_ENCRYPT), // BT_GATT_CCC(iks_atom_ccc_cfg_changed,BT_GATT_PERM_READ | BT_GATT_PERM_WRITE), // BT_GATT_CCC(iks_atom_ccc_cfg_changed,BT_GATT_PERM_READ | BT_GATT_PERM_WRITE_ENCRYPT), #else //NEW_BT_STACK BT_GATT_CCC(iks_atom_ccc_cfg, iks_atom_ccc_cfg_changed), #endif //NEW_BT_STACK
Lawrence King Principal Developer +1(416)627-7302
From: devel@... <devel@...>
On Behalf Of frv
Sent: Wednesday, December 4, 2019 2:19 AM To: devel@... Subject: [Zephyr-devel] Linkage Zephyr V1.13 versus V2.X
[Edited Message Follows] Hi all,
Recently I have moved from Zephyr 1.13 to V2.
I ported my simple BLE peripheral application based on the sample code peripheral_hr from V1.13 to V2.
However I can't seem to get it build anymore due to a linkage issue. As far as I can see the sources are well compiled but for some reason the linker reports an undefined reference.
"/home/frv/develop/zephyrproject/zephyr/samples/bluetooth/peripheral_hrORIGI/src/button.c:78: undefined reference to `bt_gatt_service_register'"
In my setup the GATT services are still defined in separate files. So next to my main.c that calls the init function (button_init()) I have the sources button.c and button.h file where I define my own GATT service (cfr. hrs.c, hrs.h as done in V1.13) to follow up a button press.
src/main.c /button.c
The CMakeLists.txt has as content (which is pretty simple):
# SPDX-License-Identifier: Apache-2.0
cmake_minimum_required(VERSION 3.13.1)
include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE) project(peripheral_hr)
FILE(GLOB app_sources src/*.c) target_sources(app PRIVATE ${app_sources} )
zephyr_library_include_directories($ENV{ZEPHYR_BASE}/samples/bluetooth) //has the button.h file zephyr_library_include_directories($ENV{ZEPHYR_BASE}/samples/bluetooth/gatt)
In the button.c code snippet: ... static struct bt_gatt_service button_svc = BT_GATT_SERVICE(attrs);
void button_init(void) { int result = bt_gatt_service_register(&button_svc); } ...
I have spend some time on looking at the boilerplate concepts but so far without any luck to prevent the linker error.
Any idea's what the issue could be and how to solve this properly. Linkage order?
BTW when I do the call, bt_gatt_service_register, in the main.c this is not seen as an undefined reference.
Thanks, Best regards, Frank
|
|||||||||
|
|||||||||
Linkage Zephyr V1.13 versus V2.X
Hi all,
Recently I have moved from Zephyr 1.13 to V2.
I ported my simple BLE peripheral application based on the sample code peripheral_hr from V1.13 to V2.
However I can't seem to get it build anymore due to a linkage issue.
As far as I can see the sources are well compiled but for some reason the linker reports an undefined reference.
"/home/frv/develop/zephyrproject/zephyr/samples/bluetooth/peripheral_hrORIGI/src/button.c:78: undefined reference to `bt_gatt_service_register'"
In my setup the GATT services are still defined in separate files.
So next to my main.c that calls the init function (button_init()) I have the sources button.c and button.h file where I define my own GATT service (cfr. hrs.c, hrs.h as done in V1.13) to follow up a button press.
src/main.c
/button.c
The CMakeLists.txt has as content (which is pretty simple):
# SPDX-License-Identifier: Apache-2.0
cmake_minimum_required(VERSION 3.13.1)
include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(peripheral_hr)
FILE(GLOB app_sources src/*.c)
target_sources(app PRIVATE
${app_sources}
)
zephyr_library_include_directories($ENV{ZEPHYR_BASE}/samples/bluetooth)
//has the button.h file
zephyr_library_include_directories($ENV{ZEPHYR_BASE}/samples/bluetooth/gatt)
In the button.c code snippet:
...
static struct bt_gatt_service button_svc = BT_GATT_SERVICE(attrs);
void button_init(void)
{
int result = bt_gatt_service_register(&button_svc);
}
...
I have spend some time on looking at the boilerplate concepts but so far without any luck to prevent the linker error.
I also had a look at this : https://github.com/zephyrproject-rtos/zephyr/issues/8851 Any idea's what the issue could be and how to solve this properly. Linkage order?
BTW when I do the call, bt_gatt_service_register, in the main.c this is not seen as an undefined reference.
Thanks,
Best regards,
Frank
|
|||||||||
|
|||||||||
Zephyr 2.1.0-rc3 tagged
David Leach
Hi Zephyr developers,
Zephyr 2.1.0-rc3 release candidate has been tagged.
Current issue status:
Testing Zephyr release candidate is 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-rc3
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
Thank you to everybody who contributed to this release!
David Leach
David Leach
NXP Semiconductors phone: +1.210.241.6761 Email: david.leach@...
|
|||||||||
|
|||||||||
Hi Mayank:
I had a similar requirement, also without a button on the same Nordic chip. I simply copied this file into my project, and called smp_svr_init() from my main() after bluetooth was up and running
zephyrproject/zephyr/samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app/src/smp_svr.c
This creates a Bluetooth advertisement for OTA update, and I can push new images from mu Ubuntu system with:
Use mcumgr to upload the new version over Bluetooth ----------------------------------------- sudo bash # must run as root to access the Bluetooth device mcumgr conn add zephyr type=ble connstring=peer_name="My Device" # make a symbolic name for the device mcumgr -c zephyr image list # Query device for its current image list. mcumgr -c zephyr image upload build/zephyr/zephyr.signed.bin # Upload new image to device. mcumgr -c zephyr image test <image-hash> # Tell the device to run the new image on its next boot ("test" the new image). mcumgr -c zephyr reset # Reboot the device. mcumgr -c zephyr image list # Query device for its current image list; ensure new image is running. mcumgr -c zephyr image confirm # Make the image swap permanent.
You do need to get the right bits in your prj.conf file, I think these are all you need, but there may be more… # mcuboot CONFIG_IMG_MANAGER=y CONFIG_MCUBOOT_IMG_MANAGER=y CONFIG_MCUBOOT_TRAILER_SWAP_TYPE=y CONFIG_IMG_BLOCK_BUF_SIZE=512 # Allow for large Bluetooth data packets. CONFIG_BT_L2CAP_TX_MTU=260 CONFIG_BT_RX_BUF_LEN=260 # Enable the Bluetooth and shell mcumgr transports. CONFIG_MCUMGR_SMP_BT=y #CONFIG_MCUMGR_SMP_SHELL=y #CONFIG_MCUMGR_SMP_UART=y # Required by the `taskstat` command. #CONFIG_THREAD_MONITOR=y # Enable statistics and statistic names. #CONFIG_STATS=y #CONFIG_STATS_NAMES=y # Enable all core commands. #CONFIG_MCUMGR_CMD_FS_MGMT=y CONFIG_MCUMGR_CMD_IMG_MGMT=y CONFIG_MCUMGR_CMD_OS_MGMT=y #CONFIG_MCUMGR_CMD_STAT_MGMT=y
Unfortunately you will need to reflash your units with JTAG/SWD to get the smp_svr in, but after that you can do OTA.
Lawrence King Principal Developer +1(416)627-7302
From: devel@... <devel@...>
On Behalf Of Mayank
Sent: Tuesday, December 3, 2019 6:47 AM To: devel@... Subject: [Zephyr-devel] DFU OTA by using mcuboot bootloader in serial recovery mode #ble #hci #nrf52480 #uart
Hello All,
|
|||||||||
|
|||||||||
Upcoming Event: Zephyr Project: APIs - Tue, 12/03/2019 9:00am-10:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: APIs When: Tuesday, 3 December 2019, 9:00am to 10:00am, (GMT-08: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 Live meeting minutes: https://docs.google.com/
|
|||||||||
|
|||||||||
API meeting: Agenda
Carles Cufi
Hi all,
This week we will focus on GPIO: - 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
|
|||||||||
|
|||||||||
Mayank <mayank7117@...>
Hello All,
Right now I'm exploring the best way to do DFU OTA. I would like to ask that how i can do the DFU by booting the mcuboot bootloader in serial recovery mode. I have one nrf52840_pca10056 chip integrated on my custom board, which has mcuboot as a bootloader. I don't have any direct pin access to the nrf chip. I'm doing an OTA for zephyr's hci_uart sample application. My aim is: - Flash mcuboot - Flash hci_uart application one time using Jlink segger (For beacon scanning) - After that i should be able to do DFU OTA on field, without having any Jlink kind of wired connection. Thanks, Mayank
|
|||||||||
|
|||||||||
Puzdrowski, Andrzej
Hi Q1 – no, this mens that higher part of BLE stack runs on HCI client which has no access to nRF52840 flash at all. Q2 – mcuboot serial recovery or your proprietary protocol which can share common uart channel.
Andrzej
From: devel@... <devel@...>
On Behalf Of Mayank via Lists.Zephyrproject.Org
Sent: 03 December 2019 10:02 To: devel@... Cc: devel@... Subject: [Zephyr-devel] How to combine smp_svr and hci_uart app's of zephyr for DFU OTA #ble #uart #samples #hci #nrf52480
Hi, I want to do an DFU OTA in nRF52840 BLE chip. I have flashed mcuboot bootloader and also flashed hci_uart (To scan BLE beacons) application. This will be one time flash using JTAG. Now, I want to perform DFU OTA with the newly updated hci_uart application. I found that we can do DFU using 'mcumgr' cli and to use 'mcumgr' zephyr's smp_svr sample application is required on the chip. But i can't do the firmware upgrade because i have only (mcuboot + hci_uart) app's on nRF52840 & not smp_svr. (Flashed one time using JTAG).
Q1 : Is it possible to combine smp_svr + hci_uart for one time flashing using JTAG. (So afterwards i can do OTA of hci_uart app directly using mcumgr tool)
Q2 : Is there any alternate way to perform DFU of hci_uart app with/without using smp_svr.
|
|||||||||
|
|||||||||
Mayank <mayank7117@...>
Hi, I want to do an DFU OTA in nRF52840 BLE chip. I have flashed mcuboot bootloader and also flashed hci_uart (To scan BLE beacons) application. This will be one time flash using JTAG. Now, I want to perform DFU OTA with the newly updated hci_uart application. I found that we can do DFU using 'mcumgr' cli and to use 'mcumgr' zephyr's smp_svr sample application is required on the chip. But i can't do the firmware upgrade because i have only (mcuboot + hci_uart) app's on nRF52840 & not smp_svr. (Flashed one time using JTAG).
Q1 : Is it possible to combine smp_svr + hci_uart for one time flashing using JTAG. (So afterwards i can do OTA of hci_uart app directly using mcumgr tool) Q2 : Is there any alternate way to perform DFU of hci_uart app with/without using smp_svr.
|
|||||||||
|
|||||||||
Re: How to add support for Silabs EFM32JG12B?
Christian Taedcke
Am Freitag, den 22.11.2019, 08:17 -0600 schrieb Kumar Gala:
I owe a response to this, but haven’t had time to think about it in aThank you, i missed the answer somehow. Your mail gives me some good pointers. Yes, it does.On Nov 19, 2019, at 6:02 AM, Christian Taedcke <hacking@taedcke.comDoes the EFM32PG12B Cortex-M4 have floating point support?wrote:Hello, There is also the e.g. efm32gg12b which has more peripherals and theBecause of this Silabs does not provide an extra development board,So I don’t know if renaming efm32pg12b to efm32Xg12b makes sense to peripherals are at different addresses. But since most of the abstraction is handled by the silabs gecko hal, it might be good to combine multiple families in the same soc folder. I will give it a try and open a RFC later. I did not think about that. That helps. I will have a look at the nxp2. Since there is no development board for the EFM32JG12B soc, iIt should be doable, we have several boards that support different board lpcxpresso54114. It does, thank you. Regards, Christian
|
|||||||||
|
|||||||||
Zephyr v2.1.0 release notes requests
David Leach
The v2.1.0 release notes are lacking any updates for the following sections:
Please help fill in these details.
David David Leach
NXP Semiconductors phone: +1.210.241.6761 Email: david.leach@...
|
|||||||||
|
|||||||||
Re: USB fails to enumerate on nrf52840_pca10056 board
lairdjm
I suspect my silicon may be too old. I've had the boards for a coupleHi Steve, There are various issues with your silicon versions: 1) SDK 14.2 was the last version to support engineering A silicon as per https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcomp_matrix_nrf52840%2FCOMP%2Fnrf52840%2FnRF52840_ic_rev_sdk_sd_comp_matrix.html 2) high voltage operation does not work on engineering C silicon or older, errata 140 3) multiple USB erratas, 162, 171, 180, 200, which prevent USB from working I think I'm wasting everybody's time and should just get a couple ofThat would be a good idea. Thanks, Jamie
|
|||||||||
|
|||||||||
Re: USB fails to enumerate on nrf52840_pca10056 board
Steve Brown
Hi Emil,
toggle quoted messageShow quoted text
Thanks for the files. Neither work on my boards. I suspect my silicon may be too old. I've had the boards for a couple of years. The build/date codes on both boards are: QIAAAA/1716AK. The labels on the jlink chips are: V0.9.2 2017.34 683955518 V0.9.2 2017.33 683137769 Some of the Nordic examples log errata 104 & 154 as enabled. Further, the usbd_cdc_acm example from the 14.2.0 SDK works, while the one from 16.0.0 fails to enumerate. I think I'm wasting everybody's time and should just get a couple of current boards. Steve
On Thu, 2019-11-28 at 09:52 +0000, Obalski, Emil wrote:
Hello,
|
|||||||||
|
|||||||||
Re: USB fails to enumerate on nrf52840_pca10056 board
Obalski, Emil <Emil.Obalski@...>
Hello,
toggle quoted messageShow quoted text
I've tested it on 77006e896 with nRF52840_pca10056 board: - samples/subsys/usb/cdc_acm - tests/subsys/usb/desc_sections Both works fine for me. Here are hex files, please verify if both works with Your board. Just in case You do not know how to falsh: nrfjprog --program <hex_file>.hex --sectorerase --reset Regards, Emil
-----Original Message-----
From: Steve Brown <sbrown@ewol.com> Sent: środa, 27 listopada 2019 20:56 To: Johann Fischer <johann_fischer@posteo.de>; Cufi, Carles <Carles.Cufi@nordicsemi.no> Cc: devel@lists.zephyrproject.org; Obalski, Emil <Emil.Obalski@nordicsemi.no>; 'Johann Fischer' <j.fischer@phytec.de>; 'Emeltchenko, Andrei' <andrei.emeltchenko@intel.com> Subject: Re: [Zephyr-devel] USB fails to enumerate on nrf52840_pca10056 board Hi Johann, Could you email me a zephyr.hex of a USB app that enumerates? With it I can eliminate my nrf52 boards as the problem. Thanks, Steve On Wed, 2019-11-27 at 17:57 +0100, Johann Fischer wrote: Can not confirm, woks fine on the latest master and on 77006e896.
|
|||||||||
|
|||||||||
Re: Add support Optiga Trust X
Carles Cufi
Hi Pawel,
We actually discussed a very similar case yesterday in the TSC meeting. The trusted-firmware-m module also requires mbedTLS, but a different version from the one we have in Zephyr. In that case the resolution was to place the required mbedTLS version *inside* the trusted-firmware-m module/repo, so that the whole repo is self-contained. I would argue that if you can make it work with the existing mbedTLS currently present as a zephyr module, that is ideal. If that doesn’t work out then you can do the same that we’ve done with trusted-firmware-m and include the copy of mbedTLS directly inside the optiga module repo.
Carles
From: Pawel Zarembski <Pawel.Zarembski@...>
Sent: 28 November 2019 12:32 To: devel@... Cc: Christoph.Reiter@...; Artem.Yushev@...; Christian.Lesjak@...; Mihai.Tudosie@...; Cufi, Carles <Carles.Cufi@...> Subject: RE: Add support Optiga Trust X
Hello,
I finished implementing basic library API (optiga/, examples/, pal/) and now I want to move on to work on mbedTLS and one questions arose:
Does Optiga Trust X module should contain mbedTLS library? Basically Zephyr have separate module for mbedTLS so if it will be included in Optiga module aswell it would create unnecessary redundancy.
If no: should i work on integrating Optiga Trust X with existing mbedTLS module?
Best regards Paweł
From:
Mihai.Tudosie@... <Mihai.Tudosie@...>
CAUTION: This email originated from outside of the organization. This message might not be safe, use caution in opening it. If in doubt, do not open the attachment nor links in the message.
Hi Carles,
Thank you for keeping us up to date and supporting with this topic. I’ve added 2 more colleagues; Artem was already in contact with Pawel to add his code to Infineon github repo too.
Best regards, Mihai
From: Cufi, Carles <Carles.Cufi@...>
Hi Pawel,
Copying a couple of people from Infineon that might be interested in your work.
About your questions.
Carles
Hello, I am currently working on project based on EFM32PG board and Optiga Trust X (security chip). I already did some work on implementing their framework and I run it with success with sample demo. I want to ask about process of adding support for that board for Zephyr.
Helpful links: Repo: https://github.com/Infineon/optiga-trust-x Implemented Platform Abstraction Layer with Zephyr support: https://github.com/Infineon/optiga-trust-x/tree/master/pal/efm32pg_zephyr
Best regards Paweł Zarembski Arrow Electronics
|
|||||||||
|
|||||||||
Re: Add support Optiga Trust X
Paweł Zarembski
Hello,
I finished implementing basic library API (optiga/, examples/, pal/) and now I want to move on to work on mbedTLS and one questions arose:
Does Optiga Trust X module should contain mbedTLS library? Basically Zephyr have separate module for mbedTLS so if it will be included in Optiga module aswell it would create unnecessary redundancy.
If no: should i work on integrating Optiga Trust X with existing mbedTLS module?
Best regards Paweł
From: Mihai.Tudosie@... <Mihai.Tudosie@...>
Sent: Tuesday, November 12, 2019 3:43 PM To: Carles.Cufi@... Cc: Pawel Zarembski <Pawel.Zarembski@...>; devel@...; Christoph.Reiter@...; Artem.Yushev@...; Christian.Lesjak@... Subject: [External] RE: Add support Optiga Trust X
CAUTION: This email originated from outside of the organization. This message might not be safe, use caution in opening it. If in doubt, do not open the attachment nor links in the message.
Hi Carles,
Thank you for keeping us up to date and supporting with this topic. I’ve added 2 more colleagues; Artem was already in contact with Pawel to add his code to Infineon github repo too.
Best regards, Mihai
From: Cufi, Carles <Carles.Cufi@...>
Hi Pawel,
Copying a couple of people from Infineon that might be interested in your work.
About your questions.
Carles
Hello, I am currently working on project based on EFM32PG board and Optiga Trust X (security chip). I already did some work on implementing their framework and I run it with success with sample demo. I want to ask about process of adding support for that board for Zephyr.
Helpful links: Repo: https://github.com/Infineon/optiga-trust-x Implemented Platform Abstraction Layer with Zephyr support: https://github.com/Infineon/optiga-trust-x/tree/master/pal/efm32pg_zephyr
Best regards Paweł Zarembski Arrow Electronics
|
|||||||||
|
|||||||||
Re: Zephyr 2.1.0-rc2 tagged
David Leach
The problem has been addressed and the release candidate is now live.
David Leach
From: David Leach
Sent: Wednesday, November 27, 2019 6:15 PM To: 'devel@...' <devel@...>; 'announce@...' <announce@...>; 'testing-wg@... Group Moderators' <testing-wg+owner@...> Subject: RE: Zephyr 2.1.0-rc2 tagged
There was a problem with how I attempted to create this release. In the process of fixing it and will send an update when ready.
Sorry for any inconvenience.
David Leach
From: David Leach
Hi Zephyr developers,
Zephyr 2.1.0-rc2 release candidate has been tagged.
Current issue status:
To get to an RC3 tag and eventual final release, we need get to 20 medium priority issues. We have existing PRs for 11 medium issues.
Testing Zephyr release candidate is 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-rc2
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
Thank you to everybody who contributed to this release!
David Leach
David Leach
NXP Semiconductors phone: +1.210.241.6761 Email: david.leach@...
|
|||||||||
|
|||||||||
Re: Zephyr 2.1.0-rc2 tagged
David Leach
There was a problem with how I attempted to create this release. In the process of fixing it and will send an update when ready.
Sorry for any inconvenience.
David Leach
From: David Leach
Sent: Wednesday, November 27, 2019 4:32 PM To: devel@...; announce@...; testing-wg@... Group Moderators <testing-wg+owner@...> Subject: Zephyr 2.1.0-rc2 tagged
Hi Zephyr developers,
Zephyr 2.1.0-rc2 release candidate has been tagged.
Current issue status:
To get to an RC3 tag and eventual final release, we need get to 20 medium priority issues. We have existing PRs for 11 medium issues.
Testing Zephyr release candidate is 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-rc2
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
Thank you to everybody who contributed to this release!
David Leach
David Leach
NXP Semiconductors phone: +1.210.241.6761 Email: david.leach@...
|
|||||||||
|