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.

TMS570LS3137: Startup tests

Part Number: TMS570LS3137

Hi Team,

From the spnu499c.pdf, for performing cpu self test, GCLK and VCLK has to be configured to 180 and 90 MHz. But, could not see any clock restrictions for CPU Compare Module for Cortex-R4F.
We are planning to skip CPU self test and execute only CCM self tests. Do we have any restrictions for this with respect to clock frequency and cpu self test?

  • Hello,

    HCLK = 180MHZ, VCLK = 80 and STCCLK = 90MHZ MHz are given in Table 8-2 not as a restriction but because given Test times (the last column) are measured at these clocks. STCCLK can be divided by 1..8 using CLKDIV field in STCCLKDIV register. So, there is no restriction.

  • Thanks Miro.

    Can you provide us the details on how timing values are calculated. Since, we want to use the HCLK/GCLK to lower frequency values than what is provided in the document.

    Also, I was requesting on CCM test (chapter 9 of spnu499c.pdf). Will the tests support even with 10 MHz of GCLK/HCLK? Can we run CCM self tests without executing cpu self tests?

  • Hello,

    In Table 8.1 (spnu499c.pdf) in addition to Test time in microseconds (last column), Test time in Cycles is given as well (third column).

    Test time = Number of cycles * tcycle
    So, for 90MHz clock and one interval:
    Test time = 1365 * (1/90MHz) = 15.17us

    Yes, you can run CCM self test at any CPU clock. Keep on mind that minimum frequency if OSCIN is used as a clock source is 5MHz (Table 6-9 in device Datasheet).

  • Sure Miro, but without executing cpu self test and with clock frequency set to 10 MHz, we are not perform ccm self tests. Can you recheck and confirm it?

    Note: It is working with HCLK configured to 180MHz but not with 10 MHz.

  • Hello,

    Would you clarify what not working means? Flag is not raised or test is not reaching the end.

  • Hello,

    You need to make sure that you run CCM selftest when you are not connected to the debugger.

  • Test s not reaching the end and we tried with and without debugger and the result is same.

  • Hello,

    Miro is correct. STC clock divider (STCCLKDIV) register in system module is used to divide HCLK(system clock) to generate STCCLK. The only restriction is that the maximum clock rate for the CPU self-test is 90MHz (Maximum STCCLK = 90MHz).

    The HCLK and VCLK should be within the clock range defined in the datasheet (Max HCLK is 180MHz, max VCLK is 100MHz). There is no other clock restriction for performing CCM self test.

  • Hello Screenivasan,

    How did you configure the PLL? and what is the OSCIN for the device?

    When you configure the PLL, the internal clock (OSCIN/refclkdiv) should be between 1MHz and OSCIN Frequency. Please double check your settings. For getting a slower PLL clock (10MHz) with OSCIN=16MHz, a bigger REFCLKDIV MIGHT be used.

  • Hi Wang,

    Can we configure VCLK2R and VCLKR fields with 0 value? The reason is that we want VCLK(2) to be same as HCLK frequency. Can you please check and confirm on this?

    OSCI freq is 16 MHz.

    PLL1 is configured 20 MHz and VCLK and VCLK2 is intented to configure 20MHz, but with that, we are not able to complete CCM self tests.

  • Hello Screenivasan,

    The VCLK can be HCLK/1, HCK/2, … or HCLK/16. Can you execute your code in normal mode (not selftest)? Can you post your PLL1 configuration? What is the reference clock divider?

  • Hi Wang,

    With PLL1=VLCK1=VCLK2=GCLK=HCLK=20MHz and by commenting CPU, CCM self tests, it was working fine. But, when we enable CPU or CCM self tests, we are seeing the issue (not coming out of cpu/ccm self tests). Do we have any restrictions on clock frequencies when configured low (as to 20 MHz)?

    *pllctl1 = (Uint32)((0x20000000UL)
    | (0x1FUL << 24UL)
    | (5UL << 16UL)
    | (0x0E00UL));

    And as i mentioned, reference clock divider will be zero in order to keep HCLK=VCLK=VCLK2.

  • Any updates on this?

  • Hi Wang,

    Any information needed further. Can you please share your updates on this?

  • Hi Wang/Miro,

    Any updates on this? Can you please share your inputs on this?

  • Sreenivasan,

    CCM self-tests do not complete if the CPU has ever entered debug mode (halted) for any reason since the last power-on-reset. If you want to check if the CCM self-tests are working correctly, you should create a pass/fail marker (I/O pin for example), program the part, disconnect debugger, and then assert power-on-reset. Once you release this reset, the code for the CCM self-tests will be executed and you can look for the pass/fail marker. Essentially, you cannot use the debugger to run these self-tests.

    Regards,

    Sunil

  • Hi Sunil,

    As mentioned earlier (Sep 4, 2019 2:19 PM In reply to Miro:Test s not reaching the end and we tried with and without debugger and the result is same.),

    we notice the same behaviour with or without debugger. The behaviour is, CCM self tests are not completed. Can you please are there any dependency with respect to clock frequencies? We see this behaviour with VCLK=VCLK2= HCLK set to 20 Mhz.

  • Hello,

    The CPU clock frequency doesn't affect the CCM4F selftest. I just tested CCM4F selftest with HCLK=20MHz, 40MHz. 

    To run the CCM4F selftest, load the code to the MCU flash, and power cycle the board. As Sunil said, please toggle one GIO pin in main().