• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 230 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

TMS320F2812: Whether the firmware support / code change is need for fusing the NFBGA code into LQFP pack of TMS320F2812 ...

TMS320F2812: TMS320F2812 technology

Links
Genius 13000 points
Part Number: TMS320F2812


Dear TI experts，

Our customers has question below

In the case of using JTAG online debugging, if the internal RAM of TMS320F2812 is insufficient, can the code be transferred to the extended external SRAM memory?

Search on the Internet to get some examples. You can allocate the .text segment to the external extension SARM in the .CMD file. Usually, you need to set the EINTF interface, but when downloading the code using JTAG, the code has not yet started to run, then Is it possible for the compiler to extract the parameters of the EINTF initialization in the code ahead of time, and is there such a mechanism?

How to implement JTAG online debugging in the external extended SRAM, can you download the method or example routine recommended by TI?

 

I hope the above three questions can be answered, thank you.

Best regards,
William
Texas Instruments | Customer Support Center

  • 0
    TI__Guru* 81920 points

    William,

    You can do what you have described, using the external interface(XINTF) to access an external SRAM.  We can initialize this on emulation connect by adding the appropriate instructions to the GEL file in the On_Reset command.  I'm attaching the implementation for the F28335 device, which should be very similar to the F2812.  Customer would need to check the addresses of the registers and configure the settings they want for the external bus.

    The GEL file for the F2812 should be located in this relative path depending on the CCS version the customer is using. Below is for CCSV11

    C:\ti\ccs1100\ccs\ccs_base\emulation\gel\F2812.gel

    3463.f28335.gel

    Once this is incorporated, on a reset it will configure the XINTF so that code can be loaded as normal with CCS.

    Best,

    Matthew