TM4C1294NCPDT: My board is halted

Hi,
In the Windows device manger, do you see the Stellaris ICDI JTAG/SWD interface?
Can you power cycle your PC or try with other Windows machine to see if you can unlock the device?

Hi, thanks for the reply. I tried in another computer, but i couldn't saw anything from Stellaris or tm4c

Hi,
Just wanted to make sure it is not any driver problem with the PC. Do you have another board that you can successfully connect to the board using the same USB cable? If yes, then your PC and drivers are running fine. The problem is on the board side. Can you use the Uniflash to perform the unlock sequence? In either LM Flash Programmer or Uniflash, please follow the instructions to unlock the device. Normally an unlock sequence will restore the device to its factory setting if you follow the steps correctly. If you are still unable to connect/unlock then check the below items on your board.

1. Check with a digital multi-meter that the VDD and VDDA supply rails are 3.3 V.
2. Check with a digital multi-meter that the VDDC rail is 1.2 V.
3. Check whether the JTAG header is damaged or not.
4. Check on the JTAG header the VTREF pin is 3.3 V.
5. Check whether the Reset Pin of the microcontroller is at 3.3 V.

Sorry, but I don't know where they are VDD, VDDA and VDDC.

I checked the voltage on pins 5V, 3.3V and they are correct.

JTAG header = TXD, RXD, TCK, TMS, TDI, TDO?

the voltage in these pins are:

RESET: 3.3V

TDO: 3.3V sometimes 1.5V

TDI:  0.6V

TMS: 3.3V

TCK: 3.3V

RXD: 0.18V

TXD: 0.6V

Hi,
Can you measure TP12 on the board which is the VDDC. It should be 1.2V.

You didn't tell me yet if you have another board and if you can successfully connect to it. This is to rule out any PC and drivers issue. Have you also tried to use Uniflash to connect and unlock the device?

Hi, sorry for the long time without answer, i was looking for another board and now, i can see the board on device manager, but, the other board is still halted.

I measured the voltage on TP12 pin and they are correct 1.2V.

Hi,
Sorry to hear that the problem cannot be recovered yet. We can rule out your PC and drivers since it is able to recognize a good board. Normally the unlock sequence is the last resort to recover the device. Not sure why the unlock is not working for you. Do you remember what was in your code before the problem happened? Just curious if you were using the EEPROM?

Yes, I have the code and i'm not using eeprom. I was using normally . I was reading diferent sensor and i changed it (so many times) without shutdown the board. I hear the relay "on and off". And then, the board is halt. I Think It passed away :/

Hi,
I understand that you are unable to connect to the target. Can the board continue to function talking to your sensors? I hate to declare that your board is bricked until I know for sure.

I don't think so. I was comunicated to the board with ethernet, now the comand ping doesn't give a anwser

Other than the Ethernet, do you have other functions such as PWM that you can examine the pins to see if they are still alive?

Yes, they are halt.

I used to toggle led D1 when the code is running, it is off.

Hi,

 Can you use a multimeter to measure the current on the JP2? How much current do you measure?

I had measured 0.06A

Hi,
60mA is not out of spec. At this moment I don't have any more things for you to check. All the voltages and current you have been collecting look fine to me. Perhaps if you can retry the unlock sequence a few more times and hopefully it will succeed by chance. While you are doing the unlock sequence you can observe the JTAG interface signals on the scope. If you don't see any TDO coming out then the JTAG interface is bad. If you still cannot unlock, I'm just going to say that either the device is bricked or the board is malfunctioning.