From owner-freebsd-mips@FreeBSD.ORG Sun Jan 11 20:24:41 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D4E65D3 for ; Sun, 11 Jan 2015 20:24:41 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B324DCE4 for ; Sun, 11 Jan 2015 20:24:40 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so10940941wiv.5 for ; Sun, 11 Jan 2015 12:24:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=0RItoulv/ZSTNj9V7tdvx1dXPw/bIOFQ9zF5ggorkJU=; b=yZS3efzdyfeBBghjltu7/aPid6PjWkMG1fE6tUeFHhvA5wm+mjYznsvzMZbCaeXghi 7PdA/mS5EgBUnNGMOExMr/buPhpfeX8mdR7M6DC1LaT7cqeiJ6lK6iY3ZuUOoxwm5vrH QKtjsQvGrWKLJSFAcYJagfuPdqzWjUtGsXKwC7/OR3rjxU0JQeeshMQXCzk/8xJER9rK Qr8oxRw6C2UBKpq5PzKBxOG/bIvdSua+Hs8uwJ2Sr2XXQs9ClMju44zc+qlGqZoeSpdi 4RvfwZxjveCrVwCGiMBRsW9q5zcx7bHyN39XyXXHHJv/CPudErKEWtK2Pd554W2dV2SM r2Dw== MIME-Version: 1.0 X-Received: by 10.194.5.37 with SMTP id p5mr24965997wjp.20.1421007878819; Sun, 11 Jan 2015 12:24:38 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.41.136 with HTTP; Sun, 11 Jan 2015 12:24:38 -0800 (PST) In-Reply-To: <20150111201748.GI46805@cicely7.cicely.de> References: <20150111160356.GG46805@cicely7.cicely.de> <20150111201748.GI46805@cicely7.cicely.de> Date: Sun, 11 Jan 2015 12:24:38 -0800 X-Google-Sender-Auth: K_zrJochigWn-Tacc9IVZfrjh-I Message-ID: Subject: Re: Booting on AR9331 based Easylink EL-M150 From: Adrian Chadd To: ticso@cicely.de Content-Type: text/plain; charset=UTF-8 Cc: Bernd Walter , "freebsd-mips@freebsd.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2015 20:24:41 -0000 Yeah, there's calibration data in the flash chip. You should be very careful. :) -a On 11 January 2015 at 12:17, Bernd Walter wrote: > On Sun, Jan 11, 2015 at 10:16:49AM -0800, Adrian Chadd wrote: >> Hi, >> >> I've had this issue reported by someone else - a tplink AR934x based >> thing. I wonder if it's an updated uboot related thing. >> >> So the TL;DR is this. >> >> uboot "bootm" doesn't boot a kernel image - it boots a uboot >> application. The application has a uboot header with details about >> "where it should be unpacked", "where it should be executed", etc. The >> tool that we're using is in ports but from an older uboot. It's >> possible the header contents are now .. wrong. >> >> So, the flash address used by the "bootm" comand is 0x9f(blah), and >> it'll unpack to wherever it says in the uboot header, and then execute >> wherever it says. Everything above is wrong - Load, entry, size, etc - >> and so that needs to be debugged. >> >> I have a tplink in a box that has the same issue, so I'll go see what >> the story is. > > Great. > > My EL-M150 module has the same hynx memory chip as the carambola 2 I compared > against, just the flash size ist different (winbond 25Q128 vs 25Q64). > Don't know if the SPI flash is hardcoded somehow, otherwise the carambola 2 > u-boot should work IMHO. > > Is there anything important in the flash, like calibration data, which > can be trashed by tampering with it? > Or failed parsing by a different u-boot version? > Guess I should dump the SPI data to tftp server anyway. > Never programmed a 25Q myself, but can't be too hard in case I brick it. > > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.