From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31347 invoked by alias); 21 Oct 2003 20:25:24 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 31298 invoked from network); 21 Oct 2003 20:25:23 -0000 Message-ID: <3F95962D.9060508@eCosCentric.com> Date: Tue, 21 Oct 2003 20:25:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.4) Gecko/20030703 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Batra Rajat-r7aadp Cc: "'ecos-maintainers@sources.redhat.com'" Subject: Re: ecos on OMAP710 using CCS References: <6728517EECE7D511981B00D0B782903103845B18@az33exm27.corp.mot.com> In-Reply-To: <6728517EECE7D511981B00D0B782903103845B18@az33exm27.corp.mot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00022.txt.bz2 Batra Rajat-r7aadp wrote: > Hi, > > I am trying to load redboot into RAM on my OMAP710 based board. I have > succesfully created a redboot.elf using ecos2.0 and the innovator for > arm9 config file. When I try to load redboot onto the board using CCS > version 2.2 using File/load program and selecting my redboot.elf file, > I get an error stating that the application has terminated because of > possible stack overflow, or writing into the wrong place. In fact CCS > shuts down. Am I even close to following the right steps? If so, what > might be the problem? This isn't really the right forum. You'll get a better chance of good responses to future queries in the ecos-discuss list. As for your problem, it looks like CCS is having a problem with the image, rather than the image being necessarily invalid. See if CCS can load another format like SREC or just raw binary to the correct address. If you're not sure if your binary has been built for the correct address for the memory map of your board, you could verify by using "arm-elf-objdump -h redboot.elf". One possible thing certainly is to verify you have built RedBoot for RAM startup type. Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine