Hi,
2.I tested the AM335x_ICE which used the AM3359ZCZ chip, I set the sync0 cycle time to 400us and it can run to OP mode with ACS master, but communication failed to modify the sync0 cycle time down to 250us.
3.We have a product which used the AM3359BZCZ chip, and 250us sync0 cycle time is work(OP mode), but 200us failed(can not run to OP mode).
What frequency your product is running?
Did you profile how much time it takes for your application to execute SYNC task and PDI task ?
Is there any more description on the error (other than can not run to OP mode) ?
Is this possible to share wireshark logs?
From ETG2000, table49, Element Factor
Used to define SYNC0 signal cycle based on the sync unit cycle time (= EtherCAT bus cycle time = cycle time in which the process data of this device is updated).Sign of value indicates mathematical operation:
Positive value:
SYNC0 cycle time = sync unit cycle time * |Factor|
Negative value:
SYNC0 cycle time = sync unit cycle time / |Factor|
NOTE: If CycleTimeSync0 and CycleTimeSync0@Factor are “0” this results in a total cycle time = 0. This may activate special features (single shot).
So you can run SYNC1 at bus cycle time by setting positive Factor value.
We do not disable features during our tests. But we are not running EoE or FoE during SYNC tests either.