Hello,
I have been using the NFC Cockpit v8.1.0.0 with the CLEV6630BM development boards. While playing with some tags, we ended up having issues with very long blocks of data. After checking, it seems the VCOM supports up to 64 bytes only, before it needs to split into multiple chunks. With more than 64 bytes, a fatal error occurs.
While debugging, I used the UcBalPCTestApp.exe tool to catch the USB-VCOM. Please find the log attached to this case. We immediately see that it fails when it requires to send multiple chunks of data (> 64 bytes).
Do you have an idea how to bypass this limitations?
Thanks for your support!
解決済! 解決策の投稿を見る。
Hello @Yann_O
Hope you are doing well.
Just to confirm, have you followed the procedure described in CLRC663 evaluation board quick start guide, Chapter 3; and NXP NFC Cockpit User Guide, Section 3.3 for the NFC Cockpit FW programming? Also, please make sure to use the latest driver version according to your NFC Cockpit version, otherwise the application might not work correctly.
What is the procedure you are following for the test in NFC Cockpit? This would be helpful for me to try to reproduce the scenario on my side.
I tested the Microcontroller BAL - PC Test Application and no errors were thrown; please, find the log I obtained from the test attached to this post.
Regards,
Eduardo.
Hello @EduardoZamora
Forget my last post. I found some JLink hardware and was able to update the CLEV6630BM FW to the latest proposed in NFCCockpit installation directory (firmware/Secondary_RC663/BootLoader_And_Nfcrdlib_SimplifiedAPI_EMVCo_Secondary.bin). I did not think that the default FW would not handled the VCOM driver properly...
Thanks for the pointers!
Hello @EduardoZamora
Thanks for the quick feedback. We are not doing software development on it, so LPC FW has not been touched. I did install the drivers as in the guidlines and NFCockpit is generally working fine with whatever commands I am using. I also tried to reinstall the drivers just in case and I am using the latest version of NFCCockpit 8.1.0.0.
For the scenario, I am doing the following steps, with a Type A PICC:
Checking the log file of NFCCockpit, I am getting the same error as when I am using the UcBalPCTestApp.exe tool: From 0x37 bytes, the it seems the packets are split in chunks of 64-byte packets for some reason.
Comparing the 2 logs, could it be related to the "Unable to load ADB process. Check if adb is part of environment variable" exception?
Thanks!
Hello @Yann_O
Hope you are doing well.
Just to confirm, have you followed the procedure described in CLRC663 evaluation board quick start guide, Chapter 3; and NXP NFC Cockpit User Guide, Section 3.3 for the NFC Cockpit FW programming? Also, please make sure to use the latest driver version according to your NFC Cockpit version, otherwise the application might not work correctly.
What is the procedure you are following for the test in NFC Cockpit? This would be helpful for me to try to reproduce the scenario on my side.
I tested the Microcontroller BAL - PC Test Application and no errors were thrown; please, find the log I obtained from the test attached to this post.
Regards,
Eduardo.