topic commissioning MCF5208 in ColdFire/68K Microcontrollers and Processors

commissioning MCF5208

fevernova — Tue, 18 Dec 2007 20:25:02 GMT

Hi at all,

I developed a board with the MCF5208 referenced to the M5208 evaluation board.

First of all I want to check the electrical connection with boundary scan, but it doesn't work.

The process failed. Then I tried the "hello world", but BDM doesn't work. There is no connection to the BDM.

Here are some information:

- voltages 3,3V and 1,5 are good

- /RESET is high-level

- RCON is pulled-down to gnd

- DRAMSEL is pulled-up to 3,3V (using sdram)

- DSCLK_/TRST, /BKPT_TMS, TDI_DSI, TDO_DSO are pulled-up

- PSTCLK_TCLK is pulled-down

- JTAG_EN is low when using BDM and high when using JTAG

Certainly there are a lot of approaches, but I'm thankful for any hints.

Are there any ideas to solve the problem? thanks to you

Re: commissioning MCF5208

JWW — Fri, 28 Dec 2007 09:48:49 GMT

fevernova,

Did you make any more progress? I would suggest getting BDM to work first, then proceeding to test JTAG.

What tools are you using to talk to the BDM?

Can you share a piece of your schematics for review?

-JWW

Re: commissioning MCF5208

fevernova — Wed, 02 Jan 2008 18:32:06 GMT

Hi,

because of non-disclosure it's not possible to publish the schematics.

I use the PEMicro BDM via parallel port and Codewarrior 5.7 as IDE.

I took the 5208EVB project and at the moment I modify some configuration, e.g. flash size, sdram config...

I can exclude a wrong connection to the pc because with a 5213 board it works fine.

The message is:"PEMICROProtocolPlugin. Can't connect to PEMicro via parallel port."

Re: commissioning MCF5208

fevernova — Wed, 16 Jan 2008 23:34:56 GMT

hi,

I have the following behaviour on my own 5208 board.

The core is supported by a crystal reference of 16MHz. After a few seconds the crystal stops to swing and goes into static high level. The fb_clk first seconds f=83.33MHz) stops at the same time, which is clear to me.

The RCON is asserted during reset and the config data pins fits with my configuration.

Is this a hardware bug in my design or is this still a normal behaviour?