Post Go back to editing

ADIS16223 Rev0 Data sheet typos?

Are these typos? The Rev 0 Data sheet for ADIS16223 as downloaded from AD website has a couple of important typos.

Page 14 of 20

Alarm Indicator states "Set GLOB_CMD[4]=1 (DIN = 0xBF10)"

The DIN should be 0xBE10 not 0xBF10 ?

 

Page 15 of 20

Self-Test states "Set GLOB_CMD[2] = 1 (DIN = 0xBE02)"

The DIN should be 0xBE04 not 0xBE02 ?

 

I have drawn up a table based on Table 27 but with the addition of the DIN commands as I understand them.

Please can you check the above observations and the table below for accuracy / errors.

Are the observations above due to typos or have I misunderstood the GLOB_CMD[x] commands?

Bits Din command Description
15 0xBF80 Reserved
14 0xBF40 Reserved
13 0xBF20

Restore capture data and settings

12 0xBF10

from flash memory

11 0xBF08

to flash memory

10 0xBF04 Set CAPT_PNTR = 0x0000
9 0xBF02 Reserved
8 0xBF01 Clear capture buffers
7 0xBE80 Software reset
6 0xBE40 Reserved
5 0xBE20

Flash test, compare sum of flash

4 0xBE10

memory with factory value

3 0xBE08

Restore factory register settings

2 0xBE04

and clear the capture buffers

1 0xBE02 Power-down
0 0xBE01 Autonull
Parents
  • If you are going to say something is "Logic based" or refer to what "others use," I would encourage a bit more support for such claims. Who else is saying that bits 1 and 2 need to be flipped?  What logic is this based on?  Just to make sure, I did review the internal firmware specifications and found that its definitions for the GLOB_CMD[1] and GLOB_CMD[2] bits are consistent with what is in Table 27 in the datasheet, and in the post that I made on Sep 10, 2017, at 12:47PM. Perhaps our internal design documentation is wrong, but I need more supporting information, to take that idea any further.

Reply
  • If you are going to say something is "Logic based" or refer to what "others use," I would encourage a bit more support for such claims. Who else is saying that bits 1 and 2 need to be flipped?  What logic is this based on?  Just to make sure, I did review the internal firmware specifications and found that its definitions for the GLOB_CMD[1] and GLOB_CMD[2] bits are consistent with what is in Table 27 in the datasheet, and in the post that I made on Sep 10, 2017, at 12:47PM. Perhaps our internal design documentation is wrong, but I need more supporting information, to take that idea any further.

Children
No Data