This wiki page will explain how to use custom data processing used to communicate between ACE, L3 and DPAS kernel.
1) ACE to L3 Communication:
0xFF64: Template tag for data used in this step
0xDF45: Container IDs in chunks of 4 bytes that define the range. For example: 0xFF630800000000000000FF covers all the container IDs in the range from 0 to FF.
0xDF44: P1 value to be used while sending Data GPO command
BF10 and other tags: These tags will replace PDOL data and BF10 value will be appended to GPO command
0xDF3C: this is extended logging data to be appended to GPO command
2) L2 to L3:
0xDF3D: Data storage directory tag read from ICC. More information on that tag can be found in the specification.
0xDF3B: Card feature descriptor tag read from ICC. More information on that tag can be found in the specification.
0xDF42: The pdol data length calculated by the kernel
3) L3 to L2:
PDOL modified elements data + BF10
0xDF43: Is data storage enabled tag
0xDF44: P1 value to be used in GPO command
0xDF3C: Extended Logging Data
How to send configuration file using ACE Client:
In FIME tool especially CONF_14 test cases contain tests related to data storage. The configuration files will arrive with ACE-Client, if there is a missing file please contact Amadis.
In the ACE-Client there is a tab designed to be used for Discover 2.0
...
That tab should be used to send the configuration file to Kizis.