Post Go back to editing

ADUCM355 Fifo threshold

Category: Software
Product Number: EVAL-ADuCM355QSPZ
Software Version: Keil uVision V5.37

Hello,

I have tried out the example M355_ECSns_SingleWE, which is working fine so far. Now i want to change the number of measurements, so i changed the pAmpCfg->M355FifoThresh = 10; in the AD5940Main.c. A threshold value of 8 or 9 works as expected, but when I change the threshold to pAmpCfg->M355FifoThresh = 3 it will send this to UART:

Hello AD5940-Build Time:13:52:47
This ADuCM355!
Note: Current Silicon is S2
AD5940LIB Version:v0.2.0
Freq:32097.126953
Calibrated Rtia = 106275.500000
Index 0:, 0.064 , uA
Index 1:, 0.064 , uA
Index 2:, 0.064 , uA
Index 0:, 0.064 , uA
Index 1:, 0.064 , uA
Index 2:, 0.064 , uA
Index 3:, 0.064 , uA
Index 4:, 0.064 , uA
Index 5:, 0.064 , uA
Index 6:, 0.064 , uA

Why does it correctly send the Index 0,1,2, as I chose 3 as threshold, but then immediately send another 7 values? I recognized, that this would happen also with other thresholds, for example 4 and it will send another 6 values afterwards. So always summing up to 10, I think.

I would appreciate any help, thank you.

Kind regards, Alexander  

Parents
  • Hi,

    Any value less than 7 for 

    pAmpCfg->M355FifoThresh is too quick for the code because

     After sleep is unlocked in AppAMPISR(), before result is finished displaying, many interrupts occur before being serviced, hence are missed.

    That's why all values >=7 work fine.

Reply
  • Hi,

    Any value less than 7 for 

    pAmpCfg->M355FifoThresh is too quick for the code because

     After sleep is unlocked in AppAMPISR(), before result is finished displaying, many interrupts occur before being serviced, hence are missed.

    That's why all values >=7 work fine.

Children
No Data