From: Chris Holgate <chris@zynaptic.com>
To: ecos-devel@sourceware.org
Subject: Problem with STM32 flash driver on Rev-Z silicon.
Date: Fri, 02 Jan 2009 11:19:00 -0000 [thread overview]
Message-ID: <495DF7FA.9090904@zynaptic.com> (raw)
Hi folks,
I have encountered a problem with the STM32 flash driver on revision Z
devices. According to the errata document, the debug registers cannot
be accessed from the processor on rev-Z devices This means that it it
not possible to get the device type by reading CYGHWR_HAL_STM32_MCU_ID,
which causes the flash driver to use invalid parameters. Maybe it would
be better to rely on the HAL configuration for this information.
I also noticed that the flash and RAM size definitions stored in the
CYGHWR_HAL_STM32_DEV_SIG register are the wrong way round for my device
(ie, the _FSIZE macro gets the RAM size and the _RSIZE macro gets the
flash size). I don't know if this is an eCos bug or a rev-Z bug, since
the documentation for this register seems a bit vague.
Chris.
next reply other threads:[~2009-01-02 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 11:19 Chris Holgate [this message]
2009-01-02 11:30 ` Simon Kallweit
2009-01-02 16:16 ` Chris Holgate
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=495DF7FA.9090904@zynaptic.com \
--to=chris@zynaptic.com \
--cc=ecos-devel@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).