Arodev Posted November 10, 2021 at 10:05 AM Share Posted November 10, 2021 at 10:05 AM (edited) Hi, We experienced an issue with the latest firmware (2.0.6) for card emulation. Scenario 1 No communication possible between NFC Bricklet and Smartphone The bricklet is not detected by a smartphone or by another bricklet in reader mode. (In the previous version, we got “Card Emulator: Transfer NDEF error” frequently (reading with an Android phone and another bricklet) but it was doable.) Scenario 2 No NFC communication possible among NFC Bricklets. One nfc bricklet in reader mode (e.g. attached to a raspberry pi), another nfc bricklet in card emulation mode (e.g. attached to a computer which will select the tag to emulate). I have tried to have the first bricklet in reader mode (NFC type 4 with NDEF) and the other in card emulation mode with some text (both connected to the same master brick to a computer for now). With version 2.0.5, I can successfully “Scan for Tag” on the reader but not read any page: I get “Card Emulator: Transfer NDEF error” on the emulator. With version 2.0.6, I’m unable to detect the emulator from the reader at all. Scenario 3 No NFC communication possible among NFC Bricklets in P2P Mode. I have also tried to use P2P mode (one reader, one writer), but there is neither discovery nor communication. Could you please assist me on this issue? My environment use Brick Viewer 2.4.20 for MacOS; Master Brick with firmware 2.5.0 Best regards, Paul Edited November 15, 2021 at 03:37 PM by Arodev Typo Quote Link to comment Share on other sites More sharing options...
borg Posted November 10, 2021 at 12:04 PM Share Posted November 10, 2021 at 12:04 PM Between 2.0.6 and 2.0.5 we added new API functions and we changed the optimization level of the compiler for some functions because we didn't have enough firmware space left otherwise. I will have to look into this, maybe this somehow changed the timing a little bit and that breaks something? 1 Quote Link to comment Share on other sites More sharing options...
Arodev Posted November 15, 2021 at 03:36 PM Author Share Posted November 15, 2021 at 03:36 PM Hello @borg, Is there any chance to get a firmware with P2P from your side (see scenario 3 of my original posting and attached screenshot)? We are in an urgent need for P2P communication among bricklets for a project. Quote Link to comment Share on other sites More sharing options...
borg Posted November 16, 2021 at 08:22 AM Share Posted November 16, 2021 at 08:22 AM Does this work with firmware 2.0.5? Quote Link to comment Share on other sites More sharing options...
Arodev Posted November 16, 2021 at 09:36 AM Author Share Posted November 16, 2021 at 09:36 AM No, it doesn't work on both 2.0.5 and 2.0.6. Quote Link to comment Share on other sites More sharing options...
Arodev Posted January 4, 2022 at 09:12 AM Author Share Posted January 4, 2022 at 09:12 AM Hi @borg Do you have any updates on those issues? Will you correct it due time? Could you provide me an ETA for the patch ? Regards Quote Link to comment Share on other sites More sharing options...
borg Posted January 4, 2022 at 03:51 PM Share Posted January 4, 2022 at 03:51 PM Very sorry for the long delays. I did take a look last month, but we didn't have any relevant changes regarding the P2P code in the last firmware versions. The P2P code was always a bit finicky to be honest... Internally we use the official library that NXP provides. Unfortunately this has been unmaintained from NXP for many years now and there are no updates available. I did put it on my TODO list to add some debug and find out where exactly we get an error during the NCI-Interface communication, but i haven't found time to do this yet. This is unfortunately a big effort because of the complexity of this protocol. I will add an update if i have any news. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.