I can't Load U-BOOT to Memory in TCI6636.

k.s shin

Expert 2115 points

Other Parts Discussed in Thread: TCI6638K2K, 66AK2H14

Hello

I make a Custom Board included TCI6636. and Board connected XDS560 JTAG.

and I want to use a ARM. So I run a CCS v5 for Load U-boot to Memory but I can't

CCS v5 printed many Error Message. What is problem?

This is Error Message.

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

CortexA15_1: Trouble Writing Memory Block at 0xc001000 on Page 0 of Length 0x7ff0: (Error -1204 @ 0x3D5B) Unable to access the DAP. 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 5.1.232.0)
CortexA15_1: Trouble Reading Memory Block at 0xc018fd0 on Page 0 of Length 0x4: (Error -1205 @ 0xC018FD0) Device memory bus has an error and may be hung. 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)
CortexA15_1: Trouble Reading Memory Block at 0xc020fc0 on Page 0 of Length 0x4: (Error -242 @ 0x3458) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 5.1.232.0)
CortexA15_1: Trouble Reading Memory Block at 0xc028fb0 on Page 0 of Length 0x4: (Error -1205 @ 0xC028FB0) Device memory bus has an error and may be hung. 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)
CortexA15_1: Trouble Reading Memory Block at 0xc030fa0 on Page 0 of Length 0x4: (Error -1205 @ 0xC030FA0) Device memory bus has an error and may be hung. 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)
CortexA15_1: Trouble Reading Memory Block at 0xc038f90 on Page 0 of Length 0x4: (Error -1205 @ 0xC038F90) Device memory bus has an error and may be hung. 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)
CortexA15_1: Trouble Reading Memory Block at 0xc040f80 on Page 0 of Length 0x4: (Error -1205 @ 0xC040F80) Device memory bus has an error and may be hung. 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)
CortexA15_1: Trouble Reading Memory Block at 0xc048f70 on Page 0 of Length 0x4: (Error -1205 @ 0xC048F70) Device memory bus has an error and may be hung. 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)
CortexA15_1: Trouble Reading Memory Block at 0xc050f60 on Page 0 of Length 0x4: (Error -1205 @ 0xC050F60) Device memory bus has an error and may be hung. 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)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_STATUS: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_STATUS: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBCR: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBR0_64B: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBR1_64B: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C3_DACR: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_STATUS: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_STATUS: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBCR: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBR0_64B: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBR1_64B: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)
CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C3_DACR: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)

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

Regards.

Shin.

over 9 years ago

0 Shankari G over 9 years ago

TI__Mastermind 43955 points

Hi Shin,
Are you able to load and run simple hello world on ARM core for your custom board ?
Please use MSMC RAM to run the hello world code as u-boot uses MSMC RAM.

0 k.s shin over 9 years ago in reply to Shankari G

Expert 2115 points

Hello

Where can I get them??

Regards

0 k.s shin over 9 years ago in reply to Shankari G

Expert 2115 points

Hi
I use Load Program Instead of Load Memory But Still don't work.

This is Error Message What is mean??

CortexA15_1: GEL Output:
Connecting Target...
CortexA15_1: GEL Output: No initialization performed since bootmode = 0x00000003
CortexA15_1: GEL Output: You can manually initialize with GlobalDefaultSetup
CortexA15_1: Trouble Writing Register PC: (Error -1204 @ 0x3D5B) Unable to access the DAP. 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 5.1.232.0)
CortexA15_1: Error: (Error -1204 @ 0x3D5B) Unable to access the DAP. 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 5.1.232.0)
CortexA15_1: AutoRun: Target not run as the symbol "main" is not defined
CortexA15_1: Unable to determine target status after 20 attempts
CortexA15_1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

Regards.
Shin.

0 Shankari G over 9 years ago in reply to k.s shin

TI__Mastermind 43955 points

Hi Shin,
You have to run the gel file in DSP core not with ARM.

You can refer to the below e2e post.

