From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29381 invoked by alias); 19 Dec 2007 23:39:45 -0000 Received: (qmail 29369 invoked by uid 22791); 19 Dec 2007 23:39:44 -0000 X-Spam-Check-By: sourceware.org Received: from 204-133-123-27.dia.static.slbbi.com (HELO mail.chez-thomas.org) (204.133.123.27) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 19 Dec 2007 23:39:40 +0000 Received: by mail.chez-thomas.org (Postfix, from userid 999) id 7737E19502BD; Wed, 19 Dec 2007 16:39:38 -0700 (MST) Received: from [192.168.1.101] (hermes_local [192.168.1.101]) by mail.chez-thomas.org (Postfix) with ESMTP id D19271950093; Wed, 19 Dec 2007 16:39:36 -0700 (MST) Message-ID: <4769ABB8.8060303@mlbassoc.com> Date: Thu, 20 Dec 2007 07:29:00 -0000 From: Gary Thomas User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: Xavier Martinez CC: ecos-discuss@ecos.sourceware.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Rooki needing help: upgrading Meraki Outdoor X-SW-Source: 2007-12/txt/msg00124.txt.bz2 Xavier Martinez wrote: > Hi, > > We are trying to flash a "Meraki Outdoor" router with the openwrt > kamikaze 7.09 firmware via Redboot. Unfortunately, the unit reboots > after a few minutes of entering the redboot and we are not able to > finish writing the linux and rootfs partitions. It seems like the > redboot of this unit (unreleased version 1.3) has some kind of bug and > we would like to load a newer version of the redboot. The board is > identified as AP61 and we suspect that its athero chipset is based on > MIPS 4kc architecture. We would like to gain ethernet and serial > access in order to flash the firmware. > > However we haven't tried to update the redboot before and we wouldn't > like to end with a plastic brick in our hands. We would be very > pleased if someone could give advice on how to update the redboot on > this unit. This device is not in the public CVS, so help on this list may be quite limited. I would expect that you could build a RAM startup version of RedBoot, load that and then work from there. If this works, you should be able to verify the proper operation of the unit & RedBoot before committing any new ROM code. I presume that you have the sources for the RedBoot in question? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss