ICODE DNA Mutual Auth not allowing key write

cancel
Showing results for 
Search instead for 
Did you mean: 

ICODE DNA Mutual Auth not allowing key write

651 Views
turbo2ltr
Contributor I

I've been able to get mutual authentication working but performing it before commands that require mutual auth still fail.

For instance:

App: Read Global Crypto Header
App: ############# Tag Discovered
App: Read Global Crypto header: 00810000
App: Changed to KEY 2
App: Read Key 2 header
App: ############# Tag Discovered
App: Read Key 2 header: 00C30000
App: Read Key 2 Privileges
App: ############# Tag Discovered
App: Read Key 2 privedges: 3F000000
App: WRITE Key 2 header
App: ############# Tag Discovered
App: Starting Mutual Authentication 
App: MAM1 CMD: 20354F609...
App: MAM1 response FULL: 04A74C76F....
App: Dec : DA839EE....
App: Challenge Match! 
App: MAM2 Cmd : 20354F....
App: MAM2 response: 00A7
App: Mutual Authentication PASSED 
App: Writing: 20C104[UID]1400E70000
App: Write Key 2 header: 010F  FAIL

I'm trying to change the key 2 header from 0xC3 to 0xE7.  The GCH doesn't bar writing it, the key's privileges has all privileges, but doing a mutual auth before a command never changes the command outcome vs without it.  I should be able to overwrite the key header and key with a mutual auth  with that key but nothing.

Any ideas?  I assume as long as I do a mutual auth and run a command after without removing the tag from the field, that it should remember the mutual auth.

Thanks.

0 Kudos
1 Reply

427 Views
uksac
NXP Employee
NXP Employee

Hello Jonathan,

The Key Header status of 0xC3 (Transport Keys) is not enabled by default. This is for customers which meet MOQ (minimum order quantity). Only valid values for Key Header status are 0x81 and 0xE7.

What is the status of GlobalCryptoHeader? 0xE7?

It was reported by me, that in DataSheet shall be stated more in detail way, that delivered IC has no option for Transport Keys feature.

Best regards,

Uros

0 Kudos