Weird linker behaviour

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
Karoolek
Posts: 1
Joined: Wed Jan 17, 2018 7:20 am

Weird linker behaviour

Post by Karoolek »

Hi, I'm writting my own kernel and I've encountered strange problem (my OS uses UEFI for boot). I'm linking all stuff with this script . Idk why, vaddr of LOAD section is correct, but paddr is always fixed to 0x0000000000000000. I've already tried everything but my linker always sets this value to 0. Can my bootloader assume that this value is 1MB or I should do something with it? Thanks for replies!
Top
User avatar
zaval
Member
Member
Posts: 659
Joined: Fri Feb 17, 2017 4:01 pm
Location: Ukraine, Bachmut
Contact:
Contact zaval

Re: Weird linker behaviour

Post by zaval »

Why are you using the AT statement at all? Are you planning to move these pieces from ROM or what? I guess you've complicated your task by yourself. Remove AT and forget about paddr fields. they are not needed for you.
ANT - NT-like OS for x64 and arm64.
efify - UEFI for a couple of boards (mips and arm). suspended due to lost of all the target park boards (russians destroyed our town).
Top
Post Reply

Return to “OS Development”