[ECOS] printf and diag_printf go to nowhere

Andrew Lunn andrew@lunn.ch
Wed Apr 15 08:42:00 GMT 2009

On Wed, Apr 15, 2009 at 09:38:39AM +0200, Edgar Grimberg wrote:
> Robert Brusa wrote:
>> This little serial example program. Compiled, linked downloaded with  
>> BDI all ok. But I can not start it with BDI/telnet go 0. Hell and  
>> death - just before I did just this!
> Are you sure that execution is supposed to start at address 0x0 ? If  
> it's a ROM application, try go 0x00100000 (I believe that's the starting  
> point for your target).
> Also, another thing that might confuse you is the configuration script  
> for BDI. It will set up the target CPU to a state that is different than  
> the one you get without the BDI. When I write applications that are  
> supposed to start up the board (ROM startup type), I use a stripped down  
> version of the config file, that will not touch the configuration  
> registers in the CPU.

Yes, it sounds like the BDI is remapped the memory. On a clean power
on, without any JTAG debugger fiddling with things, ROM is mapped both
at 0x0 and 0x00100000. The JTAG programmer i use, jumps in on reset
and maps RAM to 0x0.


Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

More information about the Ecos-discuss mailing list