New person looking for simple answers

Scott,

Here is a shot at your questions:


1. When I create a ELF in CCS, how does it get loaded? If appears I can just plug in one of those launchboards into my Windows PC, and CCS will download the code. Correct?

The LaunchPad has a JTAG debug probe built onto it. CCS will use that debug probe to program the chip on the LaunchPad.

2. LAUNCHXL-F28027 appears to be a "XDS100 class" device. So why would I purchase an XDSV100V2? If I can plug in the XDS100, what does it do instead of the F28027 (related to Q6)?

The F28027 LaunchPad is a development board. It has a built-in XDS100 class debug probe so that you don't have to purchase a separate one to use it. You would purchase a standalone debug probe like the XDS100v2 when you have your own board created that you need to program.

3. The XDS is purported to be an "emulator", which in my past has essentially meant a "simulator". In the docs and training, however, it appears that these are different. What is the difference? If the XDS100 can emulate being another chip, why would I use a launchboard? Just for the "hardware" interface?

We are really trying to stop using the term emulator anymore for that very reason. In TI it refers to a debug probe but many people think of it as a simulator, i.e. emulating the device. When you see emulation or emulator in TI material just think of a debug probe used to connect your development environment to a device.

4. I also purchased a BeagleBone Black, because I am also interested in the AM33xx chips. Is this a XDS100 class device? Can I use it past the CCS trail, and/or use the BBB with the XDS100V2 emulator.

The BeagleBone Black does not have a built-in debug probe. Thus if you wanted to load code onto it via CCS you would need to use an external debug probe. The reason for this is that the primary users are Linux developers who would not be loading their code via a debug probe. That said it is possible to attach a JTAG header to the board and use an external debug probe.

5. It would appear that CCS has a simulator to virtually run code. Does that mean it can run, step, debug internally? No device attached? Microchip MPLAB can do that, however obviously it's not real time, nor supporting hardware interfaces, etc.

CCS does not include any simulators. We did years ago but not anymore. Instead we focus on providing low cost development boards.

6. CCS has a trial period, and four license options. You can continue to use CCS if you also use an "XDS100"... sometimes it seems to indicate an "XDS100 Class Device", such as the launch board, sometimes it seems to indicate specifically the XDS100 device itself only. Which is it?

Our licensing is currently a bit confusing. That is going to get significantly cleaned up by the end of the year. If you are using an XDS100 class debug probe then CCS is free. CCS will know what type of debug probe you are using (whether standalone or built onto a LaunchPad) and if that is an XDS100 they the free license will work.

7. The output of any compiler is executable code, obviously. So, CCS will create an *.out file (probably a.out if it's based on GCC). Will CCS continue to compile even after the trial period, just not support downloading? If so, doesn't it defeat the purpose?

If you are using the time limited license then CCS will not function at the end of the period. However in your case you would be using the free limited licence that is tied to XDS100. This one does not expire. Also this is all going to be a lot more simple by the end of the year.

8. This is a little more vague then the other questions... Eventually, I would assume I will be able to use a device on a board of our design. Where is material to demonstrate how to program the device on its own, rather than when installed in a launchboard? I know in the scheme of my self-training, this is further down the road. but just thought I'd slip this in :-)

Once you have your own board you would use a debug probe and CCS to program it. Assuming you are still in development. Once you are going to production then there are a number of different options out there for production line programming that you could use with F28x devices


Hope this helps.

Regards,
John

Awesome information... So the XDS is a "debug probe" to observe my own device, like a oscilloscope probe lets you observe a circuit. Much better term.
So an F28027 board will let me develop for C2000, and I can use the XDS to connect to the BeagleBone for the Sitara line.

This clears up pretty much everything. Thanks for your quick reply.

-Scott