public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alois Z." <alois@gmx.at>
To: ecos-discuss@sources.redhat.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RAM Images on AT91SAM7s256
Date: Mon, 28 Jan 2008 17:06:00 -0000	[thread overview]
Message-ID: <20080128170611.58540@gmx.net> (raw)
In-Reply-To: <20080128164654.GC10795@lunn.ch>

> 
> 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

WARNING: multiple messages have this Message-ID

From: "Alois Z." <alois@gmx.at>
To: ecos-discuss@sources.redhat.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RAM Images on AT91SAM7s256
Date: Mon, 28 Jan 2008 17:10:00 -0000	[thread overview]
Message-ID: <20080128170611.58540@gmx.net> (raw)
Message-ID: <20080128171000.YPcAkH_gSgPEanHPDUL3Av9s6uLgAwu0pgVzzhrr4L4@z> (raw)
In-Reply-To: <20080128164654.GC10795@lunn.ch>

> 
> 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

  reply	other threads:[~2008-01-28 17:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 16:08 Alois Z.
2008-01-28 16:47 ` Andrew Lunn
2008-01-28 17:06   ` Alois Z. [this message]
2008-01-28 17:10     ` Alois Z.
2008-01-28 17:19     ` Andrew Lunn
2008-01-28 18:36       ` Alois Z.
2008-01-29 12:19         ` Tom Deconinck
2008-04-02  1:48           ` airdelroy
2008-04-02  6:12             ` Tom Deconinck
2008-04-05  0:14               ` airdelroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080128170611.58540@gmx.net \
    --to=alois@gmx.at \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).