Date   

Re: nrf.h missing....

Lawrence King
 

Yes, in fact it was the process of running ‘west update’ that broke my build in the first place.

 

Lawrence King

Principal Developer

+1(416)627-7302

 

From: users@... <users@...> On Behalf Of Nashif, Anas
Sent: Wednesday, September 4, 2019 2:10 PM
To: Lawrence King <lawrence.king@...>; Zephyr-users@...
Cc: carles.cufi@...
Subject: Re: [Zephyr-users] nrf.h missing....

 

Did you run `west update` ?

 

From: <users@...> on behalf of Lawrence King <lawrence.king@...>
Date: Wednesday, 4 September 2019 at 14:05
To: "Zephyr-users@..." <Zephyr-users@...>
Cc: "carles.cufi@..." <carles.cufi@...>
Subject: [Zephyr-users] nrf.h missing....

 

Today I upgraded to the head of the zephyr tree and my compile broke. Backing up to the labels

v2.0.0-rc3

v2.0.0-rc2

v2.0.0-rc1

I found that my compile became broken somewhere between rc1 and rc2. A quick ‘git bisect’ found that the change that breaks my compile is:

 

cf3af6af5fa3e656d6caf0b3429fde52e895fa79 is the first bad commit

commit cf3af6af5fa3e656d6caf0b3429fde52e895fa79

Author: Carles Cufi <carles.cufi@...>

Date:   Thu Aug 15 17:17:01 2019 +0200

 

    ext: hal: Make Nordic HALs a Zephyr module

   

    Moved to an external repo,

    https://github.com/zephyrproject-rtos/hal_nordic.

   

    Signed-off-by: Carles Cufi <carles.cufi@...>

 

:100644 100644 73ad5c4f4fd10c2c1e3fbc0cc718b9f44cc198e7 696b06ec0d05db577603e10331186412f60ecbe3 M              CODEOWNERS

:040000 040000 26b7c0c40f816f24989e7a7507cc21e298413f8e 8e387167b591b949828dc0ca08e0aff80ad5919f M          ext

:040000 040000 772099e01dd7e4f586c782eb079b11ffbec86d39 2b5a71ac9918e09e3c801b2e90746da19f8b9437 M              modules

:100644 100644 08f26e785ead096c10fcec7905c0e1061b8ba3f6 fe98cafd8cf915bf73f82e25abfb5a4c2b83fcbd M              west.yml

 

For now my workaround is to stay at rc1.

 

I am using today’s release of west (0.6.2), I haven’t tried reverting west yet, but I did try manually running cmake and ninja and I get the same error, so I suspect this is not a west problem.

 

Here is the build error message I get (can’t find <nrf.h>):

 

lawrence@VM:~/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky$ west build -b nrf52840_mdk

-- west build: build configuration:

       source directory: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky

       build directory: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build (created)

       BOARD: nrf52840_mdk (origin: command line)

-- west build: generating a build system

Zephyr version: 2.0.0

-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.8", minimum required is "3.4")

-- Selected BOARD nrf52840_mdk

-- Found west: /home/lawrence/.local/bin/west (found suitable version "0.6.2", minimum required is "0.6.0")

-- Loading /home/lawrence/workspace/rc-demo/zephyr/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk.dts as base

-- Overlaying /home/lawrence/workspace/rc-demo/zephyr/zephyr/dts/common/common.dts

Device tree configuration written to /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/include/generated/generated_dts_board.conf

Parsing Kconfig tree in /home/lawrence/workspace/rc-demo/zephyr/zephyr/Kconfig

Loaded configuration '/home/lawrence/workspace/rc-demo/zephyr/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk_defconfig'

Merged configuration '/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/prj.conf'

Configuration saved to '/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/.config'

 

warning: UART_CONSOLE (defined at drivers/console/Kconfig:46) was assigned the value 'y' but got the

value 'n'. You can check symbol information (including dependencies) in the 'menuconfig' interface

(see the Application Development Primer section of the manual), or in the Kconfig reference at

http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_UART_CONSOLE.html (which is updated

regularly from the master branch). See the 'Setting configuration values' section of the Board

Porting Guide as well.

 

warning: the choice symbol UART_0_NRF_UART (defined at drivers/serial/Kconfig.nrfx:28) was selected

(set =y), but no symbol ended up as the choice selection.  You can check symbol information

(including dependencies) in the 'menuconfig' interface (see the Application Development Primer

section of the manual), or in the Kconfig reference at

http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_UART_0_NRF_UART.html (which is updated

regularly from the master branch). See the 'Setting configuration values' section of the Board

Porting Guide as well.

-- Cache files will be written to: /home/lawrence/.cache/zephyr

-- The C compiler identification is GNU 6.3.1

-- The CXX compiler identification is GNU 6.3.1

-- The ASM compiler identification is GNU

-- Found assembler: /usr/bin/arm-none-eabi-gcc

-- Performing Test toolchain_is_ok

-- Performing Test toolchain_is_ok - Success

Including module: civetweb in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/civetweb

Including module: esp-idf in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/esp-idf/zephyr

Including module: fatfs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/fatfs

Including module: qmsi in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/qmsi

Including module: cypress in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/cypress

Including module: silabs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/silabs

Including module: st in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/st

Including module: stm32 in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/stm32

Including module: libmetal in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/libmetal

Including module: lvgl in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/gui/lvgl

Including module: mbedtls in path: /home/lawrence/workspace/rc-demo/zephyr/modules/crypto/mbedtls

Including module: mcumgr in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/mcumgr

Including module: nffs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/nffs

Including module: open-amp in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/open-amp

Including module: openthread in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/openthread

Including module: segger in path: /home/lawrence/workspace/rc-demo/zephyr/modules/debug/segger

Including module: tinycbor in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/tinycbor

Including module: littlefs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/littlefs

-- Configuring done

-- Generating done

-- Build files have been written to: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build

-- west build: building application

[2/109] Preparing syscall dependency handling

 

[8/109] Building C object zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj

FAILED: zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj

ccache /usr/bin/arm-none-eabi-gcc -DBUILD_VERSION=v2.0.0-rc1-156-gcf3af6af5fa3 -DKERNEL -D_FORTIFY_SOURCE=2 -D__ZEPHYR__=1 -I../../../../kernel/include -I../../../../arch/arm/include -I../../../../include -I../../../../include/drivers -Izephyr/include/generated -I../../../../soc/arm/nordic_nrf/nrf52 -I../../../../soc/arm/nordic_nrf/include -I../../../../ext/hal/cmsis/Include -isystem ../../../../lib/libc/minimal/include -isystem /usr/lib/gcc/arm-none-eabi/6.3.1/include -isystem /usr/lib/gcc/arm-none-eabi/6.3.1/include-fixed -Os -imacros/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mthumb -mcpu=cortex-m4 -imacros/home/lawrence/workspace/rc-demo/zephyr/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -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 -ffunction-sections -fdata-sections -mabi=aapcs -march=armv7e-m -std=c99 -nostdinc -MD -MT zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj -MF zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj.d -o zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj   -c /home/lawrence/workspace/rc-demo/zephyr/zephyr/arch/arm/core/offsets/offsets.c

In file included from ../../../../include/arch/arm/cortex_m/cmsis.h:17:0,

                 from ../../../../include/arch/arm/cortex_m/mpu/arm_mpu_v7m.h:10,

                 from ../../../../include/arch/arm/cortex_m/mpu/arm_mpu.h:13,

                 from ../../../../include/arch/arm/arch.h:246,

                 from ../../../../include/arch/cpu.h:17,

                 from ../../../../include/kernel_includes.h:34,

                 from ../../../../include/kernel.h:17,

                 from ../../../../kernel/include/kernel_structs.h:10,

                 from /home/lawrence/workspace/rc-demo/zephyr/zephyr/arch/arm/core/offsets/offsets.c:26:

../../../../soc/arm/nordic_nrf/nrf52/soc.h:17:17: fatal error: nrf.h: No such file or directory

#include <nrf.h>

                 ^

compilation terminated.

ninja: build stopped: subcommand failed.

ERROR: command exited with status 1: /home/lawrence/.local/bin/cmake --build /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build

 

The problem exists compiling simple things like blinky. To reproduce the issue run the following commands:

              $ cd zephyr/samples/basic/blinky

$ west build -b nrf52840_mdk

 

Lawrence King

Principal Developer

Connected Transport Market Unit

https://www.Irdeto.com

+1(416)627-7302

 

1  2 - linkedin  3 - instagram  4 - youtube  6 - facebook  7

            

CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.

 

 

 


Re: nrf.h missing....

Nashif, Anas
 

Did you run `west update` ?

 

From: <users@...> on behalf of Lawrence King <lawrence.king@...>
Date: Wednesday, 4 September 2019 at 14:05
To: "Zephyr-users@..." <Zephyr-users@...>
Cc: "carles.cufi@..." <carles.cufi@...>
Subject: [Zephyr-users] nrf.h missing....

 

Today I upgraded to the head of the zephyr tree and my compile broke. Backing up to the labels

v2.0.0-rc3

v2.0.0-rc2

v2.0.0-rc1

I found that my compile became broken somewhere between rc1 and rc2. A quick ‘git bisect’ found that the change that breaks my compile is:

 

cf3af6af5fa3e656d6caf0b3429fde52e895fa79 is the first bad commit

commit cf3af6af5fa3e656d6caf0b3429fde52e895fa79

Author: Carles Cufi <carles.cufi@...>

Date:   Thu Aug 15 17:17:01 2019 +0200

 

    ext: hal: Make Nordic HALs a Zephyr module

   

    Moved to an external repo,

    https://github.com/zephyrproject-rtos/hal_nordic.

   

    Signed-off-by: Carles Cufi <carles.cufi@...>

 

:100644 100644 73ad5c4f4fd10c2c1e3fbc0cc718b9f44cc198e7 696b06ec0d05db577603e10331186412f60ecbe3 M              CODEOWNERS

:040000 040000 26b7c0c40f816f24989e7a7507cc21e298413f8e 8e387167b591b949828dc0ca08e0aff80ad5919f M          ext

:040000 040000 772099e01dd7e4f586c782eb079b11ffbec86d39 2b5a71ac9918e09e3c801b2e90746da19f8b9437 M              modules

:100644 100644 08f26e785ead096c10fcec7905c0e1061b8ba3f6 fe98cafd8cf915bf73f82e25abfb5a4c2b83fcbd M              west.yml

 

For now my workaround is to stay at rc1.

 

