You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result from #75, we discovered that having a contiguous blob of code + ro-data presents some problems for 32-bit RISC-V simulation on QEMU. The simulation in question manages to start up the elfloader only for it to freeze up near the beginning when it's printing information about the HART that it is running on.
The text was updated successfully, but these errors were encountered:
It's highly likely that this issue is caused by the bss section not being initialized to 0 causing some issue with setup.
The spike platforms aren't configured to set CONFIG_IMAGE_BINARY so clear_bss wouldn't be called.
The opensbi compilation converts the elfloader elf into a binary image which would remove the .bss section from the end of the file as it's allocated but has default contents
When the image is initialized by the loader, the memory isn't zeroed and may have different values.
Rearranging the linker script to put the .rodata sections after the bss cause the bss sections to become contents within the binary file and would then be initialized by the loading.
As a result from #75, we discovered that having a contiguous blob of code + ro-data presents some problems for 32-bit RISC-V simulation on QEMU. The simulation in question manages to start up the elfloader only for it to freeze up near the beginning when it's printing information about the HART that it is running on.
The text was updated successfully, but these errors were encountered: