• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Subscribers 83 subscribers
  • Views 2752 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.

F28377D Delfino Experimenter Kit

user4565873
Expert 1250 points
Other Parts Discussed in Thread: TMS320F28377D, CONTROLSUITE

Hello!

Is there a possibility to wire an external parallel interface on this F28377D Delfino Experimenter Kit?

Would you have typical hardware wiring scheme ? (16 bits data on EMI1F with CS, OE and WE connected.) 

What is the clock frequency of the Kit ?Is it possible to modify it?

Thank you!

  • 0
    Guru 192875 points
    Hi,

    Check the datasheet and experimenter kit's pinout for pin availability. Wiring schemes are discussed in the Technical reference manual of the device. This mcu's clock frequency is 200MHz and can be very well configured lower.

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    TI__Guru 57255 points

    Hi,

    You could wire up the pins on the Experimenter's kit to an external memory.  The design wasn't specifically designed to make this an easy task - but it was designed such that the EMIF1 signals go from the MCU to the baseboard.

    I would recommend referring to the EMIF section of the TRM, as Gautam suggests, for help in defining the interface between the C2000 and its memory.  The TRM gives physical implementation examples.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Expert 1250 points

    Thank you i find out all i needed on the  parallel interface.

    I m now experiencing problems with ePWM interface visualing on oscilloscope.

    From " epwm_deadband_c28.c

    // TITLE: Check PWM Dead-Band"

    //During the test, monitor ePWM1, ePWM2, and/or ePWM3 outputs

    //! on a scope.

    //!

    //! - ePWM1A is on GPIO0

    //! - ePWM1B is on GPIO1

    //! - ePWM2A is on GPIO2

    //! - ePWM2B is on GPIO3

    //! - ePWM3A is on GPIO4

    //! - ePWM3B is on GPIO5

    I cant find pins GPIO0 to GPI05 are not available on this control card kit.

    I set the ePWM pins to be on pins GPIO145 to GPIO150 as stated in TMS320F28377D documentation.

    I dont see any life on the pins. Any idea why? 

    (other examples programma with SCi or blinking lights, ADC are working perfectly.)

    Thank you.

  • 0 in reply to user4565873
    TI__Guru 57255 points

    Hi,

    On this kit, the numbers on the Docking Station baseboard silkscreen do not align with the C2000 device's GPIO numbers or the C2000's pin numbers.  Instead it matches with the connector's pin numbers.

    GPIO00 - GPIO05 therefore do go to the baseboard. 

    I'd recommend taking a look at the below document to help you figure out the mapping:
    \controlSUITE\development_kits\~controlCARDs\TMDSCNCD28377D_v1_4\R1_1_A\TMDSCNCD28377D_180cCARD_pinout_R1_1.pdf


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Expert 1250 points
    Thank you!

    I sorted out my pin allocation and now everything works fine (was already working fine but couldn't see on oscilloscope)...

    I have one more question:
    How is the clock provided on the Kit ? external or internal oscillator ? if external, what is the frequency?

    Thank you.
  • 0 in reply to user4565873
    TI__Guru 57255 points

    Hi,

    The clock initialization code can be found in SysCtrl.c:
    \controlSUITE\device_support\F2837xD\v180\F2837xD_common\source\

    By default, we use the external crystal located on the controlCARD.  You could also use the internal oscillator if you change the software.

    The crystal on the cCARD is 20MHz, as seen in the schematics:
    \controlSUITE\development_kits\~controlCARDs\TMDSCNCD28377D_v1_4\R1_1_A\
    (20MHz * 20 / 2 = 200MHz)


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Expert 1250 points

    Hi,

    Finally ready with wire and experiment card (resolver) connected to my external interface. (cf discussion above)

    I experiment an unlikely problem: all my interface is EMIF1 but the pin 31 EM1WE_n is also connected to a LED.

    It seems to prevent my pin 31 (write pin) from behaving as required: the level seems to be stuck at 3v whereas it should be driven from 0 to 3 and opposite to pin EM1OE_n (read pin). 

    - Could you provide me with a HW solution to remove the LED?

    - Would you have any idea with a software workaround using EMIF1 ? 

    - Is it possible to drive the pin low when reading and high when writing?

    Thank you!

     

  • 0 in reply to user4565873
    TI__Guru** 113745 points

    Hi,

    Having LED connected to WE pin should not make it stuck at one value. It could impact the timing based on the load but should still toggle during write operations. I would suggest to check the pinmux setting to make sure the pin has been configured as EMIF pin.

    - Is it possible to drive the pin low when reading and high when writing?

    No, WE pin is for write operation only. You have to use RNW pin for that but it will be driven high during READ and low during WRITE operation (opposite of what you are looking for).

    Regards,

    Vivek Singh

  • 0 in reply to user4565873
    TI__Guru 57255 points

    Hi,

    The LED circuitry attached to GPIO31 should NOT affect the state of GPIO31 - it should not load GPIO31. 

    The LED should merely be driven high or low depending on the status of GPIO31.

    ===

    My best recommendation for debugging what you are seeing is for you to try configuring GPIO31 as a GPIO Output.  With this setup you can prove that GPIO31 can go high or low depending on how you configure its registers (in a relatively simple system).  This will help you prove out the hardware and the connectivity. 


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Expert 1250 points
    Hello i definitely think problem is in my code...

    Here s how i intend to start the EMIF interface:

    Clock:

    CpuSysRegs.PCLKCR1.bit.EMIF1 = 1;
    ClkCfgRegs.PERCLKDIVSEL.bit.EMIF1CLKDIV = 0x0;

    EALLOW;
    ///Grab EMIF1 For CPU1
    Emif1ConfigRegs.EMIF1MSEL.all = 0x93A5CE71;
    if (Emif1ConfigRegs.EMIF1MSEL.all != 0x1)
    {
    ErrCount++;
    }

    //Disable Access Protection (CPU_FETCH/CPU_WR/DMA_WR)
    Emif1ConfigRegs.EMIF1ACCPROT0.all = 0x0;
    if (Emif1ConfigRegs.EMIF1ACCPROT0.all != 0x0)
    {
    ErrCount++;
    }

    // Commit the configuration related to protection. Till this bit remains set
    // content of EMIF1ACCPROT0 register can't be changed.
    Emif1ConfigRegs.EMIF1COMMIT.all = 0x1;
    if(Emif1ConfigRegs.EMIF1COMMIT.all != 0x1)
    {
    ErrCount++;
    }

    // Lock the configuration so that EMIF1COMMIT register can't be changed any more.
    Emif1ConfigRegs.EMIF1LOCK.all = 0x1;
    if (Emif1ConfigRegs.EMIF1LOCK.all != 1)
    {
    ErrCount++;
    }

    EDIS;


    EALLOW;
    //Configuration required for datasheet
    //Configure the access timing for CS2 space
    Emif1Regs.ASYNC_CS2_CR.all = (EMIF_ASYNC_ASIZE_16 | // 16Bit Memory Interface
    EMIF_ASYNC_TA_4 | // Turn Around time of 4 Emif Clock
    EMIF_ASYNC_RHOLD_3 | // Read Hold time of 3 Emif Clock
    EMIF_ASYNC_RSTROBE_7 | // Read Strobe time of 7 Emif Clock
    EMIF_ASYNC_RSETUP_3 | // Read Setup time of 3 Emif Clock
    EMIF_ASYNC_WHOLD_3 | // Write Hold time of 3 Emif Clock
    EMIF_ASYNC_WSTROBE_7 | // Write Strobe time of 7 Emif Clock
    EMIF_ASYNC_WSETUP_3 | // Write Setup time of 3 Emif Clock
    EMIF_ASYNC_EW_DISABLE | // Extended Wait Disable.
    EMIF_ASYNC_SS_DISABLE // Strobe Select Mode Disable.
    );


    Pin assignement: EMIF 1 with only 2 adresses line A0 and BA1

    for (i=31; i<=38;i++)
    GPIO_SetupPinMux(i,0,2);

    for (i=63; i<=85;i++)
    {
    if (i != 84)
    {
    GPIO_SetupPinMux(i,0,2);
    }
    }
    //setup async mode and enable pull-ups for Data pins
    for (i=69; i<=85;i++)
    {
    if (i != 84)
    {
    GPIO_SetupPinOptions(i,0,0x31); // GPIO_ASYNC||GPIO_PULLUP
    }
    }
    }


    Do you see any thing wrong in this setup?

    Thank you!
  • 0 in reply to user4565873
    Expert 1250 points
    Additional information to the previous question:
    Memory space definition:
    - cmd file:
    in "MEMORY"
    PAGE 1 : /* Data Memory */
    ....
    RAMGS3 : origin = 0x00F000, length = 0x001000
    EMIF_CS2 : origin = 0x010000, length = 0x000200 /* EMIF CS2 - data space */
    RAMGS4 : origin = 0x010200, length = 0x000800
    RAMGS5 : origin = 0x011000, length = 0x001000
    ....
    in "SECTIONS":
    RDC_SECTION : > EMIF_CS2, PAGE = 1

    in c file:
    #pragma DATA_SECTION(rdc_mode, "RDC_SECTION");
    volatile st_rdc_mode_settings rdc_mode;

    Any help is deeply appreciated...

    Thank you.
  • 0 in reply to user4565873
    TI__Guru** 113745 points
    Hi,

    The address specified for CS2 space in cmd file is incorrect. It should be "100000" instead of "10000" (one zero is missing).

    Please correct the same and that should fix the issue.

    Regards,
    Vivek Singh
  • 0 in reply to Vivek Singh
    Expert 1250 points
    Thank you very much.. Works perfectly!