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.

Can't see external memory on SMJ320VC5416 using CCS 5.5

Other Parts Discussed in Thread: SMJ320VC5416

I have an SMJ320VC5416 and I am using CCS 5.5 (since CCS 6 doesn't support the C54XX line). I am unable to access external memory, only internal memory. I have the original C5416.gel file, which did not work, and I tried adding additional memory mapped locations. The CCS memory browser just shows these as a series of ????'s

  • Hi,

    If you added the proper GEL_MapAdd() routines, is sure there is physical memory at these addresses and properly set the OVLY and MP/MC registers, I imagine the only thing that may be happening is a misconfigured external memory interface. The GEL files for the C54x devices do not perform any configuration of the EMIF, therefore I wonder if this is preventing the debugger from properly reading anything at these addresses.

    Unfortunately I don't have a C5416 board with me to double-check these details, but I imagine the experts at the C5000 device forum will know a lot more about this device and its proper configurations. You may want to post there and see if they have any additional comments.

    Sorry for not being of much help,
    Rafael
  • Mike - are you using the C5416 DSK or custom board? If it is the DSK, you can get the gel file for that board from Spectrum Digital
    c5000.spectrumdigital.com/dsk5416

    Thanks
    ki
  • It's a custom board. We have two SMJ320VC5416's attempting to communicate with external memory. Each processor has it's own dedicated external memory, and there is also shared memory that they can both access.

  • With a custom board, you will need to use a custom gel file, one that is properly configured for your target. See this old App note:
    www.ti.com/.../litabsmultiplefilelist.tsp

    It is old and refers to old versions of CCS, but the section on setting up the memory map is still relevant.

    Thanks
    ki