• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 280 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP-EXP430F5529LP: eZ-FET lite LED Behavior: severe error has occurred

Natalie
Prodigy 40 points
Part Number: MSP-EXP430F5529LP
Other Parts Discussed in Thread: DLP-7970ABP, TIDM-NFC-RW

Background: I have been using the MSP-EXP430F5529LP LaunchPad with the DLP-7970ABP BoosterPack for RFID testing for the past few weeks. The MCU is running firmware from the "TIDM-NFC-RW Software (Rev. A)" folder and I'm using the TI NFC Tool GUI, both downloaded from the TIDM-NFC-RW page. I've verified that the USB driver is correct and up-to-date. The setup works as expected -- connects to the GUI, reads/writes tags -- and the LED behavior is correct when reprogramming the MCU (green LED turns on, red LED blinks during programming and turns solid when connected and not programming). There's no damage to either PCB as far as I can tell.

Issue: For the past few days, when I connect the LaunchPad to the computer, the green LED (LED2) does not turn on, and when I connect to the LaunchPad in the GUI, the red LED (LED1) turns on. Disconnecting and reconnecting the setup, restarting the GUI, and reprogramming the MCU does not resolve this error. Everything is working as expected as far as I can tell, but the datasheet indicates that this is indicative of "A severe ERROR has occurred; disconnect and reconnect the eZ-FET lite. If this does not resolve the error, send for repair." 

What further debug steps should I take? I'd prefer not to send this board out for repairs since it still seems to be getting the job done.

  • 0
    TI__Guru* 90906 points

    Natalie - 

    is it possible for you to try a different USB cable?

  • 0 in reply to Josh Wyatt
    Prodigy 40 points

    Yes, I just tried a different one and the error persists.

  • 0 in reply to Natalie
    TI__Guru* 90906 points

    Natalie- 

    Its been awhile since this was released, so I re-read the user manual that we created for this at that time. I think you are describing the correct behavior. 

    LED1 (Red, on front of LaunchPad, next to S1 button) should illuminate when running and the LEDs on the BoosterPack will illuminate when card is present. I didn't see any reference to usage of LED2 (green).  

  • 0 in reply to Josh Wyatt
    Prodigy 40 points

    Josh,

    Just to clarify, you are saying that the reference to LED2 in the user guide (SLAU533D) is incorrect? 

    Since you mention the BoosterPack LEDs -- is there a reason those LEDs are labeled with a tag standard but lit based on mode? E.g., D2 on the BoosterPack is labeled "ISO14443B" but in the firmware is set to turn on when reader/writer mode is enabled. The "Hardware Guide" tab in the GUI implies that the standard and mode each LED is assigned to are interchangeable or related, which is misleading (e.g. "ISO14443B: Blue LED for Reader/Writer Mode").

    Thank you!

  • 0 in reply to Natalie
    TI__Guru* 90906 points

    Natalie - 

    No - I was referring to the user guide for the firmware you are using. LED2 is most certainly green on the LaunchPad(s) and is illuminated by raising P4.7 to a logic level high. 

    I honestly don't remember the LED behavior exactly, if the GUI is working then I would for now ignore the LEDs - I can go into work sometime next week and see if I can find this hardware or contact one of the others that worked on this and verify the LED behavior to close that part of your inquiry, if that works for you. 

**Attention** This is a public forum