• State TI Thinks Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 2 answers
  • Subscribers 82 subscribers
  • Views 2310 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.

Resetting F28069 experimental kit

KV
Expert 1800 points


Hi,

I was experimenting with F28069 kit and CCS V5.  I was trying level 4 of sensorless PMSM code from RAM.  I was iterating the PID values and the system hanged.  I rebooted the kit by power booting.  However it stopped communicating with XDS100v2 emulator and unable to reset too.  I could not progress.

Could I know how to sort this issue.  Is there any way to reset the kit.  Pl suggest.

Thx & rgds

 

  • 0
    Prodigy 210 points

    Hi,

    I am new to the 28069 experimenter's kit. The one with the control card & docking station. I had configured it for XDS100V1. I have seen in docs that XDS100V2 is used for F28335 device. Can that be the reason?

    Regards

    Raghu

  • 0 in reply to Paramasivam Raghunathan
    Expert 1800 points

    Hi,

    I do not think that could be the reason.  Pl check http://processors.wiki.ti.com/index.php/XDS100 on the emulator drivers.

    Could you share how you went about boot pin setting?. If I am right the experimental kit has SW1 to take care of boot setting.

    I could successfully load the flashingLeds code.  However if I reset the controller its not pointing to main() and get the following error

    No source available for "c_int00() at 0x8493"
    No source available for "0x3ff788"

    C28xx: Trouble Reading PC Register: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 5.0.520.0)
    C28xx: Trouble Reading PC Register: (Error -1142 @ 0x0) Device blocked debug access because it is currently executing non-debuggable code. Choose 'Rude Retry' to disable polite mode and force the operation. (Emulation package 5.0.520.0)

    I tried  flashingLeds code successfully numerous times earlier.  But now I am unable to progress.

    Pl review and suggest at the earliest.  

    Thx

  • 0 in reply to Paramasivam Raghunathan
    TI__Mastermind 22025 points

    Raghu,

    All of the emulators on the docking station are XDS100v1, so if you are in fact using the docking station emulator you should select XDS100v1 as your emulator in CCS.  Some of the newer cards have a built in XDS100v2 directly on the controlcard, but I don't believe the F2806x controlcards have this.  An easy way to tell the difference is by the marking on the FTDI part.  If the chip is a FT2232H, then the emulator is an XDS100v2, otherwise the emulator is an XDS100v1.

    Are you having trouble connecting to and programming the controlCard?

    Trey

  • 0 in reply to KV
    TI__Mastermind 22025 points

    Indiantuktuk,

    I was originally concerned you may have locked the device but I don't think that is the case.  To answer your original question there is no magic button you can press to reset the kit back to its state from the factory.  The best you can do is power cycle the device and disconnect/reconnect the emulator from the PC.

    I wouldn't be concerned about the "No source available" warnings.  This just means CCS doesn't have source code available for the code the cpu is currently executing.  Once you get to main, you sources should show up in the window.  I typically prefer to "Restart" when debugging as this resets the processor and runs it until main is hit.

    I have seen the emulation errors you are getting when I run in real-time.  Sometimes I think CCS gets "out of sync" so to speak with the embedded processor, and things fall apart.  When this happens I typically power cycle the board as well as replug the emulator, this always fixes the problem for me.

    Trey

  • 0 in reply to Trey German289
    Prodigy 210 points

    Hi Tery,

    My docking station has a FT2232D with a silver dot marking on it . & the device creates two channels, channelA & channebB in the usb connection. may be bec' its a composite device.

    Let me tell you that at times its frustrating to get connected, window will report error in connecting the device & the device will not be detected even after several times of disconnecting & connecting. I am using it on my laptop & runs on windowsXP.

    Its not a very reliable plug & play device. I face no such problems with my other usb devices like printer or memory devices.

    I am not having problem debugging. But When you are debugging code run on Flash its necessary that one selects the "Launch Ti Debugger" from the drop down list in the Debug button & then select Debug Active project. This will remove all your previous old debug setting & start afresh. If u don't do this the debugger may report problems like unable to  erase or unable to read memory location..xxxx

    Regards

    Raghu

  • 0 in reply to KV
    Prodigy 210 points

    Hi tuktuk,

    if it reports " device is held in reset" why don't you try to check the voltage at the reset pin. Check if the pullup resistor to reset pin is connected properly & not left floating.

    Please try to use "launch TI debugger" every time u start a new debug operation. And then press "debug active projec"t.

    Regards

    Raghu

  • 0 in reply to Paramasivam Raghunathan
    TI__Mastermind 22025 points

    Raghu,

    Emulators with the FT2232D are XDS100v1.  All XDS100 designs enumerates as two channel devices and yes you are correct, it is a composite USB device.

    We test all of the emulators and controlcards before we ship them to customers to ensure a good user experience.  I'm suprised that you are having trouble as the emulator connection is normally very reliable for me.  Could you tell me the error you get when it doesn't work?  Does it fail when you launch the target configuration or when you actually connect to the device you are debugging?

    Trey

  • 0 in reply to Trey German289
    Expert 1800 points

    Trey and Raghu,

    Thanks for your valuable inputs.  I changed the configuration to XDS100v1 and the device is connected.  I could run the flashingLeds code successfully.  I only wonder how the exp kit has responded to XDS100V2 till level 4 of sensorless PMSM.  Nonetheless thanks for your guidance.  Trust I could proceed further with sensorless PMSM trials.

    rgds

  • 0 in reply to KV
    Expert 1800 points

    Trey and Raghu,

    As suggested I changed the configuration to XDS100v1 and could execute PMSM till level 3 without any hiccups.  However I am unable to execute level 4 as the processor hangs while reseting after the code is loaded.  I could not restart and proceed further.  The PID values were set to very low i.e., Kp = 0.005; Ki = 0.00005; Kd = 0/T

    Could you please review and suggest how to sort this issue.

    thx & rgds



  • 0 in reply to KV
    TI__Mastermind 22025 points

    Changing the example level shouldn't cause any change in how the code is loaded onto the device.  Could you further elaborate on the symptoms of the problem you are having?  You say the processor hangs after reset...after programming does it ever get to main?  Where does the processor hang (i.e. what is the PC?)?  With a little more information we can actually diagnose the problem.

    Regards,

    Trey

  • 0 in reply to KV
    Prodigy 210 points

    tuktuk,

    I think u can check your CCS GEL file for your emulator boot mode settings. You can get more information from the work shop material..

    http://processors.wiki.ti.com/index.php/C2000_Piccolo_Multi-Day_Workshop here.

    Do the following..

    press the debug button. Once the debug window opens, go to scripts from the menu & choose boot mode as EMU_BOOT_SARAM.

    You will have to do this every time your device has been power cycled.

    Regards

    Raghu.

  • 0 in reply to Paramasivam Raghunathan
    Expert 1800 points

    Trey and Raghu,

    Thanks for your suggestions.  Now I am able to progress by choosing boot mode as EMU_BOOT_SARAM.

    Rgds