我用的是IDK574x，在刚开始CCS调试的时候遇到以下的问题，请问如何解决呢

user4839655

CortexA15_1: GEL Output: --->>> AM574x IDK EVM <<<---
CortexA15_1: GEL Output: --->>> AM574x Target Connect Sequence Begins ... <<<---
CortexA15_1: GEL Output: --->>> AM574x Begin MMC2 Pad Configuration <<<---
CortexA15_1: GEL Output: --->>> AM574x End MMC2 Pad Configuration <<<---
CortexA15_1: GEL Output: --->>> AM574x PG1.0 GP device <<<---
CortexA15_1: GEL Output: --->>> PRCM Clock Configuration for OPPNOM in progress... <<<---
CortexA15_1: GEL Output: Cortex A15 DPLL OPP 0 clock config is in progress...
CortexA15_1: GEL Output: Cortex A15 DPLL is already locked, now unlocking...
CortexA15_1: GEL Output: Cortex A15 DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: IVA DPLL OPP 0 clock config is in progress...
CortexA15_1: GEL Output: IVA DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: PER DPLL OPP 0 clock config in progress...
CortexA15_1: GEL Output: PER DPLL already locked, now unlocking
CortexA15_1: GEL Output: PER DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: CORE DPLL OPP 0 clock config is in progress...
CortexA15_1: GEL Output: CORE DPLL OPP already locked, now unlocking....
CortexA15_1: GEL Output: CORE DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: ABE DPLL OPP 0 clock config in progress...
CortexA15_1: GEL Output: ABE DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: GMAC DPLL OPP 0 clock config is in progress...
CortexA15_1: GEL Output: GMAC DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: GPU DPLL OPP 0 clock config is in progress...
CortexA15_1: GEL Output: GPU DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: DSP DPLL OPP 0 clock config is in progress...
CortexA15_1: GEL Output: DSP DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: PCIE_REF DPLL OPP 0 clock config is in progress...
CortexA15_1: GEL Output: PCIE_REF DPLL OPP 0 is DONE!
CortexA15_1: GEL Output: --->>> PRCM Clock Configuration for OPP 0 is DONE! <<<---
CortexA15_1: GEL Output: --->>> PRCM Configuration for all modules in progress... <<<---
CortexA15_1: GEL Output: --->>> PRCM Configuration for all modules is DONE! <<<---
CortexA15_1: GEL Output: --->>> DDR3 Initialization is in progress ... <<<---
CortexA15_1: GEL Output: DDR DPLL clock config for 666MHz is in progress...
CortexA15_1: Trouble Writing Memory Block at 0x4a005210 on Page 0 of Length 0x4: (Error -1045 @ 0x345A) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006)
CortexA15_1: GEL: Error while executing OnTargetConnect(): Target failed to write 0x4A005210
at *((unsigned int *) base_address)=7 [AM574x_prcm_config.gel:14]
at dpll_lock_sequence((0x4a005100+0x110)) [AM574x_prcm_config.gel:970]
at dpll_ddr_config(666) [AM574x_ddr_config.gel:1002]
at AM574x_DDR3_666MHz_Config() [AM574x_startup_common.gel:93]
at AM57xx_EVM_Initialization(1) [idk_am574x.gel:54]
at OnTargetConnect()
CortexA15_1: Trouble Reading Register REG_ENDIAN: (Error -1044 @ 0x3458) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_TARGET_CONFIG: (Error -2131 @ 0x73000000) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_TARGET_CONFIG: (Error -2131 @ 0x73000000) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_TARGET_CONFIG: (Error -2131 @ 0x73000000) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_TARGET_CONFIG: (Error -2131 @ 0x73000000) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_TARGET_CONFIG: (Error -2131 @ 0x73000000) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_TARGET_CONFIG: (Error -2131 @ 0x73000000) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -2131 @ 0x73000002) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)
CortexA15_1: JTAG Communication Error: (Error -154 @ 0x0) One of the FTDI driver functions used to write data returned bad status or an error. (Emulation package 8.4.0.00006)

5 年多前

0 Nancy Wang 5 年多前

TI__Guru** 110395 points

请核对一下以下链接给出的步骤，看是否还有问题。
software-dl.ti.com/.../index_how_to_guides.html

GEL文件路径：ccs\ccs_base\emulation\boards\am574x\gel

0 user4839655 5 年多前回复 Nancy Wang

Intellectual 590 points

是按照给出的步骤进行的，am574x的gel文件显示success，但是在点击connect target时候显示，CCS还是提示不能读取内存块

0 user4839655 5 年多前回复 Nancy Wang

Intellectual 590 points

我的CCS用的是9.3版本的，这个跟CCS版本有关系吗

0 Nancy Wang 5 年多前回复 user4839655

TI__Guru** 110395 points

一般SDK的版本跟CCS版本兼容就没有问题。比如Processor SDK v06.03.00 要求 ccsv9.3.0以上。
GEL文件显示success什么意思？我从打印信息来看好像到DDR DPLL clock config for 666MHz is in progress...就开始报错。
我现在没有这块开发板，也无法测试。
能否找到script->Memory Config，单独再配置一下memory看看。

0 user4839655 5 年多前回复 Nancy Wang

Intellectual 590 points

我找到了script->Memory Config，后面有Clear_Memory、Default_Config和SMP_Config，我重新clear了memory，再配置了memory，还是显示以下错误
CortexA15_0: Trouble Writing Memory Block at 0x4a005210 on Page 0 of Length 0x4: (Error -1045 @ 0x345A) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006)
CortexA15_0: GEL: Error while executing OnTargetConnect(): Target failed to write 0x4A005210
at *((unsigned int *) base_address)=7 [AM574x_prcm_config.gel:14]
at dpll_lock_sequence((0x4a005100+0x110)) [AM574x_prcm_config.gel:970]
at dpll_ddr_config(666) [AM574x_ddr_config.gel:1002]
at AM574x_DDR3_666MHz_Config() [AM574x_startup_common.gel:93]
at AM57xx_EVM_Initialization(1) [idk_am574x.gel:54]
at OnTargetConnect()

0 user4839655 5 年多前回复 Nancy Wang

Intellectual 590 points

关于memory 0x4a005210这个位置是在0x48400000-0x4AFFFFFF之间，属性是R|W|AS4

0 Nancy Wang 5 年多前回复 user4839655

TI__Guru** 110395 points

把target configuration配置的界面图以及ccs 连接报错的界面图贴出来看一下。

0 user4839655 5 年多前回复 Nancy Wang

Intellectual 590 points

报错是这样的了现在，我用的是新到的板子，上面应该带有系统的，所以我先是插入带有MLO的SD卡，从SD卡启动，然后连接的。

0 Nancy Wang 5 年多前回复 user4839655

TI__Guru** 110395 points

把SD卡拔了试一下，连接仿真不需要这个步骤。

0 user4839655 5 年多前回复 Nancy Wang

Intellectual 590 points

拔了就变成以下结果了，DDR那儿就出现问题了，先是板子里面系统在跑，有LED亮着，当出现报错了后板子就关机了

0 Nancy Wang 5 年多前回复 Nancy Wang

TI__Guru** 110395 points

SD卡拔了之后有没有复位一下或者重新上电之后再连接。
cortexA15_0和cortexA15_1都是添加的idk_am574x.gel吗？

0 user4839655 5 年多前回复 Nancy Wang

Intellectual 590 points

我是重新上电的，cortexA15_0和cortexA15_1都是添加的idk_am574x.gel，两个核都试过了还是之前DDR那个问题

0 user4839655 5 年多前回复 Nancy Wang

Intellectual 590 points

这是 xds100v2 Test Connect的信息，如果没有问题的话，我不知道到底哪儿有问题了

[Start: Texas Instruments XDS100v2 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\YC\AppData\Local\TEXASI~1\CCS\TI\
0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Nov 25 2019'.
The library build time was '16:55:29'.
The library package version is '8.4.0.00006'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]

0 Nancy Wang 5 年多前回复 user4839655

TI__Guru** 110395 points

test connect没问题。
结合您新发的帖子e2echina.ti.com/.../582608
请问diag中的mem_test您测试过吗？有没有问题。
mem_test:
Writes and reads to external (DDR) memory of the board. Value written/read is the address of the word. This is done two times, for value and ~value (complement), to test for all bits.