UniFlash 6.2.0 / Service Pack sp_3.18.0.2_2.7.0.0_2.2.0.7 - Weird Results...

Hi,

There are a few things to keep in mind when programming CC32xx devices. The bulk of the information that I will explain is covered in the Imagecreator's user's guide as well as the Uniflash Imagecreator SimpleLink Academy module:

https://www.ti.com/lit/swru469

https://dev.ti.com/tirex/explore/node?node=ABEoqU9o3snoxDcmIpW0EA__fc2e6sr__LATEST

Now, to answer your questions:

1. The "incorrect device" warning message generally shouldn't be ignored, since each CC32xx Imagecreator project is specific to a CC32xx model. So your CC3220S project is incompatible with the CC3220SF. When you program a CC3220S image onto a CC3220SF, the bootloader will not be able to function correctly, resulting in impaired device operation. To fix this, create two projects, one specific to the CC3220S and one specific to the CC3220SF.

2. Once both projects are programmed onto their respective devices, you should be able to connect to the device using the JTAG debug functionality built-into CCS, assuming that JTAG is unlocked by the 'development' mode setting in Imagecreator.

3. You cannot check the SP version directly through Uniflash. There is the sl_DeviceGet() API that you can use in your code to check the NWP servicepack version, like so:

SlDeviceVersion_t ver;
        pConfigLen = sizeof(ver);
        pConfigOpt = SL_DEVICE_GENERAL_VERSION;
        sl_DeviceGet(SL_DEVICE_GENERAL,&pConfigOpt,&pConfigLen,(_u8 *)(&ver));
        printf("CHIP %d\nMAC 31.%d.%d.%d.%d\nPHY %d.%d.%d.%d\nNWP %d.%d.%d.%d\nROM %d\nHOST %d.%d.%d.%d\n",
                         ver.ChipId,
                         ver.FwVersion[0],ver.FwVersion[1],
                         ver.FwVersion[2],ver.FwVersion[3],
                         ver.PhyVersion[0],ver.PhyVersion[1],
                         ver.PhyVersion[2],ver.PhyVersion[3],
                         ver.NwpVersion[0],ver.NwpVersion[1],ver.NwpVersion[2],ver.NwpVersion[3],
                         ver.RomVersion,
                         SL_MAJOR_VERSION_NUM,SL_MINOR_VERSION_NUM,SL_VERSION_NUM,SL_SUB_VERSION_NUM);

This code is run and the resulting version string displayed in some of the SDK examples, such as the network_terminal example, so you can run that through JTAG to check the NWP SP version if needed.

Looking more carefully at the XDS error code you're seeing, -261 might also be related to the bootloader jumper settings. In order for the JTAG to be muxed out, you need SOP pins 2:0 to be either 000 or 010. While it sounds like you've resolved your issue, in the future I would also ensure that your jumpers are set correctly. Some more debug tips on troubleshooting XDS errors can be found here:

http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html

Let me know if you need more clarification on any of the info provided, or if you have any further questions on this topic.

Regards,

Michael

Thanks, Michael, for your considered response.

Yes, the SOP pins have been set to 010 in both cases, and have been building sample projects only, directly from SDK, for testing - each one appropriate to its respective part.

Haven't (yet!?) dug through the UniFlash Imagecreator Guide completely... This, and your notes, give me plenty to work on!

As I'm no longer seeing this issue, I must assume that I'd inadvertantly switched the boards at some point. Another late-night Operator Error, no doubt.

Thanks again.

Indeed; it was roughly this, your missive above, which had me alarmed: The "incorrect device" warning message generally shouldn't be ignored...

Had never seen this XDS Error before; hence the nervousness. In any case, these boards are not bricked - all working OK now, JTAG debug-able, etc.

Your notes give me a few other avenues to look at, as well. Thanks for your help.