• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 214 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28075: EMIF - CS3 - Running code from 2x16bit SRAM or one 32Bit SRAM. I'm a little confused.

Peter Adamcik
Prodigy 120 points
Part Number: TMS320F28075

Tool/software:

Hi Guys. I've just started learning about the EMIF. The datasheet says CS3 code+data 512k x16. This is good for my project.

I'm a little confused, the datasheet says 512k x16bit but the EMIF can support 32bit data (EM1D0 to EM1D31). Does this mean that I have to use 2x 512k x16bit SRAM chips ( one for high word and one for low word) for 32bit code + data or just one 32bit sram chip for code + data.

DATA SHEET SAYS THIS:

EMIF1_CS3n - Program + Data 512K × 16.  Starting address: 0x0030 0000 to 0x0037 FFFF

Can you please let me know which one I should use.

Thanks guys, have a great day or night and hope to hear from you soon.

Peter Slight smile

  • +1
    TI__Guru**** 192196 points

    Hi Peter,

    Peter Adamcik said:
    Does this mean that I have to use 2x 512k x16bit SRAM chips ( one for high word and one for low word) for 32bit code + data or just one 32bit sram chip for code + data.

    No, you can use one 32-bit SRAM. The memory size is up to 512KBytes (from 0x30_0000 to 0x38_0000). The x16 in 512KB x 16 is related to the architecture of C28x CPU core. The smallest instruction/data length for C28x devices is 16-bit word.

    The EMIF address pin EM1A[0] always provides the least-significant bit of a 32-bit word address. Therefore, when interfacing to a 16-bit asynchronous memory, the EM1BA[1] pin provides the least-significant bit. Please refer to EMIF chapter of the device TRM.

  • 0 in reply to QJ Wang
    Prodigy 120 points

    Thank you so much QJ Wang for the info, I totally understand now.

    Peter :)