Skip to content

I2C: Wrong behavior with function setClock #1804

@camelator

Description

@camelator

Considering 'M' a STM32Duino board as master.
Considering 'S' a STM32Duino board as slave.

1/ Having in setup() for both M and S function TwoWire::setClock(100000)
=> receiveEvent and requestEvent never called in S

2/ Having in setup() for M only function TwoWire::setClock(100000)
=> receiveEvent and requestEvent are called in S as expected.

Maybe the right way is to have this function working for masters only??? I don't know as I am not an i2c expert.

Metadata

Metadata

Assignees

Labels

bug 🐛Something isn't working

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy