Date   

v2.6.0 merge window closes Friday, May 7th

Kumar Gala
 

Hi,

This is a reminder that the v2.6.0 merge window for new features closes this Friday, 7th of May. After that, only bug fixes and documentation will be merged until the final release is tagged, which is targeted for Friday, May 28th. Exceptions require TSC approval. New feature PRs may still be submitted while the merge window is closed, but please keep in mind that maintainers will have less time to review them during the release stabilization period.

Please add the v2.6.0 milestone to PRs that need to be included in the release, and do not wait until Friday, May 7th to submit them.

https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+milestone%3Av2.6.0

Please try to help fix bugs, test release candidates, and write release notes to minimize the time the merge window is closed so we can all quickly get back to adding fun new things to Zephyr!

Thank you for your contributions!

- k


API meeting: agenda

Carles Cufi
 


Re: Support for Ambiq Apollo chips #bluetooth #ambiq

Keith Short
 

The GPIO driver for the ITE IT8xxx2 family also interleaves the register space.

You could follow the model used for that driver - create multiple reg phandles for the individual registers.


Keith

On Sun, Apr 25, 2021 at 4:19 PM <ciesielskimm@...> wrote:
Hello,

I'm trying to add support for the Ambiq Apollo series chips. I'm new to the Zephyr and not very experienced with Device Tree format.
Currently I'm working on the zephyr/dts/arm/ambiq/apollo.dtsi. I'm trying to add the GPIO control registers. I'm modyfing
the STM32 dtsi file. STM32's define the GPIO control in a different way. All the Pad A registers are defined in a continous memory block.
In Ambiq SOCs those they are interleaved. The image below shows the memory map.



First its the Pad configuration registers. Then its GPIO configuration register. I'm wondering how should I implement this
memory layout in the dtsi.


Zephyr Memory Footprint - biweekly discussion - Mon, 04/26/2021 3:00pm-4:00pm, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>
 

Reminder: Zephyr Memory Footprint - biweekly discussion

When: Monday, 26 April 2021, 3:00pm to 4:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Working doc: https://docs.google.com/document/d/1bnQLJKVhgI3zkk3MsSXun8onEsA8z1Rf5ohdbCHASmU/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,546018126# United States, Orlando
Phone Conference ID: 546 018 126#
 
 
________________________________________________________________________________


Support for Ambiq Apollo chips #bluetooth #ambiq

Michał Ciesielski
 

Hello,

I'm trying to add support for the Ambiq Apollo series chips. I'm new to the Zephyr and not very experienced with Device Tree format.
Currently I'm working on the zephyr/dts/arm/ambiq/apollo.dtsi. I'm trying to add the GPIO control registers. I'm modyfing
the STM32 dtsi file. STM32's define the GPIO control in a different way. All the Pad A registers are defined in a continous memory block.
In Ambiq SOCs those they are interleaved. The image below shows the memory map.



First its the Pad configuration registers. Then its GPIO configuration register. I'm wondering how should I implement this
memory layout in the dtsi.


Re: Private: Re: [Zephyr-devel] QSPI for ATSAME51 #flash

Bolivar, Marti
 

Adding the list back in Cc.

"Theo Hussey via Lists.Zephyrproject.Org"
<theo=open-cosmos.com@lists.zephyrproject.org> writes:

Thank you for your detailed response, I tried to use the binding you
suggested but I was not sure where to put it as I developing the
driver out of tree.
I meant that binding as an example, not as something to copy/paste --
for a different IP block you will need your own binding.


I switched to developing the driver in tree instead and was able to
get the driver working after setting up the binding correctly and
fixing some typos with the macros in my driver.

You can put the binding in a dts/bindings subdirectory of anything in
your DTS_ROOT cmake variable or any Zephyr module that declares itself a
dts-root, like modules/hal/nxp/zephyr/module.yml and
modules/hal/stm32/zephyr/module.yml do.



Thanks

Theo


Re: Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 22 April 2021 #cal-cancelled

Kumar Gala
 

Sorry for the late cancelation. Not feeling well and there wasn’t much of an agenda this week.

On Apr 22, 2021, at 8:36 AM, devel@lists.zephyrproject.org Calendar <noreply@lists.zephyrproject.org> wrote:

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, 22 April 2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: devel@lists.zephyrproject.org

Description:

________________________________________________________________________________
Join Microsoft Teams Meeting
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options


________________________________________________________________________________


<Mail Attachment.ics><invite.ics>


Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 22 April 2021 #cal-cancelled

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, 22 April 2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: devel@...

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Re: QSPI for ATSAME51 #flash

Bolivar, Marti
 

Hi Theo,

"Theo Hussey via lists.zephyrproject.org"
<theo=open-cosmos.com@lists.zephyrproject.org> writes:

Hi,

I am trying to develop an out of tree QSPI driver for the ATSAME51 micro controller.

I have added my entries to the device tree:

soc {
qspi0 : qspi@42003400 {
compatible = "atmel,sam0-qspi" ;
reg = < 0x42003400 0x40 >;
interrupts = < 134 0 >;
status = "okay" ;
label = "QSPI_0" ;
clocks = < &mclk 0x10 13 >, < &mclk 0x10 21 >, < &mclk 0x1C 13 >;
clock-names = "QSPI_AHB_Clock" , "QSPI_2X_AHB_Clock" , "QSPI_APB_Clock" ;
#address-cells = < 1 >;
#size-cells = < 0 >;
};
};
};
There is an extra unmatched "};" here. I'm assuming that is just a
copy/paste issue in this email? It looks like a syntax error.


&qspi0 {
gd25q16 : gd25q16c@0 {
compatible = "jedec,spi-nor" ;
label = "GD25Q16C" ;
reg = < 0 >;
spi-max-frequency = < 80000000 >;
size = < 0x200000 >;
has-be32k;
has-dpd;
t-enter-dpd = < 20000 >;
t-exit-dpd = < 100000 >;
jedec-id = [c8 40 15] ;
};
};

But I receive the following errors when trying to build, in comparison if I add the nor flash as an child of a sercom spi peripheral it builds fine. Does anyone have any suggestions on what could be causing this?
[snip]

zephyr/include/generated/devicetree_unfixed.h:4014:35: error: 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_BUS_P_label' undeclared (first use in this function); did you mean 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_label'?
I'm going to explain what this mess means for the sake of the list
archives before getting to what I am guessing the problem is.

'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_BUS_P_label'

The 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0' part is the 'node
identifier' for the gd25q16c@0 node.

'Node identifiers' are introduced here:

https://docs.zephyrproject.org/latest/guides/dts/api-usage.html#node-identifiers

The secret decoder ring for unpacking node identifiers is:

- 'DT_N' -> 'devicetree node'
- '_S_' -> '/'
- all special characters become '_'

So that:

DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_BUS_P_label

becomes:

devicetree node /soc/qspi@42003400/gd25q16c@0 _BUS_P_label

The trailing '_BUS_P_label' is just the devicetree API trying to figure
out what the 'label' property of the bus node for
/soc/qspi@42003400/gd25q16c@0 is.

I also see:

- 'qspi@42003400' does have a label property in your DTS, "QSPI_0"
- its compatible, 'atmel,sam0-qspi', is not upstream

So I'm guessing that the problem is:

- you've got a custom binding for 'atmel,sam0-qspi',
- it is a missing a 'bus: qspi' line

Example binding with a 'bus: qspi' line:

https://github.com/zephyrproject-rtos/zephyr/blob/master/dts/bindings/qspi/st%2Cstm32-qspi.yaml#L23

If that line is missing, please add it and try again.

Otherwise please provide more details on your binding.

Thanks and HTH,
Martí


QSPI for ATSAME51 #flash

Theo Hussey
 

Hi,

I am trying to develop an out of tree QSPI driver for the ATSAME51 micro controller.

I have added my entries to the device tree:

soc {
qspi0: qspi@42003400 {
compatible = "atmel,sam0-qspi";
reg = <0x42003400 0x40>;
interrupts = <134 0>;
status = "okay";
label = "QSPI_0";
clocks = <&mclk 0x10 13>, <&mclk 0x10 21>, <&mclk 0x1C 13>;
clock-names = "QSPI_AHB_Clock", "QSPI_2X_AHB_Clock", "QSPI_APB_Clock";
#address-cells = <1>;
#size-cells = <0>;
};
};
};

&qspi0 {
gd25q16: gd25q16c@0 {
compatible = "jedec,spi-nor";
label = "GD25Q16C";
reg = <0>;
spi-max-frequency = <80000000>;
size = <0x200000>;
has-be32k;
has-dpd;
t-enter-dpd = <20000>;
t-exit-dpd = <100000>;
jedec-id = [c8 40 15];
};
};


But I receive the following errors when trying to build, in comparison if I add the nor flash as an child of a sercom spi peripheral it builds fine. Does anyone have any suggestions on what could be causing this?

92/128] Building C object zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/spi_nor.c.obj

FAILED: zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/spi_nor.c.obj 

/home/theo/zephyr-sdk-0.11.4/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DBUILD_VERSION=zephyr-v2.4.0 -DKERNEL -D_FORTIFY_SOURCE=2 -D__PROGRAM_START -D__ZEPHYR_SUPERVISOR__ -D__ZEPHYR__=1 -I/home/theo/source/zephyr/zephyrproject/zephyr/include -Izephyr/include/generated -I/home/theo/source/zephyr/zephyrproject/zephyr/soc/arm/atmel_sam0/same54 -I/home/theo/source/zephyr/zephyrproject/zephyr/drivers -I/home/theo/source/zephyr/zephyrproject/zephyr/soc/arm/atmel_sam0/common/. -I/home/theo/source/zephyr/zephyrproject/modules/hal/cmsis/CMSIS/Core/Include -I/home/theo/source/zephyr/zephyrproject/modules/hal/atmel/asf/sam0/include/same54 -I/home/theo/source/zephyr/zephyrproject/zephyr/drivers/spi -isystem /home/theo/source/zephyr/zephyrproject/zephyr/lib/libc/minimal/include -isystem /home/theo/zephyr-sdk-0.11.4/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/9.2.0/include -isystem /home/theo/zephyr-sdk-0.11.4/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/9.2.0/include-fixed -Os -imacros /home/theo/source/zephyr/obc-watchdog/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mcpu=cortex-m4 -mthumb -mabi=aapcs -imacros /home/theo/source/zephyr/zephyrproject/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/home/theo/source/zephyr/obc-watchdog=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/theo/source/zephyr/zephyrproject/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/theo/source/zephyr/zephyrproject=WEST_TOPDIR -ffunction-sections -fdata-sections -std=c99 -nostdinc -MD -MT zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/spi_nor.c.obj -MF zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/spi_nor.c.obj.d -o zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/spi_nor.c.obj   -c /home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c

In file included from /home/theo/source/zephyr/zephyrproject/zephyr/include/arch/arm/aarch32/arch.h:20,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/arch/cpu.h:19,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/kernel_includes.h:38,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/kernel.h:17,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/init.h:11,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/device.h:22,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/drivers/flash.h:26,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:13:

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c: In function 'spi_nor_configure':

zephyr/include/generated/devicetree_unfixed.h:4014:35: error: 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_BUS_P_label' undeclared (first use in this function); did you mean 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_label'?

 4014 | #define DT_N_INST_0_jedec_spi_nor DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0

      |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1911:38: note: in definition of macro 'DT_CAT'

 1911 | #define DT_CAT(node_id, prop_suffix) node_id##prop_suffix

      |                                      ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1382:31: note: in expansion of macro 'DT_PROP'

 1382 | #define DT_BUS_LABEL(node_id) DT_PROP(DT_BUS(node_id), label)

      |                               ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1375:25: note: in expansion of macro 'DT_CAT'

 1375 | #define DT_BUS(node_id) DT_CAT(node_id, _BUS)

      |                         ^~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1382:39: note: in expansion of macro 'DT_BUS'

 1382 | #define DT_BUS_LABEL(node_id) DT_PROP(DT_BUS(node_id), label)

      |                                       ^~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1721:33: note: in expansion of macro 'DT_BUS_LABEL'

 1721 | #define DT_INST_BUS_LABEL(inst) DT_BUS_LABEL(DT_DRV_INST(inst))

      |                                 ^~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:106:36: note: in expansion of macro 'DT_N_INST_0_jedec_spi_nor'

  106 | #define UTIL_PRIMITIVE_CAT(a, ...) a##__VA_ARGS__

      |                                    ^

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:105:26: note: in expansion of macro 'UTIL_PRIMITIVE_CAT'

  105 | #define UTIL_CAT(a, ...) UTIL_PRIMITIVE_CAT(a, __VA_ARGS__)

      |                          ^~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:297:31: note: in expansion of macro 'UTIL_CAT'

  297 | #define DT_INST(inst, compat) UTIL_CAT(DT_N_INST, DT_DASH(inst, compat))

      |                               ^~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1426:27: note: in expansion of macro 'DT_INST'

 1426 | #define DT_DRV_INST(inst) DT_INST(inst, DT_DRV_COMPAT)

      |                           ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1721:46: note: in expansion of macro 'DT_DRV_INST'

 1721 | #define DT_INST_BUS_LABEL(inst) DT_BUS_LABEL(DT_DRV_INST(inst))

      |                                              ^~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:838:33: note: in expansion of macro 'DT_INST_BUS_LABEL'

  838 |  data->spi = device_get_binding(DT_INST_BUS_LABEL(0));

      |                                 ^~~~~~~~~~~~~~~~~

zephyr/include/generated/devicetree_unfixed.h:4014:35: note: each undeclared identifier is reported only once for each function it appears in

 4014 | #define DT_N_INST_0_jedec_spi_nor DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0

      |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1911:38: note: in definition of macro 'DT_CAT'

 1911 | #define DT_CAT(node_id, prop_suffix) node_id##prop_suffix

      |                                      ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1382:31: note: in expansion of macro 'DT_PROP'

 1382 | #define DT_BUS_LABEL(node_id) DT_PROP(DT_BUS(node_id), label)

      |                               ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1375:25: note: in expansion of macro 'DT_CAT'

 1375 | #define DT_BUS(node_id) DT_CAT(node_id, _BUS)

      |                         ^~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1382:39: note: in expansion of macro 'DT_BUS'

 1382 | #define DT_BUS_LABEL(node_id) DT_PROP(DT_BUS(node_id), label)

      |                                       ^~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1721:33: note: in expansion of macro 'DT_BUS_LABEL'

 1721 | #define DT_INST_BUS_LABEL(inst) DT_BUS_LABEL(DT_DRV_INST(inst))

      |                                 ^~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:106:36: note: in expansion of macro 'DT_N_INST_0_jedec_spi_nor'

  106 | #define UTIL_PRIMITIVE_CAT(a, ...) a##__VA_ARGS__

      |                                    ^

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:105:26: note: in expansion of macro 'UTIL_PRIMITIVE_CAT'

  105 | #define UTIL_CAT(a, ...) UTIL_PRIMITIVE_CAT(a, __VA_ARGS__)

      |                          ^~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:297:31: note: in expansion of macro 'UTIL_CAT'

  297 | #define DT_INST(inst, compat) UTIL_CAT(DT_N_INST, DT_DASH(inst, compat))

      |                               ^~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1426:27: note: in expansion of macro 'DT_INST'

 1426 | #define DT_DRV_INST(inst) DT_INST(inst, DT_DRV_COMPAT)

      |                           ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1721:46: note: in expansion of macro 'DT_DRV_INST'

 1721 | #define DT_INST_BUS_LABEL(inst) DT_BUS_LABEL(DT_DRV_INST(inst))

      |                                              ^~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:838:33: note: in expansion of macro 'DT_INST_BUS_LABEL'

  838 |  data->spi = device_get_binding(DT_INST_BUS_LABEL(0));

      |                                 ^~~~~~~~~~~~~~~~~

zephyr/include/generated/devicetree_unfixed.h:4014:35: error: 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_spi_max_frequency' undeclared (first use in this function); did you mean 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_reg_IDX_0'?

 4014 | #define DT_N_INST_0_jedec_spi_nor DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0

      |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1911:38: note: in definition of macro 'DT_CAT'

 1911 | #define DT_CAT(node_id, prop_suffix) node_id##prop_suffix

      |                                      ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1448:34: note: in expansion of macro 'DT_PROP'

 1448 | #define DT_INST_PROP(inst, prop) DT_PROP(DT_DRV_INST(inst), prop)

      |                                  ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:106:36: note: in expansion of macro 'DT_N_INST_0_jedec_spi_nor'

  106 | #define UTIL_PRIMITIVE_CAT(a, ...) a##__VA_ARGS__

      |                                    ^

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:105:26: note: in expansion of macro 'UTIL_PRIMITIVE_CAT'

  105 | #define UTIL_CAT(a, ...) UTIL_PRIMITIVE_CAT(a, __VA_ARGS__)

      |                          ^~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:297:31: note: in expansion of macro 'UTIL_CAT'

  297 | #define DT_INST(inst, compat) UTIL_CAT(DT_N_INST, DT_DASH(inst, compat))

      |                               ^~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1426:27: note: in expansion of macro 'DT_INST'

 1426 | #define DT_DRV_INST(inst) DT_INST(inst, DT_DRV_COMPAT)

      |                           ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1448:42: note: in expansion of macro 'DT_DRV_INST'

 1448 | #define DT_INST_PROP(inst, prop) DT_PROP(DT_DRV_INST(inst), prop)

      |                                          ^~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:843:28: note: in expansion of macro 'DT_INST_PROP'

  843 |  data->spi_cfg.frequency = DT_INST_PROP(0, spi_max_frequency);

      |                            ^~~~~~~~~~~~

In file included from /home/theo/source/zephyr/zephyrproject/zephyr/include/toolchain.h:41,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/sys/errno_private.h:10,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/lib/libc/minimal/include/errno.h:20,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:12:

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c: At top level:

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:982:1: error: static assertion failed: "jedec,spi-nor jedec-id required for non-runtime SFDP"

  982 | BUILD_ASSERT(DT_INST_NODE_HAS_PROP(0, jedec_id),

      | ^~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:991:1: error: static assertion failed: "jedec,spi-nor size required for non-runtime SFDP page layout"

  991 | BUILD_ASSERT(DT_INST_NODE_HAS_PROP(0, size),

      | ^~~~~~~~~~~~

zephyr/include/generated/devicetree_unfixed.h:4014:35: error: 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_size' undeclared here (not in a function); did you mean 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_reg'?

 4014 | #define DT_N_INST_0_jedec_spi_nor DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0

      |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:393:32: note: in expansion of macro 'DT_CAT'

  393 | #define DT_PROP(node_id, prop) DT_CAT(node_id, _P_##prop)

      |                                ^~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1448:34: note: in expansion of macro 'DT_PROP'

 1448 | #define DT_INST_PROP(inst, prop) DT_PROP(DT_DRV_INST(inst), prop)

      |                                  ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:106:36: note: in expansion of macro 'DT_N_INST_0_jedec_spi_nor'

  106 | #define UTIL_PRIMITIVE_CAT(a, ...) a##__VA_ARGS__

      |                                    ^

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:105:26: note: in expansion of macro 'UTIL_PRIMITIVE_CAT'

  105 | #define UTIL_CAT(a, ...) UTIL_PRIMITIVE_CAT(a, __VA_ARGS__)

      |                          ^~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:297:31: note: in expansion of macro 'UTIL_CAT'

  297 | #define DT_INST(inst, compat) UTIL_CAT(DT_N_INST, DT_DASH(inst, compat))

      |                               ^~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1426:27: note: in expansion of macro 'DT_INST'

 1426 | #define DT_DRV_INST(inst) DT_INST(inst, DT_DRV_COMPAT)

      |                           ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1448:42: note: in expansion of macro 'DT_DRV_INST'

 1448 | #define DT_INST_PROP(inst, prop) DT_PROP(DT_DRV_INST(inst), prop)

      |                                          ^~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:995:23: note: in expansion of macro 'DT_INST_PROP'

  995 | #define INST_0_BYTES (DT_INST_PROP(0, size) / 8)

      |                       ^~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:1001:29: note: in expansion of macro 'INST_0_BYTES'

 1001 | #define LAYOUT_PAGES_COUNT (INST_0_BYTES / CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE)

      |                             ^~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:1003:55: note: in expansion of macro 'LAYOUT_PAGES_COUNT'

 1003 | BUILD_ASSERT((CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE * LAYOUT_PAGES_COUNT)

      |                                                       ^~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:1003:14: error: expression in static assertion is not an integer

 1003 | BUILD_ASSERT((CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE * LAYOUT_PAGES_COUNT)

      |              ^

In file included from /home/theo/source/zephyr/zephyrproject/zephyr/include/arch/arm/aarch32/arch.h:20,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/arch/cpu.h:19,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/kernel_includes.h:38,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/kernel.h:17,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/init.h:11,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/device.h:22,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/include/drivers/flash.h:26,

                 from /home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:13:

zephyr/include/generated/devicetree_unfixed.h:4014:35: error: 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_jedec_id' undeclared here (not in a function); did you mean 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_reg'?

 4014 | #define DT_N_INST_0_jedec_spi_nor DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0

      |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1911:38: note: in definition of macro 'DT_CAT'

 1911 | #define DT_CAT(node_id, prop_suffix) node_id##prop_suffix

      |                                      ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1448:34: note: in expansion of macro 'DT_PROP'

 1448 | #define DT_INST_PROP(inst, prop) DT_PROP(DT_DRV_INST(inst), prop)

      |                                  ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:106:36: note: in expansion of macro 'DT_N_INST_0_jedec_spi_nor'

  106 | #define UTIL_PRIMITIVE_CAT(a, ...) a##__VA_ARGS__

      |                                    ^

/home/theo/source/zephyr/zephyrproject/zephyr/include/sys/util_internal.h:105:26: note: in expansion of macro 'UTIL_PRIMITIVE_CAT'

  105 | #define UTIL_CAT(a, ...) UTIL_PRIMITIVE_CAT(a, __VA_ARGS__)

      |                          ^~~~~~~~~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:297:31: note: in expansion of macro 'UTIL_CAT'

  297 | #define DT_INST(inst, compat) UTIL_CAT(DT_N_INST, DT_DASH(inst, compat))

      |                               ^~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1426:27: note: in expansion of macro 'DT_INST'

 1426 | #define DT_DRV_INST(inst) DT_INST(inst, DT_DRV_COMPAT)

      |                           ^~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/include/devicetree.h:1448:42: note: in expansion of macro 'DT_DRV_INST'

 1448 | #define DT_INST_PROP(inst, prop) DT_PROP(DT_DRV_INST(inst), prop)

      |                                          ^~~~~~~~~~~

/home/theo/source/zephyr/zephyrproject/zephyr/drivers/flash/spi_nor.c:1030:14: note: in expansion of macro 'DT_INST_PROP'

 1030 |  .jedec_id = DT_INST_PROP(0, jedec_id),

      |              ^~~~~~~~~~~~

[93/128] Building C object modules/qspi/CMakeFiles/..__..__obc-watchdog__drivers__qspi.dir/qspi_sam0.c.obj

../drivers/qspi/qspi_sam0.c:53:12: warning: 'qspi_sam0_configure' defined but not used [-Wunused-function]

   53 | static int qspi_sam0_configure(const struct device *dev, const struct spi_config *config)

      |            ^~~~~~~~~~~~~~~~~~~

[101/128] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mailbox.c.obj

ninja: build stopped: subcommand failed.


Zephyr Project: APIs - Tue, 04/20/2021 4:00pm-5:00pm, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>
 

Reminder: Zephyr Project: APIs

When: Tuesday, 20 April 2021, 4:00pm to 5:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description:

Meeting decisions/discussions in their respective PRs, tracked here: https://github.com/zephyrproject-rtos/zephyr/projects/18


________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


API meeting: agenda

Carles Cufi
 


Final Reminder: CFP -- Zephyr Developer Summit 2021

Brett Preston
 

Members of the Zephyr Community,

A final reminder that the Call for Papers for the Zephyr Developer Summit closes tomorrow (Tuesday, April 20):

Look for schedule announcement and registration on May 5.

Thank you,


Brett


On Wed, Apr 14, 2021 at 10:00 AM Brett Preston <bpreston@...> wrote:
Members of the Zephyr Community,

A reminder of the Call for Papers that remains open until Tuesday, April 20:

The Zephyr Developer Summit has been scheduled for Tuesday, June 8 - Thursday, June 10, 2021

This free virtual event will feature two tracks:

Track A: Mini-conference (each will be 120 minutes in length)
  • This track is designed to let the organizer(s) focus on discussing an open topic with the other key participants.  A successful mini-conference outlines a problem and provides sufficient background so participants can engage in effective discussion.   Examples where this style is used:  Linux Plumbers, Conference Fishbowl Sessions, extended BOF etc.  Goal here is to have an effective discussion session and make progress on an outstanding problem.
  • Some possible topic areas could include:
    • Firmware
    • Modules
    • Networking Stack
    • Power Management
    • Toolchain
    • Topics identified in 2020 developer survey
Track B: Presentations. (choice of 30 or 60 minutes in length or lighting talks)
  • This is designed for sharing knowledge and providing context for other discussions.
  • Some possible topic ideas include:
    • How is Zephyr being used in products
    • Demos of tools working with Zephyr
    • Overview of proposed technologies for inclusion
    • Summary of what’s happening in subsystems
    • Updates on west, modules, runtimes, etc.
    • Security & Safety team updates
    • Test infrastructure Improvements
    • BOF topics
    • Lightning talk on something cool in Zephyr you want to share

Other Key Dates
  • May 5 - Schedule announcement
  • May 5 - Registration opens

Thank you!


Brett


On Wed, Apr 7, 2021 at 4:16 PM Brett Preston <bpreston@...> wrote:
Members of the Zephyr Community,

The inaugural Zephyr Developer Summit has been scheduled for Tuesday, June 8 - Thursday, June 10, 2021.

Furthermore, the Call for Papers is Now Openhttps://forms.gle/i637wnnBp9ahrnc37 (closes April 20).

This free virtual event will feature two tracks:

Track A: Mini-conference (each will be 120 minutes in length)
  • This track is designed to let the organizer(s) focus on discussing an open topic with the other key participants.  A successful mini-conference outlines a problem and provides sufficient background so participants can engage in effective discussion.   Examples where this style is used:  Linux Plumbers, Conference Fishbowl Sessions, extended BOF etc.  Goal here is to have an effective discussion session and make progress on an outstanding problem.
  • Some possible topic areas could include:
    • Firmware
    • Modules
    • Networking Stack
    • Power Management
    • Toolchain
    • Topics identified in 2020 developer survey
Track B: Presentations. (choice of 30 or 60 minutes in length or lighting talks)
  • This is designed for sharing knowledge and providing context for other discussions.
  • Some possible topic ideas include:
    • How is Zephyr being used in products
    • Demos of tools working with Zephyr
    • Overview of proposed technologies for inclusion
    • Summary of what’s happening in subsystems
    • Updates on west, modules, runtimes, etc.
    • Security & Safety team updates
    • Test infrastructure Improvements
    • BOF topics
    • Lightning talk on something cool in Zephyr you want to share

Other Key Dates
  • May 5 - Schedule announcement
  • May 5 - Registration opens

Thank you,


Brett

--
Brett Preston
Sr. Program Manager
The Linux Foundation
+1 (971) 303-9030



--
Brett Preston
Sr. Program Manager
The Linux Foundation
+1 (971) 303-9030



--
Brett Preston
Sr. Program Manager
The Linux Foundation
+1 (971) 303-9030


Zephyr: Toolchain Working Group - Mon, 04/19/2021 #cal-notice

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Zephyr: Toolchain Working Group

When:
Monday, 19 April 2021
3:00pm to 4:00pm
(GMT+00:00) UTC

Where:
Microsoft Teams Meeting

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 


Zephyr: Toolchain Working Group - Mon, 04/19/2021 3:00pm-4:00pm, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>
 

Reminder: Zephyr: Toolchain Working Group

When: Monday, 19 April 2021, 3:00pm to 4:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: Torsten Rasmussen

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 


Updated Event: Zephyr Memory Footprint - biweekly discussion #cal-invite

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Zephyr Memory Footprint - biweekly discussion

When:
Monday, 26 April 2021
3:00pm to 4:00pm
(UTC+00:00) UTC
Repeats: Every 2 weeks on Monday

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:
Working doc: https://docs.google.com/document/d/1bnQLJKVhgI3zkk3MsSXun8onEsA8z1Rf5ohdbCHASmU/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,546018126# United States, Orlando
Phone Conference ID: 546 018 126#
 
 
________________________________________________________________________________


Event: Zephyr Memory Footprint - biweekly discussion #cal-invite

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Zephyr Memory Footprint - biweekly discussion

When:
Monday, 26 April 2021
3:00pm to 4:00pm
(UTC-07:00) America/Los Angeles
Repeats: Every 2 weeks on Monday

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:
Working doc: https://docs.google.com/document/d/1bnQLJKVhgI3zkk3MsSXun8onEsA8z1Rf5ohdbCHASmU/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,546018126# United States, Orlando
Phone Conference ID: 546 018 126#
 
 
________________________________________________________________________________


Re: Dev-Review Meeting Agenda Apr 15

Bolivar, Marti
 


Zephyr Project: Dev Meeting - Thu, 04/15/2021 3:00pm-4:00pm, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>
 

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 15 April 2021, 3:00pm to 4:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


BLE advertising device name in advert data (not scan data)

lairdjm
 

Hi,

I’m looking through the documentation to find a way (and playing with code) to try and work out how to have the device name advertised in the advert packets (on BLE) rather than scan response packets so that devices using passive scanning can determine the device name but not having any luck. The documentation for the BT_LE_ADV_OPT_USE_NAME bit states:

Include the GAP device name automatically when advertising.

By default the GAP device name is put at the end of the scan

response data.

When advertising using @ref BT_LE_ADV_OPT_EXT_ADV and not

@ref BT_LE_ADV_OPT_SCANNABLE then it will be put at the end of the

advertising data.

If the GAP device name does not fit into advertising data it will be

converted to a shortened name if possible.

 

The application can set the device name itself by including the

following in the advertising data.

@code

BT_DATA(BT_DATA_NAME_COMPLETE, name, strlen(name))

@endcode

 

So how would one put it in the advertising data without using extended advertising? The code I’m using is advertising using:

                static const struct bt_data ad[] = {

                                BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),

};

bt_le_adv_start(BT_LE_ADV_CONN_NAME, ad, ARRAY_SIZE(ad), NULL, 0);

Where the device name is 19 bytes which should fit in a normal non-extended adverts advertising packet. I do not want to use extended adverts and I’ve checked the bits that are set by using BT_LE_ADV_CONN_NAME which are bits 0 and 3, for BT_LE_ADV_OPT_CONNECTABLE and BT_LE_ADV_OPT_USE_NAME, the scan response bit is not set and a null pointer is suppled for scan response data to the advertising function, so why is it placing the device name in scan response data still?

Thanks,

Jamie

481 - 500 of 8183