Delay between two protocoll commands

[Sebastian W]

Hello,

 

we are using a Digital Discovery to stress test our DUT with I2C/I3C commands at 1 MHz. Works fine so far.

We are wondering if there is a way to reduce the time between two sequential commands.

Currently we have something like 20 ms. We know it takes some time to send the data from the Discovery to the PC because the restart is issued by the PC. But the actual data stream for the pattern generator is rather small and should not take 20 ms (assuming not the whole memory is updated, even if not fully used).

 

var length = 51
var startreg = [0x9F,0xAE]

for(var i = 0; i < 10; i++)
{
    var registers = Protocol.I2C.Read(0x50,length,startreg)
}

 

 

Best regards

Basti

[attila]

Hi @Sebastian W

The "I2C Pattern" mode is a bit faster, ~5ms. It simply generates pattern on scl/sda and it does not support clock stretching, abort... If the pullups are not strong enough, you may have to reduce the frequency for this mode.
For faster and precise timing you could use the Sensor tab. See the examples menu in this tab.

[Sebastian W]

Hello Attila,

thanks for the fast support.

How do we set the I2C pattern mode via the scripts?

Conditions:

Scan for I²C devices example, Settings: NACK continue (debug)

--> ca 25 ms between requests

 

 

Conditions:

Scan for I²C devices example, Settings: I2C Pattern (legacy mode), NACK continue (debug)

--> ca 7 ms between requests

Edited November 13 by Sebastian W

[attila]

Hi @Sebastian W

The Sensor tab is not accessible from Script since the earlier is basically a script. You can have code in the 3 sensor functions.