[Help] Getting the amiibo identification block

Hi,

I developping a small amiibo application for 3ds.
Everything go fine to communicate with the NFC reader, reading appdata amiibo settings and config ...
but despite all my search and tests i don't found a way to get the identification block.

Unlucky, it's the only thing that i need for this application to identify the scanned amiibo.

I knew that only few developpers work on the NFC service but is there a way to get this block ?

Thank for your help and sorry for my english.

 

This work with the dump of all data from the amiibo ( with a NFC reader for PC and/or android )
NFC reader for 3ds ( at least with devkitpro ) only read specific data with specific command ( for example with a command you get the config with mii's owner, amiibo's nickname, ... with an other you get the data saved by a game ... ).

So i need, with devkitpro and ctrulib, a way to get specifically this identification block or a way to dump any portion of data that work on both n3ds and o3ds with NFC reader.

 

Probably but i don't have the knowledge to do this.
Thanks for your help.

 

So ... after some test i found the datas.
It was part of the unidentified datas of the NFC_amiiboConfig element from ctrulib.

Code:

typedef struct {
    u16 lastwritedate_year;
    u8 lastwritedate_month;
    u8 lastwritedate_day;
    u16 write_counter;
    u8 characterID[3];
    u8 serie;///ID of the serie
    u8 amiiboID;///ID shared by all exact same amiibo. Some amiibo are only distinguished by this one like regular SMB Series Mario and the gold one
    u16 type;/// Type of amiibo 0 = figure, 1 = card, 2 = Plush
    u8 val_xc;
    u8 pagex4_byte3;/// "This is byte[3] from NFC page[0x4]."
    u8 appdata_size;/// "NFC module writes hard-coded u8 value 0xD8 here. This is the size of the Amiibo AppData, apps can use this with the AppData R/W commands. ..."
    u8 zeros[0x31];/// "Unused / reserved: this is cleared by NFC module but never written after that."
} NFC_AmiiboConfig;

For those who want the edited file from ctrulib with correctly named characters data :
https://github.com/Slimfr01/ctrulib/blob/master/libctru/include/3ds/services/nfc.h

 

No dev service can only be used with a dev nfc reader and even with that identication data can only be write once. After that data are locked on the nfc tag so you can't edit amiibo where you want. ( without that third party nfc reader could edit the identification data and amiiqo will be useless )

 

Homebrew can at least do what retail game do : get info about amiibo and owner and write/read an appdata with a specific appid. For now we can't get the appid with a homebrew ( so we need to work with only a game or test every appid or let the user choose the good appid ).

I don't know if it's possible with dev service to dump everything because the nfc reader do his part on data treatment and send only what is needed. ( and dev only need to be able to choose identification block one time and to be able to read/write appdata like for retail game )