Re: gcc ld and bss sections on SDRAM

Path	csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	Stefan Reuther <stefan.news@arcor.de>
Newsgroups	comp.arch.embedded
Subject	Re: gcc ld and bss sections on SDRAM
Date	Fri, 18 Mar 2022 17:57:26 +0100
Lines	17
Message-ID	<t12h67.4tc.1@stefan.msgid.phost.de> (permalink)
References	<t11duu$b0l$1@dont-email.me>
Mime-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	7bit
X-Trace	individual.net r93qGVUwtCH54QxHuZgmOw/RcSKBXNjd1Ag/IKoe7Or7wXp4DY
Cancel-Lock	sha1:y6xWMiZ+FGHfzy0U7FBoIlhvbps=
User-Agent	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 Hamster/2.1.0.1538
In-Reply-To	<t11duu$b0l$1@dont-email.me>
Xref	csiph.com comp.arch.embedded:31016

Show key headers only | View raw

Am 18.03.2022 um 08:56 schrieb pozz:
> I know I can rewrite ResetISR() or bss_init() to avoid accessing
> external bus addresses or I can configure SDRAM during ResetISR() before
> calling bss_init().
> 
> I suspect there's a better and more cleaner way. Noinit sections?

When I did bootloaders, I did the SDRAM initialisation there, before the
application starts. This also means there's a nice place to deal with
board varieties, i.e. if I have a board variant with a different SDRAM
chip, I only have to change the bootloader. And it allows loading parts
of the application code into SDRAM, if that is relevant for you.

Otherwise, I'd probably use a noinit section.


  Stefan

Thread

gcc ld and bss sections on SDRAM pozz <pozzugno@gmail.com> - 2022-03-18 08:56 +0100
  Re: gcc ld and bss sections on SDRAM David Brown <david.brown@hesbynett.no> - 2022-03-18 11:15 +0100
    Re: gcc ld and bss sections on SDRAM pozz <pozzugno@gmail.com> - 2022-03-18 11:49 +0100
  Re: gcc ld and bss sections on SDRAM Stefan Reuther <stefan.news@arcor.de> - 2022-03-18 17:57 +0100
    Re: gcc ld and bss sections on SDRAM pozz <pozzugno@gmail.com> - 2022-03-19 16:05 +0100

csiph-web