CCSTUDIO: v12.7

4657.N0139.gelThe N0139.gel  is a GEL file for custom HW. this is a project I inherited, It  was  originally developed on CCS3.3. I would like to port it to CCS v12.x which is the latest that I can tell.  I added the command you suggested to Init_PLL() but no luck, I get the same error. also upon looking closer at the N0139.gel the suggested command was being done already as well in C5502_Init() which was called before the Init_PLL().

Are there any app notes on how to use GEL files? I am reading the CCS Studio . user guide chapter 7.9 on GEL files but this is more a list of built in functions and what  they do, not how to use them properly start a new device in custom HW.

I added an updated GEL file

Thanks

Hi Michael,

I went through your GEL file, the customized parts are for EMIF and the flash or SDRAM attached to it.

Can you put the "C5502_Init();" in the first line of the OnTargetConnect(), before the "Init_PLL();"?

Best regards,

Ming

Same result, I moved the call to OnTargetConnect() as you asked, I get the same result. I also included the connection test result which seems good.

If I try to to run the commands manually from the scripting console here is what I get. the target device is programmed do I need to erase any programming before I try to setup the EMIF registers?  As I mention before i inherited this project so  I  still need to learn how this system works.

Can I remove the GEL file from the configuration will the debugger still work? 

Thanks for the help

js:> eval(' GEL_MapAdd(0x1C80u,2,0x0019u,1,1)')
0
js:> eval('*(short*)0x1c80@IO')
97
js:>

• From the N0139.GEL file :

StartUp()

{

}

OnTargetConnect()
{

C5502_Init();
Init_PLL();

Init_SED1335_5502CPUBoard();

.

.

.

• Result from the console

C55xx: GEL Output: C5502_Init Complete.
C55xx: GEL: Error while executing OnTargetConnect(): Memory verification failed at address 0x1C80
at GEL_MemoryFill(0x01C80, 2, 1, 0x08) [N0139.gel:213]
at Init_PLL() [N0139.gel:89]
at OnTargetConnect()
C55xx: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.

• Connection test result

[Start: Texas Instruments XDS2xx USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\mschmid\AppData\Local\TEXASI~1\
CCS\ccs1271\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Jul 24 2024'.
The library build time was '23:45:14'.
The library package version is '12.8.0.00189'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

This emulator does not create a reset log-file.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS2xx USB Debug Probe_0]

Hi Michael,

First of all, what is the boot mode of your custom board? 

If you are boot from some media other than the no boot mode, then you may be able to eliminate the GEL file from your target configuration. If you are using the no boot mode, the GEL is necessary for the DSP initialization.

From the display, it seems you have problems to access the PLL registers. Can you use the GEL file from the CCS 12.7.1 (C:\ti\ccs1270\ccs\ccs_base\emulation\gel\c5502.gel) to replace the N0139.gel?

Best regards,

Ming

we are booting from SPI Flash the pins are bootm[2:0] = 001b, I'm reading through the bootloader application report (SPRA911C) now to better understand what s is happening.

I try using the c5502.gel file it seems to work better but still with 1 EMIF register issue, and probably as expected external memory access issue 

C55xx: GEL: Error while executing OnReset(0): Memory verification failed at address 0x80D
at GEL_MemoryFill(0x80D, 2, 1, 0x4748) [c5502.gel:202]
at Init_CE0_SDRAM_5502CPUBoard() [c5502.gel:66]
at OnReset(0)
C55xx: GEL Output: C5502_Init Complete.
C55xx: GEL: Error while executing OnTargetConnect(): Memory verification failed at address 0x80D
at GEL_MemoryFill(0x80D, 2, 1, 0x4748) [c5502.gel:202]
at Init_CE0_SDRAM_5502CPUBoard() [c5502.gel:60]
at OnTargetConnect()
C55xx: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.
C55xx: File Loader: Verification failed: Values at address 0x600000@DATA do not match Please verify target memory and memory map.
C55xx: GEL: File: C:\Users\mschmid\workspaceCCS_v12\N0139\OutPut\N0139.out: a data verification error occurred, file load failed.

If I eliminate the GEL file this is what I get.

C55xx: Trouble Writing Memory Block at 0xbc36 on Page 0 of Length 0xe09: (Error -1023 @ 0xBC34) Requested JTAG operation failed. 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 12.8.0.00189)
C55xx: File Loader: Verification failed: Target failed to write 0x00BC36@PROGRAM
C55xx: GEL: File: C:\Users\mschmid\workspaceCCS_v12\N0139\OutPut\N0139.out: Load failed.

Hi Michael,

Can you change the boot mode to "NO BOOT" ( bootm[2:0] = 000b), then use the N0139.gel or c5502.gel?

Best regards,

Ming

I can try. This will take a few days as these values are hard wired in the schematic. I'll get back to you on the results.

Hi Michael,

The other way to try the "no boot mode" is to erase the boot image in SPI EEPROM (write zeros to the EEPROM). This way, it can save from your HW changes.

Best regards,

Ming