• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 206 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

AM2634: SDL_ESM_config groups, interrupts, and bitmaps

AM2634: SDL RTI Example Timing Error

Kai Clausen
Prodigy 30 points
Part Number: AM2634

When I run the sdl_rti_example_uc1_am263x-cc_r5fss0-0_nortos_ti-arm-clang example code on the AM2634 Control Card the WWDT0 expired interrupt is triggered immediately rather than waiting for the defined timeout (10s). The console printout indicates all tests pass, but the timing behavior is unexpected. 

Is this behavior repeatable? Is this an error in the example code? 

  • 0
    TI__Genius 15435 points

    Hi,

    What is the frequency of the RTI timer you're using? We have observed few issues with watchdog during our general testing as well. Let me check with the SDL team and get back on this.

    Thanks

  • 0 in reply to Kowshik Gudimetla
    Prodigy 30 points

    Here is the RTI0 settings from example.syscfg in the project: 

    This structure is used in SOC_moduleSetClockFrequency() 

    Fullscreen
    1
    2
    3
    4
    5
    SOC_SDL_ModuleClockFrequency sdl_gSocModulesClockFrequency[] = {
    { SOC_RcmPeripheralId_WDT0, SOC_RcmPeripheralClockSource_SYS_CLK, 32000 },
    { SOC_MODULES_END, SOC_MODULES_END, SOC_MODULES_END },
    };
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Kai Clausen
    TI__Genius 15435 points

    Hi kai,

    Is this configuration from the CCS example or you've configured it?

    Thanks,

    G Kowshik

  • 0 in reply to Kowshik Gudimetla
    Prodigy 30 points

    That is the configuration from the CCS example included with the 8.05 SDK. 

  • 0 in reply to Kai Clausen
    TI__Genius 15435 points

    Got it, let me check on this. The reason I asked is, I suspected you have written wrong value to the WDT registers and according to the TRM, if the WDT hardware detects any incorrect writes to the pre-load value register it asserts an POR of the SoC.

    Let me dig through the example and revert.

    Thanks