Thanks, I'll check it out.

Hi there, I believe RTT only currently supports output of characters, and not input. There’s an issue logging this in case you want to follow it, or contribute code to improve

Hi Manu, I think I had the same problem and solved using the process showed here. https://youtu.be/vioi4OsmB_U Cheers, Marco -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Hi Manu, Please try with the following configs: CONFIG_I2C=y CONFIG_I2C_0_NRF_TWI=y CONFIG_I2C_0=y CONFIG_I2C_NRFX=y CONFIG_I2C_0_NRF_TWI=y CONFIG_NRFX_TWI=y Some of these configurations may not be

Hello, I was trying to understand how and when interrupts occur in accelerometer program, how and when the thread switching happens. Could you please help me regarding this issue? Thanks Kowsar

Hi Manu, Try this: diff --git a/samples/drivers/i2c_fujitsu_fram/prj.conf b/samples/drivers/i2c_fujitsu_fram/prj.conf index f9659582c..484e813e7 100644 ---

CONFIG_HAS_SEGGER_RTT=yCONFIG_RTT_CONSOLE=y CONFIG_UART_CONSOLE=n Is there anything else that I am missing out? I simply want the RTT viewer to get a response to 'help' command. Thank you,

Carles, I am trying to use 1.13 and am having some issues. I can build hello_world, but when i tried to build anything with i2c, I have issues. ( drivers__i2c was created without source

Carles, appreciate the response. That was definitely one of my experiments to try. However, we have had a relatively stable base with r1.12 and I am not sure we can change to 1.13 without some

Hi Manu, The I2C driver has since been completely rewritten to use nrfx, our common driver codebase. Would it be possible for you to try with current master (or at least 1.13) to see if you still

Hi All, We have a custom board with a nrf52840 and multiple I2C devices( accel, pressure, etc). We noticed that anytime we do an I2C transaction ( reads in particular), the current draw is abnormally

I'm trying to run the sample i2c code from samples/drivers/i2c_fujitsu_fram on my board. I've tweaked the address to use the i2c address of my device, and am trying to read the who_am_i register, but

Hi all, I am using a lis2dh12 with a nrf52840, and am on occasion seeing an assertion. It happens in the i2c_nrf5_read err=0 txd=0 rxd=0 stopped=0 errsrc=0x0 ASSERTION FAIL [data->stopped] @

Charles, Thank you very much for the advice, I figured out that I built the .hex file with the incorrect parameters: cmake -DBOARD=nrf52840_pca10059 ../.. When I needed: cmake

Hi Carles, Oh !! That's Great news !!

Note that if you do not own a BLE sniffer you can still use a Nordic board to sniff traffic over the air: https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer Carles

Do you have a sniffer trace you can send to me email? It appears the peer is not responding to a control procedure. -Vinayak

Fix is now merged: https://github.com/zephyrproject-rtos/zephyr/pull/10391

Hi Vikrant, It appears a recent merged PR has introduced regression. https://github.com/zephyrproject-rtos/zephyr/pull/10289 I am analysing the issue, meanwhile you can revert the said commit so as

Hi, Today I synced my local repo with Zephyr master & while testing with Bluetooth Mesh App I got following Kernel OOPS: ***** Kernel OOPS! *****