CCS/TMS320C6727B: 16 bit EMIF write produces 2 WE signals

Hi Dave,

David Hollingsworth1 said:

When using CCS to do the same write

How are you doing this write with CCS? Are you using one of the views (Memory Browser, Expressions, etc) or via GEL or some other method?

Thanks

ki

Memory browser.

Can you provide a screenshot of the memory browser view when you are trying to do the memory write? I'd like to see how the view is formatted.

Also provide the following information:

- the exact CCS version being used

- the debug probe being used

Thanks

ki

CCS V5..5.0.00077

Spectrum Digital XDS560v2 STM

Screenshot:

16 bit write under program control – single EM_WE, EM_BA1 high.

16 bit write under CCS debugger – double EM_WE, EM_BA1 low then high.

Thank you.

And finally, can you enable debug server logging and reproduce the issue?

https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html#debug-server-logs

We just need the log for when you attempt to write to memory from the memory browser view

ki

Thanks David. I have escalated this to the engineering team for further analysis. I will keep you updated as soon as I get them.

ki

Ki said:

Thanks David. I have escalated this to the engineering team for further analysis. I will keep you updated as soon as I get them.

ki

Ki,

It has been over a week, do you have any update for me?  This is impacting a qual test for Honeywell.

When operated under program control the writes are performed as single accesses.  It is imperative that we be able to demonstrate that the debugger is able to demonstrate the same signal characteristics.  We are attempting to demonstrate for the DO 254 certification effort.

Thanks,

Dave

Hi Dave,

My apologies for the long delay.

The engineering team suggested explicitly specifying the access size as 16-bit for that address range in the debugger memory map. You can do this by using the AS2 attribute. See the CCS Help for more information (Code Composer Studio Help > Tasks > Automating Tasks with General Extension Language (GEL) > Built-In GEL Functions > List of Built-In GEL Functions -> GEL_MapAddStr() )

You can specify this in your startup GEL file. If you are not using a gel file, you can do this from the Scripting Console with something like the below command:

js:> eval('GEL_MapAddStr(0x10000, 0, 0x2000, "R|W|AS2", 0 );')

The above example is specifying a memory range with a start address of 0x10000 with length of 0x2000, being readable/writeable with an access size of 2 bytes.

Please let me know if this helps at all.

Thanks

ki

Yes, we have tried it with the above GEL function, but to no avail.  The debugger still produces the same signal pattern.  The specified address and range are reported in the "Memory" window but the behavior is the same.

Dave

Just to confirm, you see the AS2 attribute for the memory range?

Yes, that is correct.  I will get a screen shot on Monday.  The start address is in EMIF space starting at 0x9000 0000.

Dave

Thanks for confirming. We suspect that the issue is with the C6x driver and not the debugger itself. We are trying to confirm 

This is the code:

GEL_MapAddStr(0x90000000, 0, 0x10000000, "R|W|AS2", 0);   //16 bit FLASH

The debugger team has analyzed the issue and it is likely an issue with the driver. I will escalate this to the driver team.

What is the exact version of the TI Emulators component that your CCS installation is using? You can check by going to 'Help -> About Code Composer Studio -> Installation details'

Also, note that CCSv5.5 is very old and unsupported. Any chance you can give CCS v10 a try? Even if you need to stick to CCSv5.5 for your development, can you also install CCSv10 (in a completely separate location) and see if that version also exhibits the same issue?

Thanks

ki

5.1.232.0

Thanks David. Any chance you can give CCSv10 a try?

I believe we have installed 8 but haven't gotten it up and running yet.  Received an error message about supporting the tools.  I'll have to get more detail.

Dave

If you can try v10, that would be very helpful. If can just launch the debugger, connect to the target, and access memory in question while monitoring with the scope like you were doing with 5.5

Our test computer is running a 32-bit version of Windows.  Looks like 8 is as high as we can go.

understood. thanks.

David Hollingsworth1 said:

Looks like 8 is as high as we can go.

If you do get CCSv8 going, please update the TI Emulators pack to 8.4.0.00006 (the latest version for CCSv8).

Thanks

ki