Blog Archives
Does gdb for RX support setting breakpoints with command line?
Hello, Thank you for reaching out to us! GDB for Renesas RX does support the command line option to create breakpoints. Consider the following test case, which uses the GDB that comes with the Renesas Debug VS Code extension: test.c:
Anyone use clangd (VS Code extension) with gcc for RX?
Hello, Thank you for reaching out to us! Unfortunately, this support platform is dedicated to compilers used with various Renesas targets, platforms and devices. For this reason, our information about the VSCode extension and how it uses clangd is limited.
Can “GNUH8 v11.02 Windows Toolchain (ELF)” be made available?
Hello, Thank you for reaching out to us! We are very sorry, but the requested version is not available to us either. Being a legacy toolchain, all we can do is to recommend the GCC H8 Toolchain v11.02 for Linux,
Does LLVM-RL78 need the dedicated version of FDL library?
(Reposting here with full URLs.) We would like to let you know that the following data/code flash libraries are available and compatible with LLVM RL78: – FDL Type04 (LLVM compiler support version) Parent page Data Flash Library Type04 Package Ver.3.00 for the RL78
dataflash library of LLVM for RL78
(Reposting here with the full URLs.) The following data/code flash libraries are available and compatible with LLVM RL78: – FDL Type04 (LLVM compiler support version) Parent page Data Flash Library Type04 Package Ver.3.00 for the RL78 Family RL78 Family Data Flash Library Type04
Can a GDB breakpoint be set programmatically?
Hello, Thank you for reaching out to us! It depends on the target, but usually a failed assert will call the abort function. GDB users can create a breakpoint in the abort function to catch failed asserts by executing the
Equivalent to IAR’s __no_init variable qualifier
Hello, Thank you for reaching out to us! NOLOAD works regardless of the region type. The behavior of the IAR __no_init extension can be replicated by explicitly placing the variable into a special section, and modifying the linker script accordingly:
Linker trashes initialized data at start-up?
Hello, Based on the description of the bug and the attached linker file, the cause seems to be a possible mismatch between the size and address range of the source and destination (FLASH/RAM) memory regions, probably due to alignment issues.
I would like to know the difference between GCC and LLVM. Will the GCC port code support the LLVM toolchain as well?
Hello, Thank you for reaching out to us! We are not aware of any information regarding the support of the LLVM RL78 toolchain by the FreeRTOS project. Our recommendation is to contact their customer support about this issue. Given the
When I create a new project in e2studio using the GCC compiler, I see a “deprecated” warning. How can I resolve this?
Hello, Thank you for reaching out to us! We would like to inform you that the GCC RL78 toolchains are no longer being updated and will not be in the future. This is why you see the warning in e2studio

日本語