• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Subscribers 101 subscribers
  • Views 413 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.

AM6421: DebugP_log would delay enter of interrupt handler

Jenny Zhou
Prodigy 230 points

Part Number: AM6421

Tool/software:

Hi TI expert,

In my usage scenario, there's an accurate high frequency interrupt, which is expected to be executed in 12KHZ frequency.

I found if I added a loop call 'DebugP_log' , there's possibility that this 12KHZ ISR would delay to enter.

I config the 'Debug Log' like following screenshot, I believe log would be output to 'CCS log'.

So I suppose there would be an action to 'disable interrupt' inside of 'DebugP_log', right?

if it is true, we need avoid using this inside my whole application? Is there a solution to fix this?

  • 0
    TI__Guru** 110030 points

    Hello Jenny,

    What kind of delays are you seeing?

    Which core is this observed on?

    What version of the SDK are you using?

    I am sending your thread to another team member to comment.

    Regards,

    Nick

  • 0 in reply to Nick Saulnier
    Prodigy 230 points

    What kind of delays are you seeing? -- this 12KHZ isr is interactive with FPGA, FPGA observes 12K-isr has been delayed to run in some occursion.

    Which core is this observed on? -- A53

    What version of the SDK are you using? -- mcu_plus_sdk_am64x_10_00_00_20

  • 0 in reply to Jenny Zhou
    TI__Guru 62748 points

    Hi Jenny,

    Currently, the subject matter expert is out of office. Response to this thread will be delayed. Please expect responses in several business days.

    Thanks for your cooperation.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    TI__Guru 54238 points

    Hello Jenny,

    Can you please confirm where you are using DebugP_log API ?

    In ISR routine ?

    How did you generate a 12KHz frequency signal PWM or Timer + GPIO ?

    In, MCU+SDK, many places we disable global interrupts  for critical sections.

    So, this delay may also come due to different critical sections .

    Please confirm which peripheral's are used in the A53 Application.

    If you remove DebugP_log API in A53 application , the 12KHz frequency is generating  properly without delays  ?

    Regards,

    Anil.

  • 0 in reply to Swargam Anil
    Prodigy 230 points

    Hi Anil,

    pls see my answer below:

    Can you please confirm where you are using DebugP_log API ?

    In ISR routine ?

    --not in ISR, running in task schenario.

    How did you generate a 12KHz frequency signal PWM or Timer + GPIO ?

    --GPIO, and have the highest priority in my whole system.

    In, MCU+SDK, many places we disable global interrupts  for critical sections.

    So, this delay may also come due to different critical sections .

    Please confirm which peripheral's are used in the A53 Application.

    If you remove DebugP_log API in A53 application , the 12KHz frequency is generating  properly without delays  ?

    -- I believe other peripheral would not prompt this 12khz-isr, because this GPIO has the highest priority. Also, yes, if remove 'DebugP_log ', 12khz-isr would response without delay.

    Regards,

  • 0 in reply to Jenny Zhou
    TI__Guru 54238 points

    Hello Jenny,

    Based on the above results.

    The 12KHZ interrupt may delay due to Debuglog_P only. As I mentioned above inside this API there is, critical section which disables the global interrupts due to ISR is delaying.

    May I know how much time is delayed ?

    This is critical section we should not remove ..

    Regards,

    Anil.