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.

TMS320F28377S: Request for Advice on SCI Baud Rate Issue with TMS320F28377S

Part Number: TMS320F28377S
Other Parts Discussed in Thread: C2000WARE, SYSCONFIG

Hello.

I am currently working with the TMS320F28377S (176-pin package) using C2000Ware_6_00_01_00 and TI CCS. 
Since syscfg does not support the 176-pin package, I am configuring the code manually.
I have connected SCID Rx (GPIO46) and SCID Tx (GPIO47) to a PC at 115200 bps, 8N1. 
However, when I attempt to output debug messages, there is no response in Tera Term. 
Interestingly, when I set Tera Term’s baud rate to 57600, the data is displayed correctly.
This leads me to believe that the clock configuration may not be set properly. 
Could you please provide guidance or advice on how to resolve this issue?

Thank you very much for your support.

Best regards, 
sjkim

 

------------------ my test code -------------------
void initSCID(void)
{
    // (1) Mux
    GPIO_setPinConfig(GPIO_46_SCIRXDD); 
    GPIO_setPinConfig(GPIO_47_SCITXDD);

    // (2) In/Out
    GPIO_setDirectionMode(46, GPIO_DIR_MODE_IN); 
    GPIO_setDirectionMode(47, GPIO_DIR_MODE_OUT);
    
    // (3) Pad
    GPIO_setPadConfig(46, GPIO_PIN_TYPE_PULLUP);
    GPIO_setPadConfig(47, GPIO_PIN_TYPE_STD);
    
    // (4) Qualification
    GPIO_setQualificationMode(46, GPIO_QUAL_ASYNC);
    GPIO_setQualificationMode(47, GPIO_QUAL_ASYNC);
    
    SCI_disableModule(SCID_BASE);

    SCI_enableFIFO(SCID_BASE);
    SCI_resetChannels(SCID_BASE);
    
    // 115200 Baud Rate, 8N1
    SCI_setConfig(SCID_BASE, DEVICE_LSPCLK_FREQ, 115200, (SCI_CONFIG_WLEN_8 | SCI_CONFIG_STOP_ONE | SCI_CONFIG_PAR_NONE));

    SCI_enableModule(SCID_BASE);
    
    //SCI_enableInterrupt(SCID_BASE, SCI_INT_TXFF); 
}

void initSystemClock(void)
{
    InitSysCtrl();
    InitGpio();

    DINT;

    InitPieCtrl();

    IER = 0x0000;
    IFR = 0x0000;

    InitPieVectTable();
}

void main(void)
{
#if 1    
    initSystemClock();
#else
    Device_init();
#endif    
    Interrupt_initModule();
    Interrupt_initVectorTable();

    initSCID();

    for(;;)
    {
        SCI_writeCharBlockingNonFIFO(SCID_BASE, 'A');
        SCI_writeCharBlockingNonFIFO(SCID_BASE, 'B');        
        SCI_writeCharBlockingNonFIFO(SCID_BASE, 'C');                
        SCI_writeCharBlockingNonFIFO(SCID_BASE, 'D');                

        DEVICE_DELAY_US(100000); // 0.1sec delay
    }
}

  • Hello,

    Actually there is sysconfig support for the 176-pin package of the F2837xS device. However, I do see that it is a bit hard to get to. You can import the "empty_project" in C2000ware. When you open the sysconfig file, you will only be able to select the 100-pin package. However, once imported you can use the switch feature to change to the 176-pin package. 

    Once sysconfig is setup correctly you can use it to program the SCI clock appropriately. 

  • Hello.

    Thank you for your previous response.

    I am trying to use SCID Tx (GPIO46) and SCID Rx (GPIO47) as a debug port.
    For testing, I called the function :
    SCI_writeCharBlockingFIFO(SCID_BASE, 'A');

    However, in SysConfig I only see options for SCIA, SCIB, and SCIC—there is no SCID available.
    I attempted to manually edit the automatically generated board.h file to assign the pin numbers
    , but each time I rebuild the project, the file is regenerated and my changes are lost.
    Could you please advise me on how to properly configure SCID for use as a debug port?

    Best regards,
    sjkim

  • The board.h file is auto generated by sysconfig every time you build the project. You cannot edit the board.h file. Although I do see an option for using SCID in sysconfig. Have you used the "switch" command in sysconfig to move to the 176-pin package? I see that GPIO46/47 are not in the 100-pin package. Therefore, if you are still using the 100-pin package in sysconfig, then you won't be able to use these pins.