日本語
[Solved] How to solve ld.lld error ‘relocation R_RL78_DIR16U_RAM out of RAM range’
How to solve ld.lld error ‘relocation R_RL78_DIR16U_RAM out of RAM range’
Hello support team,
I get the following errors. The project can be built by GNRL78 but cannot be built by LLVM-RL78. What can I do to solve the errors?
ld.lld: error: C:/Renesas/GitHubDesktop/work/FreeRTOS/FreeRTOS/Demo/Common/Minimal\TimerDemo.c:1144:(.text._prvOneShotTimerCallback+0x59): relocation R_RL78_DIR16U_RAM out of RAM range: 1000910 is not in [1044224, 1048319]
ld.lld: error: C:/Renesas/GitHubDesktop/work/FreeRTOS/FreeRTOS/Demo/Common/Minimal\TimerDemo.c:1154:(.text._prvISRAutoReloadTimerCallback+0x9): relocation R_RL78_DIR16U_RAM out of RAM range: 1000900 is not in [1044224, 1048319]
ld.lld: error: C:/Renesas/GitHubDesktop/work/FreeRTOS/FreeRTOS/Demo/Common/Minimal\TimerDemo.c:1164:(.text._prvISROneShotTimerCallback+0x9): relocation R_RL78_DIR16U_RAM out of RAM range: 1000901 is not in [1044224, 1048319]
ld.lld: error: ../src\UART3.c:206:(.text._u_uart3_get_blk+0xD0): relocation R_RL78_DIR16U_RAM out of RAM range: 1023895 is not in [1044224, 1048319]
ld.lld: error: ../src\UART3.c:207:(.text._u_uart3_get_blk+0xD8): relocation R_RL78_DIR16U_RAM out of RAM range: 1023895 is not in [1044224, 1048319]
ld.lld: error: ../src\UART3.c:208:(.text._u_uart3_get_blk+0xDF): relocation R_RL78_DIR16U_RAM out of RAM range: 1023894 is not in [1044224, 1048319]
ld.lld: error: ../src\UART3.c:239:(.text._u_uart3_callback_receivedata+0x38): relocation R_RL78_DIR16U_RAM out of RAM range: 1023894 is not in [1044224, 1048319]
ld.lld: error: ../src\UART3.c:243:(.text._u_uart3_callback_receivedata+0x3D): relocation R_RL78_DIR16U_RAM out of RAM range: 1023896 is not in [1044224, 1048319]
ld.lld: error: ../src\r_cg_serial_user.c:220:(.text._r_uart3_callback_error+0x9): relocation R_RL78_DIR16U_RAM out of RAM range: 1023900 is not in [1044224, 1048319]
Best regards,
NoMaY
Best answer
Dear NoMaY-san, The ld.lld linker is looking for the __data symbol to get the start of RAM. If it does not find this symbol, it will consider that the start of RAM is at 0xfef00. We have changed the start files and the default linker scripts to use double underscored prefixed symbols to avoid any conflicts with user defined symbols. In order to solve these errors, you need to make the following changes in the linker script: If your linker script is originally from GCC and it contains symbols _data and _end in the linker script. You can either: Option 1:Replace all instances of _data with __data and _end with __end inside the linker script and start files. Option 2:Add __data = .; at the start of the .data output section (or equivalent first section in RAM) and __end = .; at the end of the .bss output section (or equivalent last section in RAM) If _data and _end are not present, please add them according to the above explanation. Best Regards, The Open Source Tools Team
-
NoMaY-jp -
Hello Dumitru-san,
Thank you very much for your quick reply.
Now the program can be built and works well. But unfortunately LLVM-RL78 generates bigger program than GNURL78. In Renesas’ Japanese forum, there is an opinion that such biggerness might be caused by the lack of newlib nano.
LLVM-RL78:
llvm-size –format=berkeley “RTOSDemo.elf”
text data bss dec hex filename
76648 1652 23274 101574 18cc6 RTOSDemo.elfGNURL78:
rl78-elf-size –format=berkeley “RTOSDemo.elf”
text data bss dec hex filename
50292 330 23246 73868 1208c RTOSDemo.elfBest regards,
NoMaY -
Dear NoMaY-san,
The big difference in size you are seeing can be caused by the difference in the newlib library used.
We will have newlib nano available for use in the next release (both pre-build and project build).If you can share the RTOSDemo project with us, we can check what the size would be if using newlib nano.
Thank you for your feedback. We really appreciate your observations and findings.
Best Regards,
The Open Source Tools Team -
NoMaY-jp -
Dear Dumitru-san,
Thank you for the proposal.
Can you clone repository from the GitHub (by Git, GitHubDesktop, or something else)? If so, I will inform the url of my repositories. If not, I will prepare a zip file containig source files and project files.
Best regards,
NoMaY -
Dear NoMaY-san,
Thank you – an URL of the repository would work for us. Alternatively, we can also accept ZIP files if you submit a new ticket through the internal support system.
__
Best regards,
The Open Source Tools Team -
NoMaY-jp -
Dear Dumitru-san,
Please do the following steps. (Sorry for several steps due to using submodule by upstream FreeRTOS repository.)
(1) Clone my repository – a fork of FreeRTOS (FreeRTOS Demo)
https://github.com/NoMaY-jp/FreeRTOS
(2) Clone my repository – a fork of FreeRTOS Kernel
https://github.com/NoMaY-jp/FreeRTOS-Kernel
(3) Remove the following files and folders in (1)
FreeRTOS/FreeRTOS/Source/*.* other than .git and .github/
(4) Copy the following files and folders in (2) to the following folder in (1) (or create symbolic links using Windows’ MKLINK command)
FROM: files and folders
FreeRTOS-Kernel/FreeRTOS-Kernel/*.* other than .git/ and .github/
TO: folder
FreeRTOS/FreeRTOS/Source/
(5) Import project (both projects have the same project name, so only one project can be imported at the same time)
LLVM-RL78:
FreeRTOS/FreeRTOS/Demo/RL78_RL78G14_FPB_LLVM_e2studio
GNURL78:
FreeRTOS/FreeRTOS/Demo/RL78_RL78G14_FPB_GCC_e2studio
Best regards,
NoMaY -
Dear NoMaY-san,
We can confirm that the big difference in size you are seeing is due to the use of newlib-nano for the GCC RL78 project.
We compiled and linked a newlib-nano version of newlib for the LLVM RL78 and got the following results:
llvm-size –format=berkeley “RTOSDemo.elf”
text data bss dec hex filename
45272 312 23246 68830 10cde RTOSDemo.elfAs mentioned before, newlib-nano(Pre-built and Project build) will be available in the next release.
Best Regards,
The Open Source Tools Team -
NoMaY-jp -
Dear Dumitru-san,
Thank you very much for the information.
I understand that the LLVM-RL78’s code with newlib nano will be 10% smaller than GNURL78’s code.
LLVM-RL78: (using newlib nano for next release)
llvm-size -format=berkeley “RTOSDemo.elf”
text data bss dec hex filename
45272 312 23246 68830 10cde RTOSDemo.elfGNURL78: (using already released newlib nano)
rl78-elf-size -format=berkeley “RTOSDemo.elf”
text data bss dec hex filename
50292 330 23246 73868 1208c RTOSDemo.elfBest regards,
NoMaY
