From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1649 invoked by alias); 7 Apr 2008 16:36:39 -0000 Received: (qmail 1628 invoked by uid 22791); 7 Apr 2008 16:36:38 -0000 X-Spam-Check-By: sourceware.org Received: from mail2.ultra-uems.ca (HELO exchange.Ultra-UEMS.ca) (142.176.234.162) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 07 Apr 2008 16:36:18 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Mon, 07 Apr 2008 16:43:00 -0000 Message-ID: From: "Davies, Greg" To: X-IsSubscribed: yes 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: [ECOS] Changing flash wait state on SAM7 X-SW-Source: 2008-04/txt/msg00118.txt.bz2 I've been having some strange memory issues that I've been talking about in the "eCos causing something.. Maybe?" thread. Basically I was seeing random values when I did a dump of any section of memory. The BDI folks suggested I change the flash wait state. I did this and the problem went away.=20 I now have an issue similar to this while trying to debug. I can see that the first 3 instructions set the flash wait state to 1 (by writing 0x100 to 0xffffff60), but I need it to be 3. This seems to be in a function called reset_vector (or at least that's what gdb calls it). I tried changing what looked like the same code (but called __flash_init__) in packages\hal\arm\at91\at91sam7s\current\include\hal_platform_setup.h, and I rebuilt everything, but when I loaded on the new code, it still wrote the same value. Am I changing the flash wait state in the right spot? -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss