• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 84 subscribers
  • Views 2532 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

controlSUITE examples not working with TMS320F28377S LaunchPad

DavidG
Intellectual 290 points

Other Parts Discussed in Thread: CONTROLSUITE, TMS320F28377S

Using CCSv6 (6.1.3.00033) and the TMS320F28377S board I am unable to load and execute the corresponding controlSUITE examples.  The preloaded Blinky program did work, but loading the example code of Blinky leaves the board acting like it hasn't been programmed.  Somehow during the process of trying to get the Blinky program to work I accidentally overwrote the flash memory, so the demo that came on the board is gone.

I am pulling my examples from C:\ti\controlSUITE\device_support\F2837xS\v191\F2837xS_examples_Cpu1 with a fresh install of controlSUITE.

The example of most interest at the moment is sci_echoback_cpu01 because my first priority is to get one of the UART modules working.  The program builds and enters debug mode without issue, but PuTTy never gets any feedback.  I know I am connected to the correct COM port because the board's RX LED lights up when I press a key in the PuTTy window.

PuTTy is configured with 8 bits, no parity, 9600 or 115200 baud rate (tried both).

In addition to the base code, I temporarily modified the example source code to use the uart.c module instead of the defaults.  I saw no change in the results, but I did have some compiler issues with importing the new module.  Even with the include folders being specified it seems that subfolders (#include "driverlib/uart.h") do not function as necessary, so I was forced to add these folders to the path as well.

My questions are then:

1. Could this be an incompatibility issue with Windows 10 somehow? -- edit:  Coworker tried on his Windows 8 machine with similar results.

2. Am I pulling the example code from the wrong folder (v191 vs. the others?)  Does the board revision make a difference and where can I find that?

3. I read several posts saying that CCSv6 was having serious compatibility problems with some boards (as well as an issue with the linker).  Should I try installing a different version of CCS?

4. What else could be going wrong?

I would appreciate any insight.  Thanks!

  • 0
    Guru 192875 points
    Hi David,

    Check this link: e2e.ti.com/.../1707097

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Intellectual 290 points

    I looked at the link and did the following:

    Calculated a clock frequency of 200 MHz.  F = Fosclock * (FMULT + IMULT) / SYSCLKDIV where Fosclock = 10 MHz from INT_OSC2 and FMULT + IMULT = 40 and SYSCLKDIV = 1 (later in code evaluated + 1 = 2) with the equation provided in the technical reference manual:

    fPLLSYSCLK = fOSCCLK * (SYSPLLMULT.IMULT + SYSPLLMULT.FMULT) / SYSCLKDIVSEL.PLLSYSCLKDIV

    That gave me the modified code in F2837xS_SysCtrl.c:

    InitSysPll(INT_OSC2,IMULT_40,FMULT_0,PLLCLK_BY_2);

    I also made changes to scia_echoback_init() in Example_2837xSSci_Echoback.c:

    //
// SCIA at 9600 baud
// @LSPCLK = 50 MHz (200 MHz SYSCLK) HBAUD = 0x02 and LBAUD = 0x8B.
// @LSPCLK = 30 MHz (120 MHz SYSCLK) HBAUD = 0x01 and LBAUD = 0x86.
//
//SciaRegs.SCIHBAUD.all    =0x0002; // previous value
//SciaRegs.SCILBAUD.all    =0x008B; // previous value
SciaRegs.SCIHBAUD.all    =0x0000;  // 115200 baud @LSPCLK = 22.5MHz (90 MHz SYSCLK).
SciaRegs.SCILBAUD.all    =53;  // example value from the post you linked

    which I verified with the equation found in the post:  

    • SCIBaudRate = LSPCLK/((SCIHBAUD:SCILBAUD + 1) * 8) = 50MHz/((53 + 1) * 8) = 115,741 (~115,200) Baud

    I tried connecting at 115200 baud rate with PuTTy and do not get any characters at all.  I also tried at half rate and still got nothing.  

    In addition to the aforementioned issue I still cannot change the LEDs using the Blinky program.  If it were limited to a baud rate/frequency configuration issue then the LEDs should be functioning.  Do you have any additional insight into either issue?

    Thanks!

  • 0
    TI__Expert 5940 points
    David,

    The pre-loaded LaunchPad example project is in the C:\ti\controlSUITE\development_kits\LAUNCHXL-F28377S\LaunchPadDemo directory. Lines 221-226 of Example_F28377xLaunchPadDemo.c file, also shown below, show how to set up the pins for the SCI-A port on the LaunchPad.

    // For this example, only init the pins for the SCI-A port.
    EALLOW;
    GpioCtrlRegs.GPCMUX2.bit.GPIO84 = 1;
    GpioCtrlRegs.GPCMUX2.bit.GPIO85 = 1;
    GpioCtrlRegs.GPCGMUX2.bit.GPIO84 = 1;
    GpioCtrlRegs.GPCGMUX2.bit.GPIO85 = 1;
    EDIS;


    This code should replace the SCI pin initialization in the device support SCI examples. The device support examples set up pins 28 and 29, but pins 84 and 85 are to be set up for the LaunchPad.

    Elizabeth
  • 0 in reply to DavidG
    TI__Mastermind 21600 points
    David,

    If you open F2837xS_SysCtrl.c and look at the line that calls the InitSysPll. It mentions that you can not use the internal oscillator as the PLL source if PLLSYSCLK is configured to frequencies above 194MHz. It seems that your are using INT_OSC2 as your PLL source in your last post. I would try using the external oscillator (XTAL_OSC ) as your PLL source and see if it resolves your issue.
  • 0 in reply to Elizabeth Joy
    Intellectual 290 points
    Thank you for the assistance. The solution you mentioned does work on the board, so I have something to work with now.