Date   

Re: [EXT] [Zephyr-users] #nxp #k2x

Andrei Gansari
 

Hello Anton,

 

As I understand you use a custom board that you managed to create out of tree and you’d like to change clock configuration.

The file /soc/arm/nxp_kinetis/k2x/soc.c  is used for all the SoC in Kinetis 2x family.

The functions used in clock_init() can be found here:  zephyr/../modules/hal/nxp/mcux/devices/MK22F51212/fsl_clock.h.

 

So, you need to change soc.c to accommodate your board’s changes and use either Kconfig or Device Tree to differentiate between configurations.

You can use Kconfig to make cpu/board specific changes like, e.g. CONFIG_OSC_LOW_POWER.

Device tree can be used to tell the clock source for a specific peripheral, but I’m not sure about main clock source.

 

 

Regards,

Andrei Gansari

 

From: users@... <users@...> On Behalf Of antoker via lists.zephyrproject.org
Sent: Saturday, May 16, 2020 7:24 PM
To: users@...
Subject: [EXT] [Zephyr-users] #nxp #k2x

 

Caution: EXT Email

Hi all,

I'm new to zephyr and am not sure if this is a correct place to ask questions. But here is my challenge. I've been playing with zephyr for some time now being able to both compile and run sample apps for frdm-k22f board and make my own apps. The next step was to make an out of tree board, which is based on k2x, to my suprise, after digging through /soc/arm/nxp_kinetis/k2x/soc.c i found out that clock_init() for k2x always uses external oscillator so I have a couple of questions:

  1. Is it possible to provide custom implementation of clock_init for my out of tree board which overrides /k2x/soc.c ?
  2. If yes, what is the proper way to do this?

BR

Anton


#nxp #k2x #nxp #k2x

antoker@...
 

Hi all,

I'm new to zephyr and am not sure if this is a correct place to ask questions. But here is my challenge. I've been playing with zephyr for some time now being able to both compile and run sample apps for frdm-k22f board and make my own apps. The next step was to make an out of tree board, which is based on k2x, to my suprise, after digging through /soc/arm/nxp_kinetis/k2x/soc.c i found out that clock_init() for k2x always uses external oscillator so I have a couple of questions:

  1. Is it possible to provide custom implementation of clock_init for my out of tree board which overrides /k2x/soc.c ?
  2. If yes, what is the proper way to do this?

BR

Anton


CPU hang in NMI handler at ISR exits.

Antoine Zen-Ruffinen
 

Greeting to all Zephyr users & developers!


I'm facing an issue I have trouble to debug. We are using Zephyr V2.1 (currently migrating to V2.2, but issue seems to stick) on NXP's i.MXRT 1062 wich is an ARM Cortext-M7 (ARMv7-M architecture). The first symptom I have is having the system that freeze.


Looking at where the CPU is using "west attach", we always end in the NMI ISR "z_SysNmiOnReset" which contains a short-loop. My investigations so far:


 - Reading the NMIPENDSET bit of the Interrupt Control and State Register "ICSR" show that the NMI interrupt is not pending.

 - Reading the "ISR_NUMBER" of the IPSR register show me that that the active vector is not NMI but some peripheral interrupts (ENET to be precise).

 - Following the program flow with GDB show that after the IRQ, the CPU jump to the "_isr_wrapper()" function, then execute the driver's handler code trough de-referencing the "_sw_isr_table" . Then if I try to step into "z_arm_int_ext", GDB get stuck. Hitting "CTRL+C" shows that we are in "z_SysNmiOnReset".

 - Using a break-point inside" z_SysNmiOnReset" show normal flows unit the "bx lr", where same as above happens.


I was suspecting a Stack overflow on the interrupt stack. Raising CONFIG_ISR_STACK_SIZE seems to increase the time before the issue arise. Currently the issue happens on the 4 to 8th ISR call, depending on the KConfig configuration,  but with the same setting always on the same call.  Enabling CONFIG_STACK_SENTINEL does not change the behavior nor gives better debug informations.


Does someone have seen that before ? Any suggestion where to look at ? I'm currently out of ideas.


Antoine Zen-Ruffinen

Riedo Networks Ltd
Route de la Fonderie 6, 1700 Fribourg, Switzerland
Tel: +41 26 505 50 03, Fax: +41 26 505 50 01 www.riedonetworks.com


Re: how to change the compiler from C99 to gnu99 #std

Kumar Gala
 

On May 14, 2020, at 10:29 AM, Stefan Hristozov <stefan.hristozov@...> wrote:

Hi,

I want to change the compiler from c99 to gnu99.
I have tried to set CONFIG_COMPILER_OPT="-std=gnu99" in my prj.conf file. Unfortunately this does not remove -std=c99, see e.g. a single line of my compiler output:

[9/169] ccache /home/stefan/zephyr-sdk-0.11.2/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DBUILD_VERSION=zephyr-v2.2.0-2637-g6ba69f19d4a4 -DKERNEL -DNRF9160_XXAA -D_FORTIFY_SOURCE=2 -D__PROGRAM_START -D__ZEPHYR__=1 -I/home/stefan/zephyrproject/zephyr/subsys/net/ip -I/home/stefan/zephyrproject/zephyr/include -Izephyr/include/generated -I/home/stefan/zephyrproject/zephyr/soc/arm/nordic_nrf/nrf91 -I/home/stefan/zephyrproject/modules/hal/cmsis/CMSIS/Core/Include -I/home/stefan/zephyrproject/modules/hal/nordic/nrfx -I/home/stefan/zephyrproject/modules/hal/nordic/nrfx/drivers/include -I/home/stefan/zephyrproject/modules/hal/nordic/nrfx/mdk -I/home/stefan/zephyrproject/modules/hal/nordic/. -I../src -I../cifra/src -I../cifra/src/ext -isystem /home/stefan/zephyrproject/zephyr/lib/libc/minimal/include -isystem /home/stefan/zephyr-sdk-0.11.2/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/9.2.0/include -isystem /home/stefan/zephyr-sdk-0.11.2/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/9.2.0/include-fixed -Os -imacros/home/stefan/workspaces/oscore_edhoc_on_zephyr_modules/samples/cifra_test/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mcpu=cortex-m33 -mthumb -mabi=aapcs -imacros/home/stefan/zephyrproject/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-address-of-packed-member -Wno-pointer-sign -Wpointer-arith -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -std=gnu99 -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/home/stefan/workspaces/oscore_edhoc_on_zephyr_modules/samples/cifra_test=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/stefan/zephyrproject/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/stefan/zephyrproject=WEST_TOPDIR -ffunction-sections -fdata-sections -std=c99 -nostdinc -MD -MT CMakeFiles/app.dir/cifra/src/blockwise.c.obj -MF CMakeFiles/app.dir/cifra/src/blockwise.c.obj.d -o CMakeFiles/app.dir/cifra/src/blockwise.c.obj -c ../cifra/src/blockwise.c

Best regards
Stefan
I haven’t tried this, but you should be able to do something like what is done in:

set_property(GLOBAL PROPERTY CSTD gnu99)

At the top of your CMakeLists.txt

For example I did:

diff --git a/samples/hello_world/CMakeLists.txt b/samples/hello_world/CMakeLists.txt
index 29878daa90..bd26389e09 100644
--- a/samples/hello_world/CMakeLists.txt
+++ b/samples/hello_world/CMakeLists.txt
@@ -2,7 +2,9 @@

cmake_minimum_required(VERSION 3.13.1)

+set_property(GLOBAL PROPERTY CSTD gnu99)


- k


[Zephyr 2.3] Current status as of 14th of May

Carles Cufi
 

Hi all,

This is the current bug status for Zephyr 2.3 as of today.

High priority bugs: 8 (threshold for release is ==0)
https://github.com/zephyrproject-rtos/zephyr/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22priority%3A+high%22+sort%3Aupdated-desc+-milestone%3Av1.14.1+-milestone%3Av1.14.2+

Medium priority bugs: 43 (threshold for release is <=20)
https://github.com/zephyrproject-rtos/zephyr/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22priority%3A+medium%22+sort%3Aupdated-desc+-milestone%3Av1.14.1+-milestone%3Av1.14.2+

Since we are currently quite far away from the required thresholds in order to release 2.3.0, I would like to ask you all to go through the bug lists and try to fix (or close if they are no long applicable) as many as possible so that we do not need to delay the current tentative release date of May 29th.

Thank you all in advance.

Carles


how to change the compiler from C99 to gnu99 #std

Stefan Hristozov
 

Hi,

I want to change the compiler from c99 to gnu99.
I have tried to set CONFIG_COMPILER_OPT="-std=gnu99" in my prj.conf file. Unfortunately this does not remove -std=c99, see e.g. a single line of my compiler output:

[9/169] ccache /home/stefan/zephyr-sdk-0.11.2/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DBUILD_VERSION=zephyr-v2.2.0-2637-g6ba69f19d4a4 -DKERNEL -DNRF9160_XXAA -D_FORTIFY_SOURCE=2 -D__PROGRAM_START -D__ZEPHYR__=1 -I/home/stefan/zephyrproject/zephyr/subsys/net/ip -I/home/stefan/zephyrproject/zephyr/include -Izephyr/include/generated -I/home/stefan/zephyrproject/zephyr/soc/arm/nordic_nrf/nrf91 -I/home/stefan/zephyrproject/modules/hal/cmsis/CMSIS/Core/Include -I/home/stefan/zephyrproject/modules/hal/nordic/nrfx -I/home/stefan/zephyrproject/modules/hal/nordic/nrfx/drivers/include -I/home/stefan/zephyrproject/modules/hal/nordic/nrfx/mdk -I/home/stefan/zephyrproject/modules/hal/nordic/. -I../src -I../cifra/src -I../cifra/src/ext -isystem /home/stefan/zephyrproject/zephyr/lib/libc/minimal/include -isystem /home/stefan/zephyr-sdk-0.11.2/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/9.2.0/include -isystem /home/stefan/zephyr-sdk-0.11.2/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/9.2.0/include-fixed -Os -imacros/home/stefan/workspaces/oscore_edhoc_on_zephyr_modules/samples/cifra_test/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mcpu=cortex-m33 -mthumb -mabi=aapcs -imacros/home/stefan/zephyrproject/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-address-of-packed-member -Wno-pointer-sign -Wpointer-arith -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -std=gnu99 -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/home/stefan/workspaces/oscore_edhoc_on_zephyr_modules/samples/cifra_test=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/stefan/zephyrproject/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/stefan/zephyrproject=WEST_TOPDIR -ffunction-sections -fdata-sections -std=c99 -nostdinc -MD -MT CMakeFiles/app.dir/cifra/src/blockwise.c.obj -MF CMakeFiles/app.dir/cifra/src/blockwise.c.obj.d -o CMakeFiles/app.dir/cifra/src/blockwise.c.obj   -c ../cifra/src/blockwise.c

Best regards
Stefan


OTA / DFU Flutter MobileAPp side #nrf52832 #ble #bluetooth #mcumgr

fl@...
 

Hi Zephyr developpers !

 

To sum up i'm using nrf52833 DK, with new ncs sdk.
I can do OTA with mobil App nRFConnect, but not with nRFToolbox.

We want now to code OTA/DFU feature into our own app. I'm using smp_svr example as stater base project.
We found this native code for Android and iOS:

https://github.com/JuulLabs-OSS/mcumgr-android

https://github.com/JuulLabs-OSS/mcumgr-ios

1. Is this code officilly supported by Zephyr community?
2. Is there an official source code for OTA somewhere please ? I search here and on internet but found nothing yet. 
3. Do you plan to publish a Flutter version for OTA that we could use for android and iOS please?

 

 

Thanks a lot !


API meeting: agenda

Carles Cufi
 

Hi all,

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

Today's topics:

- dma: enable edma drivers for mcux
- PR https://github.com/zephyrproject-rtos/zephyr/pull/23689

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

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

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


[Zephyr 2.3] Please set the 2.3.0 milestone on all relevant PRs

Carles Cufi
 

Hi all,

I'd like to ask you to set the milestone in all Pull Requests that need to be merged during the stabilization period (be them bugfix and documentation or special cases, in which case they also require the "TSC" label).
This will help filter out any PRs that can wait until 2.3 is released, thus alleviating the burden on reviewers and maintainers.

Thanks in advance.

Regards,

Carles


Re: Fix RAM_CONSOLE buffer address to specific address #driver

mdecandia@...
 

Hi Andrew,
thank you.

To modify the linker script, I've seen this configuration option

https://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_CUSTOM_SECTIONS_LD.html

Is this the correct way to do it?

Michele


Bluetooth examples failure with native_posix target #bluetooth #driver

mdecandia@...
 

Hi all,
I'm trying to run bluetooth examples on native_posix target an I'm facing this error:

zephyr/build/zephyr/zephyr.exe --bt-dev=hci0
*** Booting Zephyr OS build zephyr-v2.2.0-2229-g9b055ecf82c3  ***
Starting Beacon Demo
[00:00:00.000,000] <err> bt_hci_core: HCI driver open failed (-132)
Bluetooth init failed (err -132)

Here my hciconfig -a output:

hci0:    Type: Primary  Bus: USB
    BD Address: 08:3E:8E:A2:1D:BA  ACL MTU: 1021:8  SCO MTU: 64:1
    DOWN
    RX bytes:574 acl:0 sco:0 events:30 errors:0
    TX bytes:368 acl:0 sco:0 commands:30 errors:0
    Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH SNIFF
    Link mode: SLAVE ACCEPT

Any help?

Thanks,
Michele


Zephyr 2.3.0-rc1 tagged

Carles Cufi
 

Hi all,

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

The merge window for features and enhancements is now closed for this release, and it will remain closed until 2.3.0 is released; the stabilization period is now open.
During said stabilization period only bug-fix, documentation, and stabilization-related patches may be merged to master.
Additional features or enhancements for the 2.3 release will require approval by the TSC.
As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers.
Testing Zephyr master branch during the stabilization period is also 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.3.0-rc1

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

The final release is tentatively scheduled for May 29th.

Note 1: You are of course free to send Pull Requests for new features in order to gather feedback early or collaborate with others, but the release team would like to encourage everyone to focus on bugfixes and documentation improvements to the larges extent possible, so that we can release 2.3.0 on time and in the best shape possible.
Note 2: If you have a feature or enhancement you would like to submit to the TSC, please tag the Pull Request in question with the "TSC" label, make sure it is approved and passing CI, and attend the next TSC meeting.

A big Thank You to everyone that contributed to this release so far, be it with code, reviews, documentation or any other type of contribution.

Thanks,

Carles


Re: Fix RAM_CONSOLE buffer address to specific address #driver

Boie, Andrew P
 

It's just a character buffer.

 

If you need to pin it to a specific memory address, I imagine you'll have to route it to a special input section that is placed where you want it in memory in the linker script. This will require a little work but shouldn't be too bad.

 

Andrew

 

From: users@... <users@...> On Behalf Of mdecandia@...
Sent: Wednesday, May 6, 2020 11:44 PM
To: users@...
Subject: [Zephyr-users] Fix RAM_CONSOLE buffer address to specific address #driver

 

Hi all,
for a specific design need,
I would like to fix the address of the ram_console buffer in RAM_CONSOLE driver.

Which is the best way (if feasible) to set it?

Thanks,
Michele


Fix RAM_CONSOLE buffer address to specific address #driver

mdecandia@...
 

Hi all,
for a specific design need,
I would like to fix the address of the ram_console buffer in RAM_CONSOLE driver.

Which is the best way (if feasible) to set it?

Thanks,
Michele


[2.3 release] Feature merge window close (M2) tomorrow

Carles Cufi
 

Hi all,

This is just a reminder that the feature merge window closes tomorrow, the 8th of May.
This means that any changes that are not bugfixes or documentation changes must be merged by then.

Since I doubt I will be able to go through all GitHub emails in time for tomorrow, please make sure that your PR shows in the following filter if you want it merged:

https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+is%3Aopen+base%3Amaster+review%3Aapproved+status%3Asuccess+-label%3ADNM+draft%3Afalse++milestone%3Av2.3.0

This means that your PR must be approved, must pass CI and its milestone must be set to v2.3.0.

If you have additional requests or need help, please email me or ping me on Slack.

Regards,

Carles


Re: can't enable CONFIG_USE_STM32_HAL_DMA2D and CONFIG_USE_STM32_HAL_* in general

Tristen Ennemuist
 

erwan, you're a champion - thank you!


Re: can't enable CONFIG_USE_STM32_HAL_DMA2D and CONFIG_USE_STM32_HAL_* in general

Erwan Gouriou
 

Hi,


Cheers
Erwan

On Wed, 6 May 2020 at 05:44, Tristen Ennemuist <tomeaus@...> wrote:
hello zephyr users

i'm using the stmf469i discovery board and i'm trying to enable some stm32 hal drivers but, try as i might, i cannot.

