Hello
We have a problem with Renesas R7S721000 which is similar to this one: [SOVED] Unable to program in stand-alone mode - J-Link/Flasher related - SEGGER - Forum
Flashing from PC works perfectly, but in stand alone mode it gives an error.
I have updated the flasher FW to the latest version but it doesn't help.

Here is my Jlink commander output:

SEGGER J-Link Commander V7.96a (Compiled Mar 14 2024 17:15:38)
DLL version V7.96a, compiled Mar 14 2024 17:14:50

Connecting to J-Link via USB...O.K.
Firmware: J-Link / Flasher ARM V5-1 compiled Sep 11 2024 10:30:39
Hardware version: V5.10
J-Link uptime (since boot): 0d 00h 01m 23s
S/N: 165105919
License(s): JFlash, GDB
USB speed mode: Full speed (12 MBit/s)
IP-Addr: DHCP (no addr. received yet)
VTref=3.292V

Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: R7S721000_DUALSPI
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "R7S721000_DUALSPI" selected.

Connecting to target via JTAG
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 36us
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: APB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
Using preconfigured AP[1] as APB-AP
AP[1]: APB-AP found
ROMTbl[0][0]: CompAddr: 80002000 CID: B105900D, PID: 003BB906 CTI (?)
ROMTbl[0][1]: CompAddr: 80008000 CID: B105900D, PID: 003BB906 CTI (?)
ROMTbl[0][2]: CompAddr: 8000C000 CID: B105900D, PID: 003BB906 CTI (?)
ROMTbl[0][3]: CompAddr: 8000F000 CID: B105F00D, PID: 000A3FA9 ???
ROMTbl[0][4]: CompAddr: 80020000 CID: B105100D, PID: 000BB4A9 ROM Table
ROMTbl[1][0]: CompAddr: 80021000 CID: B105900D, PID: 001BB961 TMC
ROMTbl[1][1]: CompAddr: 80022000 CID: B105900D, PID: 003BB906 CTI (?)
ROMTbl[1][2]: CompAddr: 80023000 CID: B105900D, PID: 004BB912 TPIU
ROMTbl[1][3]: CompAddr: 80024000 CID: B105900D, PID: 001BB908 CSTF
ROMTbl[1][4]: CompAddr: 80030000 CID: B105900D, PID: 000BBC09 Cortex-A9
Found Cortex-A9 r3p0
6 code breakpoints, 4 data breakpoints
Debug architecture ARMv7.0
Data endian: little
Main ID register: 0x413FC090
I-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
System control register:
Instruction endian: little
Level-1 instruction cache disabled
Level-1 data cache disabled
MMU disabled
Branch prediction disabled
Memory zones:
Zone: "Default" Description: Default access mode
Zone: "AHB-AP (AP0)" Description: DMA like acc. in AP0 addr. space
Zone: "APB-AP (AP1)" Description: DMA like acc. in AP1 addr. space
Cortex-A9 identified.

And here is my serial port output:

$BTL: Bootloader started successfully
$BTL: Initializing file system... OK
$BTL: Trying to open firmware file... ERR: File not found
$BTL: Check for valid firmware... OK
$BTL: Starting firmware...<CR><NUL>$FW: Initializing file system...
$FW: Initializing NET module...
$FW: Initializing FTP server...
$FW: Initializing web server...
$FW: Initializing telnet server...
$FW: Initializing CMD module...
$FW: Firmware started successfully
#auto
#ACK
#STATUS:INITIALIZING
#STATUS:CONNECTING
#ERR255:Timeout while preparing target, core does not stop. (PC = 0xFFFF007C, CPSR = 0x600001DB, LR = 0x18000004)!

Do you have any suggestions?