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.

28069 ControlStick Variant Stuck in Halt LPM mode

Folks - I finally got my 28069 to go into Halt mode.  I have a very simple program to do this, based on the TI examples, that runs from flash (except the code between sending flash into low power mode and the device into Halt).  The problem is that I did not enable any wakeup functionality.  I figured I get her into Halt, test the current consumption, and then use the debugger to somehow bring her out of Halt for a new program load.  It appears, however, that there is no way for CCS (I've tried 5.1 and 5.5) to pull it out of Halt mode.  Any access attempt from CCS either complains that the device is in low power mode or, much more often, simply hangs trying to talk to the device.  CodeSkin C2Prog also does not work.  The circuit is, effectively and 100% digitally, equivalent to the 28069 ControlStick with USB/XDS100v1 JTAG functionality.  The circuit does not, however, have the multipin header.  Can this be saved?  Can CCS "unwedge" the micro from Halt mode somehow?  Is there a pin I need to ground or bring to 3.3V?  

Thanks or any help.  I've looked through all the forum material and, while folks have struggled getting it into Halt mode, I don't see anything that talks to getting it our of Halt mode should it get stuck there.  Likely I'm just missing something obvious within CCS.

Thanks,

John

  • John,

    Unsure about the CCS option.  However, I am pretty sure that if you can get the MCU into a different boot-mode you will not be stuck in a low-power mode.  Wait mode or boot from SCI would be decent options.  This in turn would allow you to connect to the device via CCS as normal (because it won't be in a low-power state).

    When CCS tries to connect to the F28069, it likely pops up a message asking you if you want to bring it out of the low-power mode.  Is there where things are messing up on you?


    Thank you,
    Brett

  • Brett - thanks for the reply.  I do not have an obvious means to change the boot-mode with this device.  I typically do that by modifying EMU-BMODE with the debugger, but the debugger refuses to connect to the device in Halt mode.  Some more data and, maybe/hopefully, you have other suggestions:

    - The debug activity gets stuck at "Launching..." with the indicator showing this activity is at 100% complete

    - CCS just hangs at this point, waiting.  If I unplug the device, I get Error -1041 @ 0xFFFFFF66 "The emulator reported an error"

    - If I run XDS100serial on the device, it is happily discovered

    - When I run C2Prog in an attempt to load a firmware image that won't Halt, I never get past "Programming"

    It just seems like my current configuration refuses to connect to the target if it is LPM halt.  I had thought, and some things I read would support the notion, that the debugger can access the board in Halt mode.

    Any ideas would be great.

    Thanks,

    John

  • John,

    While you can change the boot mode by setting the EMU-BMODE value, you can also do it by pulling the appropriate pins high and low.  My advice is the same as Brett's, we need to put the device into the wait boot mode and then connect with the debugger.

    In your previous message you mentioned pulling pins high and low.  Can you easily do that on the boot pins?

    BR,

  • Trey and Brett - thanks for the feedback.  I can send the board back to my manufacturing folks where they can add leads to the boot pins such that I can get her booted into another mode.  I was hoping there was some way the emulator could attach to the target in Halt mode and programmatically boot it into another state and unwedge it.  As it does not appear that is an option, I will go with "Plan B".  Thanks for your help.

    John

  • John,

    If you are using the controlSTICK as a base for your board, you should be able to remove the equivalent of R9 OR R14 and then pull the MCU side of the appropriate resistor pad to ground.  This should be a pretty easy rework assuming that you board isn't super compact (and assuming you have a soldering iron handy :) ).  Once you've reflashed your board, you can then repopulate the resistor you removed and all the blue-wire.

    Plan A may be possible, but I have some concerns based on a few experiences I've had.  I also think it will take us a while to get a solution to you.  Plan B would be the route I'd take.


    Thank you,
    Bret