serial comunication with CLEV6630b NTAG5 kit

[gasol]

I'm actually trying to write a simple python lib to redo a simple NTAG5 cockpit app

but fitting my own purpose.

I've found the phUcBal.pdf file (include in NXP NFC cockpit app zip) that describe the simple protocol between PC and CLEV6603b board

I'm using a CLEV6630b eval board that works great with NTAG5 cockpit I can sniff serial frames sent from pc and the answers from CLEV6630b board and that looks peaty straight forward

My issue is that if I send for exemple "reset states machines to idle"

01 fd 00 00 02 00 00

I need to send it 2 times to get the answer :

01 fd 00 00 00 00

that is correct

but i need to send it 2 times each time

> [01 fd 00 00 02 00 00 ]
> [01 fd 00 00 02 00 00 ]
< [01 fd 00 00 00 00 ]
> [01 fd 00 00 02 00 00 ]
> [01 fd 00 00 02 00 00 ]
< [01 fd 00 00 00 00 ]

I've seen no mentions about sending eof or equivalent caracter at end of frame and when sniffing serial exchanges with genuine NTAG5 cockpit i dont see it neither

did any one had any idea ??

thanks for reading and for any help

[gasol]

hello fabian

thank's again

I've well read ISO7816 but as specified in phUcBal.pdf it just use terminology in frame definition it's not even partially compliant with ADPU protocol

may I was not precise in my first message I dont plane to use NTAG5 cockpit as End app I just whant to make a simple python app for our production and debug proccess that talk to CLEV6630b board to acces our NTA53321G0FHKZ based device

I've continue my reverse engineering and when I sent to the CLEV6630b board 

[01 fd 00 00 02 00 ff 55 ]

I've sniff with scope what's going on CLEV6630 board SPI  betewenn µC and CRLC6630 

blue : chip select

yellow : MISO

red : MOSI

green : CLOCK

it looks that IC is well receiving the register (7F<<2+1) and 0x55 as dummy byte

it's answering 0x1A so in this case why I don't receive on my USB link something else that

[01 fd 00 00 00 00 ]

I should expect something like

[01 fd 00 00 01 00 1A ]

or

[01 fd 00 00 02 00 7F 1A ]

right ?

[Fabian_R]

Hello sir,
I believe that the VCOM source code we provide (NFC Cockpit VCOM source code, secondary firmware application for CLRC663, PN5180 and PN5190 Reader ICs) in our NFC Cockpit site, Download section. Will be quite useful for your application.
Unfortunately, the implementation of the python driver for the VCOM isn't part of my support scope. For this reason my help is quite limited on this topic.
I hope this information may have been useful.

[gasol]

sory begining of my message have been deleted just want to thank you fabian for helping me

just want to correct also CLA 01 is not only for fifo but transfer/receive clrc6630 operations just a missspeeling but dont change anything to my question

[gasol]

For exemple I'm trying to read the CLCR6630 0x7F register witch must be Version number

I'm starting by reset to idle all states machine by sending

[01 fd 00 00 02 00 00 00 ]

and i receive the ack from clev6630b board

[01 fd 00 00 00 00 ]

after what I'm sending

[01 fd 00 00 02 00 ff 55 ]

01 is for FIFO class operation 

FD for 'Full Duplex' transfer

P1 and P2 is O as explain in phUcBal.pdf

Length is 02 00 ( 16 bit little endian value for 2)

FF is the register address 7F + Read bit  as explained in §8.4.2.4 datasheet 

and then an extra byte with dummy value for keep clock generation and get the value back from CLRC6630 spi

but I only get an ack with no values

[01 fd 00 00 00 00 ]

[Fabian_R]

Hello, my name is Fabian, I've been assigned to support your case.

Thank you for your interest in our products

My recommendation is to please take a look at other ways to interface with the NTAG 5. NTAg5 Cockpit is intended to be used as a configuration tool but, it's use for an end application or solution may present some limitations.

Regarding the use of phUcBal protocol, unfortunately we don't have project that we can share for you to based your application.

As mentioned in the document, this protocol is inspired in ISO7816 commands. Nevertheless, I believe that the use of a PC/SC reader may be easier for a python implementation.

If you could please share a little more of your project or goal I may be able to provide a better help.