• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 383 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.

Running an LM4F application without the emulator

John Osen
Genius 3585 points

I have developed an application for an LM4F232H5QC using CCS 5.2 using a XDS560 emulator.  It is time to move from emulation to embedded testing.  When I stop the emulation from CCS the app is still running.  When I power-down and disconnect the emulator, the app is still running.  When I cycle power to the target device, the application does not appear to run.  One of the first things the application does is to send out a CAN message; this message is not detected after disconnecting and cycling power, indicating the application has not gotten past initialization.

What do I need to do to get the application to run after disconnecting from the emulator and cycling power?

  • 0
    Guru 117855 points

    Do we recall correctly that yours is an official EK232 Eval Board - thus the HW is not suspect?

    Assuming correctly implemented (and surviving) HW - usual suspect in such case is program placement @ "unexpected/illegal" location.   Have you attempted to employ a boot-loader - or otherwise modified your program's normal/customary use of memory? 

    And wrt (with regard to) your specific JTAG Probe (not emulator)... "When interfacing to the EK-LM4F232, the attached xml file must be placed in the CCS folder: ccs/common/targetdb/drivers folder.   (Attached xml file: 5340.tixds100v2cortexM.xml)"   Attribution: TI's Lela Garofalo.

    This leads to the natural question - had you ever loaded - then tried to run even simple programs (i.e. blinky) via, "Standalone?" 

    Suggest that you replace your custom App w/ "blinky" and see if that works.  (suspect your App may "wait" for remote CAN "line/signal presence" or such - and thus "hang.")  KISS always should be, "best/first" option...

    Yet more to this "swelling" laundry list... might your Probe be providing pull-up to MCU Reset - and your external circuit sinks sufficiently to hold the MCU in reset when the probe is removed? 

  • 0 in reply to cb1_mobile
    Genius 3585 points

    cb1_mobile

    Thanks for recalling that I have been using an EKS system.  I am now using our target HW.

    Your comments made me check again.  It appears that our first prototype circuit takes about 10 seconds for the processor to actually halt after removing power.  I was cycling power at about 4 seconds after removing power and the application was still running.  It appears if I am patient enough, the device is working just fine.

    Thanks for taking the time.

  • 0 in reply to John Osen
    Guru 117855 points

    John - Merci monsieur, J'avais l'appreciation tres grande.   Even blind (remotely diagnosing) squirrel occasionally stumbles upon tasty walnut...

    However - that ~10 second, "shut-down" window alarms!  Our units, "sniff" for potential loss (i.e. downward ramping) of un/poorly regulated Vin (before our on-board VReg) - and order an, "orderly shut down" - saving any "key" data, just in case...  I fear doing much more during such questionable, unstable periods...