From: Wolfgang Denk Date: Mon, 17 Nov 2014 17:20:25 +0100 Subject: [U-Boot] loadb problem. Hangs on START_CHAR In-Reply-To: <1416231868926-196549.post@n7.nabble.com> 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> <1416231868926-196549.post@n7.nabble.com> Message-ID: <20141117162025.7B0743814FF@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Bo, In message <1416231868926-196549.post@n7.nabble.com> you wrote: > > I keep coming back to the fact that "loads" works fine in 115200 baud, but > "loadb" does not. This is the funny part of it. > 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. But you don't even get there. You write you get stuck at the START_CHAR - eventually there is a bug in the serial driver or even in the hardware, such that it is not really 8 bit clean, or enables parity or such. "loads" s just an ASCII text transfer, i. e. it works fine when you get only 7 data bits through. "loadb" will really need an 8 bit clean link. > I am a bit baffled as you can imagine. Me too. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de Use the Force, Luke.