phyCORE-MCF548x

Module Connector

PHYTEC Order Number: VB082

FAQ

phyCORE-MCF548x

NXP MCF548x Dokumentation

Auf der Homepage von NXP auf der MCF548x Product Summary Page finden Sie  Application Notes, Datasheets und Reference Manual und vieles mehr zu dem MCF548x Controller

Link: MCF548x Product Summary Page

phyCORE-MCF5485: Configuration Settings

Question:

We are porting our RTOS, TCP/IP, and file system products to your phyCORE-MCF548x.

http://www.phytec.com/sbc/32bit/pcMCF548x.htm

For the phyCORE-MCF548x chip select and SDRAMC settings, we are using the demo applications shipped on the CD you ship with the board. I have found a discrepancy between the settings in 'phyCORE- MCF548x.cfg' and the values assigned by the routines in 'sysinit.c'.

Can I get a confirmation as to which settings are more reliable and more thoroughly developed and tested?

Answer:

The initialization values contained in the file sysinit.c should be used.

phyCORE-MCF5485: XPLD Pinout

Question:

How do I find a pin number and the corresponding signal name for the XPLD?

Answer:

In order to find a pin number and the corresponding signal name for the XPLD you need to look up the Pin Assignment. This is not done in the actual XPLD source code but a separate file. See file: P686.lct.

For example:
Pin 24 is NOT ball F2, but B8 on the XPLD. F2 in the schematics symbol for the XPLD (inside the yellow box) means logic block F2 and NOT ball F2. When you look at the BGA256.xls spreadsheet you can find pin #24 inside the matrix. And from there you can reference back to ball B8. Now you can search for B8 in the P686.lct file and you will find the signal name: nCF_CS0.

phyCORE-MCF5485: PCI Bus Access

Question:

The hardware manual release notes refers to release PCB# 1229.0.
The release notes seem to indicate that the PCI bus is not available because FBMODE is pulled down on the board. Is this true?

If so, is there a newer version of the phyCORE-MCF548x board available now that does allow access to the PCI bus?

If not, when will a new version with PCI bus access, a useable USB and a useable on-board ADC device be available?

Answer:

The limitation of USB functionality is due to NXP MCF5485 controller, not the phyCORE module. Please see the MCF5485 errata document to find out if this limitation will affect your product, errata ID# 22: http://www.nxp.com/files/32bit/doc/errata/MCF5485DE.pdf

 

phyCORE-MCF5485: Ethernet Drivers

 

Problem:

When the MCF5485 is running from external flash a TX FIFO error is being generated and is not taken care properly by the MCF5485 ethernet driver.

Solution:

As of now the only solution is to increase the TX FIFO Water Mark (Minimum number of bytes to be written to the transmit FIFO to start the transmission). With this change the Web demo works fine from the flash (not copied to RAM). The present value is 256 bytes and it has been tested to an increased value of 512 bytes. This minimizes the risk of TX FIFO underrun errors according to the processor manual MCF5485RM under section 29.3.4.17. By increasing the TX FIFO Water Mark there may be minimal transmit latency

phyCORE-MCF5485: Using P&E USB MultiLink with NXP CodeWarrior

 

<font size="4">Question:</font>

I am trying to use the USB-BDM Interface for ColdFire Devices (USB-ML_CF Rev. C) by P&E Microcomputer Systems in NXP's CodeWarrior.  When I try to connect to the processor by going into debug I get the error "PEMicroProtocolPlugin: Can't connect to PEMicro via USB"

<font size="4">Answer:</font>

To use the P&E Microcomputer Systems USB ColdFire Multilink BDM device in NXP CodeWarrior the version of CodeWarrior must be 6.2 or higher.  Please see the following NXP forum:

http://forums.freescale.com/freescale/board/message?board.id=CWCOMM&message.id=1166&srch=1

To resolve this issue issue that the most updated version of CodeWarrior is installed (follow the following link for CodeWarrior updates)

http://www.nxp.com/webapp/sps/site/overview.jsp?nodeId=01272694014080

and the Multilink cable is connected to the BDM connector with pin 1 (indicated on the back of P&E's USB ColdFire Multilink) is connect to pin 1 of the BDM port (X2) on the Phytec carrier board.  Please see the  hardware manual section 10.3.9 for more information:


Metrowerks / Freescale Code Warrior ColdFire

phyCORE-MCF5485: Using P&E USB MultiLink with NXP CodeWarrior

 

<font size="4">Question:</font>

I am trying to use the USB-BDM Interface for ColdFire Devices (USB-ML_CF Rev. C) by P&E Microcomputer Systems in NXP's CodeWarrior.  When I try to connect to the processor by going into debug I get the error "PEMicroProtocolPlugin: Can't connect to PEMicro via USB"

<font size="4">Answer:</font>

To use the P&E Microcomputer Systems USB ColdFire Multilink BDM device in NXP CodeWarrior the version of CodeWarrior must be 6.2 or higher.  Please see the following NXP forum:

http://forums.freescale.com/freescale/board/message?board.id=CWCOMM&message.id=1166&srch=1

To resolve this issue issue that the most updated version of CodeWarrior is installed (follow the following link for CodeWarrior updates)

http://www.nxp.com/webapp/sps/site/overview.jsp?nodeId=01272694014080

and the Multilink cable is connected to the BDM connector with pin 1 (indicated on the back of P&E's USB ColdFire Multilink) is connect to pin 1 of the BDM port (X2) on the Phytec carrier board.  Please see the  hardware manual section 10.3.9 for more information: