AM6442: Using GPIO1_18 (V1) and GPIO1_19 (W1) for Other Purposes When TimeSync Is Disabled (EtherNet/IP Adapter)

Hiroki Hoshina

Prodigy 50 points

Part Number: AM6442

Tool/software:

We are currently working on implementing EtherNet/IP Adapter functionality on our custom board.

The PHY device we are using is .CUST_PHY_dp83867

For further background, please refer to the "Original question".

We are using a custom board based on AM64x and the Industrial SDK, and our implementation is based on a sample project provided in response to our "Original question".

On our design, GPIO1_18 (V1) and GPIO1_19 (W1) are needed for other purposes as general-purpose outputs (GPO).

However, these pins are assigned to SYNC and LATCH signals for the TimeSync feature, which creates a conflict.

Since we do not plan to use the TimeSync functionality, is it safe to repurpose GPIO1_18 and GPIO1_19 for other uses?

Are there any potential issues or side effects we should be aware of (e.g., PRU firmware behavior)?

12 days ago

0 Hiroki Hoshina 12 days ago

Prodigy 50 points

To be more precise, the functionality we do not require is CIP Sync, not TimeSync in general.

Our concern is whether reassigning GPIO1_18 (V1) and GPIO1_19 (W1)—which are mapped to SYNC and LATCH signals—might negatively affect DLR functionality.

This concern arises because APIs such as EIP_drvInit() and EIP_drvStart() appear to initialize both DLR and PTP (TimeSync) features, suggesting a possible dependency or shared configuration.

Could reusing these pins interfere with DLR operation, even if CIP Sync is not used?
Are there any precautions or configuration changes required to ensure DLR continues to function correctly when these pins are repurposed?
Is there a clean way to disable only the CIP Sync-related features while keeping DLR fully operational?

We would appreciate any clarification on the relationship between these features and the safe reuse of the SYNC/LATCH pins.

+1 PratheeshGangadhar 12 days ago

TI__Mastermind 48231 points

Hiroki Hoshina said:
Since we do not plan to use the TimeSync functionality, is it safe to repurpose GPIO1_18 and GPIO1_19 for other uses?

Yes, this is OK.

+1 Archit Dev 12 days ago in reply to PratheeshGangadhar

TI__Expert 3300 points

Hiroki Hoshina said:
Since we do not plan to use the TimeSync functionality, is it safe to repurpose GPIO1_18 and GPIO1_19 for other uses?

As Pratheesh mentioned, this is okay.

Hiroki Hoshina said:
Could reusing these pins interfere with DLR operation, even if CIP Sync is not used?

This is not expected, since DLR functionality is unrelated and does not interact with TimeSync functionality.

Hiroki Hoshina said:
Is there a clean way to disable only the CIP Sync-related features while keeping DLR fully operational?

You can call the "TimeSync_drvDisable" API function in order to disable the TimeSync state machine.

Otherwise, it can be also enabled/disabled via the Attribute 1 (PTPEnable) of the TimeSync object (0x43).

Regards
Archit

0 Hiroki Hoshina 5 days ago in reply to PratheeshGangadhar

Prodigy 50 points

Thank you very much for your support.
I feel reassured.

0 Hiroki Hoshina 5 days ago in reply to Archit Dev

Prodigy 50 points

Thank you very much for your support.

I truly appreciate your kind assistance.

Processors

Processors forum

AM6442: Using GPIO1_18 (V1) and GPIO1_19 (W1) for Other Purposes When TimeSync Is Disabled (EtherNet/IP Adapter)