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.

CCS/TMS320F28335: XINTF communication using zone 0

Part Number: TMS320F28335
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hi,

I want to use XINTF in zone 0 with 16-bit mode, can any help me how to initialize it(sample code) and how can I confirm it is accessing zone 0 area. 

With regards,

Sivakrishna

  • sigma sigma said:
    I want to use XINTF in zone 0 with 16-bit mode, can any help me how to initialize it(sample code) and how can I confirm it is accessing zone 0 area. 

    Refer to these examples.  They configure zone 7 and can be adapted to use zone 0 instead. 

    C:\ti\c2000\C2000Ware<version>\device_support\f2833x\examples\xintf_run_from

    C:\ti\c2000\C2000Ware<version>\device_support\f2833x\examples\dma_xintf_to_ram

    Refer to the XINTF users guide section on accessing zones.  Monitor the appropriate chip select when reading/writing to the zone. 

    www.ti.com/lit/SPRU949

    Regards

    Lori 

  • Hi Lori,

    Thanks for your reply, I tried myself with zone 0 it is working fine but now I have another problem which is while I am reading from and writing to an external device(memory) in full run mode some times data is varying, for example, if I write '0' I should read '0' but I am reading garbage value.

    Looking for your reply,
    With regards,
    Sivakrishna
  • Sivakrishna,

    It may be that the configured timing is too fast for the external memory + connections. Try setting the lead/active/trail times to their maximum to see if this resolves the issue. If it does, then timing is most likely the issue. The access time of the external device plus the XINTF timing requirements documented in the data manual have to be met.

    If this does not solve the problem, then I would check if there is any consistency or pattern to the garbage values or locations. This may point to a bad connection on the board for an address or data line. Monitoring signals and strobe lines may provide a clue.

    Regards
    Lori
  • Hi Lori,

    Thanks for your reply, Your guess is correct this is the problem with timings I changed the lead/active/trail times now it is working fine, But if I read 5 words from the memory first word is reading as garbage for some time reaming 4 words are reading without any error.

    With regards,
    Sivakrishna
  • Thank you for the note, Sivakrishna. It maybe that the reads which are correct are separated by some time due to the nature of the bus. For example, there are some alignment cycles with XCLKOUT that can occur and delay an access. Extending the trail may help. For writes I recommend at lest one trail cycle.



    Best Regards
    Lori
  • Hi Lori,

    The problem with only read operation writing to the memory is working fine, I changed lead/active/trail times for reading and writing operations with maximum value, I use delay(0x155) for each read cycle now it is working fine, But as per my application it is not recommended to use any delay in the application how can I solve this issue without using delay.

    Note: Delay function has a for loop with 0x155 value.

    With regards,
    sivakrishna
  • Sivakrishna,

    Have you analyzed the timing requirements of the external device you are accessing? Timings to look at in the datasheet are access time, setup time, hold time? Is there a READY ready line you should be using to determine end of access?

    Regards
    Lori