hf 15 rdbl flag issue

[ikarus23]

Hi!

To my understanding the read block command hf 15 rdbl will always set the ISO15693 "custom flag" in its request. I think it does this, because some tag manufacturers will include the lock bit, if you define this flag.

For example, this is a hf 15 rdbl of a ICODE SLI:

Reader: 62  20  11  22  33  44  55  66  77  88  08  49  81
        ^   ^   ^                               ^   ^
        |   |   |                               |   |
        |   |   UID                             |   CRC
        |   CMD                                 Block Nr.
        Flags

Tag:    00  00  ff  ff  ff  ff  ee  3c
        ^   ^   ^               ^
        |   |   |               |
        |   |   Block content   CRC
        |   Lock bit
        Flags

If you do not set the "custom flag" the 0x62 will become 0x22. The same read does then look like this:

Reader: 22  20  11  22  33  44  55  66  77  88  08  49  81
        ^   ^   ^                               ^   ^
        |   |   |                               |   |
        |   |   UID                             |   CRC
        |   CMD                                 Block Nr.
        Flags

Tag:    00  ff  ff  ff  ff  ee  3c
        ^   ^               ^
        |   |               |
        |   Block content   CRC 
        Flags

Notice that the lock bit is missing in the response.

Although this is a convenient way to get the lock bit while reading a block, this is not a specified behavior according to ISO 15693-3. I have a tag that does not use the "custom flag". Therefore, the hf 15 rdbl command will display wrong results because it assumes that there is a lock bit information in the response.

It would be great if there would be a option to hf 15 rdbl which does disable setting the custom flag and in return just shows the block data (and no information about the lock bit).

Thanks!