From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10086 invoked by alias); 16 Sep 2013 14:35:38 -0000 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 Received: (qmail 10073 invoked by uid 89); 16 Sep 2013 14:35:37 -0000 Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 16 Sep 2013 14:35:37 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RDNS_NONE,SPF_FAIL autolearn=no version=3.3.2 X-HELO: plane.gmane.org Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VLZti-0006mf-8J for ecos-discuss@ecos.sourceware.org; Mon, 16 Sep 2013 16:35:30 +0200 Received: from dsl.comtrol.com ([64.122.56.22]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 16 Sep 2013 16:35:30 +0200 Received: from grant.b.edwards by dsl.comtrol.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 16 Sep 2013 16:35:30 +0200 To: ecos-discuss@ecos.sourceware.org From: Grant Edwards Date: Mon, 16 Sep 2013 14:35:00 -0000 Message-ID: User-Agent: slrn/1.0.1 (Linux) X-IsSubscribed: yes Subject: [ECOS] Documentation for .ldi file? X-SW-Source: 2013-09/txt/msg00005.txt.bz2 Can somebody please point me to the documentation for writing a .ldi file? I'm trying figure out how to 1) Add a new section that's always at the beginning of the binary image which contains the image entry point. 2) Set the location of the Cortex-M3 interrupt table -- which is neither at the beginning of the program image, nor does it contain the image entry point. Is hal_vsr_table the only symbol I need to worry about defing to determine the location of the M3's VTOR table? Why the multiple layers of obfuscation when just writing a gnu linker script would be so much easier? I get the impression that somehow all these layers were supposed to allow people who know nothing about hardware, the Gnu toolchain or embedded systems development do embedded systems development? AFAICT, it backfired and just makes it that much harder to create a port and figure out what's wrong when something doesn't work. -- Grant Edwards grant.b.edwards Yow! I'm gliding over a at NUCLEAR WASTE DUMP near gmail.com ATLANTA, Georgia!! -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss