Date   

Re: [Zephyr-devel] Zephyr SDK 0.12.0-beta-2 available for testing

Katsuhiro Suzuki <katsuhiro@...>
 

Hello,

Thanks for great works! I'm trying:
zephyr-toolchain-riscv64-0.12.0-beta-2-x86_64-linux-setup.run

Currently, it works fine for me.

Best Regards,
Katsuhiro Suzuki

On 2020/11/20 2:02, Kumar Gala wrote:
Hi,
Latest version of the SDK can be found here:
https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.12.0-beta-2
Please download and try things out and report any issues. Please report issues here:
https://github.com/zephyrproject-rtos/sdk-ng/issues
Known issues (these are on the Zephyr side):
* some xtensa platforms may need updating w/regards to Zephyr & Xtensa HAL
[ https://github.com/zephyrproject-rtos/zephyr/pull/23142 ]
* known issue with arm64 and linking C++ & newlib:
[ https://github.com/zephyrproject-rtos/zephyr/issues/28650 ]
Changes since the last release (beta-1):
• Enable multilibs for SPARC LEON
• DWARF binutils bug fix
• Update to openocd 20201109 snapshot
Current plan is to release SDK 0.12.0 towards the end of November.
- k


Zephyr SDK 0.12.0-beta-2 available for testing

Kumar Gala
 

Hi,

Latest version of the SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.12.0-beta-2

Please download and try things out and report any issues. Please report issues here:

https://github.com/zephyrproject-rtos/sdk-ng/issues

Known issues (these are on the Zephyr side):

* some xtensa platforms may need updating w/regards to Zephyr & Xtensa HAL
[ https://github.com/zephyrproject-rtos/zephyr/pull/23142 ]

* known issue with arm64 and linking C++ & newlib:
[ https://github.com/zephyrproject-rtos/zephyr/issues/28650 ]

Changes since the last release (beta-1):

• Enable multilibs for SPARC LEON
• DWARF binutils bug fix
• Update to openocd 20201109 snapshot


Current plan is to release SDK 0.12.0 towards the end of November.

- k


Build zephyr with Metaware toolchain

Jacob Avraham
 

Hi,
I'm trying to build the hello_world example from Zephyr 2.4.0 release to the ARC HSDK board using my installed MetaWare toolchain, but the build fails.
I did so by setting the environment variable ZEPHYR_TOOLCHAIN_VARIANT to arcmwdt and ARCMWDT_TOOLCHAIN_PATH to $METAWARE_ROOT/../  per the instructions in the Zephyr documentation.
It seems that the code is compiled for the ARC EM processor instead of the ARC HS, and at some point the compilation fails.

Does anyone have any experience in building with the Metaware toolchain for an ARC EVK board that can shed some light here?

Thanks,
Jacob


API meeting cancelled today

Carles Cufi
 

Hi all,

Due to a conflict I have had to cancel the API meeting today.
Next week we will have the meeting as usual.

Regards,

Carles


new facility for formatted output

Peter A. Bigot
 

With the merge of https://github.com/zephyrproject-rtos/zephyr/pull/29876 Zephyr printk, shell_printf, minimal libc sprintf, and some other in-tree facilities use a common formatting functionality that supports almost everything in C18 *printf, with Kconfig options to reduce the code size impact based on controlling feature availability.

That PR added a C99 stdio value formatter capability named cbprintf() (plus related variants) where generated text is emitted through a callback. This allows generation of arbitrarily long output without a buffer, functionality that is core to printk, logging, and other system and application needs.

The formater supports most C99 specifications, excluding:
  • %L[aefg] long double conversion
  • wide character output
The new solution is derived from z_prf(), which had the most complete functionality available. Format parsing has been reimplemented, while floating point conversion has been retained and enhanced.

Kconfig options allow disabling features like floating-point conversion if they are not necessary.

Benefits include:
No more inconsistencies between printk, logging, and shell formatting capabilities.
  • Reduced inconsistencies due to toolchain libc capabilities.
  • Simplified (toolchain-independent) formatting feature selection via Kconfig.
  • Core infrastructure can avoid duplication with libc printf by using cbprintf variants.
  • Potentially a path to resolving #18351 and related issues, as the infrastructure can tell a caller the total size of arguments to the conversion string.
  • Fixed bugs with several specifications.
Costs include:
  • Applications that used only printk with no extra features consume more code space than the previous implementation.
More information is available at: https://docs.zephyrproject.org/latest/reference/misc/formatted_output.html

You may see either an increase or a decrease in code size depending on what your application uses.  Some code size can be reduced by switching in-tree use of snprintf to snprintfcb to avoid pulling in libc formatters.

I expect there'll be a burn-in period while we identify Kconfig settings that have to change to maintain compatibility.  Please mention me (@pabigot) in any issues or slack questions that you have about this.

Peter


Re: Nucleo STM32F411RE PWM support

Florian Hester
 

Hello,

I have experimented a bit more, and have opened a bug report:

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

Thanks for the help so far :)

Florian

Op 13/11/2020 om 14:28 schreef Erwan Gouriou:

Thanks for feedback.

 I don't see a particular reason why some channels would not work.
For pins, there's alway a possibility of pin conflicts (as I can see that pa8 is also used on i2c2).
So please take care to this.

Otherwise, don't hesitate to raise a bug if things don't work as expected.

Erwan




On Thu, 12 Nov 2020 at 18:37, Florian Hester <florian@celaeno.org <mailto:florian@celaeno.org>> wrote:

Hello,

I've added the pin PA8 to PWM of timers1:

timers1: timers@40010000 {
             status = "okay";

             pwm {
                 status = "okay";
                 pinctrl-0 = <&tim1_ch1_pwm_pa8>;
             };
  };

This did not work (no output pulse, no error logged either).

However, the PA5 pin (configured like above for PWM of timers2) did
work, and now i have a nice 100 microsecond period pulse on that pin.

I've tried the second channel (tim1_ch2_pwm_pa9) of the first
timer, but
that one (like the first channel) also does not work (no output
pulse).

Im going try more of the PWM channels, to see what is working and
what
is not, but it seems like the first pwm device (PWM_1, as part of
timers1) is not working, any reason why not?

Florian

Op 12/11/2020 om 17:03 schreef Erwan Gouriou:
> Hi Florian,
>
> You also need to configure a pin, something like:
> &timers2 {
>            status = "okay";
>
>            pwm2: pwm {
>            status = "okay";
> +           pinctrl-0 = <&tim2_ch1_pwm_pa5>;
>            };
> };
>
> Please let us know if this was helpful.
>
> Erwan
>
> On Thu, 12 Nov 2020 at 13:58, Florian Hester via
> lists.zephyrproject.org <http://lists.zephyrproject.org>
<http://lists.zephyrproject.org <http://lists.zephyrproject.org>>
> <florian=celaeno.org@lists.zephyrproject.org
<mailto:celaeno.org@lists.zephyrproject.org>
> <mailto:celaeno.org@lists.zephyrproject.org
<mailto:celaeno.org@lists.zephyrproject.org>>> wrote:
>
>     Hello,
>
>     I have used the following overlay:
>
>     / {
>          soc {
>              timers1: timers@40010000 {
>                  status = "okay";
>
>                  pwm {
>                      status = "okay";
>                  };
>              };
>
>              timers2: timers@40000000 {
>                  status = "okay";
>
>                  pwm {
>                      status = "okay";
>                  };
>              };
>
>              timers3: timers@40000400 {
>                  status = "okay";
>
>                  pwm {
>                      status = "okay";
>                  };
>              };
>
>              timers4: timers@40000800 {
>                  status = "okay";
>
>                  pwm {
>                      status = "okay";
>                  };
>              };
>          };
>     };
>
>     The prj.conf file contains the following regarding PWM:
>
>     CONFIG_PWM=y
>     CONFIG_PWM_STM32=y
>
>     I used the following code to test:
>
>          auto dev_pwm = device_get_binding("PWM_1");
>
>          if (dev_pwm != nullptr)
>          {
>              LOG_INF("Have PWM device.");
>
>              int ret = pwm_pin_set_usec(dev_pwm, 1, 100, 50, 0);
>
>              if (ret != 0)
>              {
>                  LOG_ERR("Could not set PWM.");
>              }
>              else
>              {
>                  LOG_INF("PWM set.");
>              }
>          }
>
>     The output:
>
>     [00:00:00.006,000] <inf> main: Have PWM device.
>     [00:00:00.006,000] <inf> main: PWM set.
>
>     I am measuring pin D7 on the board (PA8 for the chip), and
no pulse.
>
>     Florian
>
>     Op 12/11/2020 om 08:36 schreef Adam Podogrocki:
>     > Hi Florian,
>     >
>     > have you set /status/ of the appropriate Timer & PWM device to
>     "okay"?
>     > Have you activated the PWM driver in Zephyr Menu Config?
Have you
>     > successfully got device binding in the source code?
>     >
>     > Cheers,
>     > Adam
>     >
>     > On Thu, 12 Nov 2020 at 01:54, Florian Hester via
>     > lists.zephyrproject.org <http://lists.zephyrproject.org>
<http://lists.zephyrproject.org <http://lists.zephyrproject.org>>
>     <http://lists.zephyrproject.org
<http://lists.zephyrproject.org> <http://lists.zephyrproject.org
<http://lists.zephyrproject.org>>>
>     > <florian=celaeno.org@lists.zephyrproject.org
<mailto:celaeno.org@lists.zephyrproject.org>
>     <mailto:celaeno.org@lists.zephyrproject.org
<mailto:celaeno.org@lists.zephyrproject.org>>
>     > <mailto:celaeno.org@lists.zephyrproject.org
<mailto:celaeno.org@lists.zephyrproject.org>
>     <mailto:celaeno.org@lists.zephyrproject.org
<mailto:celaeno.org@lists.zephyrproject.org>>>> wrote:
>     >
>     >     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
<https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html>
>   
 <https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html
<https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html>>
>     >
>   
  <https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html
<https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html>
>   
 <https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html
<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
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>
>
>     
>
>


Warning from MCUboot: Not enough space to run swap upgrade #nrf52832 #mcuboot #fota

namor.dev@...
 

Dear All,
 
I'm using the nRF Connect SDK and try to do a FOTA upgrade to my nRF52832, with MCUboot installed.
After I downloaded the binary via nRF Connect Android App to the device, i get "<wrn> mcuboot: Not enough free space to run swap upgrade".
And the device continues to start with the old image.
 
Here is my setup:
- nRF Connect SDK v1.2.0 (Zephyr v2.1.99, mcuboot v1.4.99)
- nRF52-DK (nRF52832)
- Windows 8.1
 
I did not modify the flash partitions in the device tree (default values from nrf52_pca10040.dts) and also no changes in MCUboot configuration (boot/zephyr/prj.conf).
 
These are the steps I did:
2. Build it with west (which automatically builds the bootloader and signs my application as far is I understood).
3. Flash the merged.hex (which includes also the bootloader) to device with JLink
4. Do some changes and build an update of my application. This is the output (tail) of "west build -b nrf52_pca10040":
 
[230/241] Building C object zephyr/kernel/CMakeFiles/kernel.dir/poll.c.obj
[231/241] Linking C static library zephyr\kernel\libkernel.a
[232/241] Linking C executable zephyr\zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      229348 B     232960 B     98.45%
            SRAM:       57060 B        64 KB     87.07%
        IDT_LIST:         168 B         2 KB      8.20%
[233/241] Generating linker_pass_final.cmd
[234/241] Generating isr_tables.c
[235/241] Building C object zephyr/CMakeFiles/zephyr_final.dir/misc/empty_file.c.obj
[236/241] Building C object zephyr/CMakeFiles/zephyr_final.dir/isr_tables.c.obj
[237/241] Linking C executable zephyr\zephyr.elf
[238/241] Generating zephyr/mcuboot_primary.hex
[239/241] Generating zephyr/mcuboot_primary_app.hex
[240/241] Generating ../../zephyr/app_update.bin, ../../zephyr/app_signed.hex, ../../zephyr/app_test_update.hex, ../../zephyr/app_moved_test_update.hex
[241/241] Generating zephyr/merged.hex
 
 
5. Perform the update with nRF Connect App and app_update.bin. Transfer worked well but after the device resets, I got the following output with the previously described warning:
*** Booting Zephyr OS build v2.1.99-ncs1  ***
[00:00:00.003,326] <inf> mcuboot: Starting bootloader
[00:00:00.009,704] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.020,385] <inf> mcuboot: Boot source: none
[00:00:00.026,184] <inf> mcuboot: Swap type: test
[00:00:00.356,567] <wrn> mcuboot: Not enough free space to run swap upgrade
[00:00:00.684,509] <inf> mcuboot: Bootloader chainload address offset: 0xc000
[00:00:00.692,474] <inf> mcuboot: Jumping to the first image slot
 
 
I know, the FLASH usage of 98% is bad. Interestingly enough, when I build in Segger Embedded Studio, FLASH usage of 43% is displayed. Is this because I only see the size of my application (not the merged one)?
When I disable some modules to decrease the memory footprint, the FOTA update works well! But then my application has not it's full functionality.
 
Has anyone some ideas I can do? Do I need to modify the device tree or the mcuboot configuration? Why does it not work, altough the FLASH is not 100% full?
 
Any help is appreciated.
Roman
 


Re: Nucleo STM32F411RE PWM support

Erwan Gouriou
 

Thanks for feedback.

 I don't see a particular reason why some channels would not work.
For pins, there's alway a possibility of pin conflicts (as I can see that pa8 is also used on i2c2).
So please take care to this.

Otherwise, don't hesitate to raise a bug if things don't work as expected.

Erwan




On Thu, 12 Nov 2020 at 18:37, Florian Hester <florian@...> wrote:
Hello,

I've added the pin PA8 to PWM of timers1:

timers1: timers@40010000 {
             status = "okay";

             pwm {
                 status = "okay";
                 pinctrl-0 = <&tim1_ch1_pwm_pa8>;
             };
  };

This did not work (no output pulse, no error logged either).

However, the PA5 pin (configured like above for PWM of timers2) did
work, and now i have a nice 100 microsecond period pulse on that pin.

I've tried the second channel (tim1_ch2_pwm_pa9) of the first timer, but
that one (like the first channel) also does not work (no output pulse).

Im going try more of the PWM channels, to see what is working and what
is not, but it seems like the first pwm device (PWM_1, as part of
timers1) is not working, any reason why not?

Florian

Op 12/11/2020 om 17:03 schreef Erwan Gouriou:
> Hi Florian,
>
> You also need to configure a pin, something like:
> &timers2 {
>            status = "okay";
>
>            pwm2: pwm {
>            status = "okay";
> +           pinctrl-0 = <&tim2_ch1_pwm_pa5>;
>            };
> };
>
> Please let us know if this was helpful.
>
> Erwan
>
> On Thu, 12 Nov 2020 at 13:58, Florian Hester via
> lists.zephyrproject.org <http://lists.zephyrproject.org>
> <florian=celaeno.org@...
> <mailto:celaeno.org@...>> wrote:
>
>     Hello,
>
>     I have used the following overlay:
>
>     / {
>          soc {
>              timers1: timers@40010000 {
>                  status = "okay";
>
>                  pwm {
>                      status = "okay";
>                  };
>              };
>
>              timers2: timers@40000000 {
>                  status = "okay";
>
>                  pwm {
>                      status = "okay";
>                  };
>              };
>
>              timers3: timers@40000400 {
>                  status = "okay";
>
>                  pwm {
>                      status = "okay";
>                  };
>              };
>
>              timers4: timers@40000800 {
>                  status = "okay";
>
>                  pwm {
>                      status = "okay";
>                  };
>              };
>          };
>     };
>
>     The prj.conf file contains the following regarding PWM:
>
>     CONFIG_PWM=y
>     CONFIG_PWM_STM32=y
>
>     I used the following code to test:
>
>          auto dev_pwm = device_get_binding("PWM_1");
>
>          if (dev_pwm != nullptr)
>          {
>              LOG_INF("Have PWM device.");
>
>              int ret = pwm_pin_set_usec(dev_pwm, 1, 100, 50, 0);
>
>              if (ret != 0)
>              {
>                  LOG_ERR("Could not set PWM.");
>              }
>              else
>              {
>                  LOG_INF("PWM set.");
>              }
>          }
>
>     The output:
>
>     [00:00:00.006,000] <inf> main: Have PWM device.
>     [00:00:00.006,000] <inf> main: PWM set.
>
>     I am measuring pin D7 on the board (PA8 for the chip), and no pulse.
>
>     Florian
>
>     Op 12/11/2020 om 08:36 schreef Adam Podogrocki:
>     > Hi Florian,
>     >
>     > have you set /status/ of the appropriate Timer & PWM device to
>     "okay"?
>     > Have you activated the PWM driver in Zephyr Menu Config? Have you
>     > successfully got device binding in the source code?
>     >
>     > Cheers,
>     > Adam
>     >
>     > On Thu, 12 Nov 2020 at 01:54, Florian Hester via
>     > lists.zephyrproject.org <http://lists.zephyrproject.org>
>     <http://lists.zephyrproject.org <http://lists.zephyrproject.org>>
>     > <florian=celaeno.org@...
>     <mailto:celaeno.org@...>
>     > <mailto:celaeno.org@...
>     <mailto:celaeno.org@...>>> wrote:
>     >
>     >     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
>     <https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html>
>     >   
>      <https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html
>     <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
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>
>
>     
>
>


Debugging Zephyr using no able to stop at specific source line after init.c #debugging

ngbk1993@...
 
Edited


Hi All,

I'm trying to enable Zephyr with a SoC(4-cores CPU) that not listed in the Zephyr page.

Currently I'm able to step the code using the ARM Development studio and able to step (single step)
until the source line at zephyrproject/zephyr/kernel/init.c:233  (printk(*** Botting Zephyr OS Build .......))

The zephyr will always jump to system halt when i'm trying to
1) Set a break point after the line 233 
2) Stepping source line 

