• State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 25 subscribers
  • Views 211 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289183
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

I2C, I must be stupid.

user114729

Am I the only one who finds Zephyrs I2C implementation a little cludgy? Or am I just missing something?

It may be that I'm just used to bare metal I2C but I can't seem to figure out how I can send a few bytes, followed by 512 zero's without allocating a 514 byte array?

What I'm looking for is and i2c_write() that I can tell not to send an I2C_MSG_STOP....

Or am I just looking at it the wrong way?

Thanks folks, I promise I'm working hard to get past the dumb questions.

Parents
  • 0

    OK, I acknowledge that the scope of my question was a bit broad. Lets zoom in on an example:
    I want to send 

    0x40, 0x00, 0x00..... and another 509 of them to i2c address 25 in one transaction.

    What I don't want to do is
    uint8_t buffer[513];

    It's not clear to me that this is possible? But I may just be looking at it wrong...

Reply
  • 0

    OK, I acknowledge that the scope of my question was a bit broad. Lets zoom in on an example:
    I want to send 

    0x40, 0x00, 0x00..... and another 509 of them to i2c address 25 in one transaction.

    What I don't want to do is
    uint8_t buffer[513];

    It's not clear to me that this is possible? But I may just be looking at it wrong...

Children
No Data
Related
Terms of service