There's a forum specific to the OSBDM, with posts mentioning the MCF5213 from 2011 and 2012:
https://community.nxp.com/message/109512
https://community.nxp.com/message/74936
You may want to post there.
Debug support requires there to be a description of the chip so the debugger can set up initial clocks, I/O and memory. Then you usually load your program into RAM and test it from there.
Programming support requires all of that plus a description of, and code for programming the Flash memory. There is usually a small program that is loaded into the SRAM on the CPU to communicate with the debugger and to do the programming. The MCF5213 has internal Flash, so that's only one "target". If you were using external Flash (like on an MCF5235) then there has to be a downloadable programmer for every different Flash type and every bus width - or the downloaded code has to be very flexible to handle all combinations. Then you might be using multiple chip selects that makes it more complicated.
What we do (for the MCF5235 we use) is to have a RAM-loaded Bootstrap that knows how to program the Flash. We use the debugger to set up the clocks and external Flash and RAM and then load the debugger and run it with a flag setting that tells it to "burn itself to Flash". Then we talk to it over Ethernet to burn the main firmware.
You could always write your own Flash-burner program and load that into SRAM. You could then burn from communicating with the Debugger, over a serial port, CAN or SPI. Or you could use EzPort.
Tom
