RE: Zephyr I2C Write Hangs

amcelroy — Mon, 21 Sep 2020 19:23:25 GMT

Ok, the issue was with the TM4C, the interrupt vector on the I2C peripheral wasn't configured correctly. Can confirm that Zephyr nRF52840 I2C is indeed working with the below prj.conf settings.

RE: Zephyr I2C Write Hangs

amcelroy — Mon, 21 Sep 2020 14:35:49 GMT

One more piece of data:

I've hooked up the nRF52840 to an Arduino Due and everything seems to be working, including a response from the slave, in this case the letter "C". Still not solved, as there seems to be an issue between the nRF52840 -> TM4C.

RE: Zephyr I2C Write Hangs

amcelroy — Mon, 21 Sep 2020 14:21:13 GMT

Oh, my prj.conf file has the following:

#Flash

CONFIG_FLASH=y

CONFIG_MPU_ALLOW_FLASH_WRITE=y

#Bluetooth Configuration

CONFIG_BT=y

CONFIG_BT_DEBUG_LOG=y

CONFIG_BT_SMP=y

CONFIG_BT_SIGNING=y

CONFIG_BT_PERIPHERAL=y

CONFIG_BT_GATT_DIS=y

CONFIG_BT_ATT_PREPARE_COUNT=2

CONFIG_BT_PRIVACY=y

CONFIG_BT_DEVICE_NAME="Device Name"

CONFIG_BT_DEVICE_APPEARANCE=833

CONFIG_BT_DEVICE_NAME_DYNAMIC=y

CONFIG_BT_DEVICE_NAME_MAX=65

CONFIG_BT_SETTINGS=y

#CONFIG_BT_BONDABLE=y

#I2C

CONFIG_I2C=y

CONFIG_I2C_0=y

#Dynamic Memory Heap Size

CONFIG_HEAP_MEM_POOL_SIZE=1024

#Log Config

CONFIG_PRINTK=y

CONFIG_LOG=y

CONFIG_LOG_DEFAULT_LEVEL=4

CONFIG_LOG_MODE_OVERFLOW=y

CONFIG_LOG_PRINTK=y

#Segger Config

#CONFIG_CONSOLE=y

CONFIG_UART_CONSOLE=n

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y

CONFIG_LOG_BACKEND_RTT=y

CONFIG_DEBUG_OPTIMIZATIONS=y

CONFIG_EXCEPTION_STACK_TRACE=y

CONFIG_DEBUG_INFO=y

#GPIO

CONFIG_GPIO=y

#UART Config

CONFIG_SERIAL=y

# CONFIG_UART_CONSOLE=n

#CONFIG_UART_INTERRUPT_DRIVEN=y

CONFIG_UART_ASYNC_API=y

#CONFIG_UART_ASYNC_API=y

#CONFIG_UART_0_INTERRUPT_DRIVEN=y

#CONFIG_UART_0_ASYNC=y

#CONFIG_UART_NRF=y