Hi all, We have just merged a commit [1] which renames the Arm embedded toolchain from GCC ARM Embedded to its new and current name, GNU Arm Embedded. If you use this toolchain you will see a

Hi, I'm trying to port the central_hr example to my project. In this project I'm using a peripheral that advertises a 128Bit UUID of a custom service instead of the 16Bit UUID of the HRS service. I

Is it possible to Upgrade a bare metal firmware(not from zephyr, may be from nrf sdk example) through smp server explained in zephyr project ?

Hi Joe, thanks again for your fast answer. I tried to run spi_loopback/spi.c on nrf52840_pca10056 but i am still running into problems. I will explain the problem, if someone has the time to take a

Hej, I like to implement an firmware upgrade via bcsp + manufacture specific commands. I give a quick setup of my system: BT device <---> UART3 @ MCU <---> Zephyr OS The update

Hi Moritz, SPI does not have DTS support in nordic boards yet, so you still have to set it up via Kconfig until https://github.com/zephyrproject-rtos/zephyr/issues/8758 is completely resolved. The

Hello at all, i have a question concerning the nRF52-PCA10040. I want to connect the nRF52-PCA10040 to another board via SPI. However i cannot figure out a possible way to do so. The provided samples

As you see your toolchain is not correctly picking the gcc libraries from armv7e-m. I am not on my MacBook now, hopefully someone else could help you resolve the issue or will help set the CFLAGS

Hi, Did you, "Look for the “-L … “ option supplied when compiling."??? What folder path do you have? Incorrect library supplied will cause the hardfault when div operations is

Try: “ninja -v” If using make, then, its “make VERBOSE=1” Look for the “-L … “ option supplied when compiling. You can join the IRC #zephyrproject channel at

Hi Phil, Could you please build with verbose and check if correct gcc library for armv7e-m is compiled in (from the correct gcc revision). Which version of GCC do you use?

Thank you for letting me know. May be others in the community can follow up on the original issue with the toolchain from SDK-ng. Vinayak From: Finke Philipp (lesswire GmbH)

Hi, about the possible lib gcc toolchain issue. Of the available gcc.a, I am using the one suffixed with '#' when using the sdk. Note that it seems that this is different on

On my linux machine now… For the gcc I am using it is: -L"/usr/lib/gcc/arm-none-eabi/8.2.0/thumb/v7e-m/nofp" From: Finke Philipp (lesswire GmbH) [mailto:finke@...] Sent: Friday, August

I fixed the issue by switching to the GNU ARM Embedded Toolchain downloaded here: https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads

Hey, thanks a lot so far. What are the correct gcc libs that should be used?

Hey, that’s the only reasonable line I found in the output. -L"/Users/philippfinke/Documents/Git/zephyr/sdk/macos/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/7.3.0/thumb“ Mit freundlichen

Hey, the output shows that armv7-m is given as architecture (-march=armv7e-m). It seems I’m using following compiler: arm-zephyr-eabi-gcc (crosstool-NG 1.23.0.418-d590-dirty) 7.3.0 Copyright (C)

Hey Vinayak, how do I get these information? I’m using cmake with ninja as generator as recommended on the zephyr project page. Mit freundlichen Grüßen / best regards, Philipp Finke Development

Hello, I'm trying to run the BLE peripheral sample of the zephyr v1.12.0 branch on the NRF52840 PCA10056 DK. I built the sample under macOS 10.13.6 using the arm-zephyr-eabi toolchain built with