[5.10-OOB] mbed-os-example-nfc\NFC_EEPROM failed when building with IAR compiler
soramame21 opened this issue · 23 comments
mbed-os-example-nfc\NFC_EEPROM failed, when the example built with IAR compiler.
NFC tag can not be readd by an NFC reader APP on iphone.
the NFC tag can be read when the example code built with ARM compiler.
Building command
mbed compile -t IAR -m DISCO_L475VG_IOT01A -f -c
failed to write (error: 16)
failed to read (error: 16)
Building an ndef message
failed to write (error: 16)
failed to read (error: 16)
Building an ndef message
failed to write (error: 16)
failed to read (error: 16)
APP on iphone
NFC TagInfo provided by NXP.
@soramame21 : What happens on the phone? Does it read the tag? I had the same issue but my Android phone was able to read the tag (using the same app NFC TagInfo)..
@ashok-rao yes,I can read the tag. I revised the issue description. the NFC tag doesn't exist (cannot be read) when firmware built with IAR compiler.
I verified this is the case but haven't got any fix yet.
yes, the issue is not fixed by mbed-os-5.10.0-rc2
The issue is only visible with IAR with the ST EEPROM (it is not present when the PN512 is used).
Note that the ST EEPROM library lives outside mbed-os so that shouldn't be a blocker on mbed-os repo.
I just verified that this still exists with mbed-os-5.14-rc1. I'm using the same board DISCO_L475VG_IOT01A.
@paul-szczepanek-arm has this really been outstanding for a year now ?
Reproduces with mbed-os-5.14-rc2.
fix is here ARMmbed/mbed-nfc-m24sr#5
also seems this is know issue:
https://github.com/ARMmbed/mbed-os-example-nfc/tree/master/NFC_EEPROM#known-issues
fix is here ARMmbed/mbed-nfc-m24sr#5
This issue should be closed or not?
@soramame21 thank you for raising this issue.Please take a look at the following comments:
Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@soramame21 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
IAR no longer supported