Hi, I need to include pre-compiled external libraries. I am not able to provide link directories path. I could add the library name with "target_link_libraries(app PRIVATE power)" but

Hello, I am trying to use the ADC on my Intel Galielo Gen 2 through the SPI. The problem is that all the calls of spi_transcieve() that I have tried using SPI_0 device seems to block at

Hi Luiz, The Zephyr SDK can be found on the Developers page in the Downloads section here: https://www.zephyrproject.org/developers/#downloads We'll re-work the page so its easier to find! Best, Thea

Hi Kumar, It seems there is no link for it in the developers page: https://www.zephyrproject.org/developers/ -- Luiz Augusto von Dentz

The is the first release of the Zephyr SDK that utilizes crosstool-ng to build the toolchains. We utilize crosstool-ng-1.24.0-rc2. Toolchain version: • GCC 8.3 • GDB 8.2.1 • BINUTILS

I am developing a piece of code for nrf52840 that uses 24 GPIOs. Conveniently the NRF52840-MDK board brings out exactly 24 GPIOs so I have enough hardware on hand. The application needs 12 inputs and

The nordic guys probably know better, but its possible that the flash that isn’t carved up is used for code. - k

Hi Yorick, This TEMP sensor are defined within zephyr sensors pattern. You should use it by binding the device to a struct and using the default functions from sensor.h You should use this to

Hello, I have recently started to use Zephyr. Up to now, I have been able to set up some tasks and ESS (with Temperature characteristic (dummy value for the moment)) and BAS Bluetooth profiles. The

Dear All, maybe I’m reading it wrong, but in all nRF52840-related DTS files, the memory layout ends at 524,288 bytes and I wonder why. That wastes the other 50% of the available storage. Is

Hi Marc, Just seeing this, thanks for the follow-up. I think this question of how much material to provide for auxiliary tools and dependencies is a probably a tough one. I think with pip/python,

Hi there, As you know, west now allows users to build Zephyr applications with it, and many among us have started making use of this new functionality. The signature for `west build` currently reads

Hi Phil, It doesn't have to be TLV index 0. You need to use the "type" in each type/length/value (TLV) datum to find the hash TLV in the image binary. I don't use mcumgr very much, just mcuboot, so I

---------- Forwarded message --------- From: Mani Sadhasivam <manivannanece23@...> Date: Tue, 5 Mar, 2019, 12:11 AM Subject: Re: [Zephyr-users] 96Boards GPIO standard names? To: Lawrence King

I have been writing code for a peripheral board that plugs into a Nitrogen or any other 96Boards compliant board (with 40-pin Low Speed connector) running Zephyr. I was trying to code use of the GPIOs

Hey Marti, thanks for your reply. So in my understanding the value of TLV 0 is the hash that will be displayed using "Image list", isn't it? Best Philipp

Hi Phil, If you mean the hash of the image header and body, that is available as the value for the IMAGE_TLV_SHA256 key type in your signed image's TLV area (see

Just my bad luck 😉, I checked out the master branch about 8 hours before you checked in the changes. Thanks for fixing this so others don’t have the same problem. A nice to have feature would

Hi Lawrence, On 2/27/19 8:39 AM, Lawrence King wrote: This was fixed recently in master branch:

Dear All: I am having a little problem starting the Settings on a nRF52 device. Ideally 8 blocks of flash memory should be reserved for the settings FCB, I ‘think’ this is what is configured