Open Source Tools for Renesas’s ポイント | Open Source Tools for Renesas

Open Source Tools for Renesas’s ポイント

Open Source Tools for Renesas 822 ポイント.

フォロー

Open Source Tools for Renesas's ポイント

Total 822

0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0

+1

7月 26, 2022 Commented Hi there, CC-RX and GCC RX for the most part are compatible, however there are some key differences that may cause problems (defined macros, language extensions, directives, etc.) The migration guide included with the GCC RX toolchain may help you in resolving some of the compile issues you may be experiencing: /Doc/Renesas-GNURX Migration Guide In case you encounter further problems, please provide us with more information. Please let us know if we can be of further assistance. __ Best regards, The Open Source Tools Team

+1

7月 22, 2022 Commented Dear Ignasi, You can see the commands sent to rx-elf-gdb in the Console tab (same place where the gdb server output is shown), but you must switch it to the gdb traces output. There is a console icon on the right, with a dropdown. From the command line, you would first start the gdb server, explicitly specifying the port number: C:\Users\[[Username]]\.eclipse\com.renesas.platform_233474849\DebugComp\RX\ C:\Users\[[User]]\.eclipse\com.renesas.platform_233474849\DebugComp\RX\e2-server-gdb -p 63676 -g SIMULATOR <..other options, as seen in the gdb server Console tab..> Then you could start rx-elf-gdb: rx-elf-gdb –interpreter=mi2 < command_file.txt The command file would contain the commands as seen in the Console, GDB trace log: cd /rx_default_202202 set breakpoint pending on set detach-on-fork on set python print-stack none set print object on set print sevenbit-strings on set target-async on set pagination off set non-stop on set auto-solib-add on set step-mode off set breakpoint always-inserted on symbol-file \\Debug\\rx_default_202202.elf exec-file \\Debug\\rx_default_202202.elf info inferiors inferior 1 set remotetimeout 10 set tcp connect-timeout 30 target extended-remote-rx localhost:63676 load kill .... The gdb documentation is of general purpose. Please let us know if we can be of further assistance. __ Best regards, The Open Source Tools Team

+10

7月 19, 2022 Answered rx-elf-gdb/run manual/options

+1

5月 12, 2022 Commented Hello, Thank you for reaching out to us! At the moment we provide support only for GCC and LLVM. Questions pertaining to CC-RL can be answered by contacting the relevant support team at the following link: https://en-support.renesas.com/dashboard Users which do not have a license, should check out the RenesasRulz forum, available at: https://renesasrulz.com/ Please let us know if we can be of further assistance. __ Best regards, The Open Source Tools Team

+1

5月 9, 2022 Commented Hello, The development of the flash library for LLVM RL78 is under consideration, but at this moment we cannot offer a definite answer whether if, or when it will be available. Please let us know if we can be of any further assistance. __ Best regards, The Open Source Tools Team

+1

5月 3, 2022 Commented Hello, Thank you for reaching out to us! In order to be able to help with your request, could you please be more specific regarding the type of the library you are interested in? Best regards, The Open Source Tools Team

+5

2月 28, 2022 Up vote 回答 Creating a project from scratch for RX630 using e2 studio and GCC RX.

+10

2月 7, 2022 Answered Creating a project from scratch for RX630 using e2 studio and GCC RX.

+1

1月 29, 2022 Commented Hello, Thank you for reaching out to us. We received your inquiry and we are investigating the issue. We’ll get back to you about this as soon as possible. Best regards, The Open Source Tools Team

+1

12月 7, 2021 Commented Hello, We are sorry, but we will need to check your credentials for more information regarding this series of devices. Can you give us more details about you and the company you work for, please? Alternatively, you can submit this information through a support ticket on the platform. __ Best regards, The Open Source Tools Team

+1

12月 3, 2021 Commented Hello, Unfortunately, we are not yet able to reproduce this issue, even if we use the environment mentioned by you. Can you please send us the project with the problem for further investigation? If this is not possible, can we get a complete error log please? Best regards, The Open Source Tools Team

+10

11月 30, 2021 Answered File not found

+1

7月 20, 2021 Commented Dear customer, We are happy to report that this issue should be resolved in the new 10.0.0.202107 release of the LLVM for Renesas RL78 toolchain, present on our website for download at: https://llvm-gcc-renesas.com/rl78/rl78-download-toolchains/ If you have any further questions about the issue, please let us know. __ Thank you, The Open Source Tools Team

+10

7月 12, 2021 Answered LLVM Build?

+10

6月 30, 2021 Answered LLVM-RL78 clang ld.lld’s incorrect relocation address problem

+10

6月 30, 2021 Answered ソースコードの開示について

+10

6月 25, 2021 Answered GNU Gcc compiler

+1

6月 23, 2021 Commented Dear NoMaY-san, We have managed to reproduce the issue, thank you for bringing it to our attention. While we are working on a fix, a possible workaround could be changing the output sections for the functions present in portasm.S (and for any other in similar situation) from .lowtext.* to .text.* This change resulted in the correct detection of symbol reference in the assembly files, preventing their removal by the –gc-sections option. Please let us know if this workaround works for you. __ Best regards, The Open Source Tools Team

+1

6月 18, 2021 Commented Hello, Thank you for reaching out to us! We are aware of this typo, and we will have a fix prepared for this in the next release. Until then, as a workaround we suggest using the DCENT register instead of the DECNT one. We apologize for any inconvenience caused. __ Best regards, The Open Source Tools Team

+1

6月 14, 2021 Commented Dear NoMaY-san, Thank you for reporting this. We have managed to reproduce the issue and we are currently working towards solving it. The xor1 cy, a.7 instruction is a result of the compiler treating the comparison as a signed comparison. The mov1 cy, 0xffef8.2 instruction is considered mov1 cy, x.2, but as we have discussed before, this works for bank 0 only. __ Best regards, The Open Source Tools Team

« 前へ 1 2 3 4 5 6 7 8 … 10 11 12 次へ »

サポート