EK-RA6M2 SCIBOOT模式识别不到串口

这边用EK-RA6M2 demo板突然不能仿真。用jflash连接提示如下图所示:

具体信息如下:

Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link OB-S124 compiled Feb 2 2021 16:57:21
- Device "R7FA6M2AF" selected.
- Target interface speed: 2000 kHz (Fixed)
- VTarget = 3.300V
- Found SW-DP with ID 0x5BA02477
- Found SW-DP with ID 0x5BA02477
- DPIDR: 0x5BA02477
- 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
- ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
- ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
- ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
- ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
- ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
- ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
- ROMTbl[0][6]: E0042000, CID: B105900D, PID: 002BB908 CSTF
- ROMTbl[0][7]: E0043000, CID: B105900D, PID: 001BB961 TMC
- ROMTbl[0][8]: E0044000, CID: B105F00D, PID: 001BB101 TSG
- Executing init sequence ...
- Initialized successfully
- Target interface speed: 2000 kHz (Fixed)
- ERROR: Could not detect CPU clock speed. Verification of test code downloaded into RAM failed.
- ERROR: Failed to measure CPU clock frequency
- ERROR: Failed to connect.
Could not determine CPU clock frequency.

这边改为SCI BOOT模式 连接不能识别到串口。请问有遇到过类似的情况吗?

Parents
  • 改用外接串口工具连接SCI9 P109 P110,用RFP com 连接提示如下:

    Connecting the tool
    Tool : COM port (COM9), Interface : 2 wire UART
    Connecting to the target device

    Disconnecting the tool
    Error(E3000105): The device is not responding.
    The target MCU is not connected or is not responding.
    Check the connection to and operating mode of the target MCU.
    For details, refer to the user's manual.

    Operation failed.

  • 不知道是什么操作导致MCU可能被锁死了,原因可能是OSIS寄存器地址的bit127被意外写为0.

  • 目前遇到锁死的问题出现了5  6  次了,比较有规律出现的情况是在用IAR debug刚开始立马拔掉仿真器,会导致芯片锁死。RA2L1 RA6M2 都有出现过类似情况。像出现这种问题没办法恢复吗?这个风险非常大。

  • "在用IAR debug刚开始立马拔掉仿真器"

    在没有断开仿真器和PC连接, 这种做法非常危险, 还会造成仿真器损坏.

Reply Children
No Data