• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 1204 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.

Stellaris LM4F120H5QR Launchpad connect error: Frequency is out of range

Uladzimir
Intellectual 470 points

Hi, I have got an error in CCS 5.2.1 during debugging:  CORTEX M4_0: Frequency is out of range. I have reinstalled ICDI drivers (i have tried drivers from CCS directory, and from ti site also), then tried to unlock target with the LM flash programmer, nothing to help. I see Stellaris ICDI and Virtual COM port in the device manager, but I can't connect to it with CCS or LM Flash programmer. When I trying to connect via LM flash programmer, the error appers "target is not connected".

Problem appeared when I finished lab5 (ADC, rom functions, volatile variables) and tried to debug lab6. Now, the green color of RGB led blinks twice when I power up board, then go out. 

What should I do?

  • 0
    Guru 86865 points

    Hi,

        Try "hold reset when using the lmflash unlock feature". See related post below for reference.

        http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/p/270528/945265.aspx#945265

    -kel

  • 0 in reply to Markel Robregado
    Intellectual 470 points

    Thank you! As in the related post I tried to unlock it yesterday, the notion "hold reset when power up" is in the popup dialog, so I did it. But yesterday it didn't work, today it works. I have read that this problem occured when one tried to program lab 6 from work book. Could you clear up, what's wrong with code from lab 6, or what was wrong in user's actions while programming it?

    P.S. Sorry for my poor english

  • 0 in reply to Uladzimir
    Guru 86865 points

    Hi,

        You are welcome. I don't have your setup, to verify. So, I can't really tell why. 

    -kel

  • 0 in reply to Uladzimir
    Guru 47900 points

    This reporter has neither your set-up nor lunchpad nor workbook...  (Preparation most always required)

    However - search your lab 6 code for any operation which impacts Port C - (PC0-PC3 specifically)  Should any of those pins be "harvested" by lab 6 - the JTAG will become confounded - which would explain your plight.

    If JTAG appears unaffected - mighy lab 6 have altered your System Clock - or xtal parameter, therein?  This would also "break" the JTAG.

    Agree whole-heartedly w/you - should this lab 6 issue have occurred in multiple - time to find (and solve) root cause.

    Your English is very usable/understandable - do make those checks - perhaps you can serve as lab 6's "hero."