Eval-ADuCM355 Interrupts in sample code are never executing

Moved to  Precision Microcontrollers  community.

Hi,

Kindly refer to User guide available here :EVAL-ADuCM355 Evaluation Board | Analog Devices

I am having the same issue.   Your answer about referring to the User Guide is not helpful.   Why are the interrupts stuck?

Hi ShaheenTajik 

You will have to run in debug mode with breakpoints to check why interrupts are not asserted.

Code doesn't get stuck with default configuration unless interrupt lines and circuitry around ADuCM355 have error. Kindly check out EVALADuCM355QSPZ schematic for reference.

Hi CrossCore 

Can't understand your problem as you have not given any information on your implementation.

My platform is the ADuCM355 Eval Board.   My IDE is Keil uVision version 5.38.0

I am using the M355_ADC application from the Analog Devices github repo

aducm355-examples/examples/AnalogDie/M355_ADC at master · analogdevicesinc/aducm355-examples · GitHub

I am using AD5490_ADCPolliing.c as the source file.  Using the debugger I see that the AFEINTSRC_SINC2RDY flag never gets set.

By the way I have not modified any of the source code.

The default main code doesn't even call AD5490_ADCPolliing.c.

main.c calls only AD5940_ADCMeanFIFO.c

Within the Keil IDE I added file AD5490_Polling.c instead of AD5490_ADCMeanFIFO.   That is all I did.  It looks like these two files are interchangeable.  

I did a build using the ADC5490_ADCMeanFIFO as the source file then ran it again and still, I have the same issue.   This issue is the AFEINTSRC_DATAFIFOTHRESH is never set.

Infact the register REG_INTC_INTCFLAG1 is always a value of 0x61.   The interrupts are enabled but the flags never get set.   What is going on here?

Hi,

As mentioned above, you will have to run in debug mode with breakpoints to check if ADC5490_ADCMeanFIFO .c is entered and executed. 

I am running in debug mode.   That is how I was able to see that interrupt register is stuck at 0x61

I am running in debug mode.   That is how I was able to see that interrupt register is stuck at 0x61

Hi,

The examples work properly in our ADuCM355QSPZ boards.

Kindly check if interrupt lines are correctly configured so the microcontroller receives the interrupt properly.

The example works straight from GitHub in my setup. 

It might be that they are missing the CHIPSEL_M355 definition in IAR’s Options > Runtime Checking > C/C++ Compiler > Preprocessor > Defined Symbols

If CHIPSEL_M355 is not defined, the code will not execute lines below that shift the register address to the correct location.

#ifdef CHIPSEL_M355

static void AD5940_D2DWriteReg(uint16_t RegAddr, uint32_t RegData)

{

  if(((RegAddr>=0x1000)&&(RegAddr<=0x3014)))  /* 32bit register */

    *(volatile uint32_t *)(RegAddr+0x400c0000) = RegData;

  else                                        /* 16bit register */

    *(volatile uint16_t *)(RegAddr+0x400c0000) = RegData;

}

static uint32_t AD5940_D2DReadReg(uint16_t RegAddr)

{

  if(((RegAddr>=0x1000)&&(RegAddr<=0x3014)))  /* 32bit register */

    return *(volatile uint32_t *)(RegAddr+0x400c0000);

  else                                        /* 16bit register */

    return *(volatile uint16_t *)(RegAddr+0x400c0000);

}

regards,

Mark