ColdFire/68K Microcontrollers and Processors中的主题 Re: MCF52235EVB - MCF52235EVB - Debug Targets

MCF52235EVB - MCF52235EVB - Debug Targets

Student_Exams — Mon, 09 Jul 2007 21:49:49 GMT

Hello,

maybe it´s a very simple question.

Can you tell me the difference between the Debug Target "MCF52235EVB Console Debug" and "MCF52235EVB UART Debug" ?

Thx a lot.

--
Alban Edit: please always mention part numbers in the subject line.

Message Edited by Alban on 2007-07-09 04:49 PM

Re: MCF52235EVB - MCF52235EVB - Debug Targets

CrasyCat — Tue, 10 Jul 2007 13:25:20 GMT

Hello

Main difference is the way the printf are treated.

"MCF52235EVB Console Debug" build target will use the console window within the IDE as stdout. This is where printf will show up.

"MCF52235EVB UART Debug" build target will redirect stdout to an SCI. So you have to open a hyper terminal window to see your output strings.

This build target is also performing some hardware initialization and initializing the vector table. This is not done in the RAM Console build target.

I hope this helps.

CrasyCat

Re: MCF52235EVB - MCF52235EVB - Debug Targets

Student_Exams — Tue, 10 Jul 2007 14:11:25 GMT

Hello again.

Do you know what this additional initialisation is in detail? Where can I find this code?
My problem is that my code works with uart debug but not with console.

Thx for editing

Re: MCF52235EVB - MCF52235EVB - Debug Targets

CrasyCat — Wed, 11 Jul 2007 13:15:50 GMT

Hello

Entry point of the application is asm_startmeup, located in MCF52235_io.s.

Hardware initialization is done partially in that function and then in function mcf52235_init

implemented in module mcf52235_sysinit.c.

Vector table is initialized in module mcf52235_vectors.s.

All these source files are part of the project source files.

CrasyCat