On Jan 15, 2020, at 8:49 AM, Lawrence King <lawrence.king@irdeto.com> wrote:

I have a little problem with the device tree

In zephyrproject/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk.dts the uart is defined as:

&uart0 {
compatible = "nordic,nrf-uart";
current-speed = <115200>;
status = "okay";
tx-pin = <20>;
rx-pin = <19>;
rts-pin = <5>;
cts-pin = <7>;
};

Which works just fine. However I am not using the RTS and CTS pin features of the UART, and I need to use the pins for other things. I can simply go into the DTS file and comment out the two pins:

&uart0 {
compatible = "nordic,nrf-uart";
current-speed = <115200>;
status = "okay";
tx-pin = <20>;
rx-pin = <19>;
/* rts-pin = <5>; */
/* cts-pin = <7>; */
};

And all is good. However I would prefer to use an overlay in my local working directory instead of making changes to the zephyr tree. I did try redefining uart0 in the local overlay, but RTS and CTS are still there.

What is the right way to remove RTS and CTS?

Lawrence King
Principal Developer
Connected Transport Market Unit
https://www.Irdeto.com
+1(416)627-7302

<image001.png> <image003.png> <image005.png> <image007.png> <image009.png> <image011.png>

CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.

On Jan 15, 2020, at 8:49 AM, Lawrence King <lawrence.king@irdeto.com> wrote:

I have a little problem with the device tree

In zephyrproject/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk.dts the uart is defined as:

&uart0 {
compatible = "nordic,nrf-uart";
current-speed = <115200>;
status = "okay";
tx-pin = <20>;
rx-pin = <19>;
rts-pin = <5>;
cts-pin = <7>;
};

Which works just fine. However I am not using the RTS and CTS pin features of the UART, and I need to use the pins for other things. I can simply go into the DTS file and comment out the two pins:

&uart0 {
compatible = "nordic,nrf-uart";
current-speed = <115200>;
status = "okay";
tx-pin = <20>;
rx-pin = <19>;
/* rts-pin = <5>; */
/* cts-pin = <7>; */
};

And all is good. However I would prefer to use an overlay in my local working directory instead of making changes to the zephyr tree. I did try redefining uart0 in the local overlay, but RTS and CTS are still there.

What is the right way to remove RTS and CTS?

Lawrence King
Principal Developer
Connected Transport Market Unit
https://www.Irdeto.com
+1(416)627-7302

<image001.png> <image003.png> <image005.png> <image007.png> <image009.png> <image011.png>

CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.

Hi,

using zephyr-v2.1.0

I have build the mqtt_publisher sample application for the stm32f746g_disco and it works fine.

I have build the dhcpv4_client sample application for the stm32f746g_disco and it works fine.

When I want to combine both, mqtts and dhcpv4, the dhcpv4 is always timing out.

I have tried step by step.

Using dhcpv4_client sample:

add to prj.conf

# Enable Sockets support

CONFIG_NET_SOCKETS=y

CONFIG_NET_SOCKETS_SOCKOPT_TLS=y

Then the application is no longer compiling:

zephyr/subsys/net/lib/sockets/sockets_tls.c:1735:45: error: 'struct tls_context' has no member named 'ssl'

Does sock_opt_tls is depending on mbedtls? In the guiconfig there is no dependency mentioned between CONFIG_NET_SOCKETS_SOCKOPT_TLS and CONFIG_MBEDTLS.

The sockets_tls uses different mbedtls defines.

What is the correct solution for this problem?

kr,

Wim

On Jan 7, 2020, at 3:07 PM, marciano@... wrote:

I am attempting to write a basic I2C program using Zephyr, but I am currently unable to sent a single byte over I2C. The program hangs after the first clock falling & rising edge.

I'm using external 1K pullups, and have a BME680 device on the other end. I observe the same behavior on the bus with or without the BME680 device.

Am I doing something wrong?

 

---

prj.conf

CONFIG_NEWLIB_LIBC=y

CONFIG_PRINTK=y

CONFIG_HAS_SEGGER_RTT=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y

CONFIG_UART_CONSOLE=n



# nRF5340 board config

CONFIG_TRUSTED_EXECUTION_SECURE=y



CONFIG_BT=n

CONFIG_TIMESLICING=n

CONFIG_DEVICE_POWER_MANAGEMENT=y

CONFIG_SYS_POWER_MANAGEMENT=y

CONFIG_SYS_POWER_DEEP_SLEEP_STATES=y

CONFIG_DEVICE_POWER_MANAGEMENT=y



CONFIG_I2C=y

CONFIG_I2C_1=y

---

main.c

#include 
#include 
#include <sys/printk.h>
#include <drivers/i2c.h>

/* Application main Thread */
int main(void)
{
  struct device *p_i2c = device_get_binding("I2C_1");
  u32_t dev_config = I2C_SPEED_SET(I2C_SPEED_STANDARD) | I2C_MODE_MASTER;
  int res = i2c_configure(p_i2c, dev_config);
  if (res)
  {
    return res;
  }
  struct i2c_msg msgs[2];
  u8_t data[2][2];
  data[0][0] = 0x01; // register address
  data[0][1] = 0x00;
  msgs[0].buf = data[0];
  msgs[0].len = 2U;
  msgs[0].flags = I2C_MSG_WRITE | I2C_MSG_STOP;

  data[1][0] = 0x4;
  data[1][1] = 0xff;
  msgs[1].buf = data[1];
  msgs[1].len = 2U;
  msgs[1].flags = I2C_MSG_WRITE | I2C_MSG_STOP;

  int i = i2c_transfer(p_i2c, &msgs[0], 2, 0x77);
  if  (i)
    printk("transfer failed");
  return 0;
}

<Screen Shot 2020-01-06 at 2.53.05 PM.png>

On Jan 6, 2020, at 4:16 PM, Robin Callender <robin@...> wrote:

We are trying to understand how to configure sercom3 to allow I2C support.
The I2C device is the adafruit_oled_featherwing.
I believe I have the I2C, SSD1306, framebuffer (cfg), and display.  
Below is the relevant portions of the prj.conf file

Our app builds with these setting, but doesn't seem to conduct I2C traffic.
We going though the SAMD21 datasheet, but it is very confusing.
We don't understand how the pinmux is being driven to set the pad to I2C mode.

Are there any examples showing how to configure I2C for the adafruit_feather_m0_basic board or any other samd21 type board?

CONFIG_HEAP_MEM_POOL_SIZE=4096

CONFIG_HEAP_MEM_POOL_MIN_SIZE=64

 

CONFIG_HAS_DTS_I2C=y

CONFIG_I2C=y

CONFIG_I2C_SAM0=y

CONFIG_I2C_INIT_PRIORITY=60

CONFIG_I2C_0=y

 

CONFIG_DISPLAY=y

CONFIG_SSD1306=y

 

CONFIG_CHARACTER_FRAMEBUFFER=y

CONFIG_CHARACTER_FRAMEBUFFER_USE_DEFAULT_FONTS=y

CONFIG_HEAP_MEM_POOL_SIZE=4096

CONFIG_HEAP_MEM_POOL_MIN_SIZE=64

 

CONFIG_HAS_DTS_I2C=y

CONFIG_I2C=y

CONFIG_I2C_SAM0=y

CONFIG_I2C_INIT_PRIORITY=60

CONFIG_I2C_0=y

 

CONFIG_DISPLAY=y

CONFIG_SSD1306=y

 

CONFIG_CHARACTER_FRAMEBUFFER=y

CONFIG_CHARACTER_FRAMEBUFFER_USE_DEFAULT_FONTS=y