• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 89 subscribers
  • Views 2885 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 282684
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Only i2c nodes accepted in /soc/i2c@40004000/.

Emerson Warwick

Hi, Hope you can help.

With a nrf52840dk development kit arriving tomorrow. We tried to make a start with a nRF52840 dongle, which we eventually want to use.
Connected to a MACREFDES117# Maxim Integrated Heart-Rate and Pulse Oximetry Monitor Development kit.
SDA <29>, SCL <31> ,GND, VDD OUT.

Using: nRF Connect SDK, Zephyr, MS Code.

Following the Guide > Peripherals and RF Test > TWI/I2C implementation with nRFx TWIS Driver. 4 Aug 2021
https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/peripherals/posts/twi-ic2-implementation-with-nrfx-twis-driver


>> Slight snag here:  TWIM setup using Zephyr driver.   4. Add the following node properties to boards/ .overlay

Red squiggly under twis_device1:nRF52840@28            Problem: Only i2c nodes accepted in /soc/i2c@40004000/.

Note: Compiler would be happy with 'i2c-device:nRF52840@28' unfortunately the Guide says:  'i2C or TWI?  Though technically different constructs, TWI and I2C are often considered to be operationally synonymous. Nordic has adopted the TWI nomenclature, while Zephyr has adopted I2C. For this document, I2C will only be used to be consistent with referenced Zephyr software and documentation.'

Any advice welcome. Many thanks,  Andy


Parents
  • +1

    Hi Andy, 

    As far as I can see the compiler will not give a warning when you compile, correct  ?

    The naming is just to avoid confusion that we are going to use the i2c driver from Zephyr but instead uses the nrfx driver ( also in this case we are naming the peer device, not the local device itself)
    I don't think it's a big problem. You can change the name to i2c-device:nRF52840@28 as well. 

Reply
  • +1

    Hi Andy, 

    As far as I can see the compiler will not give a warning when you compile, correct  ?

    The naming is just to avoid confusion that we are going to use the i2c driver from Zephyr but instead uses the nrfx driver ( also in this case we are naming the peer device, not the local device itself)
    I don't think it's a big problem. You can change the name to i2c-device:nRF52840@28 as well. 

Children
Related