e2e.ti.com/.../452350
e2e.ti.com/.../430233

0 k.s shin over 9 years ago in reply to Shankari G

Expert 2115 points

Hi

I used a gel file already. but the result same.

Regards
Shin.

0 Shankari G over 9 years ago in reply to k.s shin

TI__Mastermind 43955 points

Hi k.s Shin,

Please follow the procedure below to load u-boot into memory using CCS.

The below steps are for K2H EVM. While carrying out the steps, please change the device as "TCI6636" where ever applicable.

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 "TCI6638K2K" 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 k.s shin over 9 years ago in reply to Shankari G

Expert 2115 points

Hi Shankari

Thanks for your reply. and I do that your advice. but error still remain.

I loaded the JS file. and I ready for U-boot load to memory. but error is occurred.

script console says

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

Error evaluating "PC=0xc001000": Target failed to write register PC

at PC=0xc001000

(Z:\home\cyclone5\ti\mcsdk_linux_3_01_04_07\host-tools\loadlin\loadlin-evm-uboot.js#147)

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

and console says

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

IcePick_D_0: Error connecting to the target: (Error -180 @ 0x0) The controller has detected a target power loss. The user must turn-on or connect the power supply for the target. (Emulation package 5.1.232.0)

CortexA15_1: GEL Output:

Connecting Target...

CortexA15_1: GEL Output: No initialization performed since bootmode = 0x00000003

CortexA15_1: GEL Output: You can manually initialize with GlobalDefaultSetup

CortexA15_1: Trouble Reading Memory Block at 0xc048f70 on Page 0 of Length 0x4: (Error -1203 @ 0x3D5B) Unable to access the DAP. 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 5.1.232.0)

CortexA15_1: Trouble Reading Memory Block at 0xc050f60 on Page 0 of Length 0x4: (Error -1205 @ 0xC050F60) Device memory bus has an error and may be hung. 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)

CortexA15_1: Trouble Reading Register REG_SYSTEM_MMU_STATUS: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)

CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBCR: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)

CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBR0_64B: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)

CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C2_TTBR1_64B: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)

CortexA15_1: Trouble Reading Register CP15_Registers_REG_CTXA15_CP15_C3_DACR: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)

CortexA15_1: Trouble Writing Register PC: (Error -1141 @ 0x3D58) Device is not responding to the request. 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 5.1.232.0)

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

Help me please.

Regards

Shin.

0 Shankari G over 9 years ago in reply to k.s shin

TI__Mastermind 43955 points

Hi Shin,
Please make sure that you set bootmode to emulation (DSP no boot mode) mode.
What is your processor ?
K2H or K2E or some other keystone device ?

0 k.s shin over 9 years ago in reply to Shankari G

Expert 2115 points

Hi Shankari

Boot mode in My custom board is ARM nand boot. and Processor is 66AK2H14.

I tested NAND-BOOT mode in EVMK2H. Working was fine. So Custom Board has Fixed Boot mode. because I had to reduce Board Size.

Regards
Shin.

0 Shankari G over 9 years ago in reply to k.s shin

TI__Mastermind 43955 points

Hi Shin,
I would like you to request to run the gel file in DSP core0 and try to run some examples (DSP and ARM).
The log seems to be you are running the gel file with ARM core0.

Since you set boot mode to NAND and don't have emulation bootmode (DSP no boot mode) so you have to run the "GlobalDefaultSetup" via CCS script option to initialize all the peripherals.

Also you try to boot u-boot through UART boot mode.

processors.wiki.ti.com/.../MCSDK_UG_Chapter_Exploring

0 Raja over 9 years ago in reply to k.s shin

TI__Guru* 81335 points

As Shankari mentioned above, we recommend you to connect DSP core0 and run the gel file.

If that does not solve the issue then you may need to review your custom board with keystone hardware design and schematic checklist available in below link,

Thank you.

Processors

Processors forum

I can't Load U-BOOT to Memory in TCI6636.