ESP32-S2-saola-1_V1.2使用j-link调试时出现报错的原因？

开发板：ESP32-S2-saola-1_V1.2
开发环境安装方式：esp-idf-tools-setup-offline-2.8.exe
安装后是 v4.2版本
开发环境 ：eclipse
使用j-link调试时出现以下问题，未找到原因：
Open On-Chip Debugger  v0.10.0-esp32-20200709 (2020-07-09-08:54)Licensed under GNU GPL v2For bug reports, read        http://openocd.org/doc/doxygen/bugs.htmladapter speed: 9600 kHzStarted by GNU MCU EclipseInfo : Listening on port 6666 for tcl connectionsInfo : Listening on port 4444 for telnet connectionsInfo : J-Link V9 compiled Dec 13 2019 11:14:50Info : Hardware version: 9.20Info : VTarget = 3.301 VInfo : clock speed 9600 kHzInfo : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)Info : esp32s2: Target halted, PC=0x400314A4, debug_reason=00000001Info : Detected ESP32-S2 chipInfo : Listening on port 3333 for gdb connectionsInfo : accepting 'gdb' connection on tcp/3333Error: No symbols for FreeRTOSError: esp32s2: DSR (8000CC13) indicates DIR instruction generated an exception!Warn : esp32s2: Failed reading 5284 bytes at address 0x40030000Error: no working area available, can't alloc space for stub code!Error: Failed to load stub (-308)!Error: Algorithm run failed (-308)!Error: Failed to run flasher stub (-308)!Warn : Failed to get flash mappings (-308)!Error: esp32s2: DSR (8000CC13) indicates DIR instruction generated an exception!Warn : esp32s2: Failed reading 5284 bytes at address 0x40030000Error: no working area available, can't alloc space for stub code!Error: Failed to load stub (-308)!Error: Algorithm run failed (-308)!Error: Failed to run flasher stub (-308)!Error: esp32s2: DSR (8000CC13) indicates DIR instruction generated an exception!Warn : esp32s2: Failed reading 5284 bytes at address 0x40030000Error: no working area available, can't alloc space for stub code!Error: Failed to load stub (-308)!Error: Algorithm run failed (-308)!Error: Failed to run flasher stub (-308)!Error: Failed to probe flash, size 0 KBError: auto_probe failedError: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.Error: attempted 'gdb' connection rejected