Date   

Nucleo STM32F411RE PWM support

Florian Hester
 

Hello,

When i look at the documentation of the Nucleo F411RE board at:

https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html

I can see PWM as a supported feature. However,  the board YAML file (boards/arm/nucleo_f411re.yml) does not list PWM as supported and the board DTS (boards/arm/nucleo_f411re/nucleo_f411re.dts) does not enable any PWM device present on the hardware.

I've tried using an overlay to enable it anyway (the timers and the pwms), this compiles successfully and flashes (via JLink) successfully, but using the PWM API (or the shell pwm commands) does not appear to have any effect (no output pulse).

I have tried the PWM functionality in ARM mbed, where it works.

Why does Zephyr not have support for PWM on this board?


Florian


Adding linker options

Rob Meades
 

I would like to add a linker option (-Xlinker --wrap=blah) to my Zephyr build, without editing the main Zephyr files, just append some to the usual linker options for my specific build.

How would I go about doing that?

Rob


API meeting: agenda

Carles Cufi
 


Re: Using an external DTS binding for an out-of-tree driver

Diogo Correia
 

Thanks for both the replies. I was looking initially in the "Devicetree HOWTOs", would never remember to look in custom board related documentation. I had already tried to reply Kumar, by using groups.io web interface, but I guess it didn't work. After Kumar's reply I solved the issue by creating a dts directory to the project's root and adding it to CMakeLists.txt with:

list(APPEND DTS_ROOT
${CMAKE_CURRENT_SOURCE_DIR}/dts
)

Now, after Henrik's reply, I know it was unnecessary to add the directory to CMake. So thanks again to both of you.

Kind regards,
Diogo Correia


Re: Using an external DTS binding for an out-of-tree driver

Henrik Brix Andersen
 

Hi Diogo,

Please have a look at the documentation for creating custom devicetree definitions:
https://docs.zephyrproject.org/latest/application/index.html#devicetree-definitions

You can put the ‘dts’ folder in the application folder and it will automatically be picked up. A few examples in-tree of this:
- https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/drivers/espi/dts
- https://github.com/zephyrproject-rtos/zephyr/tree/master/tests/drivers/gpio/gpio_basic_api/dts
- https://github.com/zephyrproject-rtos/zephyr/tree/master/tests/drivers/regulator/fixed/dts

You can also do board-specific bindings:
- https://github.com/zephyrproject-rtos/zephyr/tree/master/boards/arm/arty/dts

Regards,
Brix
--
Henrik Brix Andersen

On 9 Nov 2020, at 17.18, diogo.correia@fraunhofer.pt wrote:

[Edited Message Follows]

Hi!

I'm developing an out-of-tree driver for Zephyr, that I would like to configure using the board overlay file (just like a normal driver in Zephyr). Is there a way to add an external DTS binding file into the project? Or do I need to modify the zephyr's source code (by adding the .yaml into /dts/bindings)?

Kind regards,
Diogo Correia


Re: Using an external DTS binding for an out-of-tree driver

Kumar Gala
 

On Nov 9, 2020, at 10:18 AM, diogo.correia@fraunhofer.pt wrote:

[Edited Message Follows]

Hi!

I'm developing an out-of-tree driver for Zephyr, that I would like to configure using the board overlay file (just like a normal driver in Zephyr). Is there a way to add an external DTS binding file into the project? Or do I need to modify the zephyr's source code (by adding the .yaml into /dts/bindings)?

Kind regards,
Diogo Correia
Have you looked at:

https://docs.zephyrproject.org/latest/application/index.html#custom-board-devicetree-and-soc-definitions
https://docs.zephyrproject.org/latest/application/index.html#devicetree-definitions

- k


Using an external DTS binding for an out-of-tree driver

Diogo Correia
 
Edited

Hi!
 
I'm developing an out-of-tree driver for Zephyr, that I would like to configure using the board overlay file (just like a normal driver in Zephyr). Is there a way to add an external DTS binding file into the project? Or do I need to modify the zephyr's source code (by adding the .yaml into /dts/bindings)?
 
