Hi, The Bluetooth Mesh sample in the default configuration simply doesn't fit on the nRF52810, unfortunately. There are a couple of config files in this sample that are designed to fit on memory const

#nrf52810 #nrf52 #bluetoothmesh

Hello everyone ! I am using the nRF52DK board to emulate the nRF52810, I succeed in running some samples like "blinky", "hello_world" or "beacon" in the path zephyrproject/zephyr/samples/bluetooth. Ho

#nrf52810 #nrf52 #bluetoothmesh

Hi, you can check the content of the build.ninja in the build directory. Look for the files that you suspect are built incorrectly and check the build flags. That should at least confirm that the prob

#builds #debug #bluetooth #nrf52 #nrf52832

Hello, NOTE: I also posted this on github:https://github.com/zephyrproject-rtos/zephyr/issues/27706 I don't know which channel is the correct one for these types of issues. I have a question about deb

#builds #debug #bluetooth #nrf52 #nrf52832

Hi Venkatesh, hciconfig uses a legacy ioctl kernel interface which is only able to retrieve the public address of a controller. nRF controllers do not come with any public address by default, which is

#hci #ble #nrf52 #nrf52840

Hi, We are willing to do the LE USB controller with the nrf52840 dongle By looking into this case https://devzone.nordicsemi.com/f/nordic-q-a/46036/mac-address-ranges. I came to know that there will b

#hci #ble #nrf52 #nrf52840

Hi Carles, Thanks for the tip. I would be really surprised that I already have a stack issue, as the application is still very simple... Nevertheless it can't harm to have this option enabled. Br, Fra

#ble #nrf52

Hi there, One of the likely culprits is stack sizing. Please enable CONFIG_HW_STACK_PROTECTION and verify that one of your stacks is not overflowing. Regards, Carles

#ble #nrf52

Hi all, I have the following setup: - nrf52 demo kit running a simple BLE peripheral application - Raspberry Pi running a BLE central application A secured connection is made (authentication based on

#ble #nrf52

Hi ibraxim, Try add below line in your prj.conf, it might solve your problem. CONFIG_BOARD_ENABLE_DCDC=n leslieli@...

#nrf52 #custom_board

One other issue I just recalled was related to the console and not having a UART properly setup and pinned out, for my custom board I ended up using a USB console which worked out well. Beyond that it

#nrf52 #custom_board

Hi, A few questions I think will help myself or others answer this easier... I'm assuming you are able to flash the board Are you using the same clock setup and crystal freqs as the dev board your bas

#nrf52 #custom_board

Hello everyone, I have a custom board based on the QIAA layout, when i try to flash the bluetooth beacon example from the zephyr samples directory, the board does not advertise at all(the board also d

#nrf52 #custom_board

Hello, I have been trying to use the periodic publishing in mesh, but I don't really see how to use it correctly. I have read the Mesh Specification, and I already asked here for help on publishing, a

#bluetoothmesh #nrf52

Hi Henry, Take a look at the configuration used in Nordic’s throughput sample: https://github.com/tejlmand/fw-nrfconnect-nrf/blob/master/samples/bluetooth/throughput/prj.conf I think you are missing s

#ble #nrf52 #nrf52832 #nrf52840

I am trying to enable data length extensions in a connection but am limited to the std 20 payload bytes. I have a Nordic PCA10040 (nRF52832) running Zephyr v1.14rc1 as a central connected to a Laird B

#ble #nrf52 #nrf52832 #nrf52840

Hey guys, I'm tryinig to create an external counter on nrf52 for 10MHz using PPI, GPIOTE and time counter but I don't know where I'm doing it wrong. Follow my code so far. The commented part is just a

#nrf52 #ppi