LAUNCHXL-F2800157: Unable to run blinky

Hi Dan,

Thanks for your question. Have you made sure to include the _LAUNCHXL_F280015X pre-define? Please follow the steps from the LaunchPad user guide.

Regards,

Vince

The last time I tried to follow the guide, adding the #define for the board broke the project and it wouldn't compile. Incidentally, I was told that this was out of date info and not necessary to do. See: https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1233873/tms320f280039c-cannot-connect-to-dev-board

That said, I just checked and that symbol is in fact defined by the project already when I import it from the C2000 Ware.

Hi Dan,

Can you provide a picture of the boot selection switch? I'm wondering if a different boot mode is being selected.

Also, is there a ".sycfg" file in your project? I'm wondering if the project is writing the output to a "non-LED" GPIO (meant for the controlCARD).

Regards,

Vince

The boot selection switch is in the correct orientation. The application is running, and I am able to debug it. The GPIO instructions just have no impact on the LED. I added a line to toggle the other LED (LED5 on the silkscreen) and that does toggle. LED4 which is what the example uses, does not. My project does have a .syscfg- it came with the example from the SDK.

Are you not able to reproduce this behavior?

    //
    // Loop Forever
    //
    for(;;)
    {
        //
        // Turn on LED
        //
        GPIO_writePin(DEVICE_GPIO_PIN_LED1, 0);
        GPIO_writePin(DEVICE_GPIO_PIN_LED2, 0);

        //
        // Delay for a bit.
        //
        DEVICE_DELAY_US(500000);

        //
        // Turn off LED
        //
        GPIO_writePin(DEVICE_GPIO_PIN_LED1, 1);
        GPIO_writePin(DEVICE_GPIO_PIN_LED2, 1);

        //
        // Delay for a bit.
        //
        DEVICE_DELAY_US(500000);
    }

// LEDs
//
#define DEVICE_GPIO_PIN_LED1        35U             // GPIO number for LED4
#define DEVICE_GPIO_PIN_LED2        49U             // GPIO number for LED5
#define DEVICE_GPIO_CFG_LED1        GPIO_35_GPIO35  // "pinConfig" for LED4
#define DEVICE_GPIO_CFG_LED2        GPIO_49_GPIO49  // "pinConfig" for LED5

Hi Dan,

I've reached out to the board design expert. It is possible that the GPIO chosen as "LED4" in the software may not actually be the correct one that is connected on the LaunchPad.

Another possibility is the LED itself may not be working correctly.

Board designer will be able to assist with this.

Regards,

Vince

According to the schematic, those are the correct IOs and the LED tests fine with a diode tester

Thank you for the help. This does fix my issue. Are these samples tested before the C2000 Ware release? I'm concerned that I'm going to keep facing other similar issues or at least delays if I rely on the example code to guide my development. Is there a better alternative?

Hi Dan,

Thank you for confirming the solution. I've already filed a bug report on this so it should get resolved. We do have regression testing for these example software so I will work with the software team to see how this bug popped up. I actually use these examples in my board testing to validate my prototype designs and I did not see this issue in the previous version of C2000Ware I was using. 

These examples should still remain a good source for your embedded software development. If you are interested in trying out a different software development tool, I employ you to check out our SysConfig tool, which generates the MCU configuration code for you and goes through its own set of validation and regression testing. It generates code that is automatically used in your project, but you can also use it as a reference i.e. configure the peripheral in the SysConfig tool and copy and paste the generated code into your own project. You can find more information at: www.ti.com/.../spracx3 

Regards,

Peter

Great. Thanks again for the fix and for the additional details. This has been very helpful.