• State TI Thinks Resolved
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 82 subscribers
  • Views 225 views
  • Users 0 members are here
Support feedback
Options
Options
Related

LAUNCHXL-F28P55X: LAUNCHXL-F28P55X sample code hangs in bool SysCtl_setClock(uint32_t config)

Abayomi Babatola
Intellectual 405 points
Part Number: LAUNCHXL-F28P55X
Other Parts Discussed in Thread: SYSCONFIG

Dear Sir/Ma,

Good afternoon.

I have a very strange experience with a new launch pad.  

Codes do not run to the while(1) after initialization.  The code get stucked in SysCtl_setClock(uint32_t config).  I find this very strange.

I also tried the gpio_ex2_toggle example and the code does not run into the 

    //
    // Loop.
    //
    for(;;)
    {
        GPIO_togglePin(myGPIOOutput0);
        DEVICE_DELAY_US(1000000);
    }
 
It also get stucks at the SysCtl_setClock(uint32_t config).
 
Please what can be the problem.  This problem is slowing down my work.
 
I have checked the settings of the launchpad and every thing looks okay, but the code does not work.  What can be the problem.  How can I resolve it?
 
Thanks.
 
Babatola Abayomi
 
 
  • 0
    TI__Genius 17605 points

    Hi Abayomi,

    In the debug panel, in the threads tab, it will mention where the issue is exactly. Please look into that.

    What is the clock source within SysConfig ClockTree Tool? The LaunchPad supports INTOSC1/2 and XTAL clock sources.

    Best Regards,

    Aishwarya

  • 0 in reply to Aishwarya Rajesh
    Intellectual 405 points

    HI,

    Thanks for the quick response.

    I am running the gpio_ex2_toggle example from the C200ware version 6

    A snapshot of the debug window is included below:

    The software I am writing also have this problem.  However, I have only one Lunchpad that behaves well and does not get stuck with this point.  The others have this probelm or jsut suddenly stop working

    When I click on comtinue the programme remain stucked there

    Thanks

  • 0
    TI__Genius 17605 points

    Abayomi,

    Do you see this issue with other examples? I was not able to replicate this issue on my end. Let me check in with the team if they've seen anything like this too.

    Best Regards,

    Aishwarya

  • 0
    TI__Genius 17605 points

    Abayomi,

    Let me know once you're able to pin-point exactly where the device is hanging/failing. 

    Which REV LaunchPad is being used? If using REV0, you will need to add REVID_REV0 in the predfined symbols, or else the device_cal function will fail. More information in sysctl.h.

    Best Regards,

    Aishwarya

  • 0 in reply to Aishwarya Rajesh
    Intellectual 405 points

    hi,

    Thank you for the reply.  

    I have checked the launchpad. The launchpad is a MCU133A version and the number is CL55240800021.  Is this a REV0 type.?

    I included the REVID_REV0 but the launchpad still has the same problem and hangs without stoping when I run it.

    Without the REVID_REV0, the cod does not run to the for (;;) loop and when I click on the stop button, stops at the position indicated in the snapshot I previously posted.

    At time it stops in the SysCtl_setClock(uint32_t config). 

    I presume the C2000 example configured the  SysConfig ClockTree  well?  The XTAL Frequency (in MHz)  is configured for 10 MHz.

    Please what can be the problem.

    Thanks

  • 0
    TI__Genius 17605 points

    Abayomi,

    MCU133A refers to CC built with Rev 0 Silicon, so you will definitely need the REVID_REV0 in your program. If I'm understanding correctly, after adding the predefined symbols, you're able to run to the for(;;), but it is still pausing at the SysCtl_setClock(uint32_t config). 

    I'm going to have to look at this further and get back to you.

    Best Regards,

    Aishwarya

  • 0 in reply to Aishwarya Rajesh
    Intellectual 405 points

    Hi,

    Thanks you for the reply.  I have tried the suggestions but the launchpad still get stuked at start up and does not run to the while (1).  The results of the suggestions are below

    1. When I include the REVID_REV0 the code did not link as there was no symbol for device_cal error.  That means that is not the solution.

    2.  I included the internal pull ups on the gpio35 and gpio37 in the code through the sysconfig but the problem is still there.

    What can I still do?.  The problem is dragging my  project back.

    Thanks.

  • 0
    TI__Genius 17605 points

    Abayomi,

    Abayomi Babatola said:
    1. When I include the REVID_REV0 the code did not link as there was no symbol for device_cal error.  That means that is not the solution.

    For MCU133A version, you must use this predefined symbol. Please rebuild the project, not just build the project LAUNCHXL-F28P55X: CPU crash when calling device_call function

    Abayomi Babatola said:
    2.  I included the internal pull ups on the gpio35 and gpio37 in the code through the sysconfig but the problem is still there.

    This is not needed.

    Best Regards,

    Aishwarya