Date   

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

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

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


DFU OTA by using mcuboot bootloader in serial recovery mode #ble #hci #nrf52480 #uart

Mayank
 

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


Re: How to combine smp_svr and hci_uart app's of zephyr for DFU OTA #hci #nrf52480 #ble #uart #samples

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.

Thanks,
Mayank


How to combine smp_svr and hci_uart app's of zephyr for DFU OTA #hci #nrf52480 #ble #uart #samples

Mayank
 

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.

Thanks,
Mayank


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 a
lot of detail.
Thank you, i missed the answer somehow. Your mail gives me some good
pointers.


On Nov 19, 2019, at 6:02 AM, Christian Taedcke <hacking@taedcke.com
wrote:
Hello,

i want to add support for the Silabs EFM32JG12B soc. It is nearly
the same as the already supported EFM32PG12B. It has the exact same
peripherals, memory etc, only a different core. The EFM32JG12B has
a Cortex-M3, the EFM32PG12B a Cortex-M4.
Does the EFM32PG12B Cortex-M4 have floating point support?
Yes, it does.


Because of this Silabs does not provide an extra development board,
since binaries built for the EFM32JG12B can run on the EFM32PG12B.
So the recommended development board for the EFM32JG12B is
efm32pg_stk3402a

Questions:

1. How to deal with a soc that only differs in the core? I would
like to reuse (without copying) a lot of stuff from the efm32pg12b
(i.e. the folder soc/arm/silabs_exx32/efm32pg12b and the device
tree stuff). Any hints on how to do that?
So I don’t know if renaming efm32pg12b to efm32Xg12b makes sense to
cover the 2 variants.
There is also the e.g. efm32gg12b which has more peripherals and the
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.


2. Since there is no development board for the EFM32JG12B soc, i
would like to add the possibility to the board efm32pg_stk3402a to
compile for the EFM32JG12B instead of the EFM32PG12B. Is that
possible or are there other recommendations?
It should be doable, we have several boards that support different
“configurations” already. Examples are the dual core SoCs in which
we have one board dir but different <BOARD>_CFG.yaml and such for the
different variants.
I did not think about that. That helps. I will have a look at the nxp
board lpcxpresso54114.


Not sure if that gives you enough to start with.
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:

 

  • Kernel
  • Bluetooth
  • Libraries/Subsystems
  • HALs
  • Documentation
  • Tests and Samples

 

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 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.
Hi 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 of
current boards.
That would be a good idea.
Thanks,
Jamie


Re: USB fails to enumerate on nrf52840_pca10056 board

Steve Brown
 

Hi Emil,

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,

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.

Johann

On Wed, 27 Nov 2019 16:50:02 +0000
"Cufi, Carles" <carles.cufi@nordicsemi.no> wrote:

Hi Steve,

Is this a regression? Have you tested this with an earlier
Zephyr
version/revision that worked?
We use this board routinely to test the USB stack and haven't
run
into this problem.

Can you please also share more details about the USB Host (Linux
I
assume) and the way you build the samples?

Thanks,

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <
devel@lists.zephyrproject.org> On Behalf Of Steve Brown via
Lists.Zephyrproject.Org
Sent: 27 November 2019 17:37
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] USB fails to enumerate on
nrf52840_pca10056
board

All the USB samples and tests fail to enumerate.
git HEAD 77006e896

Output from the desc_sections test is below:

Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB
disconnect, device number 65 Nov 27 09:12:00 nm-ws kernel:
[520542.088211] usb 7-2:
new full-speed USB device number 66 using ohci-pci Nov 27
09:12:06 nm-ws
kernel: [520547.360327] usb 7-2: device descriptor read/all,
error
-110 Nov 27 09:12:06 nm-ws kernel: [520547.516218] usb 7-2:
new
full- speed USB device number 67 using ohci-pci

And the relevant nrf console output:

D: ep 0, status 0
D: ** 0 **
D: bRequest 0x6, wIndex 0x0
D: REQ_GET_DESCRIPTOR


The Nordic usbd_cdc_acm_pca10056.hex works on the same board:

Nov 27 09:09:32 nm-ws kernel: [520393.141205] usb 7-2: USB
disconnect, device number 64 Nov 27 09:09:32 nm-ws kernel:
[520393.735742] usb 7-2:
new full-speed USB device number 65 using ohci-pci Nov 27
09:09:32 nm-ws
kernel: [520393.938828] usb 7-2: New USB device found,
idVendor=1915, idProduct=520f, bcdDevice= 1.00 Nov 27 09:09:32
nm-ws kernel:
[520393.938834] usb 7-2: New USB device strings: Mfr=1,
Product=2,
SerialNumber=3 Nov 27 09:09:32 nm-ws kernel: [520393.938838]
usb
7-2:
Product: nRF52 USB CDC Demo Nov 27 09:09:32 nm-ws kernel:
[520393.938841] usb 7-2: Manufacturer: Nordic Semiconductor Nov
27
09:09:32 nm-ws kernel: [520393.938843] usb 7-2: SerialNumber:
796cadf8f13bbb37 Nov 27 09:09:32 nm-ws kernel: [520393.940987]
cdc_acm
7-2:1.0: ttyACM1: USB ACM device

Steve




Re: USB fails to enumerate on nrf52840_pca10056 board

Obalski, Emil <Emil.Obalski@...>
 

Hello,

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.

Johann

On Wed, 27 Nov 2019 16:50:02 +0000
"Cufi, Carles" <carles.cufi@nordicsemi.no> wrote:

Hi Steve,

Is this a regression? Have you tested this with an earlier Zephyr
version/revision that worked?
We use this board routinely to test the USB stack and haven't run
into this problem.

Can you please also share more details about the USB Host (Linux I
assume) and the way you build the samples?

Thanks,

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <
devel@lists.zephyrproject.org> On Behalf Of Steve Brown via
Lists.Zephyrproject.Org
Sent: 27 November 2019 17:37
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] USB fails to enumerate on
nrf52840_pca10056
board

All the USB samples and tests fail to enumerate.
git HEAD 77006e896

Output from the desc_sections test is below:

Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB
disconnect, device number 65 Nov 27 09:12:00 nm-ws kernel:
[520542.088211] usb 7-2:
new full-speed USB device number 66 using ohci-pci Nov 27
09:12:06 nm-ws
kernel: [520547.360327] usb 7-2: device descriptor read/all, error
-110 Nov 27 09:12:06 nm-ws kernel: [520547.516218] usb 7-2: new
full- speed USB device number 67 using ohci-pci

And the relevant nrf console output:

D: ep 0, status 0
D: ** 0 **
D: bRequest 0x6, wIndex 0x0
D: REQ_GET_DESCRIPTOR


The Nordic usbd_cdc_acm_pca10056.hex works on the same board:

Nov 27 09:09:32 nm-ws kernel: [520393.141205] usb 7-2: USB
disconnect, device number 64 Nov 27 09:09:32 nm-ws kernel:
[520393.735742] usb 7-2:
new full-speed USB device number 65 using ohci-pci Nov 27
09:09:32 nm-ws
kernel: [520393.938828] usb 7-2: New USB device found,
idVendor=1915, idProduct=520f, bcdDevice= 1.00 Nov 27 09:09:32
nm-ws kernel:
[520393.938834] usb 7-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3 Nov 27 09:09:32 nm-ws kernel: [520393.938838] usb
7-2:
Product: nRF52 USB CDC Demo Nov 27 09:09:32 nm-ws kernel:
[520393.938841] usb 7-2: Manufacturer: Nordic Semiconductor Nov
27
09:09:32 nm-ws kernel: [520393.938843] usb 7-2: SerialNumber:
796cadf8f13bbb37 Nov 27 09:09:32 nm-ws kernel: [520393.940987]
cdc_acm
7-2:1.0: ttyACM1: USB ACM device

Steve





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@...>
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@...>
Sent: Dienstag, 12. November 2019 14:34
To: pawel.zarembski@...; devel@...
Cc: Tudosie Mihai (IFAT DCGR DSS SVS SCI) <Mihai.Tudosie@...>; Reiter Christoph (IFAT DCGR DSS M TPD) <Christoph.Reiter@...>
Subject: RE: Add support Optiga Trust X

 

Hi Pawel,

 

Copying a couple of people from Infineon that might be interested in your work.

 

About your questions.

 

  1. You are expected to provide the board files in a single Pull Request. If you are not able to do so maybe you can provide as much as you can using a Draft Pull Request and then ask for help in the mailing list
  2. Looking at the optiga-trust-x source code, it’s licensed under the MIT license, and it’s also a cross-platform project that is not maintained as part of Zephyr. This means that the proper way to integrate it into Zephyr is to use a separate repository with a Zephyr module. See here for more details: https://docs.zephyrproject.org/latest/guides/modules.html#submitting-a-new-module
  3. All code that goes into the main Zephyr repository should be Apache 2.0 licensed. The MIT license is fine for a module, which is a repository hosted under the zephyrproject-rtos GitHub organization but not the main repo itself. I recommend that you place all code under the MIT license in the external module, and the rest licensed as Apache 2.0 in the zephyr repo itself.

 

Carles

 

 

From: devel@... <devel@...> On Behalf Of Pawel Zarembski via Lists.Zephyrproject.Org
Sent: 12 November 2019 13:35
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] Add support Optiga Trust X

 

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.

  1. Do I need to do everything by my own and then do the Pull Request for that?
  2. Should the framework/library be implemented as external Module or for example as external library ( /ext/lib )?
  3. Is there a problem with licensing? Because this framework is build on MIT license copyrighted by Infineon Technologies and some part with MIT copyrighted by Arrow Electronics.

 

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@...>
Sent: Dienstag, 12. November 2019 14:34
To: pawel.zarembski@...; devel@...
Cc: Tudosie Mihai (IFAT DCGR DSS SVS SCI) <Mihai.Tudosie@...>; Reiter Christoph (IFAT DCGR DSS M TPD) <Christoph.Reiter@...>
Subject: RE: Add support Optiga Trust X

 

Hi Pawel,

 

Copying a couple of people from Infineon that might be interested in your work.

 

About your questions.

 

  1. You are expected to provide the board files in a single Pull Request. If you are not able to do so maybe you can provide as much as you can using a Draft Pull Request and then ask for help in the mailing list
  2. Looking at the optiga-trust-x source code, it’s licensed under the MIT license, and it’s also a cross-platform project that is not maintained as part of Zephyr. This means that the proper way to integrate it into Zephyr is to use a separate repository with a Zephyr module. See here for more details: https://docs.zephyrproject.org/latest/guides/modules.html#submitting-a-new-module
  3. All code that goes into the main Zephyr repository should be Apache 2.0 licensed. The MIT license is fine for a module, which is a repository hosted under the zephyrproject-rtos GitHub organization but not the main repo itself. I recommend that you place all code under the MIT license in the external module, and the rest licensed as Apache 2.0 in the zephyr repo itself.

 

Carles

 

 

From: devel@... <devel@...> On Behalf Of Pawel Zarembski via Lists.Zephyrproject.Org
Sent: 12 November 2019 13:35
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] Add support Optiga Trust X

 

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.

  1. Do I need to do everything by my own and then do the Pull Request for that?
  2. Should the framework/library be implemented as external Module or for example as external library ( /ext/lib )?
  3. Is there a problem with licensing? Because this framework is build on MIT license copyrighted by Infineon Technologies and some part with MIT copyrighted by Arrow Electronics.

 

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
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:

 

Priority

Count

Has PR

High

0

-

Medium

30

11

 

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:

 

Priority

Count

Has PR

High

0

-

Medium

30

11

 

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@...

 

 


Zephyr 2.1.0-rc2 tagged

David Leach
 

Hi Zephyr developers,

 

Zephyr 2.1.0-rc2 release candidate has been tagged.

 

Current issue status:

 

Priority

Count

Has PR

High

0

-

Medium

30

11

 

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: USB fails to enumerate on nrf52840_pca10056 board

Steve Brown
 

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.

Johann

On Wed, 27 Nov 2019 16:50:02 +0000
"Cufi, Carles" <carles.cufi@nordicsemi.no> wrote:

Hi Steve,

Is this a regression? Have you tested this with an earlier Zephyr
version/revision that worked?
We use this board routinely to test the USB stack and haven't run
into this problem.

Can you please also share more details about the USB Host (Linux I
assume) and the way you build the samples?

Thanks,

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <
devel@lists.zephyrproject.org> On
Behalf Of Steve Brown via Lists.Zephyrproject.Org
Sent: 27 November 2019 17:37
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] USB fails to enumerate on
nrf52840_pca10056
board

All the USB samples and tests fail to enumerate.
git HEAD 77006e896

Output from the desc_sections test is below:

Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB
disconnect,
device number 65 Nov 27 09:12:00 nm-ws kernel: [520542.088211]
usb 7-2:
new full-speed USB device number 66 using ohci-pci Nov 27
09:12:06 nm-ws
kernel: [520547.360327] usb 7-2: device descriptor read/all,
error -110
Nov 27 09:12:06 nm-ws kernel: [520547.516218] usb 7-2: new full-
speed
USB device number 67 using ohci-pci

And the relevant nrf console output:

D: ep 0, status 0
D: ** 0 **
D: bRequest 0x6, wIndex 0x0
D: REQ_GET_DESCRIPTOR


The Nordic usbd_cdc_acm_pca10056.hex works on the same board:

Nov 27 09:09:32 nm-ws kernel: [520393.141205] usb 7-2: USB
disconnect,
device number 64 Nov 27 09:09:32 nm-ws kernel: [520393.735742]
usb 7-2:
new full-speed USB device number 65 using ohci-pci Nov 27
09:09:32 nm-ws
kernel: [520393.938828] usb 7-2: New USB device found,
idVendor=1915,
idProduct=520f, bcdDevice= 1.00 Nov 27 09:09:32 nm-ws kernel:
[520393.938834] usb 7-2: New USB device strings: Mfr=1,
Product=2,
SerialNumber=3 Nov 27 09:09:32 nm-ws kernel: [520393.938838] usb
7-2:
Product: nRF52 USB CDC Demo Nov 27 09:09:32 nm-ws kernel:
[520393.938841] usb 7-2: Manufacturer: Nordic Semiconductor Nov
27
09:09:32 nm-ws kernel: [520393.938843] usb 7-2: SerialNumber:
796cadf8f13bbb37 Nov 27 09:09:32 nm-ws kernel: [520393.940987]
cdc_acm
7-2:1.0: ttyACM1: USB ACM device

Steve





Re: USB fails to enumerate on nrf52840_pca10056 board

Steve Brown
 

Hi Carles,

This is the first time I've tried the nrf usb so I have no "working
version" to compare.

West version: v0.6.3
zephyr-sdk-0.10.3

The desc_section test was build with:
west build -b nrf52840_pca10056
west flash

The host is Ubuntu 19.10 on a x86_64.
Linux nm-ws 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I get the same result with a Raspberry Pi 3B+ as the host, also 19.10.
Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:06:55 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux

The prj.conf file is unchanged. Does it need to be modified for this
board?

Other samples run fine. I've tested the onoff-app and hci_uart and they
perform as expected. The first USB sample I tried was hci_usb. When it
failed to enumerate, I tried the other samples and tests. They failed
too. All were build as above.

Thanks for the quick reply,

Steve

On Wed, 2019-11-27 at 16:50 +0000, Cufi, Carles wrote:
Hi Steve,

Is this a regression? Have you tested this with an earlier Zephyr
version/revision that worked?
We use this board routinely to test the USB stack and haven't run
into this problem.

Can you please also share more details about the USB Host (Linux I
assume) and the way you build the samples?

Thanks,

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org>
On
Behalf Of Steve Brown via Lists.Zephyrproject.Org
Sent: 27 November 2019 17:37
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] USB fails to enumerate on nrf52840_pca10056
board

All the USB samples and tests fail to enumerate.
git HEAD 77006e896

Output from the desc_sections test is below:

Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB
disconnect,
device number 65 Nov 27 09:12:00 nm-ws kernel: [520542.088211] usb
7-2:
new full-speed USB device number 66 using ohci-pci Nov 27 09:12:06
nm-ws
kernel: [520547.360327] usb 7-2: device descriptor read/all, error
-110
Nov 27 09:12:06 nm-ws kernel: [520547.516218] usb 7-2: new full-
speed
USB device number 67 using ohci-pci

