This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: STM3210E crash
- From: John Dallaway <john at dallaway dot org dot uk>
- To: Alan Bowman <alan dot michael dot bowman at gmail dot com>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 09 Nov 2010 14:11:20 +0000
- Subject: [ECOS] Re: STM3210E crash
[ re-sending with copy to ecos-discuss ]
Hi Alan
Alan Bowman wrote:
>> Some board vendors will fit alternative parts on request. Perhaps your
>> particular board has been customised?
>
> As far as I'm aware, this is a standard eval board. The printing on
> the top of the chip clearly says ZD - I may investigate whether it's a
> printing error, rather than an alternative part.
>
> It sounds like ROM startup is mainly used for Redboot to then load an
> application into RAM. I'm trying to use as little RAM as possible,
> and don't need Redboot. Am I correct in thinking that ROM startup
> mode for my application should be what I'm after?
The STM3210E-EVAL board is attractive for many developers because it
features sufficient (external) RAM to permit initial application
development in RAM. This generally allows a faster download/debug cycle
and provides greater flexibility in the use of breakpoints. However, I
would expect many production Cortex-M3 designs to feature no external
RAM, requiring a switch to ROM startup later in development in order to
reduce RAM usage.
For avoidance of doubt, you can use RAM startup without RedBoot by
disabling CYGSEM_HAL_USE_ROM_MONITOR.
I hope this helps...
John Dallaway
eCos maintainer
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss