MOD5207 to Coldfire pin mapping

[anidea]

I would like to find the pin mapping between the Cold Fire part and the pins on the Netburner.

Specifically, I'd like to know where the MDIO and MDC lines go and if they are on any of the multiplexed pins which are accessible on the header.

Thanks,

Gabriel

[lgitlitz]

Chapter 2 of the MCF5270RM lists all the signals from the processor. The MDIO and MDC pins are only brought out on one set of pins. Those pins are routed to the Ethernet PHY and not the external 50 pin headers. The average user really has no use for the PHY management interface signals... if you are experimenting then you can jumper right off the PHY pins.

-Larry

[anidea]

I've seen chapter 2 of the RM. What I don't know is the exact wiring between the NB and the CF. Am I basically left to match the signal names?

[rnixon]

When I look at the datasheet I see signal names. Are the signal names on the datasheet similar to the manual?

[lgitlitz]

You stated that you were looking to use the Ethernet Controller MDIO and MDC signals. Chapter 2 of the Freescale reference manual shows that those signals are only routed to the pins D5 and D4 of the processor. Both of these signals are routed from the CPU directly to the Ethernet PHY, specifically pins 1 (MDIO) and 2 (MDC) of the KS8721BI. Those PHY pins are going to be the best place you can solder jumper wires for these signals. The MDIO signal also has a 1.5K pull-up, labeled R11 on the newest revision of the MOD5270B. These pins are not brought out to the main 50 pin headers mainly because there are few NetBurner developers that need to manage a PHY external to the module.

Software-wise you will need to make sure you to properly share this hardware interface with the on-board Ethernet. The best way to do this would be to only run builds built in debug mode only. The debug driver does not actively communicate with the management interface so this should be safe. You can then use some functions from Etherprint.h to communicate with this MII interface. You can use SetMII to write registers of the PHY/switch and GetMII to read the values of registers. You also may want to use a modified version of the FindPHYAddr function to see if the new device is connected correctly... this function scans the bus and reads the ID register of any PHY connected to the Ethernet management interface.

-Larry Gitlitz

[lgitlitz]

There is a header file used for this pins class that lists the processor pin number for any pin that can be multiplexed on the J1 or J2 headers:
C:\nburn\MOD5270\include\pinconstant.h