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.

Project Zero debug fails CCS Cloud, Linux host, LaunchPadXL-CC2650 target

Other Parts Discussed in Thread: CC2650

Click the "Debug" icon.  It seems to proceed reasonably and then I get a dialog "... GEL_Go(main)" and it hangs.

Which I understand means the debugger is running until it reaches main().  There is a main() in the code (duh.)

I tried the BigTime example and debugger works fine (stops at main, executes to completion when your resume.)

I am reasonably sure I burned both the app and the BT stack, and that the code is as shipped from TI.  But I will try again, fresh.

I described my environ in my spurious post yesterday.

I blog about my experience here.

  • I just replicated it cleanly: delete project, reboot host, start browser, start CCS Cloud, import Project Zero (app and stack), "Run" ...ZeroStack... project (which I assume burns it), "Debug" ....ZeroApp....", it seems to go normally but gives the same result.
  • I don't have another modern BTLE device to scan the supposedly working Zero. I am using the debugger to test whether the app really downloaded and runs.
  • Hello Lloyd,

    My apologies for missing your post and for the delayed response.

    lloyd konneker said:
    I just replicated it cleanly: delete project, reboot host, start browser, start CCS Cloud, import Project Zero (app and stack), "Run" ...ZeroStack... project (which I assume burns it), "Debug" ....ZeroApp....", it seems to go normally but gives the same result.

    Is this still an issue? I followed your steps exactly with my CC2650 LaunchPad and I was able to reach main:

    There has been updates (fixes) to both the Resource Explorer content and Cloud so I'm wondering if you were running into some known issues that have since been resolved. If you have not tried in awhile, Can you try again?


    Thanks

    ki

  • Yes, I will as soon as I can.  I agree, it probably has been fixed but i have not tried it in weeks.   I am sympathetic that CCS Cloud is under development and suffers continual improvement.  But I also tried CCS Desktop and suffered comparable difficulties (probably my own ignorance, but disheartening that I failed on both.)

    (Not pertinent:   But my project is really a datagram protocol, which I had intended to implement on top of BT Broadcast/Scan.  I decided to take the path of least resistance and switched to Nordic (where I also experienced comparable difficulties: arduous build system installation, a long learning curve, and some bugs in their SDK.)  If I go back to TI radio products (I use many other TI chips and appreciate your engineering) I will probably use an architecture not using BTLE but using low level access to the radio, which apparently is not the case for the CC26xx family, since the access to the radio is in the M0 via the HCL layer.   My projects are open source on Github, I am not  commercial yet.)

  • Yes, it works fine now.  (Note since my initial report, my dev environment has changed to Ubuntu 16.04.1)

  • Thank you for the update!