From mboxrd@z Thu Jan 1 00:00:00 1970 From: bomellberg Date: Mon, 17 Nov 2014 06:44:28 -0700 (MST) Subject: [U-Boot] loadb problem. Hangs on START_CHAR In-Reply-To: <20141117133053.705AF380469@gemini.denx.de> References: <1415364802594-195144.post@n7.nabble.com> <1415622808801-195379.post@n7.nabble.com> <20141110125119.79476383346@gemini.denx.de> <1415624206506-195381.post@n7.nabble.com> <1416218063825-196499.post@n7.nabble.com> <20141117114440.822773814FF@gemini.denx.de> <1416225420788-196515.post@n7.nabble.com> <20141117123718.95B743814FF@gemini.denx.de> <1416227882897-196541.post@n7.nabble.com> <20141117133053.705AF380469@gemini.denx.de> Message-ID: <1416231868926-196549.post@n7.nabble.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Wolfgang! Thank you for your efforts to help me out. I keep coming back to the fact that "loads" works fine in 115200 baud, but "loadb" does not. If there is indeed a timing issue, it must be some handshaking in the Kermit protocol, right? The "loads" command just absorbs data as it is transferred, but the "loadb" command, using Kermit, tries to speed up the transfer by adjusting packet size according to crc-errors. I am a bit baffled as you can imagine. /Bo -- View this message in context: http://u-boot.10912.n7.nabble.com/loadb-problem-Hangs-on-START-CHAR-tp195144p196549.html Sent from the U-Boot mailing list archive at Nabble.com.