XDIMAX Products Forum

Hi,
So have my last firmware worked?

Hi,
I'm working with libusb development team on this issue.
They asked to check it with new Ubuntu 1.04 and libusb 1.0.8. Can you do it please?
(You can also try libusb 1.0.8 on Ubuntu 9.04)

Hi,
Well this is a very strange place to stretch clock. Usually clock stretching happens before ACK or during data write.
I have extended STOP condition timeout as well. Please try attached firmware.

Hi,
The 5sec is correct. Sorry.

From the waveform it is not clear where exactly the clock stretching begins. I assume that after last data byte 0x08 is written your slave is starting to hold the clock low? Is it correct?

Hi,
Timeout is generated in firmware. The firmware I have uploaded has the timeout increased up to 500ms.
Any chance you could post problematic transaction waveform?

HI, I think the best we can do is to try to redact your code to something minimal that can still generate a segfault. Please try to extract only problematic portion. In this case we could try to run it on our side and check. Another option is to try our sub_app in loop. It has repeat option -r. Plea...

You are right. Spec does not limit clock stretching timeout. And this is how our I2C module works. It waits until clock signal is released by slave. But we can not do the same on API side. API has to return timeout, otherwise i2c functions will simply stuck. Nevertheless, I have prepared a special F...

Release ready:
viewtopic.php?f=2&t=3&p=172#p172

Command line utility sub_app.exe (or sub_app for Linux) provides access to SUB-20 MDIO functionality . SYNOPSIS sub_app.exe --mdio=<R|W|a|w|r|p>,<PRT_PHY>,<DEV_REG>,<DATA> [--mdio...] where: R - Clause22 Read W - Clause22 Write r - Clause45 read w- Clause45 write a - Clause45 address write p - Claus...

Hi,
What is your timeout?
Without timeout device can stuck so this is not a good solution but we can definitely increase it. Tell me how much?