EVAL-AD5941BATZ - AD5940_BATImpedance example code stuck after 2nd measurement RCAL

The "AD5940_Impedance" example seems to run, and seems to get past the "AD5940_GetMCUIntFlag". However, the values obtained look like gibberish. 

I also tried to run the temperature example. This one also gets stuck on the GetMCUIntFlag.

Hi, Akila .

Can your team please help look into this query?

Warm regards,
Jo

on the AD5940_Impedance I figured that it can not be ran with this specific devkit, so no need to look into the faulty values. It can be used as a reference that some ADC measurements seem to run fine with an interrupt?

The issues with the Battery Impedance example still appear. For some reason it cannot reset the interrupt as written above. I have tried various debugging steps. Which narrow down to the specific check of the interrupt flag:

When running through the code with the debugger I go as deep as reading the register for interrupt flag 01. I see that when trying to read register 0x3014, the response is first hex 04808067 for a while, and then it switches to 84808067. Only before the first Rcal measurement it switches to 06808067, which is a positive response for the interrupt flag.

Secondly, the rcal volt is as little as 0 both real and imaginary, whilst a battery is connected, and a voltage of ~3.24 is read between S- and S+ AND F- and F+

hi NathanT , 

Do you have any updates on this topic?

Kind regards, 

Bas

Hi,

     May I know if you are using the correct library file?

AD5940_BatImpedance example has its own library file in this example's folder. 

AD5940_BatImpedance example should be used with its own library file, not the common library file available here: github.com/.../ad5940lib

Hi Akila , 

I have changed the AD5940.c and .h libraries as you advised. 

Unfortunately I am still getting stuck on the same piece of code. Hereby a breakdown of my debug process:

Example: AD5940_BATImpedance, LIB version v0.2.1 taken from Github

The code runs fine for the first part:

code enters "AD5940_Main();" as expected

In "AD5940_Main();" it runs through most functions, up untill "AppBATCtrl(BATCTRL_MRCAL, 0);"

In the function "AppBATCtrl(BATCTRL_MRCAL, 0);" it runs until the function "AppBATMeasureRCAL"

This function is executed, and cycles the first time performing one calibration measurement (0.000000, 0.000000)

The second time it enters the for-loop, it gets stuck awaiting the INTCTestFlag

I did print the returned flag values, shown in the console log. All I know is that it does not trigger the correct bit no more. The other parts of the flag I cannot decode with the information I have available right now.

Is this a workable starting point for you?

Can you share the library link?

hi Akila , 

I used the following codebase: https://github.com/analogdevicesinc/ad5940-examples

From this codebase I used the /examples/AD5940_BATImpedance project in KEIL uvision. 

I followed the tutorial on setting up the KEIL environment as explained on the analog devices wiki: https://wiki.analog.com/resources/eval/user-guides/circuits-from-the-lab/cn0510 

The code builds fine, no errors, and flashes to the correct target.

I have tried this with 2 versions of the AD5940ilb-master. I used the original as found in the github codebase AND I also tried replacing the AD5940 lib with the other files you sent me a link to: https://github.com/analogdevicesinc/ad5940lib

Unfortunately, I get the same deadlock on both libraries. The deadlock and debug/trace problem identification are shown in my previous comment. Each time I get stuck on INTCTestFlag not getting the correct flag value. 

Libraries to be used:

- https://github.com/analogdevicesinc/ad5940-examples/blob/master/examples/AD5940_BATImpedance/ad5940.c

- https://github.com/analogdevicesinc/ad5940-examples/blob/master/examples/AD5940_BATImpedance/ad5940.h