duplicate environment variables in U-Boot?

Hello!

Several times, I ran into troubles with the command parsing of U-Boot. Sometimes - especially if I had to do some simple corrections (backspace only, no delete, no cursor movements) the 'set xxx yyy) command doesn't get recognized.
Sometimes some commands like 'run nfsboot' gets ignored - especially after a long time doing nothing (waiting on the prompt for i.e. >15min) (no bs used or any other compilcated editing was used). I just get another prompt. If I type it again, it works fine.

And, finally, due to some of these problems, I guess, I got now a duplicate environment variable:

-----8<--------------------------------------------------------------- U-Boot 1.1.2 (Oct 28 2004 - 14:02:56)

Freescale PowerPC

     Core: E500, Version: 2.0, (0x80200020)
     System: 8540, Version: 2.0, (0x80300020)
     Clocks: CPU: 825 MHz, CCB: 330 MHz, DDR: 165 MHz, LBC:  82 MHz
     L1 D-cache 32KB, L1 I-cache 32KB enabled.
Board: MicroSys PM854
     PCI1: 32 bit, 66 MHz (compiled)

...
=> pri
...
stdin=serial
stdout=serial
stderr=serial
bootfile=/mlinux.UB.T1
bootfile=/vmlinux.UB.T1

Environment size: 1084/8188 bytes
=> -----8<---------------------------------------------------------------

Any ideas, fixes, suggestions?

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19

Dear Clemens,

Assuming that there are no hardware problems with your board I bet you _did_ use something else by backspace only.

In theory this is impossible. I have seen a couple of cases where a customer claimed to have such problems, but closer inspection always showed that the "duplicate" names were not identical, but one (or sometimes both) had some strange (and invisible) control characters embedded.

I'm afraid such a listing is useless. I guess you got it by copy & paste from the console window. This idoes not help at all, as you cannot see unvisible characters (obviously :-)

Yes. Ryn your session under a tool which records _all_ output, inclu- ding escape sequences and other control characters, like by running your terminal emulation program in a "script" session. Then use a tool which shows escape sequences and other control characters, like "vi" or "hexdump" to analyse the logfile.

I bet there are embedded control characters in your "duplicate" names.

Best regards,

Wolfgang Denk

Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Military secrets are the most fleeting of all.
	-- Spock, "The Enterprise Incident", stardate 5027.4