• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 543 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.

Issues with Blinky example (and others) on TM4C123GH6PM Launchpad

David Dominguez66
Prodigy 10 points
Other Parts Discussed in Thread: TM4C123GH6PM, TM4C123GH6PGE

I have the TM4C123GH6PM Launchpad.

When I import the blinky example, I can get it to build and debug. But nothing happens after I click the resume button.

When I try to view the registers, I get the error shown in the image.

Blinky is set for the TM4C123GH6PGE, but I've tried changing that to the PM and still have the same problem.

I've tried making a project from scratch and it still can't read the registers.

I'm very new at this. I've only done basic programming in Keil (with the UT Austin class from EDX)

  • TI__Guru**** 169874 points
    Hi,

    From the screenshot it seems you got several errors prior to properly running your application on the board ("Debug Port error occurred"). However, the call stack shows the code properly started (_c_int00) then reached main and is halted in the middle of a library (SysCtlPeripheralReady).

    The explanation why the message shown in the middle view ("Can't find a source file at") is below:
    https://youtu.be/QvK-QOdK134

    If you are able to still control your target and debug your application, then the explanation above should suffice. Otherwise, the application may be disrupting the target device and causing CCS to lose control over it. In this case, you can try to manually launch the debugger and carefully check the initialization steps until the code reaches main().
    https://youtu.be/g2aaJV_DcZY

    I think that Tiva devices contain peripherals that, when powered down, also prevent any reading from its registers. The running application is responsible for properly powering up the peripherals. I would double-check your application and see if GPIO Port B is actually powered up.

    Hope this helps,
    Rafael