Other Parts Discussed in Thread: UNIFLASH, CC3220S
Hello,
Yesterday, I was modifying the TIRTOS pwmled application to also do counting on a pin interrupt.
At one version of my code, it partially worked. As I connected P05 (set as input, interrupt enabled with pulldown) to the 3.3V pin, the interrupt triggered, but it would stop working afterwards.
Then I would reset, and the code started working again. I made a modification to my code, and suddenly everything worked for a while.
But at one point, it stopped working. and resetting it would not help again.
Here is what I tried so far:
1. I tried flashing it using UniFlash, but it says "Operation timed out". If I just press "Connect" in Uniflash, I get the same error.
2. I tried putting code to debug using CCS but it gives me the error -1170 @ 0x0 "Unable to access DAP"
3. I tried doing a factory reset, but the procedure didn't work at all. It was as if I was completely ignored. Sometimes messing with that procedure even caused a Kernel Panic on my MacBook TWICE (It's been years since I don't have a Kernel Panic)
4. I tried testing the connection in the target configuration (.ccxl) file. Here are the results:
[Start: Texas Instruments XDS110 USB Debug Probe_0]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
/Users/danielnogueira/.ti/ti/0/0/BrdDat/
testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioxds110.dylib'.
The library build date was 'Nov 6 2017'.
The library build time was '10:21:57'.
The library package version is '7.0.100.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.
-----[Print the reset-command hardware log-file]-----------------------------
The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).
-----[Perform the Integrity scan-test on the JTAG IR]------------------------
This test will use blocks of 64 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG IR Integrity scan-test has succeeded.
-----[Perform the Integrity scan-test on the JTAG DR]------------------------
This test will use blocks of 64 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG DR Integrity scan-test has succeeded.
[End: Texas Instruments XDS110 USB Debug Probe_0]
5. I tried running on the terminal the following commands:
$ ./xdsdfu -m $ ./xdsdfu -f firmware.bin -r
And apparently those two commands work just fine, which makes me think that the XDS JTAG emulator might work...
What could be wrong? How can I connect to the CC3220s again?
Thank you,
Daniel
