Date   

Compile as much code as possible.

istuoli@...
 

Hello! I want to compile as much code as possible. Is there any command like make allyesconfig in linux?


[Zephyr 2.3] Final release delayed until June 5th

Carles Cufi
 

Hi all,

After close inspection of the current state of the code when it comes to bug counts, we have decided to postpone the release for a week, until June 5th. The main reason is the existence of high priority bugs that prevent us from tagging an -rc2.

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

High priority bugs: 2 (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: 19 (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+

As always, you are encouraged to go through the bug lists above and help out in any way you can.

Thank you in advance.

Regards,

Carles


USB Questions

antoker@...
 

Hi,

I've been testing out Zephyr's USB connectivity options on FRDM-K22F and got some questions:

  1. samples/subsys/usb/console/ compiles and runs okay as long as the USB is connected. If usb is not connected the application will not run, this happens, as I can see it because of flag CONFIG_USB_UART_DTR_WAIT=y. My understanding was that if i compile the app with CONFIG_USB_UART_DTR_WAIT=n the application will run immediately, however after compiling and uploading it to target the USB CDC Serial is not being recognized by the host operating system. Is it all possible to have a console via USB without the DTR flag?
  2. Is it possible to have shell redirected to USB Serial? The documentation is kinda of cryptic regarding this.

BR

Anton


[Zephyr 2.3] Current status as of 21st of May

Carles Cufi
 

Hi all,

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

High priority bugs: 3 (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: 40 (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+

We are confident that we will be able to close all 3 high priority bugs in the few days to come.
However, we need help in closing those medium priority bugs, so any contributions towards getting the count down are welcome.

Thank you all in advance.

Carles


How to port a new board without supporting soc

Sun.Waiting 孫偉婷 IEC1 <sun.waiting@...>
 

HI,

I want to port STM32L032K6 and run the sample "blinky".
But it does work after I add the patch such as attachment.
Could you give me some advices?

Best Regard,
Waiting
Tel: 886-2-28810721 #28094



Confidentiality Note

本郵件含有英業達股份有限公司機密資訊、或受法律保護之資料,唯有原發信人指定之收信人得閱讀或使用本郵件之內容。如您並非被指定之收信人,請立即將本郵件及所有附件予以刪除;請勿揭露、儲存或使用本郵件之任何資訊,並請您立即告知原發信人本郵件的傳遞錯誤。謝謝您的合作。
This e-mail transmission and any attachments contain information from Inventec Corporation. The information is confidential and/or privileged and intended to be solely for the use of the individuals or entities named in this e-mail transmission. If you are not the intended recipient, be aware that any disclosure, saving or use of the content of this e-mail transmission and attachments is strictly prohibited. If you have received this email transmission in error, please notify us immediately, and delete the e-mail and attachments. We greatly appreciate your cooperation.


Re: [Zephyr-devel] API meeting: agenda

Carles Cufi
 

Hi Simon,

Is that the correct notes link? I don't see any notes since March.
Yes, unfortunately that is the correct notes link. I am terrible at keeping meeting minutes, apologies for that. That said I do always comment on the relevant Pull Requests or issues during the meeting by prefixing the comment with "API meeting:".

Carles


On Tue, 19 May 2020 at 08:05, Carles Cufi <carles.cufi@nordicsemi.no>
wrote:

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:

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

- Any API-related PRs or issues that are related to the 2.3 release

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







Re: [Zephyr-devel] API meeting: agenda

Simon Glass <sjg@...>
 

Hi Carles,

Is that the correct notes link? I don't see any notes since March.

Regards,
SImon

On Tue, 19 May 2020 at 08:05, Carles Cufi <carles.cufi@nordicsemi.no> wrote:

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:

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

- Any API-related PRs or issues that are related to the 2.3 release

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







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:

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

- Any API-related PRs or issues that are related to the 2.3 release

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


SDK 0.11.3 Release

Kumar Gala
 

Hi,

Some fixes based on usage of SDK v0.11.x and addition of QEMU for ARC, cmake package support, and some changes to how we build GDB. Please take NOTE of the changes w/regards to GDB.

The SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.11.3

Please download and try things out and report any issues.

- General:
* Added cmake package support to make it easier to find toolchain
* Add a -[no]rc argument to install script to allow skipping update
query for .zephyrrc

- QEMU:
* Add support for ARC
* xilinx_qemu: Fix WFI instruction for icount mode
* SPARC: fix issue with timer in QEMU machine AT697
* Add support for changing CPU type in sifive_e machine.

- GDB:
- Added a gdb build that doesn't support python (TARGET-gdb-no-py)

NOTE: The name of the gdb executable will change in the next major
release. To maintain compatibility with previous 0.11.x we left the
TARGET-gdb as the version that supports python. In 0.12.x we will change
it such that TARGET-gdb will NOT support python and thus work everywhere
and TARGET-gdb-py will be the version that supports python.

- Changed python support to build against python3.8. This is an attempt to
have the python support work on a larger number of distributions.

NOTE: This may require install a python3.8 package on your system if
python3.8 is not available. On fedora systems that can be accomplished by:

`sudo dnf install python38`

On ubuntu systems that can be accomplished by:

`sudo apt get install python3.8-dev`

- OpenOCD:
* Pull in a fix for ARC SMP support

- GCC:
- Fix build issue with CRC32 intrinsics included from arm_acle.h on ARM
compiler.Thanks to all that contributed fixes and enhancements to this version of the SDK.

- k


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@aisec.fraunhofer.de> 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

701 - 720 of 2707