Open Source Tools for Renesas’s reputation | Open Source Tools for Renesas

Open Source Tools for Renesas’s reputation

Open Source Tools for Renesas 825 Rep.

Follow

Open Source Tools for Renesas's reputation

Total 825

0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

+1

August 2, 2024 Commented Hello, The linker script documentation (https://sourceware.org/binutils/docs/ld/Location-Counter.html) mentions: "Note: . actually refers to the byte offset from the start of the current containing object. Normally this is the SECTIONS statement, whose start address is 0, hence . can be used as an absolute address. If . is used inside a section description however, it refers to the byte offset from the start of that section, not an absolute address." According to the provided linkerscript _idata is declared inside .idata, resulting in a relative offset which in this case will be 0 since .idata is has no input sections. You need to declare _idata outside the .idata section descriptor to make sure it's an absolute address. __ Best regards, The Open Source Tools Team

+1

July 25, 2024 Commented Hello, Thank you for reaching out to us! At the first look, it seems that the .textf section is not allocated (or is incorrectly allocated) in the linker script. In order to be able to help you, please provide the following: - toolchain and e2 Studio version used - compile/link options - linker script - map file - the full project or a minimally-reproducible example (if possible) If you wish to share the file(s) privately, please open up a support ticket and attach them there. Please let us know if we can be of further assistance. __ Best regards, The Open Source Tools Team

+10

July 25, 2024 Answered Can “GNUH8 v11.02 Windows Toolchain (ELF)” be made available?

+1

July 25, 2024 Commented Hello, We would like to remind you that we cannot help you if you do not attach the requested files (map, start.S) or a minimally-reproducible example. If you wish to share the file(s) privately, please open up a support ticket and attach them there. Best regards, The Open Source Tools Team

+10

July 19, 2024 Answered Does LLVM-RL78 need the dedicated version of FDL library?

+10

July 19, 2024 Answered dataflash library of LLVM for RL78

+1

July 18, 2024 Commented Hello, 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 Family RL78 Family Data Flash Library Type04 User's Manual in Japan and Other Asian Countries (Japanese Release) Rev.1.10 RL78 Family Data Flash Library Type04 Package Ver.3.00 Release Note in Japan and Other Asian Countries (Japanese Release) - FSL Type01 (LLVM compiler support version) Parent page Flash Self Programming Library Type01 Package Ver.4.00 for the RL78 Family RL78 Family Flash Self Programming Library Type01 User's Manual in Japan and Other Asian Countries (Japanese Release) Rev.1.10 RL78 Family Flash Self-Programming Library Type01 Package Ver.4.00 Release Note in Japan and Other Asian Countries (Japanese Release) - EEL Pack02 (LLVM compiler support version): EEPROM Emulation Library Pack02 Package Ver.3.00 for RL78 Family | Renesas Please let us know if we can be of any further assistance. __ Best regards, The Open Source Tools Team

+1

July 18, 2024 Commented Hello, Please consider the following: test.c: #include int main() { int x = 12; __builtin_rx_brk(); x = 13; assert(x == 12); return 0; } The commands below illustrate both approaches: rx-elf-gcc -msim test.c -g rx-elf-gdb a.out -ex "target sim" -ex "load" -ex "br abort" -ex "run" -ex "bt" -ex "c" -ex "bt" Explanation: After creating the executable from the source file, we launch a debug session and insert a breakpoint into the abort() function. When we begin execution, the debugger will first stop at the BRK instruction. If we issue the continue command, the debugger stops at the abort() breakpoint. In both cases, the program state can be inspected: in our example we display the call stack. Please elaborate further if this behavior is not what you are looking for. __ Best regards, The Open Source Tools Team

+1

July 18, 2024 Commented Hello, 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 Family RL78 Family Data Flash Library Type04 User's Manual in Japan and Other Asian Countries (Japanese Release) Rev.1.10 RL78 Family Data Flash Library Type04 Package Ver.3.00 Release Note in Japan and Other Asian Countries (Japanese Release) - FSL Type01 (LLVM compiler support version) Parent page Flash Self Programming Library Type01 Package Ver.4.00 for the RL78 Family RL78 Family Flash Self Programming Library Type01 User's Manual in Japan and Other Asian Countries (Japanese Release) Rev.1.10 RL78 Family Flash Self-Programming Library Type01 Package Ver.4.00 Release Note in Japan and Other Asian Countries (Japanese Release) - EEL Pack02 (LLVM compiler support version): EEPROM Emulation Library Pack02 Package Ver.3.00 for RL78 Family | Renesas Please let us know if we can be of any further assistance. __ Best regards, The Open Source Tools Team

+10

July 17, 2024 Answered Can a GDB breakpoint be set programmatically?

+5

July 9, 2024 Up vote answer Equivalent to IAR’s __no_init variable qualifier

+10

July 9, 2024 Answered Equivalent to IAR’s __no_init variable qualifier

+10

July 5, 2024 Answered Linker trashes initialized data at start-up?

+1

July 2, 2024 Commented Hello, Thank you for reaching out to us! Unfortunately we are not able to reproduce the issue. In order to aid our investigation, please attach the full-built e2 Studio project for both of the mentioned cases. You may also share the code privately with us by opening a dedicated support ticket, where you can attach it. __ Best regards, The Open Source Tools Team

+1

June 11, 2024 Commented Hello, Indeed, these options are useful when developers write the time critical functions in assembly, having the assurance that the reserved registers won't be allocated in other parts of the application. Avoiding fast_interrupt functions written in C, either by using normal interrupts or by writing them in assembly, should keep the mint-registers unmodified. Please let us know if we can be of further assistance. __ Best regards, The Open Source Tools Team

+1

June 11, 2024 Commented Hello, A fix was included regarding this issue in the GCC for Renesas RX 8.3.0.202405 release. When using -mint-register=2 -msmall-data-limit=512, RX 8.3.0.202405 produces the following instructions: Source code: #include "iodefines.h" unsigned char Buffer[32]; unsigned char* pHead; unsigned char* pTail; volatile unsigned char Data; void ServiceFastRXI1(void) __attribute__ ((fast_interrupt,optimize("-O2"))); void ServiceFastRXI1(void) { *pHead++ = SCI1.RDR; *pTail++ = Data++; if(&Buffer[32] == pHead) { pTail = pHead = &Buffer[0]; } ICU.IER[15].BIT.IEN6 = 1; return; } void main(void) { int i; pTail = pHead = &Buffer[0]; i = (int)&ServiceFastRXI1; return; } Compiled output: .file "test.c" .section P,"ax" .comm _Buffer,32,1 .comm _pHead,4,4 .comm _pTail,4,4 .comm _Data,1,1 .global _ServiceFastRXI1 .type _ServiceFastRXI1, @function _ServiceFastRXI1: ; Note: Fast Interrupt Handler pushm r1-r5 mov.L #_pHead, r5 mov.L [r5], r3 mov.L #_Data, r1 mov.L #_pTail, r4 add #1, r3, r2 mov.L r2, [r5] mov.L #0x8a020, r2 mov.B 5[r2], r2 mov.B r2, [r3] mov.B [r1], r2 mov.L [r4], r3 add #1, r2, r13 add #1, r3, r12 mov.B r13, [r1] mov.L r12, [r4] mov.B r2, [r3] mov.L [r5], r3 cmp #_Buffer+32, r3 beq .L5 mov.L #0x87000, r5 bset #6, 527[r5].B popm r1-r5 rtfi .L5: mov.L #_Buffer, [r5] mov.L #_Buffer, [r4] mov.L #0x87000, r5 bset #6, 527[r5].B popm r1-r5 rtfi .size _ServiceFastRXI1, .-_ServiceFastRXI1 .global _main .type _main, @function _main: push.l r10 add #-4, r0, r10 mov.L r10, r0 mov.L #_pHead, r5 mov.L #_Buffer, [r5] mov.L #_pHead, r5 mov.L [r5], r4 mov.L #_pTail, r5 mov.L r4, [r5] mov.L #_ServiceFastRXI1, [r10] nop rtsd #8, r10-r10 .size _main, .-_main .ident "GCC: (GCC_Build_8c9e6e87e) 8.3.0.202405-GNURX 20190222" Due to mint-registers being set to 2, GCC is free to use/allocate/trash r13 and r12 in the fast interrupt function, without saving and restoring them. Due to msmall-data-limit > 0, GCC will not allocate r11 anywhere. If you encountered a different behavior, please let us know. Best regards, The Open Source Tools Team

+1

May 29, 2024 Commented Hello NoMaY-san, We are pleased to inform you that the issue should be fixed in the GCC for Renesas RX 8.3.0.202405 release. __ Best regards, The Open Source Tools Team

+10

May 25, 2024 Answered I would like to know the difference between GCC and LLVM. Will the GCC port code support the LLVM toolchain as well?

+2

May 22, 2024 Selected answer When I create a new project in e2studio using the GCC compiler, I see a “deprecated” warning. How can I resolve this?

+10

May 22, 2024 Answered When I create a new project in e2studio using the GCC compiler, I see a “deprecated” warning. How can I resolve this?

« Previous 1 2 3 4 5 … 10 11 12 Next »

Support