This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Jlink cannot Erase Flash on custom board of RE01 - R7F0E01182CFP

Jlink cannot Erase Flash on custom board of RE01 - R7F0E01182CFP

- Have tried at different speed but same result. 

- Failed to prepare RAmCode using RAM

Error while determining flash info (Bank 2 @ 0x60000000) Failed to Erase chip

Jlink JFlash Project Script -> (Can not upload - Copied below)

AppVersion = 76404
FileVersion = 2
[GENERAL]
aATEModuleSel[24] = 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
ConnectMode = 0
CurrentFile = ""
DataFileSAddr = 0x00000000
GUIMode = 0
HostName = ""
TargetIF = 1
USBPort = 0
USBSerialNo = 0x00000000
UseATEModuleSelection = 0
[JTAG]
IRLen = 0
MultipleTargets = 0
NumDevices = 0
Speed0 = 4000
Speed1 = 4000
TAP_Number = 0
UseAdaptive0 = 0
UseAdaptive1 = 0
UseMaxSpeed0 = 0
UseMaxSpeed1 = 0
[CPU]
NumInitSteps = 1
InitStep0_Action = "Reset"
InitStep0_Value0 = 0x00000000
InitStep0_Value1 = 0x00000000
InitStep0_Comment = "Reset and halt target"
NumExitSteps = 0
UseScriptFile = 0
ScriptFile = ""
UseRAM = 1
RAMAddr = 0x20000000
RAMSize = 0x00020000
CheckCoreID = 1
CoreID = 0x5BA02477
CoreIDMask = 0x0F000FFF
UseAutoSpeed = 0x00000001
ClockSpeed = 0x00000000
EndianMode = 0
ChipName = "Renesas R7F0E0118"
[FLASH]
NumBanks = 3
[FLASH0]
aRangeSel[1] = 0
BankName = "Internal option-setting memory"
BankSelMode = 1
BaseAddr = 0x0100A150
[FLASH1]
aRangeSel[1] = 0-63
BankName = "Internal code flash"
BankSelMode = 1
BaseAddr = 0x00000000
[FLASH2]
BankName = "External QSPI flash"
BaseAddr = 0x60000000
[PRODUCTION]
AutoPerformsDisconnect = 0
AutoPerformsErase = 1
AutoPerformsProgram = 1
AutoPerformsSecure = 0
AutoPerformsStartApp = 0
AutoPerformsUnsecure = 0
AutoPerformsVerify = 1
EnableFixedVTref = 0
EnableTargetPower = 0
EraseType = 1
FixedVTref = 0x00000CE4
MonitorVTref = 0
MonitorVTrefMax = 0x0000157C
MonitorVTrefMin = 0x000003E8
OverrideTimeouts = 0
ProgramSN = 0
SerialFile = ""
SNAddr = 0x00000000
SNInc = 0x00000001
SNLen = 0x00000004
SNListFile = ""
SNValue = 0x00000001
StartAppType = 0
TargetPowerDelay = 0x00000014
TimeoutErase = 0x00003A98
TimeoutProgram = 0x00002710
TimeoutVerify = 0x00002710
VerifyType = 1
[PERFORMANCE]
DisableSkipBlankDataOnProgram = 0x00000000
PerfromBlankCheckPriorEraseChip = 0x00000001
PerfromBlankCheckPriorEraseSelectedSectors = 0x00000001

  • Hi ipatel, 

    Were you able to solve this issue? I saw in your other post that you already erased the flash and is facing another issue. Please confirm if this is the case. 

    Thanks for your update! Can you confirm if you have already solved your issue? 

    Herald
    RenesasRulz Forum Moderator

    https://renesasrulz.com/
    https://academy.renesas.com/
    en-us.knowledgebase.renesas.com/

  • Not yet. I see the same behavior with all the boards which I have tried so far including the one which I have just tried.

    Earlier, with "Jflash 7.58e" I have erased the chip with JFlash Lite, and it was randomly working at about 50kHz . 

    After recent update to JFlash  release(7.64d), chip erase is not working as described in this post. 

    I see the same result as described in the post after reverting the Jflash to previous release("7.58e").

  • Do you have an external QSPI connected to the RE01?

    The J-Flash is trying to erase the QSPI external address space (0x6000'0000) and it fails. However the internal codeflash has been erase correctly.

    If you don't have any QSPI on your board you can disable the QSPI Flashbank from the J-Flash configuration.

  • Hello Angler, You are correct, disabling the QSPI solved the issue since I do not have a external flash connected to QSPI but SPI. 

    Just adding a bit to above question, Do I have to follow specific pair of pins when I connect the QSPI flash or any combination of the pins which are dedicated to QSPI can work.

    CONFIG #1 

    CONFIG#2

    CONFIG#3(randomly mixed pins)

  • If you want to use the QSPI from your application only, all the possible configurations are valid.

    If you also want to be able to access the QSPI using the J-Flash you have to "guess" the configuration used by the J-Flash. This is because the J-Flash loads a small application into the uC RAM and this latter configures the I/O ports in a specific way.

    In my experience, the evaluation board of the uC is normally used by Segger as "target board".

  • Noted, Thank you. I will try to use same combination as the evaluation kit on my custom board.