Is it a hyperterm problem? Did you verify hyperterm is actually sending data? A classic problem is that Windows has handshaking enabled and it is waiting for a handshake. Make sure both software and hardware handshaking is disabled. (If your board supports handshaking, this would be a test. If it doesn't, this is essential).
gvb
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of Petre Pircalabu Sent: Thursday, May 06, 2004 2:01 PM To: u-boot-users Subject: [U-Boot-Users] FFUART problem
Hello,
I have a problem regarding the FFUART of a PXA255 processor. U-boot doesn't seem to accept any characters sent from the terminal (i'm currently using hyperterminal) even after I cleared the RDH bit in the PSSR. Did someone encountered this problem?
thanks,
Petre
This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************