Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2021.04, v2021.07-rc3 are OUT / Merge Window is CLOSED / Release v2021.07 is scheduled for 05 July 2021 / http://www.denx.de/wiki/U-Boot / Channel archives at https://libera.irclog.whitequark.org/u-boot
<tlwoerner> okay...... if i change the CONFIG_SYS_TEXT_BASE down to 0x8300.0000 everything works ?!
<tlwoerner> i'll re-enable debugging to see what math it's coming up with in this case
cambrian_invader has quit [Ping timeout: 272 seconds]
cambrian_invader has joined #u-boot
vagrantc has quit [Ping timeout: 272 seconds]
flyback is now known as canucks
canucks is now known as flyback
vagrantc has joined #u-boot
alpernebbi has joined #u-boot
<tlwoerner> i'm starting to see the pattern. regardless of where i set CONFIG_SYS_TEXT_BASE, the location of many pieces (malloc, board info, global data, fdt…) are always in the same location
vagrantc has quit [Quit: leaving]
georgem has quit [Quit: Connection closed for inactivity]
agust has joined #u-boot
Zapy has quit [Ping timeout: 264 seconds]
Zapy has joined #u-boot
flyback has quit [Ping timeout: 252 seconds]
flyback has joined #u-boot
smartin has joined #u-boot
redbrain has joined #u-boot
gsz has joined #u-boot
redbrain has quit [Ping timeout: 245 seconds]
redbrain has joined #u-boot
redbrain has quit [Read error: Connection reset by peer]
macromorgan has quit [Ping timeout: 272 seconds]
redbrain has joined #u-boot
redbrain has quit [Ping timeout: 245 seconds]
redbrain has joined #u-boot
pavelow has joined #u-boot
Raito_Bezarius has quit [Ping timeout: 268 seconds]
Guest38 has joined #u-boot
Raito_Bezarius has joined #u-boot
Guest38 has quit [Quit: Client closed]
<Forty-Bot> tlwoerner: after relocation, everything should be just before the top of ram
<Forty-Bot> which depends on CONFIG_SYS_SDRAM_SIZE or really get_effective_memsize/dram_init
macromorgan has joined #u-boot
redbrain has quit [Ping timeout: 245 seconds]
redbrain has joined #u-boot
Guest388 has joined #u-boot
vagrantc has joined #u-boot
gsz has quit [Ping timeout: 252 seconds]
alpernebbi has quit [Quit: alpernebbi]
macromorgan has quit [Quit: Leaving]
Guest388 has quit [Quit: Client closed]
smartin has quit [Quit: smartin]
agust has quit [Quit: Leaving.]
redbrain has quit [Ping timeout: 264 seconds]
paguilar__ has joined #u-boot
paguilar_ has quit [Read error: Connection reset by peer]
birkoff has quit [Quit: ZNC 1.8.2 - https://znc.in]
<tlwoerner> yes, that part is clear. what isn't clear is that before relocating, a bunch of things get RAM reserved for them (malloc, board info, global data, fdt, etc…) i'd like to know how/where those addresses are determined
<tlwoerner> they are not affected by CONFIG_SYS_TEXT_BASE in any way or the new relocated-to address (which surprises me)
<tlwoerner> what i'm finding is that if CONFIG_SYS_TEXT_BASE is set below the magic "reservation" addresses everything works, but if CONFIG_SYS_TEXT_BASE is defined above the magic reservation block, the relocation fails
kpo has quit [Read error: Connection reset by peer]
kpo has joined #u-boot
<tlwoerner> huh, and now i see it. the malloc area is so huge, it fills everything from where it starts up until relocated u-boot starts
<tlwoerner> Forty-Bot: i guess that's what you were saying ;-) everything is filled up until below the reservations, so the original pre-relocated u-boot would have to be loaded below the reserved areas
<tlwoerner> i wonder if there's a way to check for that during the build?
birkoff has joined #u-boot
birkoff has quit [Changing host]
birkoff has joined #u-boot