• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 542 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.

MSP432-DEBUGGERS: MSP432P401RIPZ Error 300 @ 0x0

Matthew Geasey
Prodigy 10 points
Part Number: MSP432-DEBUGGERS
Other Parts Discussed in Thread: UNIFLASH

Hello Everyone,

I have been trying to troubleshoot an MSP432P401RIPZ on my first prototype board and I have been using the Launchpad without any issues to build the code. When I switch to Uniflash to start the process for programming the firmware onto the MCU, I only run Verify and get the following error using the Texas Instrument XDS200:

Error Connecting to the target: (Error -300 @ 0x0) The requested TCLK PLL programming option is invalid. The utility or debugger has requested a selection of the JTAG PLL frequency or clock source that is invalid. The value of USCIF.TCLK_PROGRAM is probably bad. (Emulation package 9.4.0.00129)

I have not been successful at getting the right info for figuring out how to correct this. And this is starting to get a little out of my scope of knowledge in regards to JTAG. 

If there's any advice for this I would greatly appreciate it!

Thank you for your time.

  • 0
    TI__Mastermind 46765 points

    Hi,

    When you use the Launchpad, it is not using the JTAG to program the software right? Could you try the same programming process on the Uniflash?

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 10 points

    Hey Cash!

    Thank you for the response! So that I'm on the same page, what do you mean by the "same programming process" on the Uniflash? Are you saying connect the pins that are currently being used on the launchpad to connect the programmer and MSP432P401R and connect them to the PCB? 

    For this, would it make sense to use CCS since I know that works already or since CCS is not using JTAG, will it work?

    Thank you for your time!

  • 0 in reply to Matthew Geasey
    TI__Mastermind 46765 points

    Hi,

    The launchpad usually not uses the JTAG for programming.

    And the JTAG requires TCK TMS TCLK TDO SBWTCK SBWTDIO VCC and GND. It seems you missing one in your schematic.

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 10 points

    Hey Cash!

    I guess I'm not understanding what you meant in the first reply. 

    Cash Hao11 said:
    Could you try the same programming process on the Uniflash?

    I'm using CCS with the launchpad, so in the diagram I was seeing if that is what you meant for the same process, but now I'm a little more confused as you're saying JTAG requires SBWTCK and SBWTDIO which I don't see on the launchpad at all. Also, when I search the MSP432 Datasheet for "SBWTCK" and "SBWTDIO" those keywords don't even come up, so now I'm even more confused on what those are for haha! VCC and Ground should already be there as you can see.

    If the launchpad doesn't use JTAG to debug the launchpad MCU on the board what is it using?

    All I see is --> Ground / 5V / 3V3 / UART RX / UART TX / RST / TMS / TCK / TDO / TDI

    Thoughts?

     We are using the 100 pin chip model if that helps. 

    Also on the XDS200, I don't see anything in regards to those pins either.

     

    So going back to my original question:

    Matthew Geasey said:

    Error Connecting to the target: (Error -300 @ 0x0) The requested TCLK PLL programming option is invalid. The utility or debugger has requested a selection of the JTAG PLL frequency or clock source that is invalid. The value of USCIF.TCLK_PROGRAM is probably bad. (Emulation package 9.4.0.00129)

    Does this relate to a missing pin issue as you are describing above?

    When I got this message, I was using the TI14 Adapter in the screenshot above.

    Apologies if there's something that I'm missing as this is all new territory for me. 

    Thank you for your time!

  • 0 in reply to Matthew Geasey
    TI__Mastermind 46765 points

    Hi,

    What I mean in the first place is that the launchpad usually uses the SWD interface for debugging and downloading instead of using the JTAG interface.

    The JTAG requires 4 wire, TDI TDO TCK and TMS. I find the wrong datasheet before, please ignore. You can try with this setting and check if the issue gone.

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 10 points

    Hello! 

    Thanks for the clarification. So, here's a new one, we have been able to debug the MSP432P401RIPZ using CCS removing the bridge connections from the MCU on the Launchpad, connecting them to the JTAG header via bread board wires, but we are still unable to program the MCU through CCS with the XDS200, is there any documentation that would help me learn why I can do it from CCS through the launchpad debugger and not through the XDS200?

    Thank you for your time!

  • 0 in reply to Matthew Geasey
    TI__Mastermind 46765 points

    Hi,

    I am not sure why the XDS200 is not working. The XDS200 supporting list has the MSP432. It should work properly.

    Well, you can try the troubleshooting part of the XDS200 document in this link.https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds200.html

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 10 points

    Hey Cash! 

    Thank you for the update. Sorry about the delay. I'll keep checking this out as right now I had to abandon using the XDS. Hopefully I find the issue!

    Cheers!

    MattG