• State Not Answered
  • Replies 4 replies
  • Subscribers 25 subscribers
  • Views 261 views
  • Users 0 members are here
Attachments (4) Download All
Nordic Case Info
  • Case ID: 287315
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

I2C code on nRF connect SDK

user96161

Hi, 

I read the link https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/nrfx/drivers/twis/driver.html and updated periodic_sync example as attached below. 

But I am unable to see Request from the Master. I checked connections, addresses and all.

  

Can you please verify from your end or provide me some hint what could I miss?

I checked using Saleae logic analyzer and see it is always nak.

Parents Reply
  • 0 in reply to user81283

    Hi Oivind, Thanks for the link, it explains this well.

    I tried to implement the same example to check, but it does not work for me on nrf52832. Can you please check it in the added zip file?

    I get the error at Master side as:

    I2C device 1: i2c nRF52832 addr 0x28
    00>
    00> I2C Master: Slave ADDR: 0x28 SCL: 31, SDA: 30, CLK(Hz): 100000
    00>
    00>
    00> [00:00:00.336,364] <err> i2c_nrfx_twim: Error 0x0BAE0001 occurred for message 0
    00> twi return code 4294967291
    00>
    00>
    00> [00:00:01.336,608] <err> i2c_nrfx_twim: Error 0x0BAE0001 occurred for message 0
    00> twi return code 4294967291
    00>

    And on the Saleae, it is 

    write to 0x28 nak
    read to 0x28 nak
    write to 0x28 nak
    read to 0x28 nak
    write to 0x28 nak
    read to 0x28 nak
    write to 0x28 nak
    read to 0x28 nak
    write to 0x28 nak
    read to 0x28 nak

Children
No Data
Related
Terms of service