I am using today’s release of west (0.6.2), I haven’t tried reverting west yet, but I did try manually running cmake and ninja and I get the same error, so I suspect this is not a west problem.

 

Here is the build error message I get (can’t find <nrf.h>):

 

lawrence@VM:~/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky$ west build -b nrf52840_mdk

-- west build: build configuration:

       source directory: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky

       build directory: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build (created)

       BOARD: nrf52840_mdk (origin: command line)

-- west build: generating a build system

Zephyr version: 2.0.0

-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.8", minimum required is "3.4")

-- Selected BOARD nrf52840_mdk

-- Found west: /home/lawrence/.local/bin/west (found suitable version "0.6.2", minimum required is "0.6.0")

-- Loading /home/lawrence/workspace/rc-demo/zephyr/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk.dts as base

-- Overlaying /home/lawrence/workspace/rc-demo/zephyr/zephyr/dts/common/common.dts

Device tree configuration written to /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/include/generated/generated_dts_board.conf

Parsing Kconfig tree in /home/lawrence/workspace/rc-demo/zephyr/zephyr/Kconfig

Loaded configuration '/home/lawrence/workspace/rc-demo/zephyr/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk_defconfig'

Merged configuration '/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/prj.conf'

Configuration saved to '/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/.config'

 

warning: UART_CONSOLE (defined at drivers/console/Kconfig:46) was assigned the value 'y' but got the

value 'n'. You can check symbol information (including dependencies) in the 'menuconfig' interface

(see the Application Development Primer section of the manual), or in the Kconfig reference at

http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_UART_CONSOLE.html (which is updated

regularly from the master branch). See the 'Setting configuration values' section of the Board

Porting Guide as well.

 

warning: the choice symbol UART_0_NRF_UART (defined at drivers/serial/Kconfig.nrfx:28) was selected

(set =y), but no symbol ended up as the choice selection.  You can check symbol information

(including dependencies) in the 'menuconfig' interface (see the Application Development Primer

section of the manual), or in the Kconfig reference at

http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_UART_0_NRF_UART.html (which is updated

regularly from the master branch). See the 'Setting configuration values' section of the Board

Porting Guide as well.

-- Cache files will be written to: /home/lawrence/.cache/zephyr

-- The C compiler identification is GNU 6.3.1

-- The CXX compiler identification is GNU 6.3.1

-- The ASM compiler identification is GNU

-- Found assembler: /usr/bin/arm-none-eabi-gcc

-- Performing Test toolchain_is_ok

-- Performing Test toolchain_is_ok - Success

Including module: civetweb in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/civetweb

Including module: esp-idf in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/esp-idf/zephyr

Including module: fatfs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/fatfs

Including module: qmsi in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/qmsi

Including module: cypress in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/cypress

Including module: silabs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/silabs

Including module: st in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/st

Including module: stm32 in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/stm32

Including module: libmetal in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/libmetal

Including module: lvgl in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/gui/lvgl

Including module: mbedtls in path: /home/lawrence/workspace/rc-demo/zephyr/modules/crypto/mbedtls

Including module: mcumgr in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/mcumgr

Including module: nffs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/nffs

Including module: open-amp in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/open-amp

Including module: openthread in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/openthread

Including module: segger in path: /home/lawrence/workspace/rc-demo/zephyr/modules/debug/segger

Including module: tinycbor in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/tinycbor

Including module: littlefs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/littlefs

-- Configuring done

-- Generating done

-- Build files have been written to: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build

-- west build: building application

[2/109] Preparing syscall dependency handling

 

[8/109] Building C object zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj

FAILED: zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj

ccache /usr/bin/arm-none-eabi-gcc -DBUILD_VERSION=v2.0.0-rc1-156-gcf3af6af5fa3 -DKERNEL -D_FORTIFY_SOURCE=2 -D__ZEPHYR__=1 -I../../../../kernel/include -I../../../../arch/arm/include -I../../../../include -I../../../../include/drivers -Izephyr/include/generated -I../../../../soc/arm/nordic_nrf/nrf52 -I../../../../soc/arm/nordic_nrf/include -I../../../../ext/hal/cmsis/Include -isystem ../../../../lib/libc/minimal/include -isystem /usr/lib/gcc/arm-none-eabi/6.3.1/include -isystem /usr/lib/gcc/arm-none-eabi/6.3.1/include-fixed -Os -imacros/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mthumb -mcpu=cortex-m4 -imacros/home/lawrence/workspace/rc-demo/zephyr/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -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 -ffunction-sections -fdata-sections -mabi=aapcs -march=armv7e-m -std=c99 -nostdinc -MD -MT zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj -MF zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj.d -o zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj   -c /home/lawrence/workspace/rc-demo/zephyr/zephyr/arch/arm/core/offsets/offsets.c

In file included from ../../../../include/arch/arm/cortex_m/cmsis.h:17:0,

                 from ../../../../include/arch/arm/cortex_m/mpu/arm_mpu_v7m.h:10,

                 from ../../../../include/arch/arm/cortex_m/mpu/arm_mpu.h:13,

                 from ../../../../include/arch/arm/arch.h:246,

                 from ../../../../include/arch/cpu.h:17,

                 from ../../../../include/kernel_includes.h:34,

                 from ../../../../include/kernel.h:17,

                 from ../../../../kernel/include/kernel_structs.h:10,

                 from /home/lawrence/workspace/rc-demo/zephyr/zephyr/arch/arm/core/offsets/offsets.c:26:

../../../../soc/arm/nordic_nrf/nrf52/soc.h:17:17: fatal error: nrf.h: No such file or directory

#include <nrf.h>

                 ^

compilation terminated.

ninja: build stopped: subcommand failed.

ERROR: command exited with status 1: /home/lawrence/.local/bin/cmake --build /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build

 

The problem exists compiling simple things like blinky. To reproduce the issue run the following commands:

              $ cd zephyr/samples/basic/blinky

$ west build -b nrf52840_mdk

 

Lawrence King

Principal Developer

Connected Transport Market Unit

https://www.Irdeto.com

+1(416)627-7302

 

1  2 - linkedin  3 - instagram  4 - youtube  6 - facebook  7

            

CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.

 

 

 


nrf.h missing....

Lawrence King
 

Today I upgraded to the head of the zephyr tree and my compile broke. Backing up to the labels

v2.0.0-rc3

v2.0.0-rc2

v2.0.0-rc1

I found that my compile became broken somewhere between rc1 and rc2. A quick ‘git bisect’ found that the change that breaks my compile is:

 

cf3af6af5fa3e656d6caf0b3429fde52e895fa79 is the first bad commit

commit cf3af6af5fa3e656d6caf0b3429fde52e895fa79

Author: Carles Cufi <carles.cufi@...>

Date:   Thu Aug 15 17:17:01 2019 +0200

 

    ext: hal: Make Nordic HALs a Zephyr module

   

    Moved to an external repo,

    https://github.com/zephyrproject-rtos/hal_nordic.

   

    Signed-off-by: Carles Cufi <carles.cufi@...>

 

:100644 100644 73ad5c4f4fd10c2c1e3fbc0cc718b9f44cc198e7 696b06ec0d05db577603e10331186412f60ecbe3 M              CODEOWNERS

:040000 040000 26b7c0c40f816f24989e7a7507cc21e298413f8e 8e387167b591b949828dc0ca08e0aff80ad5919f M          ext

:040000 040000 772099e01dd7e4f586c782eb079b11ffbec86d39 2b5a71ac9918e09e3c801b2e90746da19f8b9437 M              modules

:100644 100644 08f26e785ead096c10fcec7905c0e1061b8ba3f6 fe98cafd8cf915bf73f82e25abfb5a4c2b83fcbd M              west.yml

 

For now my workaround is to stay at rc1.

 

I am using today’s release of west (0.6.2), I haven’t tried reverting west yet, but I did try manually running cmake and ninja and I get the same error, so I suspect this is not a west problem.

 

Here is the build error message I get (can’t find <nrf.h>):

 

lawrence@VM:~/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky$ west build -b nrf52840_mdk

-- west build: build configuration:

       source directory: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky

       build directory: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build (created)

       BOARD: nrf52840_mdk (origin: command line)

-- west build: generating a build system

Zephyr version: 2.0.0

-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.8", minimum required is "3.4")

-- Selected BOARD nrf52840_mdk

-- Found west: /home/lawrence/.local/bin/west (found suitable version "0.6.2", minimum required is "0.6.0")

-- Loading /home/lawrence/workspace/rc-demo/zephyr/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk.dts as base

-- Overlaying /home/lawrence/workspace/rc-demo/zephyr/zephyr/dts/common/common.dts

Device tree configuration written to /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/include/generated/generated_dts_board.conf

Parsing Kconfig tree in /home/lawrence/workspace/rc-demo/zephyr/zephyr/Kconfig

Loaded configuration '/home/lawrence/workspace/rc-demo/zephyr/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk_defconfig'

Merged configuration '/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/prj.conf'

Configuration saved to '/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/.config'

 

warning: UART_CONSOLE (defined at drivers/console/Kconfig:46) was assigned the value 'y' but got the

value 'n'. You can check symbol information (including dependencies) in the 'menuconfig' interface

(see the Application Development Primer section of the manual), or in the Kconfig reference at

http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_UART_CONSOLE.html (which is updated

regularly from the master branch). See the 'Setting configuration values' section of the Board

Porting Guide as well.

 

warning: the choice symbol UART_0_NRF_UART (defined at drivers/serial/Kconfig.nrfx:28) was selected

(set =y), but no symbol ended up as the choice selection.  You can check symbol information

(including dependencies) in the 'menuconfig' interface (see the Application Development Primer

section of the manual), or in the Kconfig reference at

http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_UART_0_NRF_UART.html (which is updated

regularly from the master branch). See the 'Setting configuration values' section of the Board

Porting Guide as well.

-- Cache files will be written to: /home/lawrence/.cache/zephyr

-- The C compiler identification is GNU 6.3.1

-- The CXX compiler identification is GNU 6.3.1

-- The ASM compiler identification is GNU

-- Found assembler: /usr/bin/arm-none-eabi-gcc

-- Performing Test toolchain_is_ok

-- Performing Test toolchain_is_ok - Success

Including module: civetweb in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/civetweb

Including module: esp-idf in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/esp-idf/zephyr

Including module: fatfs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/fatfs

Including module: qmsi in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/qmsi

Including module: cypress in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/cypress

Including module: silabs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/silabs

Including module: st in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/st

Including module: stm32 in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/stm32

Including module: libmetal in path: /home/lawrence/workspace/rc-demo/zephyr/modules/hal/libmetal

Including module: lvgl in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/gui/lvgl

Including module: mbedtls in path: /home/lawrence/workspace/rc-demo/zephyr/modules/crypto/mbedtls

Including module: mcumgr in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/mcumgr

Including module: nffs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/nffs

Including module: open-amp in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/open-amp

Including module: openthread in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/openthread

Including module: segger in path: /home/lawrence/workspace/rc-demo/zephyr/modules/debug/segger

Including module: tinycbor in path: /home/lawrence/workspace/rc-demo/zephyr/modules/lib/tinycbor

Including module: littlefs in path: /home/lawrence/workspace/rc-demo/zephyr/modules/fs/littlefs

-- Configuring done

-- Generating done

-- Build files have been written to: /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build

-- west build: building application

[2/109] Preparing syscall dependency handling

 

[8/109] Building C object zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj

FAILED: zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj

ccache /usr/bin/arm-none-eabi-gcc -DBUILD_VERSION=v2.0.0-rc1-156-gcf3af6af5fa3 -DKERNEL -D_FORTIFY_SOURCE=2 -D__ZEPHYR__=1 -I../../../../kernel/include -I../../../../arch/arm/include -I../../../../include -I../../../../include/drivers -Izephyr/include/generated -I../../../../soc/arm/nordic_nrf/nrf52 -I../../../../soc/arm/nordic_nrf/include -I../../../../ext/hal/cmsis/Include -isystem ../../../../lib/libc/minimal/include -isystem /usr/lib/gcc/arm-none-eabi/6.3.1/include -isystem /usr/lib/gcc/arm-none-eabi/6.3.1/include-fixed -Os -imacros/home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mthumb -mcpu=cortex-m4 -imacros/home/lawrence/workspace/rc-demo/zephyr/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -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 -ffunction-sections -fdata-sections -mabi=aapcs -march=armv7e-m -std=c99 -nostdinc -MD -MT zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj -MF zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj.d -o zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj   -c /home/lawrence/workspace/rc-demo/zephyr/zephyr/arch/arm/core/offsets/offsets.c

In file included from ../../../../include/arch/arm/cortex_m/cmsis.h:17:0,

                 from ../../../../include/arch/arm/cortex_m/mpu/arm_mpu_v7m.h:10,

                 from ../../../../include/arch/arm/cortex_m/mpu/arm_mpu.h:13,

                 from ../../../../include/arch/arm/arch.h:246,

                 from ../../../../include/arch/cpu.h:17,

                 from ../../../../include/kernel_includes.h:34,

                 from ../../../../include/kernel.h:17,

                 from ../../../../kernel/include/kernel_structs.h:10,

                 from /home/lawrence/workspace/rc-demo/zephyr/zephyr/arch/arm/core/offsets/offsets.c:26:

../../../../soc/arm/nordic_nrf/nrf52/soc.h:17:17: fatal error: nrf.h: No such file or directory

#include <nrf.h>

                 ^

compilation terminated.

ninja: build stopped: subcommand failed.

ERROR: command exited with status 1: /home/lawrence/.local/bin/cmake --build /home/lawrence/workspace/rc-demo/zephyr/zephyr/samples/basic/blinky/build

 

The problem exists compiling simple things like blinky. To reproduce the issue run the following commands:

              $ cd zephyr/samples/basic/blinky

$ west build -b nrf52840_mdk

 

Lawrence King

Principal Developer

Connected Transport Market Unit

https://www.Irdeto.com

+1(416)627-7302

 

1  2 - linkedin  3 - instagram  4 - youtube  6 - facebook  7

            

CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.

 

 

 


Re: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2

Bolivar, Marti
 

"Youse, Charles via Lists.Zephyrproject.Org"
<charles.youse=intel.com@lists.zephyrproject.org> writes:

Hi Marti,

In spite of the fact that it doesn't cause data loss, it seems
extremely serious, considering that west basically has one job
(versioning).
I agree that it is a serious bug (see "high impact", below), and again,
I'm sorry for the lack of test coverage that led to it happening in the
first place. I'm grateful to the reporter for bringing it up.

Now that the hotfix is out in the 0.6.x branch, I'm going to be adding
regression testing. I do my best to make sure fixes get regression
tests.

Thanks,
Marti


Thanks,
Charles


-----Original Message-----
From: devel@lists.zephyrproject.org [mailto:devel@lists.zephyrproject.org] On Behalf Of Bolivar, Marti
Sent: Wednesday, September 4, 2019 12:39 PM
To: users@lists.zephyrproject.org; devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2

Marti Bolivar <marti.bolivar@nordicsemi.no> writes:

Hi,

West v0.6.1 contains a high impact bug in the "west update" behavior
that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected.
I was requested to add a link to the bug:

https://github.com/zephyrproject-rtos/west/issues/298

It won't cause data loss, but it will cause west update to fail to check out the correct revision in some cases.

Marti


If you are using west v0.6.1 (check with west --version), please
upgrade now using the usual process:

Linux:

pip3 install -U --user west

macOS and Windows:

pip3 install -U west

Thanks,
Marti



Re: Do not use west v0.6.1; upgrade to v0.6.2

Bolivar, Marti
 

"Youse, Charles" <charles.youse@intel.com> writes:

Marti,

Thanks for letting us know.
Of course.


Perhaps, since 'west' has been made practically essential to Zephyr,
we should investigate some kind of QA process for west releases.
We have a process in place. It failed here due to lack of coverage,
which unfortunate oversight and I'm very sorry for it, especially for
those who ran into it. However, it was lack of coverage, and not lack of
process, that was to blame.

West has a test suite that works at both API and functional levels. The
repository CI runs it on each commit (on Linux, via shippable). We also
run it on supported platforms before cutting a release. In this case,
that's Windows 10 and macOS. (This is in addition to informal testing
that people are doing on the code in the master branch, which isn't
relevant to this point since you are asking about process.)

More testers and attention to testing are always welcome, so feel free
to make any concrete suggestions for how we can improve our QA.

Thanks,
Marti


Thanks
Charles

-----Original Message-----
From: devel@lists.zephyrproject.org [mailto:devel@lists.zephyrproject.org] On Behalf Of Bolivar, Marti
Sent: Wednesday, September 4, 2019 9:48 AM
To: users@lists.zephyrproject.org; devel@lists.zephyrproject.org
Subject: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2

Hi,

West v0.6.1 contains a high impact bug in the "west update" behavior that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected.

If you are using west v0.6.1 (check with west --version), please upgrade now using the usual process:

Linux:

pip3 install -U --user west

macOS and Windows:

pip3 install -U west

Thanks,
Marti


Re: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2

Youse, Charles <charles.youse@...>
 

Hi Marti,

In spite of the fact that it doesn't cause data loss, it seems extremely serious, considering that west basically has one job (versioning).

Thanks,
Charles

-----Original Message-----
From: devel@lists.zephyrproject.org [mailto:devel@lists.zephyrproject.org] On Behalf Of Bolivar, Marti
Sent: Wednesday, September 4, 2019 12:39 PM
To: users@lists.zephyrproject.org; devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2

Marti Bolivar <marti.bolivar@nordicsemi.no> writes:

Hi,

West v0.6.1 contains a high impact bug in the "west update" behavior
that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected.
I was requested to add a link to the bug:

https://github.com/zephyrproject-rtos/west/issues/298

It won't cause data loss, but it will cause west update to fail to check out the correct revision in some cases.

Marti


If you are using west v0.6.1 (check with west --version), please
upgrade now using the usual process:

Linux:

pip3 install -U --user west

macOS and Windows:

pip3 install -U west

Thanks,
Marti


Re: Do not use west v0.6.1; upgrade to v0.6.2

Bolivar, Marti
 

Marti Bolivar <marti.bolivar@nordicsemi.no> writes:

Hi,

West v0.6.1 contains a high impact bug in the "west update" behavior that
is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected.
I was requested to add a link to the bug:

https://github.com/zephyrproject-rtos/west/issues/298

It won't cause data loss, but it will cause west update to fail to
check out the correct revision in some cases.

Marti


If you are using west v0.6.1 (check with west --version), please upgrade
now using the usual process:

Linux:

pip3 install -U --user west

macOS and Windows:

pip3 install -U west

Thanks,
Marti


Re: Error in NRF SoC flash memory compilation #nrf52840

Marc Herbert
 

Hi,

 

Are these messages from a C++ compiler? If yes trying casting.

 

Marc

 

From: <users@...> on behalf of "giriprasad@..." <giriprasad@...>
Date: Wednesday, 4 September 2019 at 01:59
To: "users@..." <users@...>
Subject: [Zephyr-users] Error in NRF SoC flash memory compilation #nrf52840

 

When Iam trying to include flash.h file in my application noticed below compilation error.

Can you help me to resolve the issue

 

ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'int z_impl_flash_read(device*, off_t, void*, size_t)':
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h:104:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;
                                       ~~~~~^~~~~~~~~~
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'int z_impl_flash_write(device*, off_t, const void*, size_t)':
EPHYR/zephyrproject/zephyr/include/drivers/flash.h:128:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;
                                       ~~~~~^~~~~~~~~~
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'int z_impl_flash_erase(device*, off_t, size_t)':
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h:159:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;
                                       ~~~~~^~~~~~~~~~
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'int z_impl_flash_write_protection_set(device*, bool)':
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h:185:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;
                                       ~~~~~^~~~~~~~~~
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'size_t z_impl_flash_get_write_block_size(device*)':
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h:272:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;


Re: Do not use west v0.6.1; upgrade to v0.6.2

Youse, Charles <charles.youse@...>
 

Marti,

Thanks for letting us know.

Perhaps, since 'west' has been made practically essential to Zephyr, we should investigate some kind of QA process for west releases.

Thanks
Charles

-----Original Message-----
From: devel@lists.zephyrproject.org [mailto:devel@lists.zephyrproject.org] On Behalf Of Bolivar, Marti
Sent: Wednesday, September 4, 2019 9:48 AM
To: users@lists.zephyrproject.org; devel@lists.zephyrproject.org
Subject: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2

Hi,

West v0.6.1 contains a high impact bug in the "west update" behavior that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected.

If you are using west v0.6.1 (check with west --version), please upgrade now using the usual process:

Linux:

pip3 install -U --user west

macOS and Windows:

pip3 install -U west

Thanks,
Marti


Do not use west v0.6.1; upgrade to v0.6.2

Bolivar, Marti
 

Hi,

West v0.6.1 contains a high impact bug in the "west update" behavior that
is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected.

If you are using west v0.6.1 (check with west --version), please upgrade
now using the usual process:

Linux:

pip3 install -U --user west

macOS and Windows:

pip3 install -U west

Thanks,
Marti


eclipse

novello
 

Sorry But I have find the same problem  with eclipse.
If I use  the command line it work.
(STM32 microcontroller)
Best regards
Novello G


Error in NRF SoC flash memory compilation #nrf52840

giriprasad@...
 

When Iam trying to include flash.h file in my application noticed below compilation error.
Can you help me to resolve the issue
 
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'int z_impl_flash_read(device*, off_t, void*, size_t)':
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h:104:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;
                                       ~~~~~^~~~~~~~~~
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'int z_impl_flash_write(device*, off_t, const void*, size_t)':
EPHYR/zephyrproject/zephyr/include/drivers/flash.h:128:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;
                                       ~~~~~^~~~~~~~~~
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'int z_impl_flash_erase(device*, off_t, size_t)':
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h:159:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;
                                       ~~~~~^~~~~~~~~~
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'int z_impl_flash_write_protection_set(device*, bool)':
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h:185:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;
                                       ~~~~~^~~~~~~~~~
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h: In function 'size_t z_impl_flash_get_write_block_size(device*)':
ZEPHYR/zephyrproject/zephyr/include/drivers/flash.h:272:44: error: invalid conversion from 'const void*' to 'const flash_driver_api*' [-fpermissive]
  const struct flash_driver_api *api = dev->driver_api;


C++ support (Eclipse CDT4) - 'printk' could not be resolved #west

Leo
 

Hello!

I am failing to create a Zephyr project for Eclipse with C++ support.
Is there a working example or guide I can use as reference to set this up?
My end goal is to use Zephyr + nRF SDK in C++ with debugging in any IDE, preferably SEGGER or Eclipse.

After importing project "hello_world", Eclipse underlines function "printk" in red:
    ==> Function 'printk' could not be resolved <==
    ==> Symbol 'CONFIG_BOARD' could not be resolved <==

Here's the steps I follow to setup the project:
    Toolchain:
        Zephyr 2.0.0
        west v0.6.0
        ninja 1.9.0
        cmake 3.15.2
        Eclipse 4.12 + GNU MCU 4.5.1
    
    Edit prj.conf and .config:
        CONFIG_PRINTK=y
        CONFIG_STDOUT_CONSOLE=y
        CONFIG_NEWLIB_LIBC=y
        CONFIG_LIB_CPLUSPLUS=y
    
    Run:
        west build -b nrf52840_pca10056 C:/embedded/zephyrproject/zephyr/samples/hello_world -- -G"Eclipse CDT4 - Ninja" -D_ECLIPSE_VERSION=4.12
        One warning:
            <...>
            [18/98] Building CXX object CMakeFiles/app.dir/src/main.cpp.obj
            cc1plus.exe: warning: command line option '-Wno-pointer-sign' is valid for C/ObjC but not for C++
    
    Import project into Eclipse
        Error in main.cpp:
        Function 'printk' could not be resolved
    
    Also tried:
        set (CMAKE_CXX_STANDARD 11) in CMakeLists.txt
        Manually add "__cplusplus=201402L" as a symbol in Eclipse (cmake does not generate such symbol in .cproject)
        Force boilerplate.cmake to call eclipse_cdt4_generator_amendment with work mode = 2 (.cproject with __cplusplus)
    
Thanks!


API meeting: agenda

Carles Cufi
 

Hi all,

This week we will look at:

Agenda:

- Sensor API: Potential sharing between V4Z and rtio
- GPIO: Update on https://github.com/zephyrproject-rtos/zephyr/pull/16648 and possibly merging it

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: Have someone a guide to use PPP with the module quectel GSM/GPRS M95? #protocol #driver #ppp

William Fish
 

Lucas,
Have a look at the Sara modem driver as a good starting point.

drivers/modem

Billy..


Have someone a guide to use PPP with the module quectel GSM/GPRS M95? #protocol #driver #ppp

Lucas Peixoto
 

Hello, I'm using a module named Quectel GSM/GPRS M95 to connect to the internet. Until now I'm using it with UART and AT commands, but I'm wondering to use the PPP that released in v2.0.0-rc2 version. This module has commands to activate the communication via PPP. I'm thinking to use the module's UART to receive and send the datagrams in the network, and these datagrams will be handle by PPP. How can I do this? Does anyone have an idea?


Re: NRF52832 debugging in eclipse #nrf52832 #jlink #debugging #eclipse

Maureen Helm
 

Does the application work without the debugger attached? (i.e., did it get programmed into flash correctly?)

 

I’ve seen weird behavior if you leave the GDB client executable at the default. Try changing this so it comes from the Zephyr SDK (or GNU Arm Embedded, if you’re using that toolchain instead).

 

From: users@... <users@...> On Behalf Of stefan.hristozov via Lists.Zephyrproject.Org
Sent: Thursday, August 29, 2019 4:19 AM
To: users@...
Cc: users@...
Subject: [Zephyr-users] NRF52832 debugging in eclipse #nrf52832 #jlink #debugging #eclipse

 

Hi,
i am trying to set up eclipse, gdb and jlink for debugging NRF52832. I am using a PCA10040 board with an integrated Jlink debugger.  I have a simple project with a single main.c file. My prj.conf are:

CONFIG_DEBUG=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_SYS_PM_DEBUG=y

I configured the debugger in eclipse as shown in the figures:




Unfortunately when I start the debug session the execution stops in the _find_fd_entry:






How to properly configure the debugger for debugging zephyrs applications?


Running Zephyr on Arty, #litex

ps.lindblad@...
 

Hi, I've been trying to get a Zephyr sample running on the Arty FPGA-board without succeeding.
I’ve tried both using the zephyr-sdk toolchain and cross-compile toolchain with the same unsatisfying result.
Litex boots fine and firmware is uploaded but then nothing.

Is there any working prebuilt Litex gateware – Zephyr firmware combination available to test with?

Thanks,
Stefan


printenv | grep ZEPHYR
ZEPHYR_TOOLCHAIN_VARIANT=zephyr
ZEPHYR_BASE=/home/stefan/FPGA/Zeph/zephyr
ZEPHYR_SDK_INSTALL_DIR=/opt/zephyr-sdk/
stefan@virtLinux:~/FPGA/Zeph/zephyr$ ls
arch    CMakeLists.txt      doc      include         lib       modules     soc      version.h.in
boards  CODE_OF_CONDUCT.md  drivers  Kconfig         LICENSE   README.rst  subsys   west.yml
build   CODEOWNERS          dts      Kconfig.zephyr  Makefile  samples     tests    zephyr-env.cmd
cmake   CONTRIBUTING.rst    ext      kernel          misc      scripts     VERSION  zephyr-env.sh
stefan@virtLinux:~/FPGA/Zeph/zephyr$ west build -b litex_vexriscv samples/hello_world
-- west build: build configuration:
       source directory: /home/stefan/FPGA/Zeph/zephyr/samples/hello_world
       build directory: /home/stefan/FPGA/Zeph/zephyr/build
       BOARD: litex_vexriscv (origin: CMakeCache.txt)
-- west build: building application
ninja: no work to do.
stefan@virtLinux:~/FPGA/Zeph/zephyr$ lxterm --serial-boot --kernel build/zephyr/zephyr.bin /dev/ttyUSB1
[LXTERM] Starting....

        __   _ __      _  __
       / /  (_) /____ | |/_/
      / /__/ / __/ -_)>  <
     /____/_/\__/\__/_/|_|

 (c) Copyright 2012-2019 Enjoy-Digital
 (c) Copyright 2007-2015 M-Labs Ltd

 BIOS built on Aug 27 2019 22:09:58
 BIOS CRC passed (354dfde9)

 Migen git sha1: --------
 LiteX git sha1: 5a7b4c34

--============ SoC info ================--
CPU:       VexRiscv @ 100MHz
ROM:       32KB
SRAM:      32KB
L2:        8KB
MAIN-RAM:  262144KB

--========= Peripherals init ===========--
Initializing SDRAM...
SDRAM now under software control
Read leveling:
m0, b0: |11111100000000000000000000000000| delays: 03+-03
m0, b1: |00000000000011111111100000000000| delays: 16+-04
m0, b2: |00000000000000000000000000001111| delays: 30+-02
m0, b3: |00000000000000000000000000000000| delays: -
m0, b4: |00000000000000000000000000000000| delays: -
m0, b5: |00000000000000000000000000000000| delays: -
m0, b6: |00000000000000000000000000000000| delays: -
m0, b7: |00000000000000000000000000000000| delays: -
best: m0, b1 delays: 16+-04
m1, b0: |11111111100000000000000000000000| delays: 04+-04
m1, b1: |00000000000001111111111100000000| delays: 18+-05
m1, b2: |00000000000000000000000000000111| delays: 30+-01
m1, b3: |00000000000000000000000000000000| delays: -
m1, b4: |00000000000000000000000000000000| delays: -
m1, b5: |00000000000000000000000000000000| delays: -
m1, b6: |00000000000000000000000000000000| delays: -
m1, b7: |00000000000000000000000000000000| delays: -
best: m1, b1 delays: 18+-05
SDRAM now under hardware control
Memtest OK

--========== Boot sequence =============--
Booting from serial...
Press Q or ESC to abort boot completely.
sL5DdSMmkekro
[LXTERM] Received firmware download request from the device.
[LXTERM] Uploading build/zephyr/zephyr.bin to 0x40000000 (9608 bytes)...
[LXTERM] Upload complete (7.7KB/s).
[LXTERM] Booting the device.
[LXTERM] Done.
Executing booted program at 0x40000000
--============= Liftoff! ===============--







NRF52832 debugging in eclipse #nrf52832 #jlink #debugging #eclipse

Stefan Hristozov
 

Hi,
i am trying to set up eclipse, gdb and jlink for debugging NRF52832. I am using a PCA10040 board with an integrated Jlink debugger.  I have a simple project with a single main.c file. My prj.conf are:

CONFIG_DEBUG=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_SYS_PM_DEBUG=y

I configured the debugger in eclipse as shown in the figures:




Unfortunately when I start the debug session the execution stops in the _find_fd_entry:






How to properly configure the debugger for debugging zephyrs applications?


API meeting: agenda

Carles Cufi
 

Hi all,

This week we will look at:

Agenda:

- Sensor API: Update on progress
- GPIO: Update on https://github.com/zephyrproject-rtos/zephyr/pull/16648 and possibly merging it

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

1041 - 1060 of 2705