so for example, if i look in menuconfig for CONFIG_USE_STM32_HAL_DMA2D it appears but it is in red. if i press ? for information:

Name: USE_STM32_HAL_DMA2D
Type: bool
Value: n

Help:

  Enable STM32Cube Chrom-Art Accelerator™ controller (DMA2D) HAL module
  driver

Direct dependencies (=y):
     HAS_STM32CUBE(=y)

Kconfig definition, with parent deps. propagated to 'depends on'
================================================================

At modules/Kconfig.stm32:108
Included via /home/tristen/zephyrproject/zephyr/Kconfig:8 -> Kconfig.zephyr:10 -> modules/Kconfig:21
Menu path: (Top) -> Modules

  config USE_STM32_HAL_DMA2D
        bool
        depends on HAS_STM32CUBE(=y)
        help
          Enable STM32Cube Chrom-Art Accelerator™ controller (DMA2D) HAL module
          driver

working back it says it

HAS_STM32CUBE (=y)
SOC_SERIES_STM32F4X(=y)

yet i can't explicitly enable that specific CONFIG_USE_STM32_HAL_DMA2D and i can't include it in the prj.conf (errors about not being able to explicitly set it) and so i don't know what to do.

in my code i could

#include <stm32f4xx_hal_dma2d.h>

and compile without errors however the linking process failed whenever i tried to access a function, eg: HAL_DMA2D_Init. so it's like the environment knows i want to use that HAL and makes the include available to me, but i can't complete the build.

so i don't know if i'm getting hung up on the idea of whether linking will work if i could only enable CONFIG_USE_STM32_HAL_DMA2D or whether there is another way to get my project to compile/link the required hal driver, or indeed whether there are other options i'm not aware of.

when i look in 

zephyrproject/modules/hal/stm32/stm32cube/stm32f4xx/CMakeLists.txt

there is a whole lot of stuff about zephyr_library_sources_ifdef(CONFIG_USE_STM32_HAL_[all the things i would like to enable but cannot]) but the problem is i can't actually enable any of them.

anyway i tried google every which way and i'm stuck, so if anyone can help a brother out i'd be over the moon, cheers all, tristen.




can't enable CONFIG_USE_STM32_HAL_DMA2D and CONFIG_USE_STM32_HAL_* in general

Tristen Ennemuist
 

hello zephyr users

i'm using the stmf469i discovery board and i'm trying to enable some stm32 hal drivers but, try as i might, i cannot.

so for example, if i look in menuconfig for CONFIG_USE_STM32_HAL_DMA2D it appears but it is in red. if i press ? for information:

Name: USE_STM32_HAL_DMA2D
Type: bool
Value: n

Help:

  Enable STM32Cube Chrom-Art Accelerator™ controller (DMA2D) HAL module
  driver

Direct dependencies (=y):
     HAS_STM32CUBE(=y)

Kconfig definition, with parent deps. propagated to 'depends on'
================================================================

At modules/Kconfig.stm32:108
Included via /home/tristen/zephyrproject/zephyr/Kconfig:8 -> Kconfig.zephyr:10 -> modules/Kconfig:21
Menu path: (Top) -> Modules

  config USE_STM32_HAL_DMA2D
        bool
        depends on HAS_STM32CUBE(=y)
        help
          Enable STM32Cube Chrom-Art Accelerator™ controller (DMA2D) HAL module
          driver

working back it says it

HAS_STM32CUBE (=y)
SOC_SERIES_STM32F4X(=y)

yet i can't explicitly enable that specific CONFIG_USE_STM32_HAL_DMA2D and i can't include it in the prj.conf (errors about not being able to explicitly set it) and so i don't know what to do.

in my code i could

#include <stm32f4xx_hal_dma2d.h>

and compile without errors however the linking process failed whenever i tried to access a function, eg: HAL_DMA2D_Init. so it's like the environment knows i want to use that HAL and makes the include available to me, but i can't complete the build.

so i don't know if i'm getting hung up on the idea of whether linking will work if i could only enable CONFIG_USE_STM32_HAL_DMA2D or whether there is another way to get my project to compile/link the required hal driver, or indeed whether there are other options i'm not aware of.

when i look in 

zephyrproject/modules/hal/stm32/stm32cube/stm32f4xx/CMakeLists.txt

there is a whole lot of stuff about zephyr_library_sources_ifdef(CONFIG_USE_STM32_HAL_[all the things i would like to enable but cannot]) but the problem is i can't actually enable any of them.

anyway i tried google every which way and i'm stuck, so if anyone can help a brother out i'd be over the moon, cheers all, tristen.




Re: samples/basic/blinky

Tristen Ennemuist
 

cheers lawrence i've been tinkering and i can confirm the following will behave as i originally expected, all four leds are initially off and then cycling through 'em in turn. i'm in the right universe after all, thank you!

gpio_pin_configure(green_led, DT_ALIAS_LED0_GPIOS_PIN, GPIO_OUTPUT_INACTIVE | GPIO_ACTIVE_LOW);
gpio_pin_configure(orange_led, DT_ALIAS_LED1_GPIOS_PIN, GPIO_OUTPUT_INACTIVE | GPIO_ACTIVE_LOW);
gpio_pin_configure(red_led, DT_ALIAS_LED2_GPIOS_PIN, GPIO_OUTPUT_INACTIVE | GPIO_ACTIVE_LOW);
gpio_pin_configure(blue_led, DT_ALIAS_LED3_GPIOS_PIN, GPIO_OUTPUT_INACTIVE | GPIO_ACTIVE_LOW);

u32_t counter = 0;

while (1)
{
counter++;

if (counter == 1)
{
printk("green on\n");

gpio_pin_set(green_led, DT_ALIAS_LED0_GPIOS_PIN, 1U);
gpio_pin_set(orange_led, DT_ALIAS_LED1_GPIOS_PIN, 0U);
gpio_pin_set(red_led, DT_ALIAS_LED2_GPIOS_PIN, 0U);
gpio_pin_set(blue_led, DT_ALIAS_LED3_GPIOS_PIN, 0U);
}

if (counter == 2)
{
printk("orange on\n");

gpio_pin_set(green_led, DT_ALIAS_LED0_GPIOS_PIN, 0U);
gpio_pin_set(orange_led, DT_ALIAS_LED1_GPIOS_PIN, 1U);
gpio_pin_set(red_led, DT_ALIAS_LED2_GPIOS_PIN, 0U);
gpio_pin_set(blue_led, DT_ALIAS_LED3_GPIOS_PIN, 0U);
}

if (counter == 3)
{
printk("red on\n");

gpio_pin_set(green_led, DT_ALIAS_LED0_GPIOS_PIN, 0U);
gpio_pin_set(orange_led, DT_ALIAS_LED1_GPIOS_PIN, 0U);
gpio_pin_set(red_led, DT_ALIAS_LED2_GPIOS_PIN, 1U);
gpio_pin_set(blue_led, DT_ALIAS_LED3_GPIOS_PIN, 0U);
}

if (counter == 4)
{
printk("blue on\n");

gpio_pin_set(green_led, DT_ALIAS_LED0_GPIOS_PIN, 0U);
gpio_pin_set(orange_led, DT_ALIAS_LED1_GPIOS_PIN, 0U);
gpio_pin_set(red_led, DT_ALIAS_LED2_GPIOS_PIN, 0U);
gpio_pin_set(blue_led, DT_ALIAS_LED3_GPIOS_PIN, 1U);

counter = 0;
}

k_sleep(1000);
}


Re: API meeting: agenda

Carles Cufi
 

Updated agenda:

- RFC: API change: Add I2C bus recovery API
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/23441
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/23442

- RFC: use compatible name for prefix for device-specific API
- PR: https://github.com/zephyrproject-rtos/zephyr/issues/24978

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

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

-----Original Message-----
From: devel@... <devel@...> On
Behalf Of Carles Cufi via lists.zephyrproject.org
Sent: 05 May 2020 16:08
To: users@...; devel@...
Subject: [Zephyr-devel] API meeting: agenda

Hi all,

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

Today's topics:

- RFC: use compatible name for prefix for device-specific API
- PR: https://github.com/zephyrproject-rtos/zephyr/issues/24978

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

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

Additional items in the "Triage" column in the GitHub project may be
discussed if time permits.
If you want an item included in the meeting, please add it to the GitHub
project.

https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-
Working-Group-Meetings#zephyr-api-discussion
https://github.com/zephyrproject-rtos/zephyr/projects/18
https://docs.google.com/document/d/1lv-
8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles