• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 348 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Sometimes Imp_Sdram_Irq interrupt is not occurred

Hyunho Youn
Intellectual 260 points

Hi,

 

I use DVSDK 4.01, and my dm365 board base on DM365EVM.

The capture mode is continuous mode, the sensor is YUV 16bit 720p.

In the most case, my board is working well.

However, sometimes, Imp_Sdram_Irq interrupt is not occurred at my DM365 board, like below

# cat /proc/interrupts
           CPU0
  0:        577       AINTC  vpfe_capture0
  5:          0       AINTC  Imp_Sdram_Irq
  8:       2008       AINTC  davinci_osd
 12:          1       AINTC  musb_hdrc
 16:          0       AINTC  edma
 17:          0       AINTC  edma_error
 23:          0       AINTC  sdio0
 26:        288       AINTC  mmc0
 32:       2434       AINTC  clockevent
 33:          0       AINTC  free-run counter
 39:         86       AINTC  i2c_davinci
 40:        432       AINTC  serial
 52:          0       AINTC  eth0
 53:         84       AINTC  eth0
 54:         14       AINTC  eth0
 55:          0       AINTC  eth0
Err:          0
#

 

Once Imp_Sdram_Irq interrupt is not occurred, I power off and on my board.

After several times power off/on, it is working well.

What is the problem on my dm365 board?

 

  • 0
    Prodigy 10 points

    I have the same issue on my board using kernel 2.6.37+.

    The problem occurs every times I use the reboot command for restarting the system.

    CPU0

    0: 48 AINTC vpfe_capture0
    1: 48 AINTC vpfe_capture1
    5: 0 AINTC Imp_Sdram_Irq
    8: 3864 AINTC vpbe-v4l2
    12: 592 AINTC musb-hdrc
    16: 99 AINTC edma
    17: 0 AINTC edma_error
    18: 0 AINTC spi_davinci.1
    29: 0 AINTC davinci_rtc
    32: 2894 AINTC clockevent
    33: 0 AINTC free-run counter
    39: 23 AINTC i2c_davinci
    40: 96 AINTC serial
    42: 0 AINTC spi_davinci.0
    46: 1 GPIO-AINTC can_int
    48: 0 GPIO-AINTC mmc_door
    60: 1 AINTC davinci_keyscan
    Err: 0

    If I use poweroff and than power up the board the system work well. 

    Hyunho have you found where is the problem?

    Thank you

    Ivan Spagnolatti

  • 0 in reply to Ivan Spagnolatti
    Intellectual 260 points

    Hi, Ivan.

     

    At that time my problem was occored rarely.

    After write the question, I got no response from anyone,

    so I upgraded DVSDK 4.01 --> DVSDK 4.02 at that time.

    After DVSDK 4.02 upgrade, I didn't meet that problem. At same time, I modified my sensor related code also.

    I don't know the DVSDK upgrade is the unique solution of that problem.

    But, my case, upgrading DVSDK and modified sensor related code might be the solution.

     

    PS.

    In my experience. software-reboot make no capture function or resize-done IRQ.

    it may be related sensor control or ISIF config.

    When CPU reset, the sensor HW is need reset for somecase.