• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 415 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.

TM4C129ENCPDT: Programming for the first time

Pranav Paralikar
Prodigy 10 points
Part Number: TM4C129ENCPDT
Other Parts Discussed in Thread: EK-TM4C129EXL

Hi,

I have designed a TM4C129ENCPDT based board. The board design is based on EK-TM4C129EXL. A couple of proto boards are ready for testing. I also have Installed the TivaWare and are using the Project0 for checking the initial programming/debugging and then port pin toggling. The project is built properly with no errors. When I try to debug the code I am getting an below error:

CORTEX_M4_0: Error Initializing flash programming: Target Failed to read 0x400fE000. Below is the screenshot of the error:

I think I have done proper changes in target_config.ccxml file and the debug configuration.
Setup Details:
1. IDE: CCS v10.3.0
2. Debugger/Programmer: XDS200 USB Debug Probe
What could be the possible reasons for this error? Am I missing anything in the setup or is there an issue in the HW?
Pls. note: This is a fresh MCU which we are trying to debug/program for the very first time.
Is there any specific procedure to enable debugging/programming on a fresh MCU for the first time (e.g. setting option bytes, unlocking or so)? Pls. share if such literature is available online. Also share the documents on setting up debugger/programmer and other essential things. 
Request you to suggest the possible solution to this problem.
Thank you..
--
Best Regards,
Pranav
  • +1
    TI__Guru**** 191906 points

    Hi, 

      Can you use the same XDS200 debug probe and target configuration to debug the LaunchPad board? If yes, then we can rule out the target configuration as a possible cause of the issue. In the target configuration you create, you can also perform a JTAG scan test to see if the JTAG is functioning. Can you run it and show the outputs?

      I tend to think there is some board level issue. Can you share the schematic? Sometimes, people left out the pulldown resistor on the RBIAS pin which is required per errata workaround. Without the resistor, there is issue connecting to the target. 

      

  • 0 in reply to Charles Tsai
    Prodigy 10 points

    Hi Charles,

    Thank you for your reply. You hit it point blank.

    There is a provision to connect a Pulldown Resistor in the RBias pin, but we has kept it open. I connected the Resistor there and I am now able to program the he TM4C.

    Thank you..
    --
    Best Regards,
    Pranav