This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Load program and symbol errors

Other Parts Discussed in Thread: DM3730

Hi TI,

 

I am using Window CCS5.1 for DM3730 board with Linux booting.

The ARM program is to print "hello".

Attached are the gel files and linker cmd file.

I have tried to load progam/symbols with ARM gel file and without ARM gel file when I stop the Linux autoboot.

How to resolve the errors ?

 

When I load symbols, I have the below errors .

 Cortex_A8_0: Breakpoint Manager: Retrying with a AET breakpoint

Cortex_A8_0: Trouble Setting Breakpoint with the Action "Process CIO" at 0x80003e5c: (Error -1065 @ 0x3D5A) 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.0.569.0)

Cortex_A8_0: Breakpoint Manager: Retrying with a AET breakpoint

Cortex_A8_0: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x80004288: (Error -1065 @ 0x3D5A)

 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.0.569.0)

 

When I load program, I have the below errors :

Cortex_A8_0: File Loader: Data verification failed at address 0x80000000 Please verify target memory and memory map.

Cortex_A8_0: Unable to terminate memory download: NULL buffer pointer at 0x3a9f

Cortex_A8_0: GEL: File: D:\ccs5\workspace_v5_1\hello\Debug\hello.out: a data verification error occurred, file load failed.

 

4762.am-dm37x_cortexA.gel

2705.am-dm37x_cortexA.gel

/****************************************************************************/
/*  DM3730.cmd                                                              */
/*  Copyright (c) 2011  Texas Instruments Incorporated                      */
/*                                                                          */
/*    Description: This file is a sample linker command file that can be    */
/*                 used for linking programs built with the C compiler and  */
/*                 running the resulting .out file on an DM3730.            */
/*                 Use it as a guideline.  You will want to                 */
/*                 change the memory layout to match your specific          */
/*                 target system.  You may want to change the allocation    */
/*                 scheme according to the size of your program.            */
/*                                                                          */
/****************************************************************************/
-c
-heap  0x2000
-stack 0x4000

MEMORY
{
    ISRAM:      o = 0x40200000  l = 0x00010000  /* 64kB Internal SRAM */
    CS0_SDRAM:  o = 0x80000000	l = 0x20000000	/* 512MB of external mDDR in CS0 */
    CS1_SDRAM:  o = 0xA0000000  l = 0x20000000	/* 512MB of external mDDR in CS1 */

/* DM3730 EVM */
    FLASH:      o = 0x20000000  l = 0x10000000  /* 256MB of external NAND FLASH */
}

SECTIONS
{
	.text          >  CS0_SDRAM
	.stack         >  CS0_SDRAM
	.bss           >  CS0_SDRAM
	.cio           >  CS0_SDRAM
	.const         >  CS0_SDRAM
	.data          >  CS0_SDRAM
	.switch        >  CS0_SDRAM
	.sysmem        >  CS0_SDRAM
	.far           >  CS0_SDRAM
  .args          >  CS0_SDRAM
	.ppinfo        >  CS0_SDRAM
	.ppdata        >  CS0_SDRAM

  /* TI-ABI sections */
	.pinit         >  CS0_SDRAM
	.cinit         >  CS0_SDRAM

  /* EABI sections */
  .binit         >  CS0_SDRAM
	.init_array    >  CS0_SDRAM
  .neardata      >  CS0_SDRAM
	.fardata       >  CS0_SDRAM
	.rodata        >  CS0_SDRAM
	.c6xabi.exidx  >  CS0_SDRAM
	.c6xabi.extab  >  CS0_SDRAM
}

 

 

  • Hi,

    If I understood correctly, you are trying to load ARM code to your device when u-boot already started running and you halted it in autoboot, right?

    In this case, if your hello application was built with TI's ARM compiler or GCC Baremetal, you need to completely prevent u-boot from running, use a GEL file to initialize the hardware and then load your code. U-boot performs hardware initialization that may not be compatible with your hello application.

    If your hello application was built with GCC for Linux, then you need to let Linux boot and then run a debug session according to the Run Mode debug of the CCSv5 Linux Debug page.

    Hope this helps,

    Rafael