TI E2E Community
Digital Signal Processors (DSP)
C6000 Single Core DSP
C64x Single Core DSP Forum
C6482 and AET
Does anyone know any good documentation about the access to AET-registers from a program, like the AETlib does?
I mean, there are probably J-TAG registers (or the like) somewhere in the HW that can be accessed "from the inside"?
How about a good document of how to use AETlib?
The idea is to implement memory protection for an address range thet cannot be covered by the megamodule memory protection.
I guess some exception can be triggered by AET if the protected region is accessed?
There is no C6482 device. If you mean the TCI6482, it is not supported through the forums but through your established marketing channels. Or do you mean the C6452?
If so, the information available on AETLIB is what you find from a search on TI.com. Some information is in the download package, some in the Wiki pages, and some on the product page on TI.com.
Search for answers, Ask a question, click Verify when complete, Help others, Learn more.
"If you mean the TCI6482..."
I thought AETlib and J-TAG-registers wouldn't be that device dependent:. C64x+ core with megamodule.
I thought the J-TAG-stuff would be pretty close to that of C6782.
I also thought that AETlib is common to quite many C6000 series devices. The info is just quite fragmented and spread around. I wondered if there was a document that contained it all (more or less).
We do not publicly expose JTAG registers. Of course, that depends on exactly what you mean and exactly which device.
The other thread you posted to was for the C6713 where you also mentioned the C6482 and now you mention the C6782, which implies floating point but is a part I have never heard of.
This is really not a place to talk about all emulation features of all C6000 devices, and no, AETLIB is not common to all C6000 devices. Yes, it is available for many, but we need to know what you are asking about and the more precise you can make the question the more likely you are to get the answer you want.
If you are using the TCI6482, you have a specific support path and very capable people to help you there.
I am at a loss of what to add for your underlying question, which is documentation for AETLIB. Have you searched TI.com and the Wiki for AETLIB? You will find all the available information there, and it seems pretty good, at least to me. AETLIB does what you seem to be asking, so I am at a loss how to add more to that.
Please help me figure out what you need by telling us what is missing from the AETLIB and its documentation.
Well, my device is TCI6482, but I recall there was a commercial version of it, some 67xx device (can't remember which), and I think the AET/JTAG is probably very similar.
The thing is: I need the AET to implement memory protection. It should work without any JTAG debuggers. I understand there is no other way to trap null-pointer references.
Also, if I implement the protection using AET, can I use JTAG debugger at all (for loading and starting programs)?
I was also wondering if I could do that without AETlib.
Please be aware that 1) the TCI6482 is not supported through the forums but through your established marketing channels (if you need help with those contacts, please go to your TI salesperson, or friend me so we can start a conversation about your company situation), and 2) the AETLIB and emulation are best supported in the Code Composer Forum.
The E in AET is emulation, so I am not sure if the AETLIB works without emulation, but I suspect it does. Use of AETLIB will not affect your ability to do anything else with your JTAG emulator, except that you cannot use the same AET resources at the same time.
Do the C64x+ Exceptions give you what you are looking for? These are described in the Megamodule Reference Guide.
Unfortunately the Megamodule HW only protects the actual internal memory - the cache region. Not the "reserved" areas.
Also I've been waiting our "TI sales person" to respond to my questions, but for some reason it's been quiet. The guys typically answer in the same day.
Those same guys told me that protecting the beginning of the memory space (null-pointer trap) is only possible with AETlib.
We apologize that you have not had the response time that you wanted from the local TI team. They are the right path for your support for a TCIxxxx device; getting clear communication on what you need and what is available is much easier that way.
On this thread, for example, we have gone full circle twice now, back to you having current direction to use the AETLIB and you are looking for documentation on AETLIB. I assume you have the AETLIB documentation which is included with the AETLIB download, and that is what we have available for you. To learn more about how the AET resources are used, I will recommend that you use the CCS-based commands to configure the AET and test the functionality that you want to have. Once you have it working through the CCS menus, you will know that the required resources will be available through AETLIB also.
The C64x+ Megamodule's Exceptions are not the same as the Memory Protection provided for the internal memories. There may be features of the C64x+ Exceptions that will help with what you are trying to do.
"We apologize that you have not had the response time that you wanted from the local TI team."
No need, they are usually very quick and very helpful. I guess Mayday may have some affect... :-)
The problem is HW that could detect "illegal address range" data access (and maybe generate an exception).
About the exceptions: I'm somewhat familiar with the exceptions having to write an exception register context saving routine as a wedge to the actual exception handler.
I guess you gave me the answer:
" I assume you have the AETLIB documentation which is included with the AETLIB download, and that is what we have available for you. "
I just thought that there might be some application note or something about the AETlib, or some other document about the JTAG SW interface.
BTW, can AETlib be used in commercial software?
BTW, can AETlib be used in commercial software?
Aha, the local people are back in business. I got some answers.
So the AET HW interface is not for customers, but to be used only via CCS or AETlib.
Also, the documentation is essentially the doxygen-stuff and some example code (except for some specific stuff, like profiling).
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.