Tool/software: Code Composer Studio
Hello, people of the internet.
I have run into an issue related to programming an MSP432 on a production board, it passes the JTAG test but then fails to program.
Context: The MSP432 is on a board with several buck converters and motor drivers, none of the external devices are active except for the buck converters. The whole purpose of the device is to run an automated control system. The MSP432 is being programmed through the use of CCSv7 and an XDS110 debugger on an MSP432 launchpad board.
Programming the development board works as intended but once the production board is used as a target, issues being to arise.
Issues: Conducting the JTAG test inside of CCSv7 yields the results of [i]"The JTAG IR Integrity scan-test has succeeded."[/i] and [i]"The JTAG DR Integrity scan-test has succeeded."[/i]. But once I attempt to program the target with a blank project, CCS produces the error:
"Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 7.0.48.0)"
After some initial googling, I found there was a procedure to hardware reset the device. I attempted to do so and reach an error:
"Trouble Writing Register DP_RESET:
(Error -1170 @ 0x2)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 7.0.48.0)
No connection possible. This could be caused by the device having gone to low power mode and disabling JTAG PINs.
You have the option to either toggle reset or try to use SWD instead."
This has been tested with a JTAG clock of 1MHz and 500kHz and both yields the same result.
Following the advice, I have tried to use SWD with AUX COM as TDO pin.
This produces an error:
"Error connecting to the target:
(Error -613 @ 0x0)
The target indicates that it is busy. Either try the SWD request
again, or abort the transaction.
(Emulation package 7.0.48.0)"
[b]Question:[/b] This leads me to believe that the MSP432 itself is somehow stuck in a software loop? I thought that the JTAG has some form of hardware priority over the processing core as it is an external peripheral. Is it possible to revive this seemingly bricked MSP432? Is there a critical design error that somehow allows a JTAG test to pass but then a subsequent programming attempt to fail?
To cover all my bases, I have attached an image of the local parts around the MSP432 (Yes, I know the placement is horrendous but this is one of my first boards so please be gentle). P9 is the JTAG header.
My only comment is that I have not populated an external oscillator, DOCR resistor or an inductor L1 (I am assuming it will operate in linear mode, assumptions are naughty, I know).
I have tested the 3.3v rail and it is present.
I will also attach a photo of my setup: (to prove that JTAG wires are not too long)
I've been beating my head against the wall with this issue as I cannot come to a solution. Any words of advice at all would be appreciated.|O
