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.
I'm trying to evalute the '423A SD16 using theMSP-FET430UIF debug interface and the MSP-TS430PM64 target board. Everything on the chip works except a write to the SD16 control register SD16CTL at address 0x0100. Writing a zero works. Trying to write 0x0084 to the control register causes the debugger to float off into space and I frequently have to power cycle the UIF interface.
I've used mov.w and bis.w instructions using absolute, symbolic, indexed, or indirect addressing modes. It fails in the same way using the IAR and CCS tools, using two different UIF debug modules, and using two different lot codes of '423A. The only thing I haven't changed is the 64-pin target board, and I have one on order.
To recreate the problem all I have to do is fire up the chip with a reset routine that turns interrupts and the wdt off and then issue "mov.w #0084h, &SD16CTL" and the debugger is dead.
Please, somebody tell me there's something stupid I don't know about.
Thanks, Mike Cushing
This has become more like a Keystone Cops movie than a chip evaluation - the fault has become worse.
I did find that the fault occurs only when trying to turn Vref or Vmid on in the SD16CTL register, but it took 24 hours, because after executing the write several times, the debugger totally fails to download to chip, complaining "Error connecting to target: Unknown device." Killing CCS5 and doing a full power cycle on the PC and the UIF multiple times didn't fix it.
That happened yesterday. This morning, it worked fine, failing to write to the control register but still working, about three times. Then it stopped downloading again.
At this point, I think this is just for your amusement. The "Unknown device" failure occurs both with CCS5 running under Windows 7 and IAR5 running under XP.
- Mike Cushing
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Michael Cushing:
The only remaining component that I had not changed was the 64-pin target board (MSP-TS430PM64), which clearly can't effect the debugger, but...
The replacement target board arrived today, I plugged the "Unknown device" '423A in, and it runs perfectly. I suspect there's a pattern-sensitive JTAG problem on the original target board.
Michael Cushing I suspect there's a pattern-sensitive JTAG problem on the original target board.
Time to say goodbye - I don't have the time anymore to read and answer forum posts. See my bio for details.Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.I'm sorry that I can no longer provide help in the forum or by private conversation.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.