Hello ashish! The current version of Zephyr support I2C driver for nRF5, you also can find some examples in samples/ directory, the samples/drivers/i2c_fujistsu_fram is a simple example which use

Hi I am looking for guidance about how to set following kernel config options. CONFIG_BT_L2CAP_RX_MTU, CONFIG_BT_L2CAP_TX_MTU. In build/zephyr/.config, both of these are set to 65 bytes.

Hello everyone !!! There is I2C support for nRF5 micro controllers, is there any sample code available to interface an I2C device with nRF5. Also, is there adc support for nRF5 series controllers?

You probably want to look at renode: https://github.com/renode/renode Also see https://www.youtube.com/watch?v=3g3T1cXtReg Anas

Hi there! I'm wondering what would be the best way to emulate a full board with peripherals. In this case, I'm building a quadcopter based on a stm32f401 with some sensors like an IMU, TOF,

Hi there! I'm wondering what would be the best way to emulate a full board with peripherals. In this case, I'm building a quadcopter based on a stm32f401 with some sensors like an IMU, TOF,

Issue with IPSP sample (recent master branch) : Ping fails. BLE address is assigned to k64f board. bluetoothctl utility and its scan discover IPSP node. BLE connection is up, interface bt0 is up. On

Hi Johan, >There's something not matching up with the description of your configuration however. >You said that NODE1 has both Relay and GATT Proxy states disabled for NODE1, Proxy is enabled. This

Hi Johan, Thanks for in detailed explanation, that clarified related issues. -- Warm regards, Ashish Shukla Jr. Embedded Engineer Research & Development www.corvi.com Please consider the

Hi Ashish, There's something not matching up with the description of your configuration however. You said that NODE1 has both Relay and GATT Proxy states disabled, however bt_mesh_net_relay() has the

Hi Ashish, Are you concluding that the relaying happens because you see the "Relaying packet" log message? If so, then that's a wrong assumption, and the log message is indeed misleading. Please take

Hi Johan, NODE1 does receives the messages and process it. But it relay/forward the same message to network by reducing TTL value by 1. In my case, GATT client is mobile phone so it isn't possible

Hi Ashish, Publishing is not tied to any specific bearer, rather the message is expected to be delivered to all network interfaces the network layer is connected to, including GATT. What exactly do

Thanks. I could resolve this issue on qemu_x86 by increasing MAIN_STACK_SIZE in the configuration. I am not sure whether increasing stack size is required for my hardware board as well or is it only

Hi Johan, Here is brief about my experimental setup : 1. NODE1 : Proxy enabled, Relay disabled 2. NODE2 : Proxy disabled, Relay disabled Now, both nodes belong to same group, which means they are

Hi Vakul, addr2line -e zephyr/zephyr.elf 0x00003f6f /home/vudentz/git/zephyr-github/ext/lib/crypto/tinycrypt/source/hmac_prng.c:187 This is with samples/bluetooth/ipsp sample build with

Hi Ashish, As I said earlier, when the Proxy feature is enabled, the proxy *should* be relaying messages from the network to any connected GATT client, regardless of the Relay feature being enabled

Hi Johan, I was not understanding meaning of *CONFIG_BT_MESH_RELAY=n* correctly. Thanks for clarification. However, when I enabled the proxy feature of a node, and disabled its relay feature, it

Hi Ashish, Setting CONFIG_BT_MESH_RELAY=n will actually force the value of cfg.relay to BT_MESH_RELAY_NOT_SUPPORTED when you initialize mesh, so trying to set it to disabled shouldn't have any

Hi everyone !!! I'm trying to disable relay feature of node by making these two changes 1. setting CONFIG_BT_MESH_RELAY=n in the prj.conf file. 2. static struct bt_mesh_cfg_srv cfg_srv = {