From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2155 invoked by alias); 20 Feb 2003 14:38:37 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2132 invoked from network); 20 Feb 2003 14:38:36 -0000 Received: from unknown (HELO ascomax.hasler.ascom.ch) (139.79.135.1) by 172.16.49.205 with SMTP; 20 Feb 2003 14:38:36 -0000 Received: from eiger.ma.tech.ascom.ch (eiger.ma.tech.ascom.ch [139.79.100.1]) by ascomax.hasler.ascom.ch (8.11.4/8.11.4) with ESMTP id h1KEcWY11189; Thu, 20 Feb 2003 15:38:32 +0100 (MET) Received: from biferten.ma.tech.ascom.ch ([139.79.100.27]) by eiger.ma.tech.ascom.ch with smtp (Exim 3.16 #1) id 18lrqI-0001zj-00; Thu, 20 Feb 2003 15:38:30 +0100 Received: by biferten.ma.tech.ascom.ch (SMI-8.6/SMI-SVR4) id PAA14126; Thu, 20 Feb 2003 15:38:28 +0100 Date: Thu, 20 Feb 2003 14:38:00 -0000 From: Andrew Lunn To: Pierre Habraken Cc: Mark Salter , jifl@ecoscentric.com, gary.thomas@mind.be, qqi@theworld.com, gdb@sources.redhat.com, ecos-discuss@sources.redhat.com Subject: Re: [ECOS] Can't connect to remote Evaluator 7T Message-ID: <20030220143827.GN11159@biferten.ma.tech.ascom.ch> Mail-Followup-To: Pierre Habraken , Mark Salter , jifl@eCosCentric.com, gary.thomas@mind.be, qqi@theworld.com, gdb@sources.redhat.com, ecos-discuss@sources.redhat.com References: <20030219174138.A6E4578A6D@deneb.localdomain> <1045676870.18484.6026.camel@hermes.chez-thomas.org> <3E53C60E.6000305@eCosCentric.com> <20030219192255.962AE78A6D@deneb.localdomain> <3E54E606.D1FDC422@imag.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E54E606.D1FDC422@imag.fr> User-Agent: Mutt/1.4i X-Filter-Version: 1.6 (ascomax) X-SW-Source: 2003-02/txt/msg00403.txt.bz2 > Loading section .text, size 0x3bec lma 0x8000 I think you have used the wrong startup type. The ROM startup uses: SECTIONS { SECTIONS_BEGIN CYG_LABEL_DEFN(__reserved_bootmon) = 0x1800000; . = CYG_LABEL_DEFN(__reserved_bootmon) + 0x 20000; SECTION_rom_vectors (rom, ALIGN (0x8), LMA_EQ_VMA) SECTION_text (rom, ALIGN (0x1), LMA_EQ_VMA) SECTION_fini (rom, ALIGN (0x4), LMA_EQ_VMA) SECTION_rodata (rom, ALIGN (0x4), LMA_EQ_VMA) SECTION_rodata1 (rom, ALIGN (0x4), LMA_EQ_VMA) SECTION_fixup (rom, ALIGN (0x4), LMA_EQ_VMA) SECTION_gcc_except_table (rom, ALIGN (0x4), LMA_EQ_VMA) SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) SECTION_data (ram, 0x8000, FOLLOWING (.gcc_except_table)) SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA) CYG_LABEL_DEFN(__heap1) = ALIGN (0x8); SECTIONS_END } You see that the data section goes at address 0x8000. Im assuming you have a ROM redboot. So its data section is at the same address you are downloading your application. The RAM startup code uses this layout: SECTIONS { SECTIONS_BEGIN SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) SECTION_rom_vectors (ram, 0x10000, LMA_EQ_VMA) SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA) SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA) SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA) SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA) SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA) SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA) SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA) SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA) CYG_LABEL_DEFN(__heap1) = ALIGN (0x8); SECTIONS_END } Notice that rom_vectors section goes at 0x10000, and everythig else follows that. Make sure your build is a RAM build. You may need to delete your work tree and start again. Andrew