And the relevant nrf console output:

D: ep 0, status 0
D: ** 0 **
D: bRequest 0x6, wIndex 0x0
D: REQ_GET_DESCRIPTOR


The Nordic usbd_cdc_acm_pca10056.hex works on the same board:

Nov 27 09:09:32 nm-ws kernel: [520393.141205] usb 7-2: USB
disconnect,
device number 64 Nov 27 09:09:32 nm-ws kernel: [520393.735742] usb
7-2:
new full-speed USB device number 65 using ohci-pci Nov 27 09:09:32
nm-ws
kernel: [520393.938828] usb 7-2: New USB device found,
idVendor=1915,
idProduct=520f, bcdDevice= 1.00 Nov 27 09:09:32 nm-ws kernel:
[520393.938834] usb 7-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3 Nov 27 09:09:32 nm-ws kernel: [520393.938838] usb 7-
2:
Product: nRF52 USB CDC Demo Nov 27 09:09:32 nm-ws kernel:
[520393.938841] usb 7-2: Manufacturer: Nordic Semiconductor Nov 27
09:09:32 nm-ws kernel: [520393.938843] usb 7-2: SerialNumber:
796cadf8f13bbb37 Nov 27 09:09:32 nm-ws kernel: [520393.940987]
cdc_acm
7-2:1.0: ttyACM1: USB ACM device

Steve




Re: USB fails to enumerate on nrf52840_pca10056 board

Johann Fischer
 

Can not confirm, woks fine on the latest master and on 77006e896.

Johann

On Wed, 27 Nov 2019 16:50:02 +0000
"Cufi, Carles" <carles.cufi@nordicsemi.no> wrote:

Hi Steve,

Is this a regression? Have you tested this with an earlier Zephyr version/revision that worked?
We use this board routinely to test the USB stack and haven't run into this problem.

Can you please also share more details about the USB Host (Linux I assume) and the way you build the samples?

Thanks,

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On
Behalf Of Steve Brown via Lists.Zephyrproject.Org
Sent: 27 November 2019 17:37
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] USB fails to enumerate on nrf52840_pca10056
board

All the USB samples and tests fail to enumerate.
git HEAD 77006e896

Output from the desc_sections test is below:

Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB disconnect,
device number 65 Nov 27 09:12:00 nm-ws kernel: [520542.088211] usb 7-2:
new full-speed USB device number 66 using ohci-pci Nov 27 09:12:06 nm-ws
kernel: [520547.360327] usb 7-2: device descriptor read/all, error -110
Nov 27 09:12:06 nm-ws kernel: [520547.516218] usb 7-2: new full-speed
USB device number 67 using ohci-pci

And the relevant nrf console output:

D: ep 0, status 0
D: ** 0 **
D: bRequest 0x6, wIndex 0x0
D: REQ_GET_DESCRIPTOR


The Nordic usbd_cdc_acm_pca10056.hex works on the same board:

Nov 27 09:09:32 nm-ws kernel: [520393.141205] usb 7-2: USB disconnect,
device number 64 Nov 27 09:09:32 nm-ws kernel: [520393.735742] usb 7-2:
new full-speed USB device number 65 using ohci-pci Nov 27 09:09:32 nm-ws
kernel: [520393.938828] usb 7-2: New USB device found, idVendor=1915,
idProduct=520f, bcdDevice= 1.00 Nov 27 09:09:32 nm-ws kernel:
[520393.938834] usb 7-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3 Nov 27 09:09:32 nm-ws kernel: [520393.938838] usb 7-2:
Product: nRF52 USB CDC Demo Nov 27 09:09:32 nm-ws kernel:
[520393.938841] usb 7-2: Manufacturer: Nordic Semiconductor Nov 27
09:09:32 nm-ws kernel: [520393.938843] usb 7-2: SerialNumber:
796cadf8f13bbb37 Nov 27 09:09:32 nm-ws kernel: [520393.940987] cdc_acm
7-2:1.0: ttyACM1: USB ACM device

Steve





Re: USB fails to enumerate on nrf52840_pca10056 board

Carles Cufi
 

Hi Steve,

Is this a regression? Have you tested this with an earlier Zephyr version/revision that worked?
We use this board routinely to test the USB stack and haven't run into this problem.

Can you please also share more details about the USB Host (Linux I assume) and the way you build the samples?

Thanks,

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On
Behalf Of Steve Brown via Lists.Zephyrproject.Org
Sent: 27 November 2019 17:37
To: devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: [Zephyr-devel] USB fails to enumerate on nrf52840_pca10056
board

All the USB samples and tests fail to enumerate.
git HEAD 77006e896

Output from the desc_sections test is below:

Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB disconnect,
device number 65 Nov 27 09:12:00 nm-ws kernel: [520542.088211] usb 7-2:
new full-speed USB device number 66 using ohci-pci Nov 27 09:12:06 nm-ws
kernel: [520547.360327] usb 7-2: device descriptor read/all, error -110
Nov 27 09:12:06 nm-ws kernel: [520547.516218] usb 7-2: new full-speed
USB device number 67 using ohci-pci

And the relevant nrf console output:

D: ep 0, status 0
D: ** 0 **
D: bRequest 0x6, wIndex 0x0
D: REQ_GET_DESCRIPTOR


The Nordic usbd_cdc_acm_pca10056.hex works on the same board:

Nov 27 09:09:32 nm-ws kernel: [520393.141205] usb 7-2: USB disconnect,
device number 64 Nov 27 09:09:32 nm-ws kernel: [520393.735742] usb 7-2:
new full-speed USB device number 65 using ohci-pci Nov 27 09:09:32 nm-ws
kernel: [520393.938828] usb 7-2: New USB device found, idVendor=1915,
idProduct=520f, bcdDevice= 1.00 Nov 27 09:09:32 nm-ws kernel:
[520393.938834] usb 7-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3 Nov 27 09:09:32 nm-ws kernel: [520393.938838] usb 7-2:
Product: nRF52 USB CDC Demo Nov 27 09:09:32 nm-ws kernel:
[520393.938841] usb 7-2: Manufacturer: Nordic Semiconductor Nov 27
09:09:32 nm-ws kernel: [520393.938843] usb 7-2: SerialNumber:
796cadf8f13bbb37 Nov 27 09:09:32 nm-ws kernel: [520393.940987] cdc_acm
7-2:1.0: ttyACM1: USB ACM device

Steve



USB fails to enumerate on nrf52840_pca10056 board

Steve Brown
 

All the USB samples and tests fail to enumerate.
git HEAD 77006e896

Output from the desc_sections test is below:

Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB disconnect, device number 65
Nov 27 09:12:00 nm-ws kernel: [520542.088211] usb 7-2: new full-speed USB device number 66 using ohci-pci
Nov 27 09:12:06 nm-ws kernel: [520547.360327] usb 7-2: device descriptor read/all, error -110
Nov 27 09:12:06 nm-ws kernel: [520547.516218] usb 7-2: new full-speed USB device number 67 using ohci-pci

And the relevant nrf console output:

D: ep 0, status 0
D: ** 0 **
D: bRequest 0x6, wIndex 0x0
D: REQ_GET_DESCRIPTOR


The Nordic usbd_cdc_acm_pca10056.hex works on the same board:

Nov 27 09:09:32 nm-ws kernel: [520393.141205] usb 7-2: USB disconnect, device number 64
Nov 27 09:09:32 nm-ws kernel: [520393.735742] usb 7-2: new full-speed USB device number 65 using ohci-pci
Nov 27 09:09:32 nm-ws kernel: [520393.938828] usb 7-2: New USB device found, idVendor=1915, idProduct=520f, bcdDevice= 1.00
Nov 27 09:09:32 nm-ws kernel: [520393.938834] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 27 09:09:32 nm-ws kernel: [520393.938838] usb 7-2: Product: nRF52 USB CDC Demo
Nov 27 09:09:32 nm-ws kernel: [520393.938841] usb 7-2: Manufacturer: Nordic Semiconductor
Nov 27 09:09:32 nm-ws kernel: [520393.938843] usb 7-2: SerialNumber: 796cadf8f13bbb37
Nov 27 09:09:32 nm-ws kernel: [520393.940987] cdc_acm 7-2:1.0: ttyACM1: USB ACM device

Steve

1061 - 1080 of 7591