• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 33 subscribers
  • Views 771 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

TDA4VM: How to read or write PHY register data of CPSW PHYs within Linux

DP83867ERGZ-R-EVM: DP83867E Accessing Extended Registers

Jaclyn Shimada
Prodigy 10 points
Part Number: DP83867ERGZ-R-EVM
Other Parts Discussed in Thread: DP83867E, MSP430F5529

I am configuring the DP83867E PHY and am testing out read/write indirect register access to an extended register. I followed the 8.4.2.7.1 steps in the DP83867E datasheet, and after step 4, I am only reading 0x0170h instead of 0x0C10h. I'm not sure what I am doing wrong. I do have REGCR as address 0x000Dh and ADDAR as 0x000Eh. 

Any help would be appreciated - thanks! 

  • 0
    TI__Mastermind 39755 points

    Hi Jaclyn,

    This is the correct procedure for extended register access. Can you please verify that the command works for non-register reads? IE, what do you read if you directly read register 0x1? What happens if you try to access this value via extended register access?

    Can you also verify the PHY ID? If defaulted, the PHY will be address 0 if no bootstraps are configured to modify the address.

    Sincerely,

    Gerome

  • 0 in reply to Gerome Cacho
    Prodigy 10 points

    Hi Gerome, 

    The PHY ID is 0 as I don't have any bootstraps to modify the address. I only use this address once in the beginning of my configuration script. 

    The read command does work for non-register reads. 

    For extended registers, it doesn't seem to work and seems to read the offset address instead of the data. 

  • 0 in reply to Jaclyn Shimada
    TI__Mastermind 39755 points

    Hi Jaclyn,

    This does seem odd. I confirmed that this sequence is valid using our DP83TC812EVM which has DP83867 on board, and got the following results:

    Are you using our DP83867 EVM? If so, would it be possible to have an MSP430 connected to MDC/MDIO to replicate this on our USB2MDIO software?

    Other points of debug:

    - Is it extended reads that are not behaving expectedly, or is write process also odd? Can you please try the CLKOUT example and probe to verify the write took effect?

    Sincerely,

    Gerome

  • 0 in reply to Gerome Cacho
    Prodigy 10 points

    Hi Gerome, 

    I did try the example CLK_OUT write process and it did disable the clock. 

    Seems like it's only the reads that are not behaving correctly. I am using the DP83867 EVM. I do not have a MSP430 on hand, but I do have a MSP432. Can I use that module with the MSP430 GUI software? 

    Besides this GUI, is there other points of debug I can try for the reads? 

  • 0 in reply to Jaclyn Shimada
    TI__Mastermind 39755 points

    Hi Jaclyn,

    The normal component we use in lab is MSP430F5529's launchpad. 

    In terms of other debug, it appears that you are reading as part of a script. Is it possible to do manual commands? Trying to see if timing plays a factor...

    On the clockout disable scenario, after validating that the signal is gone, can you try doing a new instance of extended read of the same register?

    Sincerely,

    Gerome