Kind regards,
Diogo Correia
 


How to read and write GPIO pins on nRF5340 #gpio

mohamed.belaroussi@...
 

Hello,

Can someone please tell how to read/write to GPIO pins (ports P0 and P1)?
I am using zephyr and NRF Connect v1.30

Thank you.

Kind regards

Mohamed Belaroussi


CPU frequency and RISC-V boards

Peter Kietzmann
 

Dear community,

how is the CPU frequency configured in zephyr? I found `clock-frequency`
configurations for `cpu0` in different device tree source files. This is
missing for hifive1_revb or rv32m1_vega_zero_riscy, however,
hifive1_revb defines `clock-frequency = <16000000>` (16 MHz) in multiple
peripheral structures. Is this the CPU frequency? The platform is
supposed to run with up to 320 MHz, though.

More specifically, I would like to run both platforms with maximum
speed. How can I achieve that? I'd be happy about any advice :).

Cheers
Peter


Re: Cortex support for OpenISA VEGAboard?

Peter Kietzmann
 

Thanks for the fast response, Henrik!

Best
Peter


Am 04.11.20 um 23:51 schrieb Henrik Brix Andersen:

Hi Peter,

Until recently there was an open draft PR adding support for the CM4 core within the RV32M1:
https://github.com/zephyrproject-rtos/zephyr/pull/27497

Unfortunately it was closed due to inactivity.

Regards,
Brix
--
Henrik Brix Andersen

On 4 Nov 2020, at 12.15, Peter Kietzmann <peter.kietzmann@haw-hamburg.de> wrote:

Dear community,

is there support for operating the OpenISA VEGAboard with the Cortex M4F
or Cortex M0+ processors? If yes, can someone point me to the
development procedure? If no, is anyone working on that?

Cheers
Peter








--
Peter Kietzmann

Hamburg University of Applied Sciences
Dept. Informatik, Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49-40-42875-8426
Web: http://www.haw-hamburg.de/inet


Re: Cortex support for OpenISA VEGAboard?

Henrik Brix Andersen
 

Hi Peter,

Until recently there was an open draft PR adding support for the CM4 core within the RV32M1:
https://github.com/zephyrproject-rtos/zephyr/pull/27497

Unfortunately it was closed due to inactivity.

Regards,
Brix
--
Henrik Brix Andersen

On 4 Nov 2020, at 12.15, Peter Kietzmann <peter.kietzmann@haw-hamburg.de> wrote:

Dear community,

is there support for operating the OpenISA VEGAboard with the Cortex M4F
or Cortex M0+ processors? If yes, can someone point me to the
development procedure? If no, is anyone working on that?

Cheers
Peter





Cortex support for OpenISA VEGAboard?

Peter Kietzmann
 

Dear community,

is there support for operating the OpenISA VEGAboard with the Cortex M4F
or Cortex M0+ processors? If yes, can someone point me to the
development procedure? If no, is anyone working on that?

Cheers
Peter


Re: set a pin as out

Erwan Gouriou
 

Hi Sarvg,

To configure a pin in a gpio mode, please have a look to the gpio API (you'll find exemples under tests/drivers/gpio)

Chevets
Erwan


Le mar. 3 nov. 2020 à 18:49, <sarvg@...> a écrit :
Hello,
How can i set an gpio pin as output? Is there any examples or tutorials for this?
For example
PIN: PB_12 in St nucleo H743zi2
 
Thanks for your help
 
sarvg 


Re: MCUboot placed to immutable flash #nrf52840 #crypto #dts

Bolivar, Marti
 

In general, that's left as an exercise for the user, as far as I know.

"Nikos Karamolegkos via lists.zephyrproject.org"
<nkaram=ics.forth.gr@lists.zephyrproject.org> writes:

Hello, I am studying this ( https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.zephyrproject.org%2Fmcuboot-security-part-1%2F&;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C5786fbc8d5064bb910c308d87f42f246%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637399274195312166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=kj5gkT%2BTyB7To%2BLmZE%2FvKojeHKTTTW3Sqd%2FL%2F91Wx50%3D&amp;reserved=0 ) which mentions that the MCUboot is placed to immutable section of flash. How is this implemented? I can not see anywhere information about immutable MCUboot partition.



set a pin as out

sarvg@...
 

Hello,
How can i set an gpio pin as output? Is there any examples or tutorials for this?
For example
PIN: PB_12 in St nucleo H743zi2
 
Thanks for your help
 
sarvg 


Re: zephyr API to read the nRF5340 die temperature #nrf5340

Martin Kozusky
 

Hi Mohamed,
i think
#include <drivers/sensor.h>
with standard #include <zephyr.h> etc
should work.

Martin


Dne 02.11.2020 v 9:37 Mohamed Belaroussi napsal(a):

Hi Martin,

Thank you for sharing the snippet of your MCU temperature code.
I will let you know how I got on when I get a chance to try it.
Any specific #include that this code requires?

Kind regards
Mohamed 

On Fri, Oct 30, 2020 at 2:11 PM Martin Kozusky <news@...> wrote:
Hi,
try this, I hope it will work

      #define TEMP_SENSOR_NAME "TEMP_0"
      int valid = 0;
       const struct device *tempSensor device_get_binding(TEMP_SENSOR_NAME);
       sensor_value sensor_val;
        int rc = sensor_sample_fetch(tempSensor);
        if (rc == 0) {
            rc = sensor_channel_get(tempSensor, SENSOR_CHAN_DIE_TEMP,&sensor_val);
        }else{
            valid=0;
        }
        if (rc == 0) {
            double temp = sensor_val.val1 + sensor_val.val2/1000000.0;
            //printk("Temp: %d.%d\n", sensor_val.val1, sensor_val.val2/10000);
            valid=1;
        }else{
            valid=0;
        }

you also need to enable
CONFIG_SENSOR=y
CONFIG_TEMP_NRF5=y
in prj.conf

Martin

Dne 30.10.2020 v 9:16 Mohamed Belaroussi napsal(a):
Hi Martin.
If you have some code that you are willing to share then please share it to save time.
Thank you.

Kind regards
Mohamed


On Thu, Oct 29, 2020 at 9:15 PM Martin Kozusky <news@...> wrote:
Hi,
I would recommend looking at samples\bluetooth\peripheral_ht\src  
I managed to create my code for nrf52832  based on that sample.  If you have problems with that sample, I can paste some code here.

Martin

Dne 29.10.2020 v 15:45 mohamed.belaroussi@... napsal(a):

Hello,

I am looking for some some nRF5340 example code that reads the nRF5340 die temperature using zephyr APIs.

I've looked at previous posts but I could only find this one https://devzone.nordicsemi.com/f/nordic-q-a/56171/how-to-get-die-temperature-on-nrf52832-using-zephyr from 10 months ago that stated none existed.
I am hoping someone, somewhere musty have done something similar.

Thank you.

Kind regards




Please consider the environment before printing this email.
*********************************************************************
This communication may contain information which is confidential, personal and/or privileged. It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited. If you have received it in error please contact the sender immediately by return e-mail. Please then delete the e-mail and any copies of it and do not use or disclose its contents to any person.
Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them. Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.
This message has been checked for viruses on behalf of the company.
*********************************************************************


G4S Regional Management (UK&I) Limited, Registered Office: Southside, 105 Victoria Street, London, SW1E 6QT. Registered in England No. 3189802. G4S Care and Justice Services (UK) Limited, trading as G4S Central Government Services, Registered in England No. 390328. G4S Health Services (UK) Limited, Registered in England No. 5121608. G4S Government and Outsourcing Services (UK) Limited, trading as G4S Outsourcing Services, Registered in England No.3175173. G4S Facilities Management (UK) Limited, Registered in England No. 3333860. G4S Investigation Solutions (UK) Limited, Registered in England No. 3749819. G4S Monitoring Technologies Limited, Registered in England No. 2626613. G4S Ordnance Management Limited, Registered in England No. 7068855. G4S Risk Management Limited, Registered in England No. 1540857. G4S Secure Solutions (Iraq) Limited, Registered in England No.5128617. G4S Risk Consulting Limited, Registered in England No. 4047630. The Registered office of all the above companies is Southside, 105 Victoria Street, London, SW1E 6QT. G4S Aviation Services (UK) Limited, Registered in England No. 2837136. G4S Secure Solutions (UK) Limited, Registered in England No. 1046019. G4S Security Services (UK) Limited, Registered in England No.2380900. G4S Gurkha Services (UK) Limited, Registered in England No.6304482. G4S Cash Solutions (UK) Limited, Registered in England No.354883. G4S Cash Centres (UK) Limited, Registered in England No.1485104. G4S Bullion Solutions (UK) Limited, Registered in England No.7860383. The Registered office of all the above companies is Sutton Park House, 15 Carshalton Road, Sutton, Surrey SM1 4LD. 




Please consider the environment before printing this email.
*********************************************************************
This communication may contain information which is confidential, personal and/or privileged. It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited. If you have received it in error please contact the sender immediately by return e-mail. Please then delete the e-mail and any copies of it and do not use or disclose its contents to any person.
Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them. Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.
This message has been checked for viruses on behalf of the company.
*********************************************************************


G4S Regional Management (UK&I) Limited, Registered Office: Southside, 105 Victoria Street, London, SW1E 6QT. Registered in England No. 3189802. G4S Care and Justice Services (UK) Limited, trading as G4S Central Government Services, Registered in England No. 390328. G4S Health Services (UK) Limited, Registered in England No. 5121608. G4S Government and Outsourcing Services (UK) Limited, trading as G4S Outsourcing Services, Registered in England No.3175173. G4S Facilities Management (UK) Limited, Registered in England No. 3333860. G4S Investigation Solutions (UK) Limited, Registered in England No. 3749819. G4S Monitoring Technologies Limited, Registered in England No. 2626613. G4S Ordnance Management Limited, Registered in England No. 7068855. G4S Risk Management Limited, Registered in England No. 1540857. G4S Secure Solutions (Iraq) Limited, Registered in England No.5128617. G4S Risk Consulting Limited, Registered in England No. 4047630. The Registered office of all the above companies is Southside, 105 Victoria Street, London, SW1E 6QT. G4S Aviation Services (UK) Limited, Registered in England No. 2837136. G4S Secure Solutions (UK) Limited, Registered in England No. 1046019. G4S Security Services (UK) Limited, Registered in England No.2380900. G4S Gurkha Services (UK) Limited, Registered in England No.6304482. G4S Cash Solutions (UK) Limited, Registered in England No.354883. G4S Cash Centres (UK) Limited, Registered in England No.1485104. G4S Bullion Solutions (UK) Limited, Registered in England No.7860383. The Registered office of all the above companies is Sutton Park House, 15 Carshalton Road, Sutton, Surrey SM1 4LD. 



API meeting: agenda

Carles Cufi
 

Hi all,

Agenda for tomorrow.

Note: the API and component naming conventions (https://github.com/zephyrproject-rtos/zephyr/issues/29569) discussion has been postponed until next week since tomorrow the availability of US-based engineers is restricted.

- devicetree-based device definitions and dependency representations
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/29644

- Reminder and questions about: API to correlate system time with external time sources and translate uptime to wall-clock time
- PR https://github.com/zephyrproject-rtos/zephyr/pull/28977

- Introduction of a new work queue
- PR https://github.com/zephyrproject-rtos/zephyr/pull/29618

and then, time permitting we'd like to follow-up on pinctrl:

- Pinmux and pinctrl API: Decide what the priorities for this are, and how to get to LTS with it
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/22748

Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d

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


Network forum agenda

Jukka Rissanen
 


MCUboot placed to immutable flash #nrf52840 #crypto #dts

Nikos Karamolegkos
 

Hello, I am studying this which mentions that the MCUboot is placed to immutable section of flash. How is this implemented? I can not see anywhere information about immutable MCUboot partition.


Re: zephyr API to read the nRF5340 die temperature #nrf5340

Martin Kozusky
 

Hi,
try this, I hope it will work

      #define TEMP_SENSOR_NAME "TEMP_0"
      int valid = 0;
       const struct device *tempSensor device_get_binding(TEMP_SENSOR_NAME);
       sensor_value sensor_val;
        int rc = sensor_sample_fetch(tempSensor);
        if (rc == 0) {
            rc = sensor_channel_get(tempSensor, SENSOR_CHAN_DIE_TEMP,&sensor_val);
        }else{
            valid=0;
        }
        if (rc == 0) {
            double temp = sensor_val.val1 + sensor_val.val2/1000000.0;
            //printk("Temp: %d.%d\n", sensor_val.val1, sensor_val.val2/10000);
            valid=1;
        }else{
            valid=0;
        }

you also need to enable
CONFIG_SENSOR=y
CONFIG_TEMP_NRF5=y
in prj.conf

Martin

Dne 30.10.2020 v 9:16 Mohamed Belaroussi napsal(a):

Hi Martin.
If you have some code that you are willing to share then please share it to save time.
Thank you.

Kind regards
Mohamed


On Thu, Oct 29, 2020 at 9:15 PM Martin Kozusky <news@...> wrote:
Hi,
I would recommend looking at samples\bluetooth\peripheral_ht\src  
I managed to create my code for nrf52832  based on that sample.  If you have problems with that sample, I can paste some code here.

Martin

Dne 29.10.2020 v 15:45 mohamed.belaroussi@... napsal(a):

Hello,

I am looking for some some nRF5340 example code that reads the nRF5340 die temperature using zephyr APIs.

I've looked at previous posts but I could only find this one https://devzone.nordicsemi.com/f/nordic-q-a/56171/how-to-get-die-temperature-on-nrf52832-using-zephyr from 10 months ago that stated none existed.
I am hoping someone, somewhere musty have done something similar.

Thank you.

Kind regards




Please consider the environment before printing this email.
*********************************************************************
This communication may contain information which is confidential, personal and/or privileged. It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited. If you have received it in error please contact the sender immediately by return e-mail. Please then delete the e-mail and any copies of it and do not use or disclose its contents to any person.
Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them. Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.
This message has been checked for viruses on behalf of the company.
*********************************************************************


G4S Regional Management (UK&I) Limited, Registered Office: Southside, 105 Victoria Street, London, SW1E 6QT. Registered in England No. 3189802. G4S Care and Justice Services (UK) Limited, trading as G4S Central Government Services, Registered in England No. 390328. G4S Health Services (UK) Limited, Registered in England No. 5121608. G4S Government and Outsourcing Services (UK) Limited, trading as G4S Outsourcing Services, Registered in England No.3175173. G4S Facilities Management (UK) Limited, Registered in England No. 3333860. G4S Investigation Solutions (UK) Limited, Registered in England No. 3749819. G4S Monitoring Technologies Limited, Registered in England No. 2626613. G4S Ordnance Management Limited, Registered in England No. 7068855. G4S Risk Management Limited, Registered in England No. 1540857. G4S Secure Solutions (Iraq) Limited, Registered in England No.5128617. G4S Risk Consulting Limited, Registered in England No. 4047630. The Registered office of all the above companies is Southside, 105 Victoria Street, London, SW1E 6QT. G4S Aviation Services (UK) Limited, Registered in England No. 2837136. G4S Secure Solutions (UK) Limited, Registered in England No. 1046019. G4S Security Services (UK) Limited, Registered in England No.2380900. G4S Gurkha Services (UK) Limited, Registered in England No.6304482. G4S Cash Solutions (UK) Limited, Registered in England No.354883. G4S Cash Centres (UK) Limited, Registered in England No.1485104. G4S Bullion Solutions (UK) Limited, Registered in England No.7860383. The Registered office of all the above companies is Sutton Park House, 15 Carshalton Road, Sutton, Surrey SM1 4LD. 


341 - 360 of 2659