+ Reply to Thread
Results 1 to 4 of 4

Thread: XMC4500 ETH0 Promblem with PORT2

  1. #1
    New Member New Member markus.mandl is on a distinguished road
    Join Date
    Oct 2018
    Posts
    4
    Points
    42.5

    XMC4500 ETH0 Promblem with PORT2

    Hi,

    I have a strange behaviour concerning the ETH0 on the XMC4500.

    1. Im configurating the ports on the XMC as follows:
    P2.10 reset Pin -> software controlled
    P1.10, ETH0_MDC => O
    P1.11, ETH0_MDIO => I0
    P1.12, ETH0_TX_EN => O ALT1
    P1.12, ETH0_TX_EN => O ALT1
    P1.13, ETH0_TXD0 => O ALT1
    P1.14, ETH0_TXD1 => O ALT1
    P2.2, ETH0_RXD0 A => I
    P2.4, ETH0_RXER A => I
    P2.11, ETH0_TXER => O ALT1
    P2.12, ETH0_TXD2 => O ALT1
    P2.13, ETH0_TXD3 => O ALT1
    P5.1, ETH0_RXD1 D => I
    P5.2, ETH0_RXDV D => I
    P5.5, ETH0_COL D => I
    P5.8, ETH0_RXD2 A => I
    P5.11, ETH0_CRS A => I
    P6.3, ETH0_RXD3 B => I
    P6.5, ETH0_CLKRX D => I
    P6.6, ETH0_CLK_TX B => I

    2. Scanning the PHY Address to use
    When scanning the PHY cannot be found, because im not getting valid data from the Physical (MICREL KSZ8863MLL) via the MDIO interface (it seems that the PHY is not up, because im getting only 1's)
    Reconfiguring the P2.12 to INPUT causes the PHY to boot and im getting valid data via the MDIO and im able to configure the Micrel, but - surely - getting no data via the MII interface.
    Configuring the P2.12 back to OUT ALT1 after the PHY bootet somehow kills the PHY (not getting any valid data via MDIO anymore).
    Configuring the P2.12 back to INPUT again causes the PHY to boot again and im able to receive valid data via da MDIO again... and so on.

    I used an oscilloscope, when P2.12 is configured as OUT ALT1 the pin on the PHY connected to the XMC4500 is low - configured as IN the pin is high.

    Hopefully anyone can help me with this issue - i would be very grateful

  2. #2
    New Member New Member markus.mandl is on a distinguished road
    Join Date
    Oct 2018
    Posts
    4
    Points
    42.5

    I hade time to describe the problem better

    I have a Infineon XMC4500 cpu connected to a KSZ8863MLL (two port Ethernet switch) operating in MII mode.

    We built some Boards - arround 50 are working but now im facing an isssue.

    The board that does not work properly behaves as follows (testing using SWD)

    When XMC4500 is in reset - KSZ8863MLL operates (network leds and activity leds active).

    In the XMC4500's code setup, the XMC4500 pins are mapped into MII mode.

    When XMC4500 pin P2.12 is set to MMI mode (Output ALT1) - the pin goes from a floating input (3.3v on scope) to GND as the pin becomes an output.

    At the conclusion of executing THAT pin's related instruction - all LEDS on the KSZ8863MLL go out and the device becomes inactive.

    Programming all other MMI related pins on the XMC4500 have expected results.

    I have looked at the board under an inspection microscope and found no trace/solder issues.

    I have scoped adjacent PCB traces to see if an internal PCB layer may have shorted traces (PCB is 4 layer) -- no change to adjacent traces found when pin goes from input to output.

    I have placed a break point after the instruction to make sure other code was not executing and to isolate the KSZ8863MLL behavior to just that single instruction.

    I've narrowed it to that single pin - going from input (pin at 3.3v) to output (pin a GND) that causes the KSZ8863MLL to stop operating.

    I'm lost as were to look/proceed further. As stated earlier -- some other boards work perfectly which suggest the issue is related to parts/assembly of this specific board.

    The KSZ8863MLL appears to be OK since it shows activity as long as the XMC4500 has not set that pin's mode to MMI.

    The 3 other related TX pins (TX0, TX1, TX3) all go from 3.3v to GND when their mode is switched to MMI.

    When i run the code and TXD2 is configured as Output ALT1 - The KSZ8863MLL does not operate - then i configure the TXD2 as INPUT (pin goes back to 3.3V) the KSZ8863MLL operates (but surely getting no data via the MMI), configuring the TXD2 back to Output ALT1 causes the KSZ8863MLL to stop operating again, and so on...

  3. #3
    New Member New Member markus.mandl is on a distinguished road
    Join Date
    Oct 2018
    Posts
    4
    Points
    42.5
    I measured VDD, Reset and TXD2 on a good and on a bad board, but couldn't find any differences.

    Click image for larger version

Name:	vergleich_klein.jpg
Views:	3
Size:	487.0 KB
ID:	3651

  4. #4
    New Member New Member markus.mandl is on a distinguished road
    Join Date
    Oct 2018
    Posts
    4
    Points
    42.5
    Still working on this issue...

+ Reply to Thread

Tags for this Thread

Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.