The correct second byte of the response of DAP_ID_TIMESTAMP_CLOCK

[llinjupt]

From the newest DAPLink Spec the second byte is not the lenght(4) of a 32bit int. Instead , it is a strange arbitrary number 8. So my question is which one is correct? If it shoule be 8, then there is a bug in DAP.c for sure and otherwise the spec should be updated.

DAP_Info Response (for ID=0xF1): The ID=0xF1 Test Domain Timer obtains the parameter information about an optional 32-bit Test Domain Timer that may be used for various time measurements.

| BYTE | BYTE | WORD | < 0x00 | 0x08 | Frequency | |||******| Frequency: Input frequency of the Test Domain Timer which indicates the resolution of the 32-bit TD_TimeStamp values.