arm_a15_0: Trouble halting target cpu

Johnthan, 

From the procedure you mentioned, it seems the u-boot is indeed throwing the device off its rails and taking down the ability to connect via JTAG. 

Unfortunately there is not a single way to properly find out what may be going on in this case. A few suggestions:

There is a chance that only the A15 core is off. You can try to see which cores of your device are still running or being reset or powered down using the Target Status feature - check section 7.5.7 of the CCS User's Guide at:

https://software-dl.ti.com/ccs/esd/documents/users_guide/index.html

One additional step you may try to do is manually load u-boot to the device via CCS and see if everything is working. Something that can be done via the CCS Memory Browser view by loading the u-boot binary to a specific address (I think MSMC for the 66AK2 devices).

The address is mentioned at the presentation below. I also attach it at the end of this post. 

https://processors.wiki.ti.com/images/6/6a/KeyStone_Bootloader.pdf

I couldn't find a specific procedure to load and debug u-boot for the Keystone II devices, but a similar procedure are described for a similar device family at the references below:

https://training.ti.com/linux-board-porting-series-module-7-debugging-u-boot-jtag-ccs

https://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_uboot_linux_debug_with_ccsv5

https://e2e.ti.com/support/tools/ccs/f/81/p/719488/2654350

You can also try to load using a different method of fully booting the device, so you can validate the executable or the parameters of the u-boot. 

https://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#How_to_boot_from_USB_Flash_drive.3F

Unfortunately I am not well versed on the intrinsic aspects of the device itself, but hopefully this helps debugging your environment.

Hope this helps,

Rafael

KeyStone_Bootloader.pdf

Hi, Johnthan,

I see Rafael has posted info on how to debug u-boot with CCS. I just want to add info if you want to load u-boot with CCS. Please refer to 

<sdk-u-boot>/board/ti/ks2_evm/README on the section of "Load and Run U-Boot on keystone EVMs using CCS". 

Ignore the links to wiki pages. They are obsolete. For the Hardware Setup Guide, please go to 

http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/How_to_Guides_Hardware_Setup_with_CCS.html

You will need to build u-boot.bin when load and run u-boot using CCS. Please refer to u-boot user's guide for the build instruction

http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_U-Boot.html#u-boot-user-s-guide

Rex

thank you rafael,

ccs is a bit complicated to debug u-boot, can i use openocd+gdb?

i can load_image in openocd in its console, jump to the start address and run.

maybe i can use:

software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds_software_package_download.html

in this scenario, are gel files needed to initialize the target?

i have built u-boot.bin, and dss format-nand, run it, i assume, successfully.

to install or to run ccs, requires a lot of packages to be installed beforehand.

to debug u-boot, i have to spend days to learn how to use ccs, impractical.

i will try openocd + j-link + gdb later.

thank you both for your time~