Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SMBus features request for PIC32MZ series devices. #42

Open
youpko opened this issue Feb 21, 2022 · 2 comments
Open

SMBus features request for PIC32MZ series devices. #42

youpko opened this issue Feb 21, 2022 · 2 comments

Comments

@youpko
Copy link

youpko commented Feb 21, 2022

I am trying to implement SMBus logic with the I2C driver for a PIC32MZ2048EFM100.
My application uses the above mention PIC MCU but this feature request is probably mostly the same for other MCUs in the PIC32MZ EF series.

The MCU should be an SMBus Master & Slave .

  • Current harmony only allows me to select either a I2C Master or I2C Slave implementation not both.

SMBus BlockRead & BlockWrite-BlockRead not supported.

  • The BlockRead & BlockWrite-BlockRead Protocols specify that the first byte read specifies the number of bytes that follow and the current driver doesn't support this dynamical reading capability.
  • All other SMBus BUS Protocols I can make with the available driver functions.

I checked "PIC32 Family Reference Manual, Sect. 24 Inter-Integrated Circuit" manual and in the overview it gives an example that this is possible as the I2C Master & I2C Slave work independently form each other in the I2C Module.

As I am not to familiar with the internal workings of the Harmony project I didn't manage to implement this myself yet, hence my request to look if this can be integrated in the driver for the devices that support is.

@dsettu
Copy link
Collaborator

dsettu commented Jul 19, 2022

@youpko , We have logged the request to add support for SMbus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants
@youpko @dsettu and others