The issue was that the "Exclude" is remembered on IAR with each project config. I had to change it in ALL the configs - debug, release, etc. Thanks lc
↧
Forum Post: RE: error initializing fault tolerant file system
↧
Forum Post: RX231 to AWS
Hello everyone! I have bought a Renesas RX-231 board in order to explore the Renesas Sandbox supported by Medium One. The example the board has is very good, it works well. I would like to know if there is a firmware to connect the board to Amazon Web Services. At the same time, I would like to connect the RX-231 to the Synergy Enterprise Cloud Toolbox Dashboard, which is quite different from the Renesas IoT Sandbox. If there is someone who can guide me on this issue I would really appreciate it. Thanks in advance. JM Orona
↧
↧
Forum Post: RE: i2c wires connection
Hi adboc, I'm sorry my delay to reply but i'm ussing SSP version 1.3. When you say the application should exit this loof after some time , how long do you think it should take to exit the loop ? regards, Phillipe
↧
Forum Post: RE: how can the data flash be excluded from erase by E2 debugger RL78/G13
Hi @nicholas, Please experiment passing -ueraseRom=0 as parameter to the e2-server-gdb before invocating it.
↧
Forum Post: RE: how can the data flash be excluded from erase by E2 debugger RL78/G13
Hi @nicholas, Please experiment passing -ueraseRom=0 as parameter to the e2-server-gdb before invocating it. By default, a Debug Configuration has this option enabled. It can be found here: Debugger - Connection Settings - Erase Flash ROM When Starting Disable this option within e² studio debug configurations in order to prevent the E1 Debugger to erase Data Flash contents between two debug sessions. It would be the same as passing the parameter -ueraseRom=0 to the e2-gdb-server.exe, although the IDE's checkbox option is mandatory for controlling this specific option.
↧
↧
Forum Post: RE: Support multiple USB drives (Mass Storage)
Thank you adboc!
↧
Forum Post: RE: \DebugComp\renesas_cc_converter.exe removed from E2studio 6.2.0: is there a replacement?
Hi @PB, The referred executable has been moved in this new release. Please search for the DWARF conversion utility on the following paths: \Utilities\ccrl\renesas_cc_converter.exe \Utilities\ccrx\renesas_cc_converter.exe The integrated toolchains for these results are: CC-RL v1.0.6 and CC-RX v2.0.7
↧
Forum Post: PK-S5D9 code flash locked
Hi, I've been playing around with PK-S5D9 evalboard trying to learn Synergy platform. I was using SSP 1.4.0 with IAR. Everything was working fine, I was able to upload blink and initial example code without a problem. I've started to play around with placing printf() in blink example and reading the output via SWO following 'debugging with IAR' appnote. At some point MCU has stopped to accept new code downloads. IAR complained that flashloader has returned an error. I've tried to reboot my PC but problem persisted. Then I tried to do full flash erase by going to JLink commander and issuing 'erase' command it returned following status: J-Link>erase Erasing device (R7FS5D97E)... J-Link: Flash download: Only internal flash banks will be erased. To enable erasing of other flash banks like QSPI or CFI, it needs to be enabled via "exec EnableEraseAllFlashBanks" J-Link: Flash download: Total time needed: 0.069s (Prepare: 0.064s, Compare: 0.000s, Erase: 0.001s, Program: 0.000s, Verify: 0.000s, Restore: 0.003s) ****** Error: Failed to erase sectors 0 @ address 0x00000000 (erase error) J-Link: Flash download: Total time needed: 0.067s (Prepare: 0.062s, Compare: 0.000s, Erase: 0.001s, Program: 0.000s, Verify: 0.000s, Restore: 0.004s) ERROR: Erase returned with error code -5. Then I've tried to use Renesas Flash Programmer V3.04. I was able to connect to the MCU and download its contents but each time I try to program and or erase code flash i get: Error(E100000E): A protection error occurred in the device. (Response 12:DA) I can program/erase data flash and config flash but if I touch code segment MCU just disconnects. So I have following questions: 1. What I could've mess up? I don't recall touching anything related to flash/MCU protection settings. My code was basic blink generated by SSC with couple printfs in it. 2. How to perform full chip erase to unlock code flash and be able to continue my work? Nordic MCUs I'm more familiar with have 'magic' JLink script that does that. Googling I've found something similar for Synergy s7g2 https://renesasrulz.com/synergy/f/synergy---forum/7546/code-flash-erase-issue?pi5277=1&pi5273=2 Could someone point me to a version for s5d9? Thanks, ML
↧
Forum Post: RE: What are the steps to migrate from SSP 1.x to 1.x ?
Hi Jmax604, According to e2 Studio 6.2.0 Release Notes (section 2.2), you should change SSP version in BSP, regenerate project content and rebuild the project. Regards, adboc
↧
↧
Forum Post: RE: Merging Synergy Projects
Hi Jmax604, Copying stacks between threads of the same project is currently supported, but not across separate projects. However you might be interested in export/import function that is described in e2 Studio 5.4.0.018 release notes (section 2.2). Regards, adboc
↧
Forum Post: RE: i2c wires connection
Hi Phillipe, It depends on clock settings (ICMR1.CKS na PCKLB frequency), according to section 36.12.1 of the S7G2 User's Manual, the internal counter can be configured as 14- or 16-bit. In master mode, the RIIC driver configures it as 14-bit counter, it should exit the loop after 2^14 cycles of the configured IIC clock. Regards, adboc
↧
Forum Post: [RCar-H3]Can I know what are the audio codecs supported in R-Car H3?
I need information on the audio codecs supported by R-Car H3. We are using Android O as operating system. Also Does RCar-H3 support VP6 decoding?
↧
Forum Post: RE: PK-S5D9 code flash locked
It sounds like the Flash Access Window has been set some how. If you fire up jlink commander, and dump the memory contents at 0x0100A160 using the command "mem32 0x0100A160,8" if it isn't all 0xFFFFFFFF then the Flash Access Window has been set:- ROMTbl[0][6]: E0042000, CID: B105900D, PID: 002BB908 CSTF ROMTbl[0][7]: E0043000, CID: B105900D, PID: 001BB961 TMC ROMTbl[0][8]: E0044000, CID: B105F00D, PID: 001BB101 TSG Cortex-M4 identified. J-Link>mem32 0x0100A160, 4 0100A160 = FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF J-Link> Above is my S5D9-PK board, with the FAW as it should be, all 0xFFFFFFFF. To erase the FAW, run the attached script, e.g. :- jlink -commanderscript S5_Flash_access_window_clear.jlink if the script is successful, it should show :- 0100A150 = FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 0100A160 = FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF Script processing completed. (Please visit the site to view this file)
↧
↧
Forum Post: RE: I2C problem with S3A1 and SSP v1.3.3 ?
Hi Dave and thank you, your code resolved my problem !.
↧
Forum Post: RE: Using SFMA0 to read/write SPI RAM
Hi JB, I studied this pdf "70_SFMA_Driver_Rev.0.54_e.pdf" but I don't find about how can I set the SFMA for RAM and how does it reading/writing the RAM directly? BR, Frank
↧
Forum Post: RE: PK-S5D9 code flash locked
Thanks, the script solved my problem. Judging by contents of FWAMON register: FAWMON 0x87FF87DF ReadOnly BTFLG 1 ReadOnly FAWE 0x7FF ReadOnly FSPR 1 ReadOnly FAWS 0x7DF ReadOnly FAWS bits were set. How this could happen in simple blink + printf program? Is there a gui setting I might have accidentally set? I don't remember touching anything flash related.
↧
Forum Post: RE: Helpers for converting NXD_ADDRESS to strings and vice versa?
Thank you adboc for your response. Regards, Franck
↧
↧
Forum Post: third part library integration error
Hello All, My project consist of bootloader and application build on RL78 - G13 controller. Bootloader starts from 0000H and Application starts from 2000H. This project works fine, but when the third party library is added, i get following error : Can some help to know what could be the probable cause for this error
↧
Forum Post: Linker error with stdlib and GNURX
e2Studio 6.2.0 GNURX 4.8.4.201801 Hi all, I am facing problems at linking time on my e2Studio project (target RX65). I seem to have trouble using stdlib : rx-elf-g++ -O0 -ffunction-sections -fdata-sections -g2 -mcpu=rx64m -misa=v2 -mlittle-endian-data -nofpu -o "EOHifiv2.elf" -Wl,--start-group -lstdc++ -lEOHifiv2 -lgcc -Wl,--end-group ./task/taskFreeRtos.o ./src/EOHifiv2.o ./src/identFirmware.o ./rtos/Source/portable/MemMang/heap_3.o ./rtos/Source/portable/GCC/RX600v2/port.o ./rtos/Source/croutine.o ./rtos/Source/event_groups.o ./rtos/Source/list.o ./rtos/Source/queue.o ./rtos/Source/stream_buffer.o ./rtos/Source/tasks.o ./rtos/Source/timers.o ./renesas/r_flash_rx/r_flash_rx/src/flash_type_4/r_flash_type4.o ./renesas/r_flash_rx/r_flash_rx/src/r_flash_fcu.o ./renesas/r_flash_rx/r_flash_rx/src/r_flash_group.o ./renesas/r_flash_rx/r_flash_rx/src/r_flash_rx.o ./renesas/cgc_hoco.o ./renesas/cgc_xtal.o ./renesas/hwinit.o ./renesas/inthandler.o ./renesas/lowlvl.o ./renesas/r_init_non_existent_port.o ./renesas/start.o ./renesas/vects.o ./renesas/watchDog.o ./hard/serial/MessageSerial.o ./hard/serial/SerialManager.o ./hard/serial/System.o ./hard/radio/RemoteContol.o ./hard/radio/SerialSpiCmdRadio.o ./hard/radio/SerialSpiDataRadio.o ./hard/radio/sx1232.o ./hard/leds.o ./hard/relays.o ./fsm/Event.o ./bootloader/bootloaderMain.o ./alloc/tiny-malloc.o libEOHifiv2.a -T "C:/Users/Administrateur/e2_studio/workspace/EOHifiv2/renesas/linker_script.ld" -L"C:\Users\Administrateur\e2_studio\workspace\EOHifiv2\HardwareDebug" -Wl,--start-group -lEOHifiv2 -lgcc -lstdc++ -Wl,--end-group -nostartfiles -Wl,--gc-sections c:/program files (x86)/gcc for renesas rx 4.8.4.201801-gnurx-elf/rx-elf/rx-elf/bin/../lib/gcc/rx-elf/4.8.4.201801-GNURX/../../../../rx-elf/lib/no-fpu-libs/rxv2\libc.a(lib_a-closer.o): In function `__close_r': (.text._close_r+0x10): warning: _close is not implemented and will always fail c:/program files (x86)/gcc for renesas rx 4.8.4.201801-gnurx-elf/rx-elf/rx-elf/bin/../lib/gcc/rx-elf/4.8.4.201801-GNURX/../../../../rx-elf/lib/no-fpu-libs/rxv2\libc.a(lib_a-fstatr.o): In function `__fstat_r': (.text._fstat_r+0x12): warning: _fstat is not implemented and will always fail c:/program files (x86)/gcc for renesas rx 4.8.4.201801-gnurx-elf/rx-elf/rx-elf/bin/../lib/gcc/rx-elf/4.8.4.201801-GNURX/../../../../rx-elf/lib/no-fpu-libs/rxv2\libc.a(lib_a-isattyr.o): In function `__isatty_r': (.text._isatty_r+0x10): warning: _isatty is not implemented and will always fail c:/program files (x86)/gcc for renesas rx 4.8.4.201801-gnurx-elf/rx-elf/rx-elf/bin/../lib/gcc/rx-elf/4.8.4.201801-GNURX/../../../../rx-elf/lib/no-fpu-libs/rxv2\libc.a(lib_a-lseekr.o): In function `__lseek_r': (.text._lseek_r+0x14): warning: _lseek is not implemented and will always fail c:/program files (x86)/gcc for renesas rx 4.8.4.201801-gnurx-elf/rx-elf/rx-elf/bin/../lib/gcc/rx-elf/4.8.4.201801-GNURX/../../../../rx-elf/lib/no-fpu-libs/rxv2\libc.a(lib_a-readr.o): In function `__read_r': (.text._read_r+0x14): warning: _read is not implemented and will always fail c:/program files (x86)/gcc for renesas rx 4.8.4.201801-gnurx-elf/rx-elf/rx-elf/bin/../lib/gcc/rx-elf/4.8.4.201801-GNURX/../../../../rx-elf/lib/no-fpu-libs/rxv2\libstdc++.a(pure.o): In function `___cxa_pure_virtual': (.text.__cxa_pure_virtual+0xc): warning: _write is not implemented and will always fail Note that compilng works when commenting out standard libs. The following thread implies that I am linking stdC before stdC++ instead of the other way round : https://renesasrulz.com/rx/f/rx---forum/2480/_rx_fini/8303 which leads to another problem : I can't modify this order. This has been set by e2Studio when creating the project and now the listbox are greyed and can't be changed. Does anybody have any idea ? Thanks for your replies
↧
Forum Post: RE: how can the data flash be excluded from erase by E2 debugger RL78/G13
Thanks but this will also prevent the code flash to be updated. I want to develop my code (flashing / debugging ) but not touch the data-flash. correct me if I am wrong.
↧