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.

CCS: SimpleLink™ Wi-Fi™ Enabled NFC Card Reader

Tool/software: Code Composer Studio

pivc

i am getting this error how to overcome this  in this particular applictaion SimpleLink™ Wi-Fi™ Enabled NFC Card Reader...what might be the issue its very important can u suggest us please plase

  • Hi c m thejaswini,

    It looks like sl_NetAppEmailConnect() fails for some reason when you run the example. You should use the debugger and step into that sl_NetAppEmailConnect() function call, and determine exactly where you encounter an error, and what the underlying error code is. The error code you see of -1 is a catch-all code that doesn't really mean much.

    Let me know what the underlying error is and I'll be able to better help you find the root cause of the problem.

    Regards,
    Michael
  • Hi cm thejaswini,

    Looking through the email settings, I realized that you need to change the email server settings, as the NFC example uses settings such as SSLV3 that have since been unsupported by Google. Take a look at this thread for the changes you'll want to make:
    e2e.ti.com/.../1943339

    Let me know if changing those email server settings help.

    Regards,
    Michael
  • this actually helped me .. thank you.
  • hi sir,

    we are getting the mail, but the content of the tag is in some format  so how to retrive the actual read content of the tag to the mail, can you pls help us out..

  • Hi c m thejaswini,

    So it looks like your tag is formatted as an ISO15693 tag. There is an excellent application report on that type of tag that you can read here:
    www.ti.com/.../sloa166a.pdf

    Using the report as a guide, you can tell all sorts of interesting information about your tag. The first block of data indicates that the tag is an HF-I Plus transponder. The second block of data interestingly enough, says that the length is 0. This might mean that the rest of the data is not valid. Assuming that the data is valid, the third block of data indicates that the payload has a length of 0x3b bytes, and that has type 0x54 = T = text. After that, you have the ascii data payload of 65 6e 66 61 72 => enfar.

    Hopefully that helps you decode your tag.

    Regards,
    Michael