RE: Unrecognised product of type com.ti.rtsc.xdais is required by project

Hi Matthew,

I have split this into a new thread for you to make it more efficient for support.

Could you please describe your issue in detail.  

Best Regards,

Lisa

Hi Matthew,

just thought to check for updates or further information here.

Best Regards,

Lisa

I'm having the same trouble, I think.
I'm new to piccolo, but have a fair amount of Arduino experience.
Windows 7.

Code Composer Studio , Version: 6.1.0.00104
C2000 Piccolo Launchpad LAUNCHXL-F28027, and F28069M (same problem with each, I believe)
When pushing Debug, I get:
... lots of successful lines... then
md/DSP2802x_Headers_nonBIOS.cmd" "../F28027_FLASH_FlashingLeds.CMD" -l"libc.a"
<Linking>
"../F28027_FLASH_FlashingLeds.CMD", line 51: error: BOOT_RSVD memory range
overlaps existing memory range BEGIN
"../F28027_FLASH_FlashingLeds.CMD", line 52: error: progRAM memory range
....
then lots of similar failure lines - memory range has already been specified
---

CCS\View\Preferences\Code Composer Studio\RTSC\Products shows successful installation of:
- SYS/BIOS
- XDCTools
- powerSUITE (two entries below that)
Can someone help me figure out this first use of Launchpad?
Thanks
Dave

Hi Dave,

David Elvig said:

md/DSP2802x_Headers_nonBIOS.cmd" "../F28027_FLASH_FlashingLeds.CMD"

It looks like two linker command files are being used in your project and they likely have conflicting information. Did you mean to have both cmd files in the project?

Thanks

ki

Thanks.  I deleted a .CMD from from the project (one that was higher in the project, and included the word "RAM") which appeared to have the memory ranges with which the Flashing Lights demo was conflicting.  Now it builds without error.

Now I try the next step in the F2802x Flashing LEDs Project

Step 3, Debugger Configuration...

I press this and get an 11-item list,

- starting with "Data Snapshot Viewer",
- ending with UART Connection,
- and having 8 "Texas Instruments.... Probe"
- and one "Texas... cJTAG with external converter"

I've tried 4 of them, including one ending in onboard debug probe.

None of them seem to "stick" as my choice (even when pick in Project Properties", and all lead to this error when pressing "Debug the imported project"

Can't Initialize Target CPU:
**Error**: Serial Communication failed at port: COM65, baud rate:9600!

 To use serial monitor, please ensure the following prerequisites are satisfied:
 1.    Make sure the cable is plugged into both the target and the host on the right COM port.
 2.    Make sure a compatible target side serial monitor is loaded and running on the target device.

Does that make sense?

Thanks

the 28027 LaunchPad has an integrated XDS100 debug connection. So this is the one you want. Choose "Texas Instruments XDS100v1 USB Debug Probe" as the connection type.

Thanks
ki

I restarted from scratch, the then used the "Texas Instruments XDS100v1 USB Debug Probe" for the connection type as you suggested.
I can now build and start the debugger without error.
Two things:
- I still needed to remove an extra CMD file from my project (that was added at the start from ControlSuite). It included the word ...RAM... and had similar low-memory (zero memory range) addresses that were being mapped.

I feel like I've missed an overview or two (or documentation) that would have guided me through these setup issues without creating a new forum entry.

I've fiddled with many of the moving parts (including the 3rd switch on the board... which is now back in the On position).

1) can you guide me to some good overviews for learning the basic setup for TI Piccolo boards, their project requirements and target hardware?
2) Now that I can get the debugger started... and I can trace through the code... I expected it to blink some lights on the board. Are you aware of a good tutorial that will allow me to see the board react to the code I'm debugging?

Also, if there's a better forum for this kind of question, please let me know.

I appreciate your help to date.

Thanks

David Elvig said:

- I still needed to remove an extra CMD file from my project (that was added at the start from ControlSuite). It included the word ...RAM... and had similar low-memory (zero memory range) addresses that were being mapped.

I imported the project myself and noticed that there are three cmd files listed in the Project Explorer: DSP2802x_Headers_nonBIOS.cmd, F28027_FLASH_FlashingLeds.CMD, and F28027_RAM_FlashingLeds.CMD. The last one is automatically excluded from the build. It is that one that has conflicting information with the first one. Since you it already excluded by default, you should be able to just build right after import and it should be successful (at least it was for me). Is that file not excluded from the build for you when you import it?

As for tutorials, I strongly suggest taking a peek at the CCSv6 beginner workshop for F2802x LaunchPad. It will help you get started with CCS on your LaunchPad:

For training that focuses on the actual hardware more than just CCS, see:

Thanks

ki