When I try to single step, it can go very far beyond line of init.c:233.

Then I try to edit the init.c and place a forever while loop before line:233, hopefully the program will help me to stop at line 233 without me to do a single step for debug, but still no luck, zephyr will still jump into system halt.

Want to ask Is there any watchdog timer implemented on zephyr that check if zephyr hang?

Regards,
ngbk

PS: Sorry for the incomplete title, Debugging Zephyr using ARMDS and not able to stop at specific source line after init.c


Re: Nucleo STM32F411RE PWM support

Florian Hester
 

Hello,

I've added the pin PA8 to PWM of timers1:

timers1: timers@40010000 {
            status = "okay";

            pwm {
                status = "okay";
                pinctrl-0 = <&tim1_ch1_pwm_pa8>;
            };
 };

This did not work (no output pulse, no error logged either).

However, the PA5 pin (configured like above for PWM of timers2) did work, and now i have a nice 100 microsecond period pulse on that pin.

I've tried the second channel (tim1_ch2_pwm_pa9) of the first timer, but that one (like the first channel) also does not work (no output pulse).

Im going try more of the PWM channels, to see what is working and what is not, but it seems like the first pwm device (PWM_1, as part of timers1) is not working, any reason why not?

Florian

Op 12/11/2020 om 17:03 schreef Erwan Gouriou:

Hi Florian,

You also need to configure a pin, something like:
&timers2 {
           status = "okay";

           pwm2: pwm {
           status = "okay";
+           pinctrl-0 = <&tim2_ch1_pwm_pa5>;
           };
};

Please let us know if this was helpful.

Erwan

On Thu, 12 Nov 2020 at 13:58, Florian Hester via lists.zephyrproject.org <http://lists.zephyrproject.org> <florian=celaeno.org@lists.zephyrproject.org <mailto:celaeno.org@lists.zephyrproject.org>> wrote:

Hello,

I have used the following overlay:

/ {
     soc {
         timers1: timers@40010000 {
             status = "okay";

             pwm {
                 status = "okay";
             };
         };

         timers2: timers@40000000 {
             status = "okay";

             pwm {
                 status = "okay";
             };
         };

         timers3: timers@40000400 {
             status = "okay";

             pwm {
                 status = "okay";
             };
         };

         timers4: timers@40000800 {
             status = "okay";

             pwm {
                 status = "okay";
             };
         };
     };
};

The prj.conf file contains the following regarding PWM:

CONFIG_PWM=y
CONFIG_PWM_STM32=y

I used the following code to test:

     auto dev_pwm = device_get_binding("PWM_1");

     if (dev_pwm != nullptr)
     {
         LOG_INF("Have PWM device.");

         int ret = pwm_pin_set_usec(dev_pwm, 1, 100, 50, 0);

         if (ret != 0)
         {
             LOG_ERR("Could not set PWM.");
         }
         else
         {
             LOG_INF("PWM set.");
         }
     }

The output:

[00:00:00.006,000] <inf> main: Have PWM device.
[00:00:00.006,000] <inf> main: PWM set.

I am measuring pin D7 on the board (PA8 for the chip), and no pulse.

Florian

Op 12/11/2020 om 08:36 schreef Adam Podogrocki:
> Hi Florian,
>
> have you set /status/ of the appropriate Timer & PWM device to
"okay"?
> Have you activated the PWM driver in Zephyr Menu Config? Have you
> successfully got device binding in the source code?
>
> Cheers,
> Adam
>
> On Thu, 12 Nov 2020 at 01:54, Florian Hester via
> lists.zephyrproject.org <http://lists.zephyrproject.org>
<http://lists.zephyrproject.org <http://lists.zephyrproject.org>>
> <florian=celaeno.org@lists.zephyrproject.org
<mailto:celaeno.org@lists.zephyrproject.org>
> <mailto:celaeno.org@lists.zephyrproject.org
<mailto:celaeno.org@lists.zephyrproject.org>>> wrote:
>
>     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
<https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html>
>   
 <https://docs.zephyrproject.org/latest/boards/arm/nucleo_f411re/doc/index.html
<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
>
>
>
>
>
>
>
>




Add custom code

sarvg@...
 

Dear community,
ist it possible to add my own file.c , file.h code to my zephyr project? If yes, how can i do that? Any examples or tutorial?
 
Thanks in advance
 
sarvg


Re: Nucleo STM32F411RE PWM support

Erwan Gouriou
 

Hi Florian, 

You also need to configure a pin, something like:
&timers2 {
           status = "okay";

           pwm2: pwm {
           status = "okay";
+           pinctrl-0 = <&tim2_ch1_pwm_pa5>;
           };
};

Please let us know if this was helpful.

Erwan

On Thu, 12 Nov 2020 at 13:58, Florian Hester via lists.zephyrproject.org <florian=celaeno.org@...> wrote:
Hello,

I have used the following overlay:

/ {
     soc {
         timers1: timers@40010000 {
             status = "okay";

             pwm {
                 status = "okay";
             };
         };

         timers2: timers@40000000 {
             status = "okay";

             pwm {
                 status = "okay";
             };
         };

         timers3: timers@40000400 {
             status = "okay";

             pwm {
                 status = "okay";
             };
         };

         timers4: timers@40000800 {
             status = "okay";

             pwm {
                 status = "okay";
             };
         };
     };
};

The prj.conf file contains the following regarding PWM:

CONFIG_PWM=y
CONFIG_PWM_STM32=y

I used the following code to test:

     auto dev_pwm = device_get_binding("PWM_1");

     if (dev_pwm != nullptr)
     {
         LOG_INF("Have PWM device.");

         int ret = pwm_pin_set_usec(dev_pwm, 1, 100, 50, 0);

         if (ret != 0)
         {
             LOG_ERR("Could not set PWM.");
         }
         else
         {
             LOG_INF("PWM set.");
         }
     }

The output:

[00:00:00.006,000] <inf> main: Have PWM device.
[00:00:00.006,000] <inf> main: PWM set.

I am measuring pin D7 on the board (PA8 for the chip), and no pulse.

Florian

Op 12/11/2020 om 08:36 schreef Adam Podogrocki:
> Hi Florian,
>
> have you set /status/ of the appropriate Timer & PWM device to "okay"?
> Have you activated the PWM driver in Zephyr Menu Config? Have you
> successfully got device binding in the source code?
>
> Cheers,
> Adam
>
> On Thu, 12 Nov 2020 at 01:54, Florian Hester via
> lists.zephyrproject.org <http://lists.zephyrproject.org>
> <florian=celaeno.org@...
> <mailto:celaeno.org@...>> wrote:
>
>     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
>     <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
>
>
>
>
>
>     
>
>






Re: Nucleo STM32F411RE PWM support

Florian Hester
 

Hello,

I have used the following overlay:

/ {
    soc {
        timers1: timers@40010000 {
            status = "okay";

            pwm {
                status = "okay";
            };
        };

        timers2: timers@40000000 {
            status = "okay";

            pwm {
                status = "okay";
            };
        };

        timers3: timers@40000400 {
            status = "okay";

            pwm {
                status = "okay";
            };
        };

        timers4: timers@40000800 {
            status = "okay";

            pwm {
                status = "okay";
            };
        };
    };
};

The prj.conf file contains the following regarding PWM:

CONFIG_PWM=y
CONFIG_PWM_STM32=y

I used the following code to test:

    auto dev_pwm = device_get_binding("PWM_1");

    if (dev_pwm != nullptr)
    {
        LOG_INF("Have PWM device.");

        int ret = pwm_pin_set_usec(dev_pwm, 1, 100, 50, 0);

        if (ret != 0)
        {
            LOG_ERR("Could not set PWM.");
        }
        else
        {
            LOG_INF("PWM set.");
        }
    }

The output:

[00:00:00.006,000] <inf> main: Have PWM device.
[00:00:00.006,000] <inf> main: PWM set.

I am measuring pin D7 on the board (PA8 for the chip), and no pulse.

Florian

Op 12/11/2020 om 08:36 schreef Adam Podogrocki:

Hi Florian,

have you set /status/ of the appropriate Timer & PWM device to "okay"? Have you activated the PWM driver in Zephyr Menu Config? Have you successfully got device binding in the source code?

Cheers,
Adam

On Thu, 12 Nov 2020 at 01:54, Florian Hester via lists.zephyrproject.org <http://lists.zephyrproject.org> <florian=celaeno.org@lists.zephyrproject.org <mailto:celaeno.org@lists.zephyrproject.org>> wrote:

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







Re: Nucleo STM32F411RE PWM support

Adam Podogrocki
 

Hi Florian,

have you set status of the appropriate Timer & PWM device to "okay"? Have you activated the PWM driver in Zephyr Menu Config? Have you successfully got device binding in the source code? 

Cheers,
Adam


On Thu, 12 Nov 2020 at 01:54, Florian Hester via lists.zephyrproject.org <florian=celaeno.org@...> wrote:
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









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

361 - 380 of 2693