Quantcast
Channel: Tools
Viewing all articles
Browse latest Browse all 91752

Forum Post: Trouble Writing Memory Block at 0x4c0000e8 when connecting CortexA9_0 on Pandaboard ES

$
0
0

When I lauched my target configuration and try to connect the CortexA9_0, the below errors are shown.

CortexA9_0: GEL Output: --->>> omap4460_startup_sequence <<<---
CortexA9_0: GEL Output: --->>> ------------------------------------------------------------------
CortexA9_0: GEL Output: --->>> OMAP4460 ES 1.1 Device <<<---
CortexA9_0: GEL Output: --->>> GP device <<<---
CortexA9_0: GEL Output: Reconfigure PSRAM for accessing if device type = GP
CortexA9_0: GEL Output: --->>> BANDGAP trimmed <<<---
CortexA9_0: GEL Output: Set system clock to 38.4MHz
CortexA9_0: GEL Output: --->>> start FORCE VCORE1, VCORE2 and VCORE3 to 1010mV <<<---
CortexA9_0: GEL Output: --->>> PHOENIX RELEASE => (0x02), EEPROM => (0x24) <<<---
CortexA9_0: GEL Output: --->>> PHOENIX RELEASE => (0x02), EEPROM => (0x24) <<<---
CortexA9_0: GEL Output: --->>> end FORCE VCORE1, VCORE2 and VCORE3 to 1010mV <<<---
CortexA9_0: GEL Output: searching... memory type
CortexA9_0: GEL Output: found... memory type = (24)
CortexA9_0: GEL Output: --->>> !!!! UNKNOWN MEMORY (0x00000018), PLEASE RETRY or UPDATE GEL FILES !!!! <<<---
CortexA9_0: GEL Output: Memory name :0
CortexA9_0: GEL Output: >>OPP100_400CortexA9_0: GEL Output: >> Start emif_config
CortexA9_0: Trouble Writing Memory Block at 0x4c0000e8 on Page 0 of Length 0x4: (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)
CortexA9_0: GEL: Error while executing OnTargetConnect():Target failed to write 0x4C0000E8 at *((int *) register_address)=0x449FF418 [omap4460_ddr_config.gel:477] at emif_shadow_reg(OPP, emif_index) [omap4460_ddr_config.gel:434] at emif_config(CORE_OPP, 1, memoryType) [omap4460_ddr_config.gel:214] at ddr_config_top(2, memory_name) [omap4460_startup_common.gel:409] at omap4460_startup_sequence() [omap4460_startup_common.gel:62] at OnTargetConnect() .

I am using the  Version: 5.5.0.00077 and the JTAG emulator is XDS100V2, with TCLK is set "Adaptive with user specified limit" to 1.0Mhz.

Looks like some wrong with the address. My target is pandaboard ES and I have a flash with U-Boot. The autoboot is stopped before countdown is finished.  The bdinfo can also show the start address is 0x80000000, thus I guess there are something wrong with the DDR address int he GEL files, which are provided by the CCS. But I doubt that I need to manually modify the GEL files as these files should be prepared for Pandaboard ES as default, right?

This is what the target is shown on minicom console:

U-Boot SPL 2013.01.-rc1-00003-g43ee87a (Dec 25 2013 - 03:17:53)
OMAP4460 ES1.1
Bypassing DPLL failed 4a008180
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2013.01.-rc1-00003-g43ee87a (Dec 25 2013 - 03:17:53)

CPU : OMAP4460 ES1.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment

In: serial
Out: serial
Err: serial
Net: No ethernet found.
checking for preEnv.txt
reading preEnv.txt
** Unable to read file preEnv.txt **
Hit any key to stop autoboot: 0
Panda #
Panda # bdinfo
arch_number = 0x00000AE7
boot_params = 0x80000100
DRAM bank = 0x00000000
-> start = 0x80000000
-> size = 0x40000000
ethaddr = (not set)
ip_addr = <NULL>
baudrate = 115200 bps
TLB addr = 0xBFFF0000
relocaddr = 0xBFF81000
reloc off = 0x3F101000
irq_sp = 0xBFF00F68
sp start = 0xBFF00F58
FB base = 0x00000000
Panda #


Viewing all articles
Browse latest Browse all 91752

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>