Just to be sure. Specifying pins is not enough. hw-flow-control property must be set like here: https://github.com/zephyrproject-rtos/zephyr/blob/0f93d58994cd17753cfdf02fd022c2f226ec0471/samples/bluet

Hi, do you have flow control enabled? When it is disabled then after each byte receiver is stopped and restarted after reading the byte. Restarting may happen when transmitter is already started, in t

Hi, One thing to consider is that k_timeout_t structure used for k_sleep and kernel timeouts can hold absolute value. Check out K_TIMEOUT_ABS_MS() for setting timeout in uptime milliseconds. Regards,

#api

Hi, What do you mean when you say “the Clock”? clock control in case of Nordic is using single device and subsys argument determines the type of the clock (high frequency, low frequency, etc.). Howeve

Hi Dave, I think you could try to look into selecting root command feature. Create dummy command with only “login” subcommand. Set this dummy command during system startup (shell_set_root_command(“dum

#uart #api

Hi Diogo, As written before “Note that for other drivers enabling instances happens in Device Tree. Counter will be aligned to that at some point.”. We are going towards instances being enabled in DT

#nrf52832

Hi Diogo, CMake is complaining because even though COUNTER driver is enabled there is no COUNTER instance enabled. In the example there is a Kconfig (samples/drivers/counter/alarm/Kconfig) which enabl

#nrf52832

Hi Martin, Nrf52832 has 3 RTC's. RTC0 is used for Bluetooth, RTC1 for system clock and RTC2 is usually available for application. You can use RTC2 with counter driver API (see counter.h). Then you can

#nrf52-pca10040