OMAP2420 Driver

H4 Configuration and Emulator Startup:

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

You can verify the basic connection of the emulator to H4 board using

SdConfig.

1) From the SdConfig select your emulator (either 0x378 or 0x510).

2) Then do an Emulator->Reset.

3) Then do Emulator->Test. By default the OMAP2420 should assume the

default configuration of:

11 Ir bit length and 3 devices in the scan chain.

At this point the TCK to the OMAP2420 and RTCK from OMAP2420 should

be less then 1.5Mhz. OMAP2420 requires a slow TCK on startup just like

other OMAP devices.

4) At this point you should be able to connect to the OMAP2420 with ARM11

default configuration. Testing has shown that OMAP2420 has similar

startup issues as other OMAP devices when running from unprogrammed

FLASH or uninitialzed memory. The typical failure mode is error -2072

and -1152. Error -2072 occurs when the emulator cannot halt the ARM11.

Error -1152 generally occurs when TCK/RTCK has glitched or completely

gone away. In general a H4 reset will cure the problem and they retry

CCS.

5) Once CCS is started then ARM11 watchdog should be disabled as it can

cause RTCK to go away or glitch if it triggers a reset. The watchdog

should also be disabled following an ARM11 reset from CCS. The

ARM11 reset in CCS is now a hardware warm reset vs a psuedo software

reset as on ARM9/ARM7. This reset, resets the watchdog and it needs

to be disabled again. This can be handled automaticly from .gel with

use of the OnReset() gel function.

Known H4 HW Issues:

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

1) The H4 board does not include pullup resistors on the EMU0/1 pins

of the JTAG header. Testing has shown that these pins may not always

float high to put the OMAP2420 in emulation mode. You can generally

see this problem using SdConfig Emulator->Test. Two most common

failures show up as an IrLength of 8 or 2 and and 1 device in the

scan chain. If this occurs you may be able to clear with a hardware

reset to the H4 board. If the problem persists then you generally

have to remove the JTAG cable and maybe even the USB cable on the

XDS510USB. Adding pullups on EMU0/1 of 4.7K-10K clears this problem

and significantly reduces the "halt" failures (CCS error -2072).

2) TCK noise has been seen when running SDRAM tests. The general failure

mode is that CCS will just stop for no apparent reason, often without

reporting any errors. This problem is still under investigation but

adding a 12pf cap to TCK signal at R195 on the OMAP2420 CPU card seems

to cure the problem.

IcePick Configuration:

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

IcePick configuration is still being developed but basic support is

included via the utility IcePickConfig. This utility and the source

code can be found in the <CCS_Install_Dir>\sdjtag directory.

IcePickConfig takes two primary parameters, port address and config

mask.

Valid Port Addresses

-p 0x378,0x278,0x3BC ;Spi515

-p 0x510 ;xds510usb

Valid IcePick masks

-t 0x03 ;IcePick+ARM11+ETB default config on power up

-t 0x07 ;IcePick+ARM11+ETB+C55

-t 0x47 ;IcePick+ARM11+ETB+ARM7

If you wish to use IcePickConfig then you should first configure

CCS via cc_setup for your scan chain config. Then run IcePickConfig

with corresponding mask. IcePickConfig will read the ccs board

config file and verify that minimal enable requirements have been

met.

The OMAP2420 device looses it's IcePickConfig after a power cycle,

hardware reset, emulator reset or TMS=1 for 5 TCK cycles (trst state).

So if you are using anything other then the default config you should

run IcePickConfig prior to starting CCS.

A couple of shortcuts have been setup as an example for the XDS510USB.

You will probably have to edit these to get the proper path for your

install.