From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Tue, 29 May 2007 08:44:23 -0400 Subject: [U-Boot-Users] loads command is not working In-Reply-To: <465AAA1C.7050601@anagramm.de> References: <20070526130851.B6D52353428@atlas.denx.de> <4659DD9B.6050004@box74238.elkhouse.de> <4659F597.7090506@anagramm.de> <465AAA1C.7050601@anagramm.de> Message-ID: <465C2027.8080004@smiths-aerospace.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Clemens Koller wrote: > Hi, > > ksi at koi8.net schrieb: >> On Sun, 27 May 2007, Clemens Koller wrote: >>> Just to make the list complete: >>> Linux Host: >>> minicom v2.2 >>> http://alioth.debian.org/projects/minicom/ >> Minicom is crap, sorry for an expression... > > Technically, it works fine. Propably, some don't > like the UI, which has a vi like flavour. > Well... it works for me. YMMV > > Greets, > > Clemens Koller The problem is not the interface, the problem is that minicom is unreliable. I actually generally use it as the path of least resistance, but occasionally it messes me up. I have used cu as well and should switch, but have not yet. The typical problem I have with minicom is that the tty port gets messed up (baud rate, handshake, etc. is wrong) and minicom cannot recover it. Minicom will tell you it is changing the port configuration (baud rate, for instance) and say that the baud rate is what you set it to, but it really isn't. As you can imagine, this is very confusing and frustrating when the board you are connecting to appears to only put out garbage characters and trying all the common baud rates does not change anything. It looks like there is a serious problem with the development board, but actually it is minicom. Interestingly, I've never had a problem getting kermit to reset the port characteristics to a sane setting when this happens, and then minicom will behave again, for a while. Best regards, gvb