XDS200 cannot connect to ARM core 1 in No Boot/DSP JTAG Little Endian Mode

Mohamed Sarjoondeen K M

Other Parts Discussed in Thread: TCI6638K2K, 66AK2E05

Hi Team,

I am working on EVMK2E V1.0.2.2 board

I got this board and I found that by default this version of EVMK2E will boot U-boot from SPI NOR and Kernel, File system from NAND.

********************************************************************************************************

Now I want to boot U-boot and other kernel images which I build through Yocto Arago Project.

I tried to Boot throug CCS software with XDS200 JTAG Emulator support

I followed the instructions mentioned in the User Guide in the link http://processors.wiki.ti.com/index.php/MCSDK_User_Guide_for_KeyStone_II

and in the link : http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Installation_Guide to install CCS.

I installed CCSv5(ccs_setup_5.5.0.00077) in Windows 7 64 bit PC successfully.

Once after installtion is done i installed the "ti_emupack_keystone2_setup_1.1.1.0".

******************************************************************************************************

Once CCS installation is done, I powered on the EVM board, Once after BOOT COMPLETE message is displayed in EVM LCD

I opened CCS appplication and followed the below steps from http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Loading_and_Running_U-Boot_on_EVM_through_CCS

and I loaded the U-boot and I verified the PC register also.

But when I click "Resume" it got crashed and u-boot prompt didn't turn up. I attached the file "corruption.txt" for reference

Then I realised I didnt set the DIP Switch to No boot mode/JTAG DSP Little endian and I did the above steps with SPI NOR ARM Master boot

So I changed the DIP switch to No boot mode and I turned on EVM and CCS

But when I tired to connect the Target this time. I got the below error message

Error connecting to the target:
Connect to PRSC failed

And after this I couldn't able to connect to the Target(Texas Instruments XDS2xx USB Onboard Emulator_0/arm_A15_1) in No Boot Mode

I can able to launch the Target configuration but i couldn't able to connect the target alone

But in "SPI NOR ARM Master mode" I can able to connnect to the Target (Texas Instruments XDS2xx USB Onboard Emulator_0/arm_A15_1)

I need to to boot U-boot through CCS. So please help me with this.

I installed CCSv6 and tried and it also gives the same issue.

5314.corruption.txt

over 10 years ago

0 Shankari G over 10 years ago

TI__Mastermind 43955 points

Hi Mohamed,

The following are the steps to get the u-boot prompt on K2H / K2E EVM through CCS which is the easiest method.

I have attached the necessary screenshots for your reference.

1. Flashing and booting u-boot.bin
======================

The u-boot.bin can be flashed into the EVM through CCS method.

1.1 HW Set up on K2HK EVM:

==================

In EVMK2hk, rev 3.0 board, you will find two FTDI -USB connectors. The top one is for the emulator (CCS) and
the bottom one is for opening two channels ( one for displaying the u-boot messages and another one is for BMC commands)
Connect the USB cables between your host PC where in the CCS is installed and the K2HK EVM. One for Emulation and the other one for receiving the u-boot messages and the BMC commands.
To flash the u-boot.bin, EVM dip switches are to be set for no-boot mode

SWITCH	Pin1	Pin2	Pin3	Pin4
SW1	Off	Off	Off	On

1.2 CCS set up and u-boot flashing Steps to get u-boot prompt.

==================================================

In CCS, navigate to view--> Target configuration--> create new target configuration file --> and open the file.
Select the XDS2xx USB emulator as "connection" and "66AK2H12" as board/device, save and test connection.
Now, launch the target configuration file and open -->view scripting console, you will get a console prompt with "js:>"
You might have already installed the MCSDK at windows and you will find the js file at C:/ti/mcsdk_linux_3_00_03_15/host-tools/loadlin/loadlin-evm-uboot.js
Connect the coretexA15_1 to the target.
In the scripting console, use loadJSfile command to load the "loadlin-evm-kern.js" file. Before loading, openup the js file in CCS and modify the
paths of u-boot, kernel like below
PATH_LOADLIN = <path of release folder>/host-tools/loadlin
var pathUboot = PATH_LOADLIN + "/u-boot-keystone-evm.bin";
var pathSKern = PATH_LOADLIN + "/skern-keystone-evm.bin";
loadJSFile C:\ti\mcsdk_linux_3_00_03_15\host-tools\loadlin\loadlin-evm-uboot.js
----> Observe a progress bar which will complete the loading of images given in the "loadlin-evm-uboot.js"
----> Hit the play button in CCS and in the tera term observe the output messages from "u-boot.bin" image ( flashed through CCS just now) and the u-boot prompt like below.

-------

0 Mohamed Sarjoondeen K M over 10 years ago in reply to Shankari G

Intellectual 605 points

Hi Shankari,

Thank you so much for your reply.

I did as you asked me to do, But still I got this error message

"arm_A15_1: Error connecting to the target: Connect to PRSC failed"

Then I realized that I have been connecting the wrong target core

*************************************************************************************************************

First of all, In the Code Composer Studio - Device Debugging menu,

For 66AK2xx devices The core name I think I should connect is Texas Instruments XDS2xx USB Emulator_0/arm_15_0

instead of Texas Instruments XDS2xx USB Emulator_0/arm_15_1

Because I think there is a core name difference betweeen 66AK2xx devices and other devices(Ex: TCI6638K2K device)

66AK2E05 Device Debugging core options

TCI6638K2K Device Debugging core options

Note: 1st image is the core options for 66AK2E05 device and 2nd image is TCI6638K2K device

As you can see, the TCI6638K2K device core name stands as

coretexA15_1, coretexA15_3, coretexA15_5, coretexA15_7

whereas in 66AK2xx devices its

arm_A15_0, arm_A15_1, arm_A15_2, arm_A15_3

So I should select arm_A15_0 core for 66AKExx devices ???

If I select that core I can able to load U-boot binary successfully from CCS :)

Please clarify me whether the things I said regarding the core selection is correct and correct me if I am wrong.

Cheers. Thank you sooo much for the steps.

Regards

Sarjoon.

0 Shankari G over 10 years ago in reply to Mohamed Sarjoondeen K M

TI__Mastermind 43955 points

Hi Sarjoon,

Yes, your understanding is right.
If there is any core name mismatch, feel free to edit either in the *.ccxml-->Source option or in the gel file.

0 Mohamed Sarjoondeen K M over 10 years ago in reply to Shankari G

Intellectual 605 points

Hi,

Thanks for the reply,

I can able to boot u-boot through CCS.

Now the next step is I tried to boot from SPI.

I followed these steps http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Single_Stage_SPI_Flash_Boot

Once after u-boot prompt appears, I stopped the autoboot.

1. In CCS, I clicked Run->Suspend

2. Then Tools->Load memory.

3. Browsed the u-boot-keystone-evm.bin file in my PC and selected it.

4. Then in Start address i entered 0x0c300000 and clicked finish

After this step I don't know whether u-boot is written into that particular temporary address(0x). How to verify it ??

5.Then in CCS. Run->Resume

6. In U-boot prompt, To format the memory entered ->

K2E EVM # fmtimg spi 0x0c001000 0x0c300000 54308

formatted image - Addr 0x0c300000 (Bytes: 344856(0x54318))

where 54308 is the size in hex bytes of my u-boot-keystone-evm.bin. I attached the u-boot.bin file.

My U-boot.bin file is (337KB)344840 bytes which I converted to hex value which is 54308.

I noted down the formatted images size of (Bytes: 344856(0x54318))

7. Then did the below commands to prepare SPI flash for saving formatted u-boot.bin and to flash the u-boot to SPI

K2E EVM # sf probe

SF: Detected N25Q128A with page size 64 KiB, total 16 M iB

K2E EVM # sf erase 0 0x60000 ( where its mentioned that len must be at least the size of formatted image size, my fmt img size is 0x54318 so i gave 0x60000)

K2E EVM # sf write 0x0c300000 0 0x54318

After this It didn't receive any successful msg or any error. It just finished writting

8. Then I switched off EVM, changed the DIP to 0010 and disconnected the CCS from EVM.

9.Powered on the EVM. But I didn't receive any u-boot prompt, it didn't boot at all.

Actually it erased the already existed U-boot.bin. :(

Is Something went wrong with the commands I entered or in the way I flashed U-boot through CCS

I have printed the address through printenv command

addr_fdt=0x87000000
addr_fs=0x82000000
addr_kern=0x88000000
addr_mon=0x0c140000
addr_secdb_key=0xc000000
addr_ubi=0x82000000
addr_uboot=0x87000000

Is my issue something related to memory address, whether I have written in the wrong memory location in my K2E board. I know that the steps mentioned in the EXPLORING THE MCSDK link is for K2H board.

Please tell me like what changes need to be done in K2E to flash u-boot to SPI through CCS method.

Thanks & Regards

Sarjoon

0 Shankari G over 10 years ago in reply to Mohamed Sarjoondeen K M

TI__Mastermind 43955 points

Hi Mohamed,

Glad to hear that you are able to successfully boot the u-boot.

It is better to open up a new query.

There is no method in CCS to flash the u-boot directly into the SPI flash memory.

Do the u-boot flashing into the MSCMSRAM as you have done already and get the u-boot prompt.

For SPI flashing follow these steps.

SPI flashing:

=============

Try to get u-boot shell when power up from any media (NAND or MSC MSRAM (CCS) etc., ) and do the following

------------------------------------------------------------------------------------------------------------

#tftpboot 0x88000000 u-boot-spi.gph

#sf probe

#sf erase 0 0x100000 (Offset is depends on u-boot image size )

#sf write 0x88000000 0 0x100000

SPI Booting:

=============

Boot switch : 0:0:1:0

Processors

Processors forum

XDS200 cannot connect to ARM core 1 in No Boot/DSP JTAG Little Endian Mode