I2C Slave not implemented

[Curclamas]

Description

It seams that the I2C slave functionality from the Arduino Wire Lib is not implemented.

Code example

#include <Wire.h> 

void setup() 
{ 
 Wire.begin(0x03);
 Wire.onRequest(requestEvent);
} 

void loop() 
{ 
 delay(10); 
} 

void requestEvent() 
{
 Wire.send(0x13);
}

Error occured during compilation

exit status 1
'class TwoWire' has no member named 'onRequest'

EDIT: Fixed errror message.

[gryzli133]

did you find a solution for that issue?

[marcolettieri]

no news? i've done with esp-idf but arduino way is simpler and clearer

[lbernstone]

@stickbreaker is working on slave I2C (https://github.com/stickbreaker/arduino-esp32/tree/master/libraries/Wire). Not sure where he is at with it, but development is active.

[marcolettieri]

Found out  it... many errors in compile... Il 14/05/2018 15:14, lbernstone ha scritto:

…

@stickbreaker <https://github.com/stickbreaker> is working on slave I2C (https://github.com/stickbreaker/arduino-esp32/tree/master/libraries/Wire). Not sure where he is at with it, but development is active. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#118 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHSe24shLRHFJIzYM4QyD6lNilDrSxa3ks5tyYMagaJpZM4LbtDd>.

-- Marco Lettieri Head of Developments microBees Technology Ltd

[Nightreaver]

Updates?

[stickbreaker]

I've got a working Slave mode, but I am still working through coexistence with Master mode. Slave mode on ESP32 has to call onRequest() before the Slave is addressed. So the outbound data is always stale. Currently Slave mode exists in a separate task, and I haven't decide on the 'correct' design to refresh this data:

• never
• every time onReceive() activates
• manually controlled by application
• every time a Master transactions supplant Slave mode.
• so some combination of all of these.

It is base on a re-implementation of Wire() that is designed for multi-tasking support Multiple Wire() objects are create, each Object is designed as single threaded, The multiple Wire() Objects are safely multi-threaded and share the hardware. But, the Application must transactionalize their access if necessary. The transaction locking with MUTEX's can be abused to cause deadlocks. The 'simple' Arduino 'it just work' philosophy is tough to implement with complex interactions.

Chuck.

[Zhairgling]

Hi @stickbreaker , Any news ?
Can you share code ?
Thanks

[canDry]

BUMP! Anyone have a slave receive solution/fix/workaround?