[I may have posted this in the wrong group, so I've also raised it in Zephyr Users.] I'm new to Zephyr and am trying to get a Linux VM hosted native_posix unit test build environment set up for our Ze

#nrf52

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

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

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 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 ibraxim, Try add below line in your prj.conf, it might solve your problem. CONFIG_BOARD_ENABLE_DCDC=n leslieli@...

#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

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