Tech Support > Computer Hardware > Microprocessors > More on Coldfire BDM project
More on Coldfire BDM project
Posted by David Brown on May 22nd, 2006


Jim Adamthwaite wrote:
I don't think posting to the newsgroup would be appreciated by many -
this is strictly a text-only newsgroup.

Have you joined the bdm tools mailing list?
http://sourceforge.net/cvs/?group_id=81515

As far as converting the files is concerned, there's really only two
things that can be done. One is generating output formats - a pdf image
for the schematic, and gerber files for the pcb. The other is saving
the files in Protel ASCII format, which can then be imported by some
other systems (such as Pulsonix and Orcad, and probably several others).
For the pcb file, it's also worth making an ASCII format of the pcb
without planes - if someone wants to import it, it's almost certainly
easier to add the planes later. It's also worth making the netlist
available in a few different formats. That way, anyone trying to make
their own version using different tools have a comparison check, and can
also skip the schematics step.

I haven't looked at the design in detail yet - I'll see if I get a
chance this evening.

The BDM for Coldfire doesn't really need much logic, so 74xxx devices
should be sufficient (they are really only needed for signal reshaping).
The CPU32 is another matter - a PLD really helps there.

I haven't used anything beyond the MCF52xx devices myself.

You need a cross-compiler. When gcc binaries are built, you can choose
the host you compile on, the host they are to run on (frequently these
are the same), and the target for the generated binaries (if this is
different, you've got a "cross-compiler"). For "standard" gcc, these
three are all the same. To build your cross-compiler, you need to get
the sources for binutils and gcc (and perhaps newlib) and configure them
for the "m68k-elf" target. The sources are the standard gnu sources.

gdb works fine with the standard P&E parallel port debugger, using the
patches from the bdm sourceforge project. If your debugger is
compatible (I haven't yet checked), it will work with that too. If it
is incompatible, it should be straightforward to change the patches to
suit - although it is almost certainly easier just to change your
schematics a little.

mvh.,

David