Cannot read data with EVAL kit. AD4134 - WaitOnDataCapture, Failed

Hi RyanScion ,

Can you please confirm ACE and AD4134 plug-in are updated?

We will look into this. In the meantime, please try reducing the number of samples captured and retry data capture.

Thanks,
Janine

Hello, 

Thank youf ro the quick response. I can confirm that ACE software and the plug in are up to date. They were both downloaded and installed yesterday and I have performed an update check for the software and the board/chip plug-in. Everything is up-to-date. 

I've tried to get a read out with two seperate EVAL-AD4134FMCZ boards with the same results.

I have found that the "default" config defined in the UserGuide was inaccurate. JP16 was actually set to closed. Which forced the board into Slave mode. I have now addressed this and set it to "High" or open. 

Unfortunately I still cannot get it to work.Here is the current configuration and some measurements of the hardware + my register settings for review. 
I have removed R19 and R28 to remove the U4 bypass. 

Then fit 0R links for R38, 39, 62 and 63 to allow common mode biasing of CH1. 
My board signal levels are:
J1 AIN+INP = 1.001V
J1 AIN-INP = 0.001V

ADC Input AIN1+ = 2.55, AIN- = 1.4V 
With VCM out enabled the U4.2 pin reads 2.04V as expected
With Clk out enabled the Clkout tp111 shows a stable 48MHz

The 1.8V, 5V and Vref signals are all within spec. All voltage rail resistors are configured as per default configuration in the UserGuide.

All 4 channels are enabled. Ch0, 2 and 3 have floating inputs with op-amp circuits bypassed. 

It's worth noting that the only default option in the Ace software for setting the output data format is 24bit + CRC which is explicitly stated as not compatible with ACE. I have to go into the memory map and set register 0x11 = 0x20 to overcome this issue. As per the following 2 images.

Here are the register Settings I'm using now:
0x00000010,0x02,AD4134
0x00000011,0x30,AD4134
0x00000012,0x02,AD4134
0x00000013,0x00,AD4134
0x00000015,0x1D,AD4134
0x00000016,0x080,AD4134
0x00000017,0x25,AD4134
0x00000018,0x00,AD4134
0x00000019,0x00,AD4134
0x0000001A,0x00,AD4134
0x0000001B,0x00,AD4134
0x0000001C,0x00,AD4134
0x0000001D,0x00,AD4134
0x0000001E,0x0AA,AD4134
0x0000001F,0x00,AD4134
0x00000020,0x00,AD4134
0x00000021,0x0FF,AD4134
0x00000022,0x00,AD4134
0x00000023,0x00,AD4134
0x00000024,0x00,AD4134
0x00000025,0x00,AD4134
0x00000026,0x00,AD4134
0x00000027,0x00,AD4134
0x00000028,0x00,AD4134
0x00000029,0x00,AD4134
0x0000002A,0x00,AD4134
0x0000002B,0x00,AD4134
0x0000002C,0x00,AD4134
0x0000002D,0x00,AD4134
0x0000002E,0x00,AD4134
0x0000002F,0x00,AD4134
0x00000030,0x00,AD4134
0x00000031,0x00,AD4134
0x00000032,0x00,AD4134
0x00000033,0x00,AD4134
0x00000034,0x00,AD4134
0x00000035,0x00,AD4134
0x00000036,0x00,AD4134
0x00000037,0x00,AD4134
0x00000038,0x00,AD4134
0x00000039,0x00,AD4134
0x0000003A,0x00,AD4134
0x0000003B,0x00,AD4134
0x0000003C,0x00,AD4134
0x0000003D,0x00,AD4134
0x0000003E,0x00,AD4134
0x0000003F,0x00,AD4134
0x00000040,0x00,AD4134
0x00000041,0x0F,AD4134
0x00000042,0x00,AD4134
0x00000047,0x00,AD4134
0x00000048,0x00,AD4134
0x00000000,0x18,AD4134
0x00000001,0x080,AD4134
0x00000002,0x0F1,AD4134
0x00000003,0x07,AD4134
0x00000004,0x0D2,AD4134
0x00000005,0x0D,AD4134
0x00000006,0x00,AD4134
0x00000007,0x02,AD4134
0x0000000A,0x00,AD4134
0x0000000B,0x02,AD4134
0x0000000C,0x56,AD4134
0x0000000D,0x04,AD4134
0x0000000E,0x00,AD4134
0x0000000F,0x00,AD4134

Analysis Settings prior to selecting "Run Once"

I've also found that setting 0x25 (Diagnostics register) bit 2 (ERR_SPI_CRC_EN_HARD) will cause write errors. It seems to cause register edits to fail.
While setting 0x25 bit 1 (ERR_MM_CRC_EN - Memory Map Integrity Check bit) also causes errors and bit flips every time I perform a read all and diff.
Setting 0x25 bit 4 ( ERR_PWR_MON_EN) also causes the NO_CHIP_ERR bit in register 0x02 = 0. 
This flag is not defined in the datasheet Figure. 123. Errors
Infact PWR_MON_EN doesn't show up in the datasheet at all. It seems to be a reserved bit. Which doesn't align with the plugin for the AD4134 dev kit.

None of these errors/inconsistencies are documented in the UserGuide.

An additional update. I managed to get one successful reading this morning. By powering up the board > start software > reset board in software > straight to analysis (not fixing the error of default format having CRC enabled) > perform analysis 

This resulted in a single reading decent reading. I have not been able to repeat this process over multiple attempts. 

Hi RyanScion ,

I have tried duplicating your setup.

The frame should remain in 24bit+CRC, (DCLK will still be 24 bits in this case) Changing this to other configurations will result to transaction errors.

Are you encountering the same "Transaction Errors" in analysis?

Thanks,
Janine

Hi RyanScion ,

Thank you for noting these. I observed the same results as you. I will look into this further and verify if these diagnostics are supported in the evaluation software.

After which, we will adjust the documentation accordingly.

Thank you,
Janine

The exact error I was seeing appears at the bottom left corner of the Ace software, the status message. It shows "AD4134 - WaitOnDataCapture, Failed". 

That's all i can say for sure. 

So based on what you have said above should the device use 24bit+CRC or not? I know it defaults to this and I did manage to get one successful reading like this. But it's explicitly stated that it shouldn't work in this mode. 
It's worth noting my testing implied that using 24bit+CRC results in failures to read/write registers successfully. So I am hesitant to trust any data reading it might provide. 

Also, could you elaborate on what "transaction errors" means. Perhaps with a screenshot, just in case I am getting that same error and I'm not aware off it.

Hello RyanScion ,

Yes. I am getting the same error.

In *Main mode, retain the setting 24bit+CRC, DCLK and DOUT are 32 bits. This is the only data format supported in ACE.

In *Secondary mode, I was able to capture data for all data formats. Are you planning to use the device in *Main mode?

I have also escalated this issue to our software team and will get back once I have more information.

Thanks,
Janine

*ADI: Words Matter - Help Articles - How to Use EngineerZone - EngineerZone

Hi RyanScion ,

Can you advise on the status of your issue?

I am able to capture data by retaining the setting of the output format.

Thanks,
Janine

Hi RyanScion ,

Can you upload the AppTrace file found in the directory below after encountering the error.

C:\Users\Username\AppData\Local\Analog Devices\ACE

Thanks,
Janine