I'm trying to use Code Composer to run the NANDEraser / NANDWriters on a custom DM368 board, but I am having trouble and need help. I am getting a "Data verification failed" error when I try to verify the Writer. I'm also new to Code Composer, so please bear with me.
Here's info about my system:
Development host OS - Ubuntu Linux, 10.04
Code Composer version - 5.3
Processor - DM368, custom board
JTAG - Spectrum Digital XDS200
The steps I'm using are:
- Connect to the custom board in the debugger
- Load the gel file "evmdm368.gel," which came with Code Composer
- Let the gel file run (yes, it is running Setup_Memory_Map)
- In Code Composer, select (from the menu bar) Run -> Load -> Verify Program, and browse to NANDWriter.out
After I select NANDWriter.out, I see this error in the console:
ARM9: File Loader: Data verification failed at address 0x8E000000 Please verify target memory and memory map.
If I try to Load the program rather than Verify it, I get this error:
IcePick_C_0: Error: (Error -2172 @ 0x0) Unable to communicate with the emulator. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.872.0)
And I see this in the Ubuntu console:
E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Send::dtc_io
E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Receive::dtc_io
E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Send::dtc_io
Is the problem with the JTAG connection? Running "Test Connection" with my .ccxml configuration yields no errors when I start up CCS. Is there a way I can use CCS to test or write to NAND directly, to see if it's set up correctly for writing? I found the Memory Browser, and I tried writing something to 0x8E000000, but I am not sure it worked.
(If I run the JTAG "Test Connection" after I have loaded the gel file, I also get the IcePick "unable to communicate with the emulator" error, but I don't know if running Test Connection at this stage is the right thing to do.)
When I searched the forums for the "data verification failed" error, most (if not all) of the posts said to make sure the gel file was setting up a memory map. When I'm in the debugger, if I select "Memory Map" from the Control Panel after I load the gel file, I can see memory address range 0x80000000 - 0x8FFFFFFF is listed as R|W|AS4.
Before we worked on this custom DM368, I had been working on a Spectrum Digital DM365EVM. When I followed the steps I outlined above to use the NANDWriter on the 365 (using an appropriate gel file, evmdm365.gel), I had no problems whatsoever with the NANDWriter.
Finally, if this matters, here is my Target Configuration:
Board Data File - auto generate
Emulator /O Port - 0
JTAG nTRST Boot-Mode - Enabled
Power-On-Reset Boot-Mode - Enabled
JTAG TCLK Frequency - Adaptive with user specified limit; value is 1.0MHz
JTAG Signals Isolation Upon Disconnect - Isolate
Apply nRESET/RST pin - Do NOT pulse
cJTAG Converter Features - by[assed, use 1149.1
Thanks!