[ECOS] Re: Question about diag_printf

Jonathan Larmour jifl@eCosCentric.com
Tue Jan 9 15:38:00 GMT 2007


Guillaume Menant wrote:
> Hi,
> 
> I'm porting RedBoot on a new platform: ATMEL AT697E on EvaB board and I've
> got a problem when RedBoot is starting. 
> 
> 1 - It writes the RedBoot header over the serial link:
> 
>     RedBoot(tm) bootstrap and debug environment [RAM]
>     Non-certified release, version v2_0 - built 11:14:36, Jan  9 2007
> 
>     Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
> 
>     RAM: 0x40000000-0x60000000, 0x40011060-0x40100000 available
> 
>     This part is always the same.
> 
> 2 - It writes the RedBoot prompt (with diag_printf):
> 
>     RedBoo>t>tt>
> 
>     Like you see, this part is altered but not always the same way
> 
> 3 - Too many arguments - stopped at: 't> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> '
>
>     Too many arguments - stopped at: 't> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> '
>     Too many arguments - stopped at: 't> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> '
>     Too many arguments - stopped at: 't> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t>
> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t> t
> 
>     Few seconds later this message arrives. It corresponds to an error when
> receiving a string on the serial link which is not correct. But nothing has
> been sent to the serial link. And it is the end of the previous transmitted
> string (RedBoot> ).
> 
> -> It appears like interferences between transmitting and receiving data on
> serial port. What can I do to prevent this behaviour ?

Perhaps your serial port is in loopback mode? There's often a configuration 
bit in the registers for that. Although I wouldn't expect to have seen any 
output on the physical port in that case.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
Company legal info, address and number:   http://www.ecoscentric.com/legal
------["The best things in life aren't things."]------      Opinions==mine

-- 
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