From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4598 invoked by alias); 28 Jan 2008 17:06:36 -0000 Received: (qmail 4508 invoked by uid 22791); 28 Jan 2008 17:06:36 -0000 X-Spam-Check-By: sourceware.org Received: from mail.gmx.net (HELO mail.gmx.net) (213.165.64.20) by sourceware.org (qpsmtpd/0.31) with SMTP; Mon, 28 Jan 2008 17:06:16 +0000 Received: (qmail 19125 invoked by uid 0); 28 Jan 2008 17:06:14 -0000 Received: from 128.131.86.182 by www163.gmx.net with HTTP; Mon, 28 Jan 2008 18:06:10 +0100 (CET) Cc: ecos-discuss@sources.redhat.com Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 28 Jan 2008 17:06:00 -0000 From: "Alois Z." In-Reply-To: <20080128164654.GC10795@lunn.ch> Message-ID: <20080128170611.58540@gmx.net> MIME-Version: 1.0 References: <20080128160738.64350@gmx.net> <20080128164654.GC10795@lunn.ch> To: ecos-discuss@sources.redhat.com X-Authenticated: #979605 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) Content-Transfer-Encoding: 8bit X-GMX-UID: tDKtf+siMmA6fP6eZWFn1Mk5MjQ1N12g 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: Re: [ECOS] RAM Images on AT91SAM7s256 X-SW-Source: 2008-01/txt/msg00192.txt.bz2 > > With only 64Kbytes of RAM, you will be very limited to what you can > do. I strongly suggest you get a JTAG debugger which can set hardware > breakpoints. You can then run your application from ROM and single > step, set a couple of breakpoints etc. > I know, but for first test 64k are quite fine. And for my first tests I like to be as none invasive as possible. The board is the mindstorms NXT board and to have JTAG debugging I would need to disassamble the brick and solder a connector in. However I can image that I will not come far without debugging support. > > How are you going to get this image into RAM? I thought of useing sam-ba for loading and starting images. > > You also need to make sure that RAM is mapped to address 0x0 as well > as 0x00200000. I know ROM startup does this, but i think RAM startup > probably does not. Is this necessary for the vectors to be at the right place? -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5180 invoked by alias); 28 Jan 2008 17:06:39 -0000 Received: (qmail 5081 invoked by uid 22791); 28 Jan 2008 17:06:38 -0000 X-Spam-Check-By: sourceware.org Received: from mail.gmx.net (HELO mail.gmx.net) (213.165.64.20) by sourceware.org (qpsmtpd/0.31) with SMTP; Mon, 28 Jan 2008 17:06:16 +0000 Received: (qmail 19125 invoked by uid 0); 28 Jan 2008 17:06:14 -0000 Received: from 128.131.86.182 by www163.gmx.net with HTTP; Mon, 28 Jan 2008 18:06:10 +0100 (CET) Cc: ecos-discuss@sources.redhat.com Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 28 Jan 2008 17:10:00 -0000 From: "Alois Z." In-Reply-To: <20080128164654.GC10795@lunn.ch> Message-ID: <20080128170611.58540@gmx.net> MIME-Version: 1.0 References: <20080128160738.64350@gmx.net> <20080128164654.GC10795@lunn.ch> To: ecos-discuss@sources.redhat.com X-Authenticated: #979605 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) Content-Transfer-Encoding: 8bit X-GMX-UID: tDKtf+siMmA6fP6eZWFn1Mk5MjQ1N12g 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: Re: [ECOS] RAM Images on AT91SAM7s256 X-SW-Source: 2008-01/txt/msg00193.txt.bz2 Message-ID: <20080128171000.YPcAkH_gSgPEanHPDUL3Av9s6uLgAwu0pgVzzhrr4L4@z> > > With only 64Kbytes of RAM, you will be very limited to what you can > do. I strongly suggest you get a JTAG debugger which can set hardware > breakpoints. You can then run your application from ROM and single > step, set a couple of breakpoints etc. > I know, but for first test 64k are quite fine. And for my first tests I like to be as none invasive as possible. The board is the mindstorms NXT board and to have JTAG debugging I would need to disassamble the brick and solder a connector in. However I can image that I will not come far without debugging support. > > How are you going to get this image into RAM? I thought of useing sam-ba for loading and starting images. > > You also need to make sure that RAM is mapped to address 0x0 as well > as 0x00200000. I know ROM startup does this, but i think RAM startup > probably does not. Is this necessary for the vectors to be at the right place? -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss