Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #31020
| From | pozz <pozzugno@gmail.com> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: gcc ld and bss sections on SDRAM |
| Date | 2022-03-19 16:05 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <t14rfu$6i6$1@dont-email.me> (permalink) |
| References | <t11duu$b0l$1@dont-email.me> <t12h67.4tc.1@stefan.msgid.phost.de> |
Il 18/03/2022 17:57, Stefan Reuther ha scritto: > 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. Yes, you're right, bootloader is another good place to configure hw and next launch application. Thank you for your suggestion.
Back to comp.arch.embedded | Previous | Next — Previous in thread | Find similar | Unroll 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