• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 221 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.

TMS320F28379D: Count cpu resets and sources

UserHomeInit
Expert 2205 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE

Dear TI,

I'm encountering multiple issues while attempting to configure the PLL clock for my project . I'm using the TI function to set the configuration.

Specifically, the following line in the IniSysPll() that check the overflow of timers (1&2), the execution is stoped in this line cause timer 2 is not runing

        while((s_sDrvTIM_CoreCpuTimer2Regs.TCR.bit.TIF == 0) && (s_sDrvTIM_CoreCpuTimer1Regs.TCR.bit.TIF == 0));

I'm uncertain if my DSP is resetting each time, and I'm struggling to comprehend why my timer 2 isn't counting even when I'm using the identical code provided by TI.

Is there a register that tracks the number of resets caused by the watchdog? How can we verify the source of the reset if it occurs?

I coudl notice aslo that some EALLOW are not followed by EDIS in this funciton is it normale?

Thank you in advance.

Sincerely, Tarik

  • +1
    TI__Guru* 95315 points

    Tarik,

                    I suggest you switch to Driverlib. Support for bit-fields is deprecated and only Driverlib is updated and maintained (for bug fixes etc). In any case, all C2000ware functions are tested before release. If a (modified) function does not produce the intended result, it is likely that there is some issue with your modification (or some hardware issue).

    UserHomeInit said:
    Is there a register that tracks the number of resets caused by the watchdog?

    No.

    UserHomeInit said:
    How can we verify the source of the reset if it occurs?

    Using the RESC register.

    UserHomeInit said:
    I coudl notice aslo that some EALLOW are not followed by EDIS in this funciton is it normale?

    Generally, EALLOW and EDIS instructions are always used in pairs in C2000ware functions. Regardless, absence of EDIS should not cause a problem during debug.

  • 0 in reply to Hareesh Janakiraman
    Expert 2205 points

    Hello Hareesh Janakiraman,

    Hareesh Janakiraman said:
    it is likely that there is some issue with your modification (or some hardware issue).

    I have personally tested my time TI examples and can confirm that they function correctly.

    I want to clarify that I'm not implying that TI has any bugs, but I am seeking assistance to identify why my timer2 is not operational. I am confident that the issue lies within my code because I am attempting to run a project that was originally designed for the 280049 on a 28377D DSP. This discrepancy could be attributed to a variety of factors.