Error using example project (micro_ros_udp_freertos)

[web2543]

Hi, I tried to use example project " micro_ros_udp_freertos " When I Debug project . It show error in consloe:

Could someone help me solve this problem?

[Acuadros95]

Hi @web2543, let us replicate this problem and come back with feedback.

[web2543]

Hi @Acuadros95, I tried other demo project. "micro_ros_uart" work properly but this problem occur in "micro_ros_udp_threadX" . Maybe help you.

[Acuadros95]

I could not replicate this, lets try to find the problem:

• Which version of e2_studio are you using?
• Are you using the latest FSP version 3.5.0?
• Which branch of this repository are you building?

Could you copy (not on an image) the full debug report? I am looking for this part, just before the one you passed:

GDB Server for Renesas targets.
	Version 8.6.0.v20210906-115139 [d3ef8c54] (Sep 16 2021 13:13:04)


Starting server with the following options: 
        Raw options                : /home/username/.eclipse/com.renesas.platform_725534088/DebugComp//RA/e2-server-gdb -g SEGGERJLINKARM -t R7FA6M5BH -uSelect= USB -uJLinkSetting= "/home/username/workspace/Boards/renesas/micro_ros_renesas_demos/micro_ros_udp_freertos/micro_ros_udp_freertos Debug_Flat.jlink" -uLowPower= 0 -uInteface= SWD -uIfSpeed= 4000 -uNoReset= 1 -uResetPreRun= 1 -uResetCon= 1 -uResetBefDownload= 1 -uReleaseCM3= 0 -uSWOcoreClock= 0 -uresetOnReload= 1 -n 0 -uFlashBp= 1 -uSimulation= 0 -ueraseRomOnDownload= 0 -ueraseDataRomOnDownload= 0 -uOSRestriction= 0 -uProgReWriteIRom= 0 -uCPUFrequency= 0 -uCECycle= 1 -uMemRegion= 0x20000000:0x7E000:RAM:s -uMemRegion= 0x2007E000:0x0:RAM:c -uMemRegion= 0x2007E000:0x2000:RAM:n -uMemRegion= 0x00000000:0x200000:FLASH:s -uMemRegion= 0x00200000:0x0:FLASH:c -uMemRegion= 0x00200000:0x0:FLASH:n -uMemRegion= 0x08000000:0x2000:DATA_FLASH:s -uMemRegion= 0x08002000:0x0:DATA_FLASH:n -uMemRegion= 0x0100A100:0x80:OPTION_SETTING:s -uMemRegion= 0x0100A180:0x80:OPTION_SETTING:n -uMemRegion= 0x0100A200:0xCC:OPTION_SETTING_S:s -uMemRegion= 0x0100A2CC:0x34:OPTION_SETTING_S:n -uMemRegion= 0x00000000:0x0:ID_CODE:s -uMemRegion= 0x00000000:0x0:ID_CODE:n -uMemRegion= 0x90000000:0x0:SDRAM:s -uMemRegion= 0x90000000:0x0:SDRAM:n -uMemRegion= 0x60000000:0x0:QSPI_FLASH:s -uMemRegion= 0x60000000:0x4000000:QSPI_FLASH:n -uMemRegion= 0x68000000:0x0:OSPI_DEVICE_0:s -uMemRegion= 0x68000000:0x8000000:OSPI_DEVICE_0:n -uMemRegion= 0x70000000:0x0:OSPI_DEVICE_1:s -uMemRegion= 0x70000000:0x10000000:OSPI_DEVICE_1:n -l -uCore= SINGLE_CORE|enabled|1|main -uSyncMode= async -uFirstGDB= main --english
Using J-Link version V7.56b - /home/username/.eclipse/com.renesas.platform_725534088/DebugComp/RA/ARM/Segger_v7.56.2/libjlinkarm.so

Connecting to R7FA6M5BH, ARM Target
        ...

[web2543]

• I download e2studio for Linux with FSP version 3.5.0 (AppImage) from this github repository and install on Ubuntu 20.04.3LTS.

• I use default branch of micro_ros_renesas_demos(main) and micro_ros_renesas2estudio_component(foxy) to build project.

This full debug report:

GDB Server for Renesas targets.
	Version 8.6.0.v20210906-115139 [d3ef8c54] (Sep 16 2021 13:13:04)


Starting server with the following options: 
        Raw options                : /home/***/.eclipse/com.renesas.platform_503796918/DebugComp//RA/e2-server-gdb -g SEGGERJLINKARM -t R7FA6M5BH -uSelect= USB -uJLinkSetting= "/home/***/Downloads/micro_ros_renesas_demos-main/micro_ros_udp_freertos/micro_ros_udp_freertos Debug_Flat.jlink" -uLowPower= 0 -uInteface= SWD -uIfSpeed= 4000 -uNoReset= 1 -uResetPreRun= 1 -uResetCon= 1 -uResetBefDownload= 1 -uReleaseCM3= 0 -uSWOcoreClock= 0 -uresetOnReload= 1 -n 0 -uFlashBp= 1 -uSimulation= 0 -ueraseRomOnDownload= 0 -ueraseDataRomOnDownload= 0 -uOSRestriction= 0 -uProgReWriteIRom= 0 -uCPUFrequency= 0 -uCECycle= 1 -uMemRegion= 0x20000000:0x7E000:RAM:s -uMemRegion= 0x2007E000:0x0:RAM:c -uMemRegion= 0x2007E000:0x2000:RAM:n -uMemRegion= 0x00000000:0x200000:FLASH:s -uMemRegion= 0x00200000:0x0:FLASH:c -uMemRegion= 0x00200000:0x0:FLASH:n -uMemRegion= 0x08000000:0x2000:DATA_FLASH:s -uMemRegion= 0x08002000:0x0:DATA_FLASH:n -uMemRegion= 0x0100A100:0x80:OPTION_SETTING:s -uMemRegion= 0x0100A180:0x80:OPTION_SETTING:n -uMemRegion= 0x0100A200:0xCC:OPTION_SETTING_S:s -uMemRegion= 0x0100A2CC:0x34:OPTION_SETTING_S:n -uMemRegion= 0x00000000:0x0:ID_CODE:s -uMemRegion= 0x00000000:0x0:ID_CODE:n -uMemRegion= 0x90000000:0x0:SDRAM:s -uMemRegion= 0x90000000:0x0:SDRAM:n -uMemRegion= 0x60000000:0x0:QSPI_FLASH:s -uMemRegion= 0x60000000:0x4000000:QSPI_FLASH:n -uMemRegion= 0x68000000:0x0:OSPI_DEVICE_0:s -uMemRegion= 0x68000000:0x8000000:OSPI_DEVICE_0:n -uMemRegion= 0x70000000:0x0:OSPI_DEVICE_1:s -uMemRegion= 0x70000000:0x10000000:OSPI_DEVICE_1:n -l -uCore= SINGLE_CORE|enabled|1|main -uSyncMode= async -uFirstGDB= main --english
Using J-Link version V7.56b - /home/***/.eclipse/com.renesas.platform_503796918/DebugComp/RA/ARM/Segger_v7.56.2/libjlinkarm.so

Connecting to R7FA6M5BH, ARM Target
        GDBServer endian           : little
        Target power from emulator : Off 
Starting target connection
RA TrustZone memory boundaries successfully updated.

Current status of the RA TrustZone device
	DLM state	: Secure Software Development (SSD)
	Debug level	: 2
	Secure/NSC memory partition size	: 
	-	Code Flash Secure	(kB)	: 2048
	-	Code Flash NSC		(kB)	: 0
	-	Data Flash Secure	(kB)	: 8
	-	SRAM Secure		(kB)	: 504
	-	SRAM NSC		(kB)	: 0

Finished target connection
GDB: 45901
Target connection status - OK
Target connection status - OK
Starting download
Option Function Select, writing to address 0x0100a100 with data ffffffffffffffffffffffffffffffff...
Option Function Select, writing to address 0x0100a200 with data fffdffffffffffffffffffffffffffff...
GDB action 'write register', has failed with error code, 0xffffffff
Disconnected from the Target Debugger.

[Acuadros95]

After looking into this, it looks like an internal configuration problem of the board.

You can check this forum post which tries to solve your same problem: https://renesasrulz.com/ra/f/forum/19063/can-t-flash-specific-project-on-ra6m3-board, please give it a read and try the given solutions.

Anyway, we are going to ask for support for this problem.

[web2543]

I found this problem for a while but I'm too busy to close this issue.

This link will provide information to others. https://renesasrulz.com/ra/f/forum/19033/e2studio-debugger-not-started/63008#63008

Now, I contact Renesas support.
Thank you for supporting me. @Acuadros95

[Acuadros95]

@web2543 Does this mean that your evaluation kit was faulty? Or did you found and solve the problem?

[Acuadros95]

@web2543 Hi again! After some communication with Segger this issue was solved:

Issue was the FW of the J-Link OB used on those kits. A patch version (v7.60d) of the JLink software has been released today with the fix in the release notes:

J-Link-OB-S124
1.     If bigger chunks of memory were read / written (>= 8 KB) the USB communication could break down and the OB has reset itself. Fixed.

So, please download and install this update and try flashing the device with JLink-Lite from this version which should trigger a firmware update.

https://www.segger.com/downloads/jlink/

[web2543]

Thank you @Acuadros95. I updated J-Link OB on evaluation kit and it work !!!!!!