• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 16 subscribers
  • Views 821 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

PaLFI connection issue

Tiago Almeida
Prodigy 80 points


I bought the PaLFI kit with target board, base station and emulator stick. I installed the RFID Demo software 1.0, tested the RFID communication and everything worked fine. Issues had started when i just uploaded successfully the reader firmware (archive file slac350.zip) available on TI website, relatively to the PaLFI page, using the JTAG debugger MSP430 FET. When I open the PaLFI Demo GUI, a connection is established on respective COM Port but the device (reader) couldn't be recognized (says: Device on COM Port Unknown). When i press some test button, the app throws exception errors (screenschot image attached) and there is no communication at all. I tried to do everything i could manage to do, uploaded different firmware, used different versions of the GUI Demo, changed COM Ports, reinstalled USB ports, installed different drivers, but nothing has changed. What could it be the problem?
 
  • 0
    TI__Guru*** 135355 points

    Hello Tiago,

    We haven't seen this error before. We will try and re-create it on our side and get back to you early next week.

  • 0 in reply to Ralph Jacobi
    Prodigy 80 points
    Thanks, Ralph J., i'm very appreciated.

    My guess is that a slightly different firmware was uploaded on my board and when i just uploaded the original firmware (contained in slac350.zip), something changed and this app is not recognizing the board anymore. Analyzing the RI-ACC-ADR2 datasheet, the schematic of the daughter board contains the CP2102 USB IC but my board has FT232 instead.
  • 0 in reply to Ralph Jacobi
    Prodigy 80 points

    Found the solution, the issue was a timing issue because my reader board probably has a different clock from the original one when this firmware was created. Had to modify on this firmware, the frequency divider of the timer and the timing specs to adjust the baudrate of the uart software implemented on reader.

    EDIT: Found some errors in the provided code by TI, that stopped me from getting a communication between reader and tag. This should be reviewed for error correction and optimization.