求解Jlink V9连接正常，用V11就不正常，版本6.82g
本帖最后由 styleno1 于 2021-4-1 10:48 编辑买了个新仿真器，发现连不上芯片，另外的一块M0连接、仿真都正常，AT403的用V11就连不上，求解？
V9连接正常：
- Executing init sequence ...
- Initialized successfully
- Target interface speed: 2000 kHz (Auto)
- Found 1 JTAG device. Core ID: 0x2BA01477 (None)
- Connected successfully
V11连接不成功：
Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link V11 compiled Feb4 2021 12:59:17
- Device "AT32F403_EXT_TYPE2_1MB" selected.
- ConfigTargetSettings() start
-
- ConfigTargetSettings() end
- InitTarget() start
- InitTarget() end
- Found SW-DP with ID 0x2BA01477
- DPIDR: 0x2BA01477
- AP map detection skipped. Manually configured AP map found.
- AP: AHB-AP (IDR: Not set)
- AP: Skipped. Could not read CPUID register
- ConfigTargetSettings() start
-
- ConfigTargetSettings() end
- InitTarget() start
- InitTarget() end
- Found SW-DP with ID 0x2BA01477
- DPIDR: 0x2BA01477
- AP map detection skipped. Manually configured AP map found.
- AP: AHB-AP (IDR: Not set)
- AP: Skipped. Could not read CPUID register
- ERROR: Could not find core in Coresight setup
- Target interface speed: 200 kHz (Auto)
- VTarget = 3.373V
- ConfigTargetSettings() start
-
- ConfigTargetSettings() end
- InitTarget() start
- InitTarget() end
- Found SW-DP with ID 0x2BA01477
- DPIDR: 0x2BA01477
- AP map detection skipped. Manually configured AP map found.
- AP: AHB-AP (IDR: Not set)
- AP: Skipped. Could not read CPUID register
- ConfigTargetSettings() start
-
- ConfigTargetSettings() end
- InitTarget() start
- InitTarget() end
- Found SW-DP with ID 0x2BA01477
- DPIDR: 0x2BA01477
- AP map detection skipped. Manually configured AP map found.
- AP: AHB-AP (IDR: Not set)
- AP: Skipped. Could not read CPUID register
- ERROR: Could not find core in Coresight setup
- ERROR: Failed to connect.
Could not establish a connection to target.选ARM Cortex-M4时连接正常：Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link V11 compiled Jul 17 2020 16:24:07
- Device "CORTEX-M4" selected.
- Target interface speed: 4000 kHz (Fixed)
- VTarget = 3.364V
- Found SW-DP with ID 0x2BA01477
- DPIDR: 0x2BA01477
- Scanning AP map to find all available APs
- AP: Stopped AP scan as end of AP map has been reached
- AP: AHB-AP (IDR: 0x24770011)
- Iterating through AP map to find AHB-AP to use
- AP: Core found
- AP: 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 @ E00FF000
- ROMTbl: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
- ROMTbl: E0001000, CID: B105E00D, PID: 003BB002 DWT
- ROMTbl: E0002000, CID: B105E00D, PID: 002BB003 FPB
- ROMTbl: E0000000, CID: B105E00D, PID: 003BB001 ITM
- ROMTbl: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
- ROMTbl: E0041000, CID: 00000000, PID: 00000000 ???
- Executing init sequence ...
- Initialized successfully
- Target interface speed: 4000 kHz (Fixed)
- Found 1 JTAG device. Core ID: 0x2BA01477 (None)
- Connected successfully编辑说明：补充Log
理论上来说不应该，连不上什么意思，是指jlink命令行都无法连上吗 084425 发表于 2021-3-30 13:22
理论上来说不应该，连不上什么意思，是指jlink命令行都无法连上吗
已更新Log信息 你这里device选择很奇怪怎么会是AT32F403_EXT_TYPE2_1MB，完全不合理，应该是at32的型号才对。 本帖最后由 styleno1 于 2021-3-30 23:10 编辑
muyichuan2012 发表于 2021-3-30 22:08
你这里device选择很奇怪怎么会是AT32F403_EXT_TYPE2_1MB，完全不合理，应该是at32的型号才对。 ...
这是官方芯片列表里带的，烧录外挂的SPI Flash。这个到不用困扰，用V9也是这个上位机，它是正常的 我知道是spim的文件，这是我写的。我是觉得device 这里选择有点问题。可否告知jlink v11购买链接，我们买一个测试一下。 muyichuan2012 发表于 2021-3-31 12:51
我知道是spim的文件，这是我写的。我是觉得device 这里选择有点问题。可否告知jlink v11购买链接，我们买一 ...
我在贸泽上买的Jlink Base，www.mouser.cn 您好 我们的FAE已经与您取得联系，后面我们会持续跟进。
页:
[1]