Thanks, minicom works perfectly.
>>> cyril.bazin@... 22/08/2005 14:00 >>>
There was a thread about this problem on the gumstix mailing list.=20
Frank gave the answer and Craig the explanation.
Try to use "minicom -o" communicate throught ttyS0. I never had problems=20
concerning the keyboard using this technique.
<frannk_m1@...> to gumstix-users
More options Jul 19 Just do a "saveenv" from u-boot and the problem will go=
next time you boot the board...
Craig Hughes <craig@...> to gumstix-users
I've reduced the erroriness of this warning message in the buildroot
version of u-boot. It's a perfectly safe messages -- as Frank points
out, it just means that since u-boot was flashed, you haven't yet
saved the enviroment variables, therefore the CRC for the saved env
is bad, therefore it just falls back to using the compiled-in default
env, which is normal.
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.
CSIR E-mail Legal Notice
CSIR Copyright, Terms and Conditions
For electronic copies of the CSIR Copyright, Terms and Conditions and the C=
Legal Notice send a blank message with REQUEST LEGAL in the subject line to
This message has been scanned for viruses and dangerous content by MailScan=
and is believed to be clean. MailScanner thanks Transtec Computers for the=