> CFInit is supported by M52211EVB (MCF52211)?
CFInit is a Windows program that generates example C code for initialising MCF CPUs.
CFInit doesn't list the MCF52211. It does support 50 other CPUs and 11 development boards.
Since all you want is an example of UART initialisation, pick the "closest" CPU that CFInit supports and compare the UART chapters of the Reference Manuals. The Coldfire manuals are all "cut and paste" jobs of chapters that match the modules that the chip is made from, so apart from the chapter and page numbers you'll find the chapters match. If they don't, pick another chip reference manual until they do.
Then get CFInit to generate the initialisation code for a couple of UARTs and start with that.
> I´ll use interrupts.( in emergency case= Panic button)
I don't see that as a requirement for interrupts. A simple "polling loop" can poll for a panic button press.
You have everything you need to design a simple flow-chart for the program to do what you need it to do.
The program is:
0 - Initialise everything.
1 - If there's an incoming byte in the UART, read it and store in a buffer.
2 - If there's output data in the buffer and the output UART is ready, send another byte.
3 - When there's a full receive buffer (when the terminator is there), process it into the output buffer.
4 - Keep an eye on the Panic Switch.
5 - Blink LEDs and so on.
6 - Go back to step 1.
That's easy. What isn't easy is coding up all the initialisation, all the interrupt service code, buffering and whatever "operating system" you need to support your program.
That's what products like uTasker are for.
Is this a commercial product or a hobby? If it is a hobby, then uTasker is free. If it is a commercial product, then uTasker is $485. How much is your time worth? How much do you cost to your employer? How many hours is $485 worth? How many hours/days/weeks is it going to take you to get this project working, then debugged?
Tom