This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: AT91 extended internal SRAM


actually, i used this 128KB SRAM for GDB-stub. By this way, it can save more
space for application debuging. My borad is not EB40, it is designed by
myself. The GDB stub runs directly from Flash, no shadow into SRAM. The
steps are as below:

1. change the 0x02020000 to 0x00100000 in "target.ld" after check out the
stub configuration.
2. add some code in hal_platform_setup.h to disable the wirte protect.

regards,

----- Original Message -----
From: "Robert Martin" <rmartin_ecos@yahoo.com>
To: "eCos Discuss" <ecos-discuss@sources.redhat.com>
Sent: Tuesday, January 08, 2002 3:20 PM
Subject: [ECOS] AT91 extended internal SRAM


> Hello,
>
> I would like to add support for the 128k of internal
> SRAM on the AT91R40807, the CPU on the AT91EB40. I
> would like to do this so that I can have access to the
> only large chunk of 32 bit wide memory available for
> this chip and to bump up the memory available on the
> board by 25%.  From what I can tell so far, to do this
> I need to modify the AT91 startup code to disable
> write protection of this region, modify the linker
> map(s) for the configuration(s) that would use this,
> and modify RedBoot so that it will know about this
> additional region of memory. (I have done the first
> two and found out about RedBoot not allowing the load
> the hard way.)   I have no problem doing all of this
> in my local copy.  I would like to be able to feed the
> modifications back into the mainline sources.  I have
> a few questions on the best way to do this.
>



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]