I am working on an RA6M3G device.
I tried to erase the chip using J-Flash Lite V7.92c but was unsuccessful.
I used Jlink Commander V7.92c but still failed.
SEGGER J-Link Commander V7.92c (Compiled Aug 30 2023 15:00:03)
DLL version V7.92c, compiled Aug 30 2023 14:58:23
Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-S124 compiled Jun 20 2023 17:09:11
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 06m 55s
USB speed mode: Full speed (12 MBit/s)
Type "connect" to establish a target connection, '?' for help
Please specify device / core. <Default>: R7FA6M3AH
Type '?' for selection dialog
Please specify target interface:
J) JTAG (Default)
Specify target interface speed [kHz]. <Default>: 4000 kHz
Device "R7FA6M3AH" selected.
Connecting to target via SWD
Identifying target device...
SWD selected. Executing JTAG -> SWD switching sequence...
DAP initialized successfully.
InitTarget() end - Took 11.2ms
Found SW-DP with ID 0x5BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP: Stopped AP scan as end of AP map has been reached
AP: AHB-AP (IDR: 0x24770011)
AP: APB-AP (IDR: 0x44770002)
Iterating through AP map to find AHB-AP to use
AP: Core found
AP: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
ROMTbl @ E00FF000
: E000E000 CID B105E00D PID 000BB00C SCS-M7
: E0001000 CID B105E00D PID 003BB002 DWT
: E0002000 CID B105E00D PID 002BB003 FPB
: E0000000 CID B105E00D PID 003BB001 ITM
: E0040000 CID B105900D PID 000BB9A1 TPIU
: E0041000 CID B105900D PID 000BB925 ETM
: E0042000 CID B105900D PID 002BB908 CSTF
: E0043000 CID B105900D PID 001BB961 TMC
: E0044000 CID B105F00D PID 001BB101 TSG
Zone: "Default" Description: Default access mode
No address range specified, 'Erase Chip' will be executed
'erase': Performing implicit reset & halt of MCU.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
T-bit of XPSR is 0 but should be 1. Changed to 1.
T-bit of XPSR is 0 but should be 1. Changed to 1.
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"
****** Error: Timeout while erasing sectors, RAMCode did not respond in time (PC = 0x1FFE040A, XPSR = 0x41000000, SP = 0x1FFE08C0)!
Failed to erase sectors.
J-Link: Flash download: Total time needed: 10.220s (Prepare: 0.161s, Compare: 0.000s, Erase: 10.006s, Program: 0.000s, Verify: 0.000s, Restore: 0.052s)
ERROR: Erase returned with error code -5.
Could you please help me check it and give me the solution?
Thanks for reaching out Renesas Community.
Can you try to initialize device back to factory default using Renesas Devision Partition Manager through e2studio, take a look below:
I think the problem is in your connection. Did you supply 3.3V externally on your VCC pin of your Segger Tool and your board?
Hello @nskrkmz ,
Because the RA6M3 device supports debugging on board, I using Micro USB to connect J10 (Board RA6M3) and PC.
If you want to check what I mean, you can disconnect the connection between PC and board and supply 3.3V externally and try your connection because segger tool can not supply 3.3V. Did you try download any software with your connection before?
I understand your mentions.
RA have 4 way to connect.
Please, inform us if you have successful initialization.
This is the result when I apply your solution
- Need to correct SWD instead of SCI or not?
- Need to use an external power supply or not?
Do you use your customized board with RA6M3 chip or the EK- RA6M3G ?
I use EK- RA6M3G.
Please, try to re-program your board with Renesas Flash Programmer and share with me a screenshot of the messages with specific error code you get.
I created the blinky project for ra6m3g and used RFP to flash.
Please, check the possible causes for your issue, below:
I checked the possible cause but was not successful.
I used 1 RA6M5 and ran Renesas Device Partition Manager/RFP. It's OK.
Is there any case of chip locked?
RTT Viewer still connects to the board normally.
If you have written data in Option Settinh Memory 0x400 in code flash, the only way to recover the flash is by trying the attached jlink script to erase the first block of code flash( as the Security MPU be enabled). If that doesn't work the device may be not recoverable.
This is log:
SEGGER J-Link Commander V7.82d (Compiled Nov 23 2022 16:10:38)link -CommanderScript RA6M3_Block_0_Erase.jlinkDLL version V7.82d, compiled Nov 23 2022 16:09:10
J-Link Command File read successfully.Processing script file...J-Link>Device R7FA6M3AHJ-Link connection not established yet but required for command.Connecting to J-Link via USB...O.K.Firmware: J-Link OB-S124 compiled Jun 20 2023 17:09:11Hardware version: V1.00J-Link uptime (since boot): 0d 00h 27m 21sS/N: 831334275USB speed mode: Full speed (12 MBit/s)VTref=3.300VJ-Link>si SWDSelecting SWD as current target interface.J-Link>speed 4000Selecting 4000 kHz as target interface speedJ-Link>connectDevice "R7FA6M3AH" selected.
Connecting to target via SWDFound SW-DP with ID 0x5BA02477Found SW-DP with ID 0x5BA02477DPIDR: 0x5BA02477CoreSight SoC-400 or earlierScanning AP map to find all available APsAP: Stopped AP scan as end of AP map has been reachedAP: AHB-AP (IDR: 0x24770011)AP: APB-AP (IDR: 0x44770002)Iterating through AP map to find AHB-AP to useAP: Core foundAP: AHB-AP ROM base: 0xE00FF000CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)Found Cortex-M4 r0p1, Little endian.FPUnit: 6 code (BP) slots and 2 literal slotsCoreSight components:ROMTbl @ E00FF000: E000E000 CID B105E00D PID 000BB00C SCS-M7: E0001000 CID B105E00D PID 003BB002 DWT: E0002000 CID B105E00D PID 002BB003 FPB: E0000000 CID B105E00D PID 003BB001 ITM: E0040000 CID B105900D PID 000BB9A1 TPIU: E0041000 CID B105900D PID 000BB925 ETM: E0042000 CID B105900D PID 002BB908 CSTF: E0043000 CID B105900D PID 001BB961 TMC: E0044000 CID B105F00D PID 001BB101 TSGCortex-M4 identified.J-Link>rsettype 0Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.J-Link>rReset delay: 0 msReset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.Reset: Halt core after reset via DEMCR.VC_CORERESET.Reset: Reset device via AIRCR.SYSRESETREQ.T-bit of XPSR is 0 but should be 1. Changed to 1.J-Link>hPC = F44F6210, CycleCnt = 00000000R0 = DFFE997D, R1 = BF79F66B, R2 = 78148615, R3 = 7C9EE779R4 = 6F9E5E0B, R5 = B1BFF157, R6 = 694EB6E7, R7 = C7FBD8F7R8 = EAE76113, R9 = EB3A4E3E, R10= 8BDD35E7, R11= 5D4BBDBCR12= FDFE675BSP(R13)= EA412100, MSP= EA412100, PSP= EEA1BC3C, R14(LR) = FFFFFFFFXPSR = 01000000: APSR = nzcvq, EPSR = 01000000, IPSR = 000 (NoException)CFBP = 00000000, CONTROL = 00, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00
FPS0 = F4A59958, FPS1 = F1F0919A, FPS2 = 739D2079, FPS3 = 29EA7E89FPS4 = B2F517B4, FPS5 = 276E3839, FPS6 = 93FE8E41, FPS7 = BAB8F621FPS8 = EA6BFBB9, FPS9 = BEFEB612, FPS10= 71FB7FD7, FPS11= 8D18043EFPS12= E25BB1DA, FPS13= 6A7AF33D, FPS14= FFFF7EBE, FPS15= F17F57E1FPS16= 7263FE7C, FPS17= 0A8DFDC5, FPS18= 557137D9, FPS19= B32BEFD9FPS20= 2D3C5AFC, FPS21= DBAED1EC, FPS22= F323C96F, FPS23= 4C7A62D9FPS24= 3EFEF03D, FPS25= 22CACCBF, FPS26= F9FBCA4D, FPS27= 93DBEA3CFPS28= B0ECFC11, FPS29= C3D5E9FE, FPS30= 6ABF2DDC, FPS31= F23BAE81FPSCR= 00000000J-Link>sleep 100Sleep(100)J-Link>w2 0x4001e3fe, 0xa50BWriting A50B -> 4001E3FEJ-Link>w4 0x4001e020, 0x11011221Writing 11011221 -> 4001E020J-Link>w1 0x4001E416, 0x01Writing 01 -> 4001E416J-Link>w2 0x407fe08c, 0x2d01Writing 2D01 -> 407FE08CJ-Link>sleep 10Sleep(10)J-Link>w2 0x407fe08c, 0x2d00Writing 2D00 -> 407FE08CJ-Link>sleep 10Sleep(10)J-Link>w2 0x407FE0E4, 0x1E04Writing 1E04 -> 407FE0E4J-Link>w2 0x407FE084, 0xAA01Writing AA01 -> 407FE084J-Link>w4 0x407FE030, 0x00000000Writing 00000000 -> 407FE030J-Link>w1 0x407E0000, 0x20Writing 20 -> 407E0000J-Link>w1 0x407E0000, 0xD0Writing D0 -> 407E0000J-Link>mem32 0x407FE080, 1407FE080 = 00000000J-Link>sleep 1000Sleep(1000)J-Link>mem32 0x407FE080, 1407FE080 = 00000000J-Link>w2 0x407FE084, 0xAA00Writing AA00 -> 407FE084
Script processing completed.
Type "connect" to establish a target connection, '?' for helpJ-Link>
=> I reset the board and re-debug again but did not success