Hi, See inline. "Moiz Terem via lists.zephyrproject.org" <moiz.terem=inomize.com@...> writes: I'm not sure what you are asking. PyPI doesn't have any relationship with Symantec tha

Hi, The hci_spi sample was originally upstreamed for use on the nRF51 chip on the 96Boards Carbon board. Please refer to the documentation for that board for more information. You can refer to 96b_car

Hi, "Frank Duignan via lists.zephyrproject.org" <frank.duignan=gmail.com@...> writes: Yes, this is a GPIO nexus node. For details on these, see "2.5 Nexus Nodes and Specifier Mappi

Hi again Ilkka, "ilkka.virtanen via lists.zephyrproject.org" <ilkka.virtanen=sensoan.com@...> writes: I'm glad; thanks! Yes, you can, you just need to make sure the initialization

#driver #sensor

Hi, This email list is for upstream zephyr, not NCS, but since the sample is available in upstream zephyr I will respond here. "ilkka.virtanen via lists.zephyrproject.org" <ilkka.virtanen=sensoan.com@

#driver #sensor

"DKaplan via lists.zephyrproject.org" <DKaplan=amiglobal.com@...> writes: Hello! Since you're using NCS, if you haven't figured this out yet, I'd recommend asking on DevZone. This

#nrf9160

Marti Bolivar <marti.bolivar@...> writes: D'oh, I forgot to reply-all.

Hi, +Armando "frank.duignan via lists.zephyrproject.org" <frank.duignan=gmail.com@...> writes: Did you send a pull request with the fix? If not, please do. Although I'm confused ab

#i2c #driver #lis2dw12

Hi again Kristoff, "Kristoff Bonne via lists.zephyrproject.org" <kristoff=skypro.be@...> writes: Just to be clear although I mentioned this in my response to your other thread, the

Hi there, The error message may have gotten lost in the rest of the output, but it describes what went wrong, a stack trace where it went wrong, and how to fix it: "wbasser via lists.zephyrproject.org

#customboard #dts

Hi Raz, I'm curious what version of Zephyr you're running. Since your error message mentions devicetree_fixups.h, it seems it might be on the older side. The DT "fixups" feature was deprecated in Zeph

Hello, Please refer to this troubleshooting item: https://docs.zephyrproject.org/latest/guides/west/troubleshooting.html#invalid-choice-build-or-flash-etc "Olga Syrbachova via lists.zephyrproject.org"

Hi there, You can read through the 'west flash -H -r openocd' output to see what options you have for overriding the default behavior, but the short answer is no, most of this is determined by the boa

Hi, "Steven Ghekiere via lists.zephyrproject.org" <steven.ghekiere=student.kuleuven.be@...> writes: The location of the zephyr repository is available to CMake in the ZEPHYR_BASE v

In general, that's left as an exercise for the user, as far as I know. "Nikos Karamolegkos via lists.zephyrproject.org" <nkaram=ics.forth.gr@...> writes:

#nrf52840 #crypto #dts

Hi, You should just need to add it to the build system's Kconfig and CMakeLists.txt hierarchy like any other file in your module. There are worked examples in https://github.com/nrfconnect/sdk-nrf/tre

Hi, I've uploaded a 2.2.0a1 release of the windows-curses package to PyPI. This is a dependency on Windows for the 'menuconfig' build system target. (POSIX platforms have curses and thus 'menuconfig'

Hi, It's not clear what you are asking. By 'Zephyr requires the ability', what part of Zephyr do you mean? Some optional Zephyr subsystems (like DFU or file systems) require rewriting nonvolatile stor

Hello, I'm announcing the release of west v0.8.0. https://pypi.org/project/west/0.8.0/ https://github.com/zephyrproject-rtos/west/tree/v0.8.0 Release notes: https://docs.zephyrproject.org/latest/guide

"Henrik Brix Andersen via lists.zephyrproject.org" <henrik=brixandersen.dk@...> writes: I have one and it's working for me also. Try plugging it in while 'udevadm monitor' is runni

#reel_board #flash