Bricked DK-S7G2 Less expensive to replace chip

We are migrating from SSP 1.5.3  to 2.5 which requires changing the IDE and SSP. During the process we entered a debug session with our custom S7G2 board. Afterwards the board would not allow further programming. The first two of the three progress bars are successful, but the third or program download fails. We can read the configuration blocks. We can erase the chip with various scripts, including entering the 32 FF ID code. We attempted this process with hope a quick recovery from the bricking. Our technicians replace the chip. If it was worth the investment of time, Renasas would have an application note and downloads for the process. Sadly the hobby project will suffer because it is cheaper to us manufacturers to trash a chip.

If you are curious this is the config dump of our bricked S7G2

SEGGER J-Link Commander V7.84b (Compiled Jan 11 2023 16:38:37)
DLL version V7.84b, compiled Jan 11 2023 16:37:10


J-Link Command File read successfully.
Processing script file...
J-Link>Device R7FS7G27H
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link V12 compiled Jun 21 2023 09:20:55
Hardware version: V12.00
J-Link uptime (since boot): 0d 00h 15m 12s
S/N: 52002513
License(s): GDB
USB speed mode: High speed (480 MBit/s)
VTref=3.268V
J-Link>si SWD
Selecting SWD as current target interface.
J-Link>speed 4000
Selecting 4000 kHz as target interface speed
J-Link>connect
Device "R7FS7G27H" selected.


Connecting to target via SWD
Found SW-DP with ID 0x5BA02477
Found SW-DP with ID 0x5BA02477
DPIDR: 0x5BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: APB-AP (IDR: 0x44770002)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: 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
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
[0][6]: E0042000 CID B105900D PID 002BB908 CSTF
[0][7]: E0043000 CID B105900D PID 001BB961 TMC
[0][8]: E0044000 CID B105F00D PID 001BB101 TSG
Memory zones:
Zone: Default Description: Default access mode
Cortex-M4 identified.
J-Link>halt
T-bit of XPSR is 0 but should be 1. Changed to 1.
PC = 68564D14, CycleCnt = 16857DF1
R0 = 00000021, R1 = F10C5905, R2 = 000000FC, R3 = 00000800
R4 = 1FFE0964, R5 = FE4FB172, R6 = 1FFE09BC, R7 = 000000FF
R8 = 6610EC9C, R9 = FFF75FBB, R10= FFFFFF97, R11= FFFBE7BF
R12= 1FFE08E8
SP(R13)= 1FFF2198, MSP= 1FFF2198, PSP= 95EFFFDC, R14(LR) = FFFFFFF9
XPSR = 01000003: APSR = nzcvq, EPSR = 01000000, IPSR = 003 (HardFault)
CFBP = 00000000, CONTROL = 00, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00

FPS0 = ED42FB4B, FPS1 = EEC7DFA7, FPS2 = C1A6E067, FPS3 = 65122DD3
FPS4 = F766DCAB, FPS5 = 97256F4F, FPS6 = BEEED829, FPS7 = F3A7FBA7
FPS8 = F6BD2B82, FPS9 = B5BFAF83, FPS10= 64971D66, FPS11= 7638FCE2
FPS12= 64BA7D9F, FPS13= F6711C4D, FPS14= 8BA2DC87, FPS15= EC1EA473
FPS16= D1E0CAD7, FPS17= 71417A5F, FPS18= 753860AF, FPS19= FC74AD1F
FPS20= FFEDB7EF, FPS21= 79BEAAD6, FPS22= 7FAB4FD5, FPS23= ADA9BEE5
FPS24= 7F6C9E06, FPS25= 2BC798A7, FPS26= BBE4BD0F, FPS27= F38BF4E5
FPS28= BB35BDEB, FPS29= CEA1D68F, FPS30= AF1FFC14, FPS31= BBE6D98F
FPSCR= 00000000
J-Link>mem32 0x00000400, 0x10
00000400 = 33014A0B 0383EB03 6013005B 7960E704
00000410 = EB037923 F7F72000 E6FDFF1B 1FFF2194
00000420 = 20011BBC 1FFF21C0 2001004C 200121E4
00000430 = 20010058 1FFF21C6 20006380 200067A4
J-Link>mem32 0x40120040, 0xb
40120040 = 00000000 00000000 00000000 00000000
40120050 = 00000000 00000000 00000000 00000000
40120060 = 00000000 00000000 00000000
J-Link>q

Script processing completed.

Parents
  • You might consider using a socket for your development system, you don't mention which exact part you use so I cannot recommend a specific socket to fit the package.

    Tokyo-Eletech and Ironwood Electronics likely have a socket to support the device.  The socket is not cheap, but not having to replace a device soldered to a PCB is quite convenient. 

Reply
  • You might consider using a socket for your development system, you don't mention which exact part you use so I cannot recommend a specific socket to fit the package.

    Tokyo-Eletech and Ironwood Electronics likely have a socket to support the device.  The socket is not cheap, but not having to replace a device soldered to a PCB is quite convenient. 

Children
No Data