CCM_ENET3_REF_CLK vs CCM_ENET_REF_CLK3 vs CCM_ENET_PHY_REF_CLK

[x10]

Hi, 

In Table 5-10 of iMX7D RM, there is external signal CCM_ENET3_REF_CLK with following mux-mode:

Check GPIO1_IO01 pad muxmode, there is:

ALT2_CCM_ENET_REF_CLK3 — Select mux mode: ALT2 mux port: ENET_REF_CLK3 of instance: CCM

and GPIO1_IO09 pad muxmode:

ALT2_CCM_ENET_PHY_REF_CLK — Select mux mode: ALT2 mux port: ENET_PHY_REF_CLK of instance: CCM

and I2C2_SDA pad muxmode:

ALT4_CCM_ENET_PHY_REF_CLK — Select mux mode: ALT4 mux port: ENET_PHY_REF_CLK of instance: CCM

As my understanding, three different signal names represent the same signal, coresponding to IMX7D_ENET_PHY_REF_ROOT_DIV in DTS file. Is it right?

BR

Cheng Shi

[x10 · Accepted solution]

With test:

CCM_ENET3_REF_CLK = CCM_ENET_REF_CLK3 = CCM_ENET_PHY_REF_CLK;

Please update document in later version.

[rjm]

documentation...

I just found that CCM_ENET_PHY_REF_CLK could be found at different places in a reference manual (my use case: iMX8plus reference), if the pdf version of the source document at NXP offices would not break this search term into two snippets. A screenshot says more than 1000 words:

This pdf exporter behaviour (should keep texts within table cells as concise searchable) is a true catastrophe, aggravated by the partially unclear or in detail too sparse documentation details. But even when the cursor selection of a word is highlighted cleanly within a cell, a linefeed character is part of this selection, and hence a search across the document may not find the search term (dependent on pdf viewer used).

I can only repeat: please update the documentation, as the thread starter wrote, but now especially targeted on using another pdf exporter!

Anyway, I found AN 14149, which is helpful.