• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 419 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.

AM2432: DCC configuration issue

Jimmy
Prodigy 180 points
Part Number: AM2432


Tool/software:

Hello Expert

We are configuring the DCC function. The clock source selection uses HFOSC0_CLKOUT (25M) and CLK_12M_RC, with DRIFT set to 1. An abnormality report is generated after initialization. Here are our questions:

1、What is the accuracy of the CLK_12M_SC clock?

2、In accordance with the chip and functional safety requirements, does the DCC function have any requirements for the accuracy of the selected clock source?

3、Within what range is it recommended to set DRIFT during DCC configuration?

SDK:mcu_plus_sdk_am243x_09_01_00_41

Thank you.

Jimmy

  • 0
    TI__Mastermind 22686 points

    Hello Jimmy,

    Are you using the SDL DCC APIs to configure the DCC module? Ca you share the DCC configuration you are currently using in your application?

    Regards,
    Nihar Potturu. 

  • 0 in reply to Nihar Potturu
    Prodigy 180 points
    Hi Potturu
    My DCC configuration is as follows：
            .cSrcStr = "RC OSC",
            .cTestStr = "HFOSC0",
            .DccInst = SDL_DCC_INST_DCC0,
            .Clk0Src = SDL_DCC_CLK0_SRC_CLOCK0_2,
            .ulClk0Freq = 12000U, /* 12.5 MHz for RC OSC */
            .Clk1Src = SDL_DCC_CLK1_SRC_CLOCKSRC4,
            .ulClk1Freq = 25000U, /* 25 MHz for HSOSC0 */
            .Mode = SDL_DCC_MODE_CONTINUOUS,
            .ulErrorTest = 0x0U

    Thank you.

    Jimmy

  • 0 in reply to Jimmy
    TI__Mastermind 22686 points

    Hello Jimmy,

    I tried to reproduce the issue at my end. I was unable to see any ESM error getting generated for the below configuration in the SDL DCC example.

    SDK:mcu_plus_sdk_am243x_09_01_00_41

    #define NUM_USE_CASES          (0x1U)

static DCC_TEST_UseCase DCC_Test_UseCaseArray[NUM_USE_CASES] =
{
    /* Continuous - no error */
    {
        "RC OSC",
        "HFOSC0",
        SDL_DCC_INST_DCC0,
        SDL_DCC_CLK0_SRC_CLOCK0_2,
        12000, /* 12.5 MHz for RC OSC */
        SDL_DCC_CLK1_SRC_CLOCKSRC4,
        25000, /* 500 MHz for MAIN_SYSCLK0 */
        SDL_DCC_MODE_CONTINUOUS,
        0x0,
        0xFFFF,
        0x0
    },
};

    Did you make any other changes to the DCC example? 

    Regards,

    Nihar Potturu. 

  • 0 in reply to Nihar Potturu
    Prodigy 180 points

    Hi Potturu:

    I modified the value of APP_DCC_TEST_CLOCK_SRC_1_DRIFT in the SDK to 1. I believe this reflects a requirement for precision, and the macro definition is located in dcc_uc1.h.

    Thank you.

    Jimmy

  • 0 in reply to Jimmy
    TI__Genius 9751 points

    Hi Nihar, 

        Could you please sync up with hardware team and answer the CLK_12M_SC accuracy question directly? Thanks.

    Linjun

  • 0 in reply to Linjun Meng
    TI__Mastermind 22686 points

    Hello Linjun,

    Linjun Meng said:
        Could you please sync up with hardware team and answer the CLK_12M_SC accuracy question directly? Thanks.

    As discussed earlier, we cannot use CLK_12M_SC for getting 1% accuracy in DCC. They would have to use the an external clock for this 

    Closing this thread now. 

    Regards,

    Nihar Potturu.