From: Rudi Pfister <Rudi.Pfister@informatik.stud.uni-erlangen.de>
To: ecos-devel@ecos.sourceware.org
Subject: Flashdriver for TC1796
Date: Sat, 18 Nov 2006 15:07:00 -0000 [thread overview]
Message-ID: <200611181606.45988.Rudi.Pfister@informatik.stud.uni-erlangen.de> (raw)
Hello,
I'm porting Redboot to the Tricore-architecture. In special to the
TC1796-variant on a Infineon-Triboard.
The TC1796 has onchip 2 MByte of Flashmemory devided into several
blocks with sizes from 16 KByte up to 512 KByte.
The TC1796 has about 192 KByte RAM in total.
The Triboard has 1 MByte SRAM used by the TC1796 as external
Memory.
I want to write a driver for the flash memory of the TC1796.
If the Redboot wants to change data in the flash memory it stores
the block to which the data should be written to a buffer in RAM.
Then it changes the data in the buffer and writes it back to flash
memory. The size of the buffer has to be the same size as the
largest block in the flash memory.
Here is my problem. The size of the buffer has to be 512 KByte, but
the TC1796 has less than 512 KByte in total, so there is no space to
create the Buffer an a TC1796.
In my case I could use the RAM of the Triboard, which is large enough.
But then the the driver for the flash memory of the TC1796-variant would
depend on the properites of the Triboard-platform.
I could also use only a part of the flash of the TC1796. In special the blocks
with the size of 16 KBytes. In total I would then be able to use 128 Kbytes
of Flashmemory, which would be enough for me.
But in my opinion both ways are very unsatisfying.
Is there a better way to deal with this problem ?
And what is the best resolution in respect to the
eCos-design-philosophy ?
Thanks !
Rudi
next reply other threads:[~2006-11-18 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 15:07 Rudi Pfister [this message]
2006-11-18 20:39 ` Andrew Lunn
2006-11-21 11:04 Rudi Pfister
2006-11-21 13:19 ` Andrew Lunn
2006-11-22 10:51 Rudi Pfister
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=200611181606.45988.Rudi.Pfister@informatik.stud.uni-erlangen.de \
--to=rudi.pfister@informatik.stud.uni-erlangen.de \
--cc=ecos-devel@ecos.sourceware.org \
/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).