TMS320F28384D: JTAG debugger memory access issue

Hi Inno,

Is this issue with CPU1 or CPU2 ? Also with JTAG Debugger connected, can you check the value in GSxMSEL register using CCS register view ? 

Regards,

Vivek Singh

Hi Vivek,

Sorry that I forgot to mention. This issue is with CPU1.

Checked with JTAG Debugger connected, using CCS register view, all bits of GSxMSEL register are 0. Actually, the value of all MemCfgRegs registers is 0.

By the way, please note that GSxMSEL does not appear in table 3-245 (MEM_CFG_REGS Registers) on section 3.14.11 (page 450) of the Technical Reference Manual (SPRUII0C). Also the description of GSxMSEL register does not exist on the sections following that table.

Regards,

Inno.

HI,

Are you seeing this issue on multiple boards ? Also are you able to read correctly from GS2 RAM  ? 

Also can you check the value at address location 0x5D070 ?

inno said:

By the way, please note that GSxMSEL does not appear in table 3-245 (MEM_CFG_REGS Registers) on section 3.14.11 (page 450) of the Technical Reference Manual (SPRUII0C). Also the description of GSxMSEL register does not exist on the sections following that table.

Yes, we are aware of this issue and it'll be fixed in next document release.

Regards,

Vivek Singh

Hi,

We see this issue on multiple boards. It is the same when working with an evaluation board (TMS320F28388D device and XDS100v2 USB Debug Probe) and with our target (TMS320F28384D device and XDS100v3 USB Debug Probe).

I am able to read correctly from GS2 RAM. Furthermore, if I suspend the debugger, I am able to manually write to GS2 RAM via the Memory Browser view in CCS.

I am not sure, but it seems that CCS uses GS2 RAM for firmware download, and the last firmware download data in GS2 RAM remains also when my application runs.

The value at address location 0x5D070 is 0 (read from both CPU1 and CPU2).

Regards,

Inno.

Hi,

inno said:

The value at address location 0x5D070 is 0 (read from both CPU1 and CPU2).

This value does not look correct. Can you please double check this ? Also can you read this location value from application when there is no issue ?

Regards,

Vivek Singh

Hi,

Evaluation board (TMS320F28388D device and XDS100v2 USB Debug Probe):

Issue exists.

Snapshot of CCS Memory Browser view of CPU 1:

Our target (TMS320F28384D device and XDS100v3 USB Debug Probe):

Issue does not exists.

Snapshot of CCS Memory Browser view of CPU 1:

Our target without Debug Probe:

Issue does not exists.

I can't provide CCS memory snapshot because the debug probe is not connected.

When my application reads memory location 0x5D070 using "*(int *)0x5D070" it reads 0.

Regards,

Inno.

Sorry, I was providing you the x8 (byte) address instead of x16. Can you check address 0x5D038.

inno said:

Our target (TMS320F28384D device and XDS100v3 USB Debug Probe):

Issue does not exists.

Snapshot of CCS Memory Browser view of CPU 1:

It says, issue does not exist with your target. Is that correct ?

inno said:

I am not sure, but it seems that CCS uses GS2 RAM for firmware download, and the last firmware download data in GS2 RAM remains also when my application runs.

Yes, debugger does use GSx RAM for code download but if you are not invoking debugger to load the code, it should not matter. May be you can list the step you are following when you see this issue.

Regards,

Vivek Singh

Hi,

Evaluation board (TMS320F28388D device and XDS100v2 USB Debug Probe):

Issue exists.

The value at address 0x5D038 is 0xFFFF.

Snapshot of CCS Memory Browser view of CPU 1:

Our target (TMS320F28384D device and XDS100v3 USB Debug Probe):

Issue exists. Last post (yesterday) I reported that the issue does not exist for this configuration. Maybe yesterday I did something in different order, but I can't think of such. I am sorry that yesterday I didn't repeat this test few more times to see if the "issue does not exist" is consistent.

The value at address 0x5D038 is 0xFFFF.

Snapshot of CCS Memory Browser view of CPU 1:

Our target without Debug Probe:

Issue does not exists.

When my application reads memory location 0x5D038 using "*(int *)0x5D038" it reads 0xFFFF.

  Here is the steps I am following when I see this issue:

- Build the project in CCS (CPU1 and CPU2).

- Connect to target and load program to flash, CPU1 then CPU2.

- Run both CPUs (CPU1 first).

- Instruct my application to collect data and write it to RAM.

- Send this data over SCI to a PC and analyze it (print a graph).

- The part stored in GS2 RAM is fixed and is not the data stored by the application. The part stored in GS3 RAM is Ok.

Regards,

Inno.