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.

Configuration DM6437 via PCI

Other Parts Discussed in Thread: TMS320DM6437

Dear all:

Recently,I use  the TMS320DM6437 EVM.

I want to access on-board DDR2 via PCI but I always fail it.

I figure out I need to configure the dm6437.

Because I  can configure dm6437 via CCS.

But I don't know how to configure the dm6437 via PCI.

Can I configure the device via PCI??

If not,How did I suppose to do??

 

 

  • Dennis Su said:

    Because I  can configure dm6437 via CCS.

    But I don't know how to configure the dm6437 via PCI.

    When you mention configuring the TMS320DM6437 via CCS, would you please elaborate on what it is you are doing?  Is this simply via established GEL scripts that are being used to configure the TMS320DM6437 DDR2 interface?  Or is this a program that you are downloading to the target and running?

    Regardless, the initialization that is being performed, either from a GEL script or from a program downloaded and run, will need to be mimicked over the PCI interface.

    Dennis Su said:

    Can I configure the device via PCI??

    If not,How did I suppose to do??

    Yes, the TMS320DM6437 datasheet does indicate the DDR2 controller can be accessed via the PCI interface.  Table 4-1 in the datasheet indicates the PCI slave interface acts as a master on the switched central resource 1 to access the DDR2 controller as a slave on the SCR1.  Therefore, the host accessing the TMS320DM6437 via the PCI interface will need to initialize the DDR2 controller appropriately before any data can be written into the DDR2 memory.

  •  

    BrandonAzbell said:

    When you mention configuring the TMS320DM6437 via CCS, would you please elaborate on what it is you are doing?  Is this simply via established GEL scripts that are being used to configure the TMS320DM6437 DDR2 interface?  Or is this a program that you are downloading to the target and running?

    I used the pci example program and I change 0x10800000UL to 0x80000000UL for accessing DDR2 DRAM.

    Once I established GEL scripts,I could access DDR2 DRAM sucessfully.

    BrandonAzbell said:

    Regardless, the initialization that is being performed, either from a GEL script or from a program downloaded and run, will need to be mimicked over the PCI interface.

    So I can initialize the TMS320DM6437 EVM over the PCI interface,right??

     

     

     

  • Dennis Su said:

    So I can initialize the TMS320DM6437 EVM over the PCI interface,right??

    As I mentioned before, the TMS320DM6437 datasheet in Section 4 discusses the internal interconnect of the device.  The PCI slave interface, which is what is responding to your external host device, has access to the following modules based on information in Table 4-1, the C64x+ SDMA, the DDR2 memory controller, SCR4, SCR2, SCR6, SCR7 and SCR8.  The footnote indicates if a master peripheral/module has access to a particular switched central resource (aka. SCR), then it has access to the peripherals/modules connected to those respective SCRs.

    This means you can initialize all peripherals which are connected to the above SCRs, including the PLLs, GPIO, DDR2 controller registers and memory, etc.  You would not have access to the C64x+ CPU itself, but the code that you load into the device should be responsible for initializing the C64x+ CPU.

  • Got it.

    Thanks for helping.