Forum Replies Created
Re: Reply To: NXP lib not working on Android 7+ due to missing Apache HTTP client10. November 2020 at 9:27 in reply to: NXP lib not working on Android 7+ due to missing Apache HTTP clientI am also facing the same issue,
My gradle file settings are,
implementation fileTree(dir: "libs", include: ["*.aar"])
But I get the following error,
java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/params/BasicHttpParams;
Caused by: java.lang.ClassNotFoundException: Didn't find class "org.apache.http.params.BasicHttpParams" on path: DexPathList[[zip file "/data/app/com.example.desfiresdklogic-LiEY84vPfw9mjz1PO1XFaQ==/base.apk"],nativeLibraryDirectories=[/data/app/com.example.desfiresdklogic-LiEY84vPfw9mjz1PO1XFaQ==/lib/arm64, /system/lib64, /system/product/lib64]]
Could you please let me know regarding the same.
+ 0 | - 0
Re: Reply To: NTAG213 Tranceive error and TAG lost exception seen10. November 2020 at 9:23 in reply to: NTAG213 Tranceive error and TAG lost exception seenThank you, I tried in the new card and certain sequence of steps of above apis worked as referred from datasheet,
However just one Api call failed.
I tried calling,
public interface INTag213215216
enableCounter(boolean isEnable) -> Enables the NFC counter.
called as enableCounter(true);
But I am getting this error,
W/System.err: com.nxp.nfclib.exceptions.NxpNfcLibException: Transceive failed
2020-10-15 13:30:58.908 30551-30551/com.example.desfiresdklogic W/System.err: at com.nxp.nfclib.NfcAReader.transceive(:71)
2020-10-15 13:30:58.908 30551-30551/com.example.desfiresdklogic W/System.err: at com.nxp.nfclib.AndroidApduHandler.apduExchange(:42)
2020-10-15 13:30:58.908 30551-30551/com.example.desfiresdklogic W/System.err: at com.nxp.nfclib.ntag.AbstractNTag.Ž(:197)
2020-10-15 13:30:58.908 30551-30551/com.example.desfiresdklogic W/System.err: at com.nxp.nfclib.ntag.AbstractNTag.?(:403)
2020-10-15 13:30:58.908 30551-30551/com.example.desfiresdklogic W/System.err: at com.nxp.nfclib.ntag.NTag213215216.enableCounter(:374)
Referred to datasheet 8.5.7,
NFC_CNT_EN -> If the NFC counter is enabled, the NFC counter will be automatically increased at the first READ or FAST_READ command after a power on reset
But unable to understand why this error is thrown for this API.
Can you please help me getting some insights what could be wrong with this?
+ 0 | - 0
Re: Reply To: NTAG213 Tranceive error and TAG lost exception seen6. October 2020 at 6:28 in reply to: NTAG213 Tranceive error and TAG lost exception seenThanks for the reply.
I shall check on TAG LOST exception, hoping I have not programmed the password and I had called the authentication API, assuming this can be the reason.
Can you please look into the major error I am facing that is Transceive failed exception ,
When trying to programPWDPack or disabling the password protection I get this exception.(MORE DETAILS ABOVE )
All APIs used are just straight forward, unable to understand why this error is thrown, not much documentation found, also underlying code not available to debug further?
Any sample code etc will be of great help to debug further.
Thanks in advance.
+ 0 | - 0
Re: Reply To: Desfire EV1, format, writedata, changekey all failed with Authentication Error5. October 2020 at 15:30 in reply to: Desfire EV1, format, writedata, changekey all failed with Authentication ErrorThanks for the reply. Yes totally agree, however, one of my card authentication is failing with basic code changes of default values itself.
Where it worked for the first time, later its consistently failing..
However, I shall try again on a new card. But still unable to understand, why authentication of PICC is failing on this card, since I have not yet changed the key, Also used the sample code of TapLinux v1.7 only with 2k3des default.
+ 0 | - 0
Re: Reply To: Desfire EV1, format, writedata, changekey all failed with Authentication Error5. October 2020 at 7:12 in reply to: Desfire EV1, format, writedata, changekey all failed with Authentication ErrorThanks for the reply,
ChangeKey never executed, since very first authentication of PICC is failing.
Just one quick question
Keeping master key as default 2k3des, I can create applications under it with AES128 key?
Also will it be tamper proof for application data? External world should not be able to access our application data, even if PICC is 2k3des key.
Can you please throw some insights on the same.
Want to try this in new card, hoping we don't face the earlier problem.
+ 0 | - 0
Viewing 5 posts - 1 through 5 (of 5 total)