Hi Carles, Thanks for the feedback. It seems the Qt QLowerEnergyController object selects the first valid address different from the zero address for addressing the HCI controller/adapter. In my case

Hi Paul, I have found it in this link - https://github.com/zephyrproject-rtos/zephyr/issues/10561 By referring the config file also we can able to find Echo client and server example can be built for

I managed to solve this by calling "k_thread_access_grant(k_current_get(), dev, NULL)" before calling the "Z_SYSCALL_DRIVER_SENSOR" macro. This question remains open.

Hello Zephyrs, I'm developing a shell module for the sensor drivers and I want to validate if the device name passed from the user is a sensor device. I have the CONFIG_USERSAPCE=y. After calling

Hi Nick, Once you’ve generated your project with CMake and imported it into Eclipse, you can edit source files in Eclipse and click the “Make” button to recompile your application. Just be

Hello, I want to develop applications using the FRDM-K64F board from NXP using Eclipse. Is there any way to use Eclipse as an IDE and create a program, then flash it onto the board? I want to do

We do dump this info to the console on a fatal CPU exception. On x86 there's even a crude stack trace. But it would be nice, if running some application under GDB, for the exception to simply break

It's better to call k_oops() or k_panic() than _SysFatalErrorHandler() directly. You will actually get useful information about where the error occurred, instead of having to pass in a NULL exception

Thanks everyone, I will have a look at the DTS. Cheers, From: Diego Sueiro [mailto:diego.sueiro@...] Sent: Friday, November 9, 2018 10:32 AM To: Andrei <andrei.emeltchenko.news@...> Cc:

Take a look at the documentation to understand how this process works: https://docs.zephyrproject.org/latest/devices/dts/device_tree.html

Hi, It is done somehow through DTS, you need to search i.e. ./zephyr/include/generated/generated_dts_board.h Best regards Andrei Emeltchenko

Hi, I am currently working on the Zephyr OS with a FDRM_K64f board from NXP. I am just going through the documentation and the code example for now. I have trouble to understand where is the

Hallo Zephyr community, Anyone knowing why the BD address is always the ZERO address, when using the nRF52 board running the Zephyr HCI uart hex. I also see that the random address remains the

Current implementation: The __ASSERT macro is extensively used in the Zephyr codebase and in application code for debugging during development. In case of an ASSERT, the code jumps to __ASSERT_POST

Thanks for your reply Paul. Perhaps something simliar to this: #if defined(CONFIG_ARCH_POSIX) extern void posix_exit(int exit_code); #define __ASSERT_POST posix_exit(1) #elif

Hi there, The *public* address is all zeroes because Nordic ICs do not come with one pre-assigned. The *random static* address is set by BlueZ itself, so it will be whatever BlueZ decides it to

Hello Kristoffer, As a quick reply, definitely ack on the problem statement. I can say more, I'm patiently waiting for a paradise times when on CPU exception, assert, etc., we'll be ending up in

Hallo Zephyr community, Anyone knowing why the BD address is always the ZERO address, when using the nRF52 board running the Zephyr HCI uart hex. I also see that the random address remains the

https://github.com/zephyrproject-rtos/zephyr/pull/11231 Could you please test the PR on your board and let me know if its better. Find attach the patch file as alternative to the diff in PR. Use

Current implementation: The __ASSERT macro is extensively used in the Zephyr code base and in application code for debugging during development. In case of an ASSERT, the code jumps to __ASSERT_POST