提问 + BeagleBone Black + CCS V5.5 怎么才能裸奔？【已解决】

azhiking

提问 + BeagleBone Black + CCS V5.5 怎么才能裸奔？【已解决】 [复制链接]

操作系统： Win7 32位

IDE: CCS V5.5

平台： 英蓓特  BeagleBone Black (B4)

利用CCS的TI Resource Explorer ，选择BeagleBone Black 下Generic Examples中的Hello World.

Step 3:        Debugger Configuration        
Connection: Texas Instruments XDS100v2 USB Emulator
Click on the link above to change the device connection. Additionally, this option is also available in the project properties.
最后Step 4Debug the imported project总是出现

Error connecting to the target:
(Error -1266 @ 0x0)
Device is held in reset. Take the device out of reset, and retry the operation.
(Emulation package 5.1.232.0)

在配置文件中测试连接：

[Start]

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\ZHOUMA~1\AppData\Local\.TI\4084209646\
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 'Aug 20 2013'.
The library build time was '22:56:19'.
The library package version is '5.1.232.0'.
The library component version is '35.34.40.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 512 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 512 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 512 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]

请问是什么原因导致无法调试的呢？

CortxA8: Output: **** AM335x BeagleBlack Initialization is in progress ..........
CortxA8: Output: **** AM335x ALL PLL Config for OPP == OPP100 is in progress .........
CortxA8: GEL: Error while executing OnTargetConnect(): Target failed to read 0x44E10040 at (*((unsigned int *) (0x44E10000+0x40))>>22) [beagleboneblack.gel:362] at GetInputClockFrequency() [beagleboneblack.gel:433] at ARM_OPP100_Config() [beagleboneblack.gel:353] at AM335x_BeagleBlack_Initialization() [beagleboneblack.gel:339] at OnTargetConnect() .
CortxA8: Trouble Writing Memory Block at 0x800145b0 on Page 0 of Length 0x5c0: (Error -2130 @ 0x800145B0) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.232.0)
CortxA8: GEL: File: D:\BB Black\hello_BeagleBone_Black_CortexA\Debug\hello_BeagleBone_Black_CortexA.out: Load failed.

尝试更换不同的gel,最后总是Load Failed. 什么原因呢？

还是有什么地方操作不正确？

我是用了StarterWare，也不行。

参考过：http://processors.wiki.ti.com/in ... e_board_using_CCSv5

chenzhufly

裸奔不好 有损风化

airqj

在board or devive 那里有beaglebone black 的选项的   不要根据教程里的选am335x
或者重启试试看。。。实在不行再重新配置一遍，，
还是不行的话去TI 社区吧///

azhiking

找到原因了，是因为Linux启动了，不让Linux启动就可以正常进行调试了。

kingback00001

楼主您好，我现在遇到跟你一样的情况，您说的不让linux启动指的是更改了启动模式还是拔了SD卡？我现在用的是SD卡启动