-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customize linker for cv32e40p #22
Comments
Hi @saumeister Could you post the full linker script and compile command you are using. Thanks, Jeremy |
Hi @jeremybennett , The linker script with my modified additions. I run the command
and then the following:
Not sure if this mess of copied commands make sense to you. I can try to make it more clear. The generated files dhrystone.hex, dhrystone.readelf and dhrystone.objdump. |
@saumeister Apologies for letting this languish. I can't immediately see the problem. You might find you can get an answer by asking on the |
Hi,
I'm trying to use the cv32e40p core in a customized system with individual 32 kB memory space for instruction and data memory. However, I do not manage to customize the linker script to create only use signals within this memory space. I use the linker script provided in the bsp folder of the verification core-v-verif repository. The program I intend to initial run is the provided dhrystone.
My inital try was change the MEMORY map to be within my memory size 0x65536
ram (rwxai) : ORIGIN = 0x00000000, LENGTH = 0x64100
dbg (rwxai) : ORIGIN = 0x64200, LENGTH = 0x800
However, when I look at the generated hex_file, some sections are still placed outside my memory map address scope. Does anyone have some pointers to what basics I'm missing to change in the linker script?
Br
Saumeister
The text was updated successfully, but these errors were encountered: