|
Re: Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle
#nrf52832
Hi Frank,
Right, since this seems to be more about BlueZ and Qt than about Zephyr or nRF, because nRF chipsets do not come with a public address registered and burned into the chip, I have copied
Hi Frank,
Right, since this seems to be more about BlueZ and Qt than about Zephyr or nRF, because nRF chipsets do not come with a public address registered and burned into the chip, I have copied
|
By
Carles Cufi
·
#5387
·
|
|
Re: Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle
#nrf52832
Hi Carles,
Humm... not quite, I have recently created a QT bug report (See : https://bugreports.qt.io/browse/QTBUG-71727) although I think different parties are to blame, I'm still not sure who is
Hi Carles,
Humm... not quite, I have recently created a QT bug report (See : https://bugreports.qt.io/browse/QTBUG-71727) although I think different parties are to blame, I'm still not sure who is
|
By
frv
·
#5386
·
Edited
|
|
Re: Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle
#nrf52832
Hi Frank,
I understand, so does that mean that you don’t need a public address? Since Qt seems to be doing the right thing.
Carles
Hi Frank,
I understand, so does that mean that you don’t need a public address? Since Qt seems to be doing the right thing.
Carles
|
By
Carles Cufi
·
#5385
·
|
|
Re: Zephyr Project using Eclipse
Fwd: List
On 12/11/18 09:44, Serafin wrote:
Fwd: List
On 12/11/18 09:44, Serafin wrote:
|
By
Serafin
·
#5384
·
|
|
Re: Zephyr Project using Eclipse
Morning,
A bit tricky because Eclipse CDT integration of cmake is only available at the latest release and imho not very good.
1.) build from eclipse
Simplest way:
Morning,
A bit tricky because Eclipse CDT integration of cmake is only available at the latest release and imho not very good.
1.) build from eclipse
Simplest way:
|
By
Stefan Jaritz
·
#5383
·
|
|
Re: #nrf52840 #ble unstable connection
#nrf52840
#ble
Hi Vinayak,
I merge the patch, host (nRF Connect) get update connection parameter request. After CI change to 30ms, it can keep connection a bit longer but it still disconnect after few minutes
Hi Vinayak,
I merge the patch, host (nRF Connect) get update connection parameter request. After CI change to 30ms, it can keep connection a bit longer but it still disconnect after few minutes
|
By
Randy Chou <rchou3@...>
·
#5382
·
|
|
Re: Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle
#nrf52832
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 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
|
By
frv
·
#5381
·
Edited
|
|
Re: lwip integration with OpenThread
#nrf52840
#lwip
#openthread
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
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
|
By
deepa.gopinath@...
·
#5380
·
|
|
Re: thread permissions issue
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.
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.
|
By
Diego Sueiro
·
#5379
·
|
|
thread permissions issue
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
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
|
By
Diego Sueiro
·
#5378
·
|
|
Re: Zephyr Project using Eclipse
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
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
|
By
Maureen Helm
·
#5377
·
|
|
Zephyr Project using Eclipse
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
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
|
By
Nicholas Yameen <Nicholas.Yameen@...>
·
#5376
·
|
|
Re: __ASSERT - transfer to error handler
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
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
|
By
Boie, Andrew P
·
#5375
·
|
|
Re: __ASSERT - transfer to error handler
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
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
|
By
Boie, Andrew P
·
#5374
·
|
|
Re: Zephyr: FDRM_K64f board from NXP
Thanks everyone, I will have a look at the DTS.
Cheers,
Thanks everyone, I will have a look at the DTS.
Cheers,
|
By
Florian Fouillet <Florian.Fouillet@...>
·
#5373
·
|
|
Re: Zephyr: FDRM_K64f board from NXP
Take a look at the documentation to understand how this process works:
https://docs.zephyrproject.org/latest/devices/dts/device_tree.html
Take a look at the documentation to understand how this process works:
https://docs.zephyrproject.org/latest/devices/dts/device_tree.html
|
By
Diego Sueiro
·
#5372
·
|
|
Re: Zephyr: FDRM_K64f board from NXP
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,
It is done somehow through DTS, you need to search i.e.
./zephyr/include/generated/generated_dts_board.h
Best regards
Andrei Emeltchenko
|
By
Andrei
·
#5371
·
|
|
Zephyr: FDRM_K64f board from NXP
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
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
|
By
Florian Fouillet <Florian.Fouillet@...>
·
#5370
·
|
|
Zephyr 1.13.0 HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle
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
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
|
By
Vieren Frank <F.Vieren@...>
·
#5369
·
|
|
__ASSERT - transfer to error handler
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
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
|
By
Skøien, Kristoffer <Kristoffer.Skoien@...>
·
#5368
·
|