From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7788 invoked by alias); 24 Aug 2007 17:24:16 -0000 Received: (qmail 7386 invoked by uid 22791); 24 Aug 2007 17:24:11 -0000 X-Spam-Check-By: sourceware.org Received: from bay0-omc3-s36.bay0.hotmail.com (HELO bay0-omc3-s36.bay0.hotmail.com) (65.54.246.236) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 24 Aug 2007 17:23:54 +0000 Received: from hotmail.com ([207.46.8.105]) by bay0-omc3-s36.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Fri, 24 Aug 2007 10:23:52 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 24 Aug 2007 10:23:51 -0700 Message-ID: Received: from 207.46.8.123 by by117fd.bay117.hotmail.msn.com with HTTP; Fri, 24 Aug 2007 17:23:47 GMT X-Sender: mpashea@hotmail.com From: "Mike Pashea" To: ecos-discuss@ecos.sourceware.org Bcc: Date: Fri, 24 Aug 2007 17:24:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed 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] AXIOM CME555 Redboot FLASH Memory Read Problems X-SW-Source: 2007-08/txt/msg00135.txt.bz2 Hi All, I have questions regarding problems with Redboot crashing on a CME-555 platform when using FLASH memory support. The symptoms appear to be the same as the problem described by Miguel Vega in his posts, but I haven’t found any follow-up posts from him describing whether he found any solution(s). I’ve modified am29xxxxx_parts.inl to include the AM29LV400 device and Redboot successfully recognizes the device ID and completes the FLASH initialization. However, it crashes when memcpy() is used to copy the Redboot configuration data in load_flash_config() located in flash.c. I’ve used gdb to investigate this crash and have found that the problem always occurs on a read from FLASH. If I try to examine the memory location with gdb, I receive the message “Cannot access at address 0x880000”. Yet, a read of 0x880001 returns the proper data. Has anyone else come across this, and is there a solution? Any help would be greatly appreciated. Mike Pashea _________________________________________________________________ A new home for Mom, no cleanup required. All starts here. http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss