PN7221+Android16 EDLA certification issues

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

PN7221+Android16 EDLA certification issues

Jump to solution
67 Views
zhangkai
Contributor II
PN7221, Android 16
 
The EDLA-certified build only supports partial NFC functions. Card detection works in our tests, but EMVCo, firmware upgrade and other features are unavailable. Root cause identified via comparison is as follows:
 
The EDLA build uses Google's prebuilt NFC service, while the AOSP build is compiled with NXP patches integrated.
 
Below is the EDLA-related build configuration snippet:
 
apex_set {
 
name: "com.google.android.nfcservices_compressed",
 
apex_name: "com.android.nfcservices",
 
overrides: ["com.android.nfcservices"],
 
owner: "google",
 
set: "com.google.android.nfcservices_compressed.apks",
 
filename: "com.google.android.nfcservices_compressed.apex",
 
exported_bootclasspath_fragments: ["com.android.nfcservices-bootclasspath-fragment"],
 
}
Could you advise how to import NXP patches under this scenario? Are there alternative solutions? For other customers using NXP NFC chips, what approaches are adopted to pass EDLA certification while retaining full NFC functionality?
0 Kudos
Reply
1 Solution
33 Views
KaiLi
NXP TechSupport
NXP TechSupport

Hello @zhangkai 

Based on our analysis, the issue is likely caused by the EDLA build using Google's prebuilt NFC APEX (com.android.nfcservices) instead of the NFC module integrated with NXP Android middleware.

The NXP Android 16 solution extends multiple layers of the Android NFC stack, including the NFC framework, NFC service, EMVCo framework, HAL, and associated libraries. If the Google prebuilt NFC service is used, only standard NFC features may remain available, while NXP-specific features such as EMVCo functionality, firmware update support, and other middleware extensions may not be active.

At present, NXP's Android 16 porting documentation does not describe a method to directly patch or modify Google's prebuilt EDLA NFC APEX. The typical NXP integration approach is based on AOSP source integration and rebuilding the NFC stack with NXP middleware.

For customers requiring full PN7221 functionality, we recommend evaluating whether the NFC APEX can be rebuilt with the NXP NFC middleware included, or consulting Google/OEM support regarding customization of the EDLA NFC module while maintaining EDLA compliance.

View solution in original post

0 Kudos
Reply
1 Reply
34 Views
KaiLi
NXP TechSupport
NXP TechSupport

Hello @zhangkai 

Based on our analysis, the issue is likely caused by the EDLA build using Google's prebuilt NFC APEX (com.android.nfcservices) instead of the NFC module integrated with NXP Android middleware.

The NXP Android 16 solution extends multiple layers of the Android NFC stack, including the NFC framework, NFC service, EMVCo framework, HAL, and associated libraries. If the Google prebuilt NFC service is used, only standard NFC features may remain available, while NXP-specific features such as EMVCo functionality, firmware update support, and other middleware extensions may not be active.

At present, NXP's Android 16 porting documentation does not describe a method to directly patch or modify Google's prebuilt EDLA NFC APEX. The typical NXP integration approach is based on AOSP source integration and rebuilding the NFC stack with NXP middleware.

For customers requiring full PN7221 functionality, we recommend evaluating whether the NFC APEX can be rebuilt with the NXP NFC middleware included, or consulting Google/OEM support regarding customization of the EDLA NFC module while maintaining EDLA compliance.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2393451%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EPN7221%2BAndroid16%20EDLA%20certification%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2393451%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CDIV%3E%3CDIV%3EPN7221%2C%20Android%2016%3CDIV%3E%26nbsp%3B%3C%2FDIV%3EThe%20EDLA-certified%20build%20only%20supports%20partial%20NFC%20functions.%20Card%20detection%20works%20in%20our%20tests%2C%20but%20EMVCo%2C%20firmware%20upgrade%20and%20other%20features%20are%20unavailable.%20Root%20cause%20identified%20via%20comparison%20is%20as%20follows%3A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3EThe%20EDLA%20build%20uses%20Google's%20prebuilt%20NFC%20service%2C%20while%20the%20AOSP%20build%20is%20compiled%20with%20NXP%20patches%20integrated.%3CDIV%3E%26nbsp%3B%3C%2FDIV%3EBelow%20is%20the%20EDLA-related%20build%20configuration%20snippet%3A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3Eapex_set%20%7B%3CDIV%3E%26nbsp%3B%3C%2FDIV%3Ename%3A%20%22com.google.android.nfcservices_compressed%22%2C%3CDIV%3E%26nbsp%3B%3C%2FDIV%3Eapex_name%3A%20%22com.android.nfcservices%22%2C%3CDIV%3E%26nbsp%3B%3C%2FDIV%3Eoverrides%3A%20%5B%22com.android.nfcservices%22%5D%2C%3CDIV%3E%26nbsp%3B%3C%2FDIV%3Eowner%3A%20%22google%22%2C%3CDIV%3E%26nbsp%3B%3C%2FDIV%3Eset%3A%20%22com.google.android.nfcservices_compressed.apks%22%2C%3CDIV%3E%26nbsp%3B%3C%2FDIV%3Efilename%3A%20%22com.google.android.nfcservices_compressed.apex%22%2C%3CDIV%3E%26nbsp%3B%3C%2FDIV%3Eexported_bootclasspath_fragments%3A%20%5B%22com.android.nfcservices-bootclasspath-fragment%22%5D%2C%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%7D%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CDIV%3ECould%20you%20advise%20how%20to%20import%20NXP%20patches%20under%20this%20scenario%3F%20Are%20there%20alternative%20solutions%3F%20For%20other%20customers%20using%20NXP%20NFC%20chips%2C%20what%20approaches%20are%20adopted%20to%20pass%20EDLA%20certification%20while%20retaining%20full%20NFC%20functionality%3F%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2393945%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20PN7221%2BAndroid16%20EDLA%20certification%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2393945%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F262699%22%20target%3D%22_blank%22%3E%40zhangkai%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBased%20on%20our%20analysis%2C%20the%20issue%20is%20likely%20caused%20by%20the%20EDLA%20build%20using%20Google's%20prebuilt%20NFC%20APEX%20(com.android.nfcservices)%20instead%20of%20the%20NFC%20module%20integrated%20with%20NXP%20Android%20middleware.%3C%2FP%3E%0A%3CP%3EThe%20NXP%20Android%2016%20solution%20extends%20multiple%20layers%20of%20the%20Android%20NFC%20stack%2C%20including%20the%20NFC%20framework%2C%20NFC%20service%2C%20EMVCo%20framework%2C%20HAL%2C%20and%20associated%20libraries.%20If%20the%20Google%20prebuilt%20NFC%20service%20is%20used%2C%20only%20standard%20NFC%20features%20may%20remain%20available%2C%20while%20NXP-specific%20features%20such%20as%20EMVCo%20functionality%2C%20firmware%20update%20support%2C%20and%20other%20middleware%20extensions%20may%20not%20be%20active.%3C%2FP%3E%0A%3CP%3EAt%20present%2C%20NXP's%20Android%2016%20porting%20documentation%20does%20not%20describe%20a%20method%20to%20directly%20patch%20or%20modify%20Google's%20prebuilt%20EDLA%20NFC%20APEX.%20The%20typical%20NXP%20integration%20approach%20is%20based%20on%20AOSP%20source%20integration%20and%20rebuilding%20the%20NFC%20stack%20with%20NXP%20middleware.%3C%2FP%3E%0A%3CP%3EFor%20customers%20requiring%20full%20PN7221%20functionality%2C%20we%20recommend%20evaluating%20whether%20the%20NFC%20APEX%20can%20be%20rebuilt%20with%20the%20NXP%20NFC%20middleware%20included%2C%20or%20consulting%20Google%2FOEM%20support%20regarding%20customization%20of%20the%20EDLA%20NFC%20module%20while%20maintaining%20EDLA%20compliance.%3C%2FP%3E%3C%2FLINGO-BODY%3E