CCS/LAUNCHXL-CC1352R1: UniFlash v5.0 not detect the LAUNCHXL-CC1352R1 Rev.B

Hello Henry,

If you have access to a PC with CCS installed, can you check what the serial number for the launchpad is? See steps 1&2 of:

http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#updating-the-xds110-firmware

Thanks

ki

Thanks for a fast answer.

C:\Users\hkw>cd C:\ti\ccs901\ccs\ccs_base\common\uscif\xds110

C:\ti\ccs901\ccs\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 2.3.0.14
Manufacturer: Texas Instruments
Serial Num: L41006BU
Mode: Runtime
Configuration: Standard

Found 1 device.

Henry

Heniek said:

Serial Num: L41006BU

You serial number looks good (a bad serial number can impact autodetect).

Hmm.. not sure why autodetect is not working for you then.

Can you provide a screenshot of what you see when UniFlash tries to detect the launchpad. For example, I see:

Thanks

ki

Hi,

I try on UnifFlesh v.4.5.0.2056 and v.4.6.0.2176.

And typically the result is like this: x1.pdf

Only the UnifFlesh v.4.5.0.2056 work always well.

This feature is independent to the version of Emu pkg (8.2.0.00004, 8.1.007, 8.0.27.9). I have 8 CC1352R1 LP. The version 5.0 and 4.6 not work on all.

But on the TI Cloud Tools page detection is well

Henry

Henry,

It looks like UniFlash (4.6 and 5.0) is getting stuck on the detection stage for some reason. 

Do you have any other LaunchPads except for the CC1352R1 LaunchPad to see if it is able to detect other devices?

Can you also try to change it from "Auto" mode to "Manual" mode and then click on "Detect" to see if it works if you manually start up the detection?

Lastly, can you see if detection works in the online version of UniFlash (https://dev.ti.com/uniflash/)?

Thanks,

Ricky

Hi Ricky,

I have CC1350 LP and CC1310 LP.

I try the UniFlash (4.6 and 5.0) on this LP's, with the Manual option and with Cloud version, too.

Only the UnifFlesh v.4.5.0.2056 work always well.

Thanks,

Henry

Hi Ricky,

On the XDS110 Product page I found the information on JTAG Clock speed considerations.

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

I changed the USB cable length to 0.5 m, and UniFlash 5.0 (and 4.6) start to work.

With the USB cable length 1 m it work sometimes.

It may be depend of USB port quality.

But CCS 9.01 and UniFlash 4.5 work well with 1.5 m USB cable too.

And the xdsdfu app work well on all cable length.

Best Regards,

Henry

Henry,

Thanks for the updated observation; it's definitely interesting. I'm going to see if I can find longer USB cables to test this.

When you use the 1.5m cable, is it only detection that is not working for you in UniFlash 4.6 or newer, or does flash programming not work as well?

Thanks,
Ricky

Hi Ricky,

Eureka!

I installed the SmartRF Flash Programmer-2 v.1.8.1.

It work very well with all USB cables.

But, now the UniFlash v.4.5.0.2056 start to work.

With all length of USB cable.

But only if it start in Manual mode.

I may change the mode to Auto and it can detect the new connected LP.

But if it start in the Auto mode not detect nothing.

Best Regards,

Henry

Hi Ricky,

I uninstalled all TI software (Windows 7).

And instaled UniFlash v. 5.0.0.2289 only.

If UniFlash start in Manual mode, it work well, detect all modules.

But if it start in the Auto mode, detect nothing.

Next I installed CCS v9.1.0 and TI Cloud Agent v2.

Autodetect work well on the TI Cloud Tools page and in CCS.

But without a change in UniFlash operation.

By the way.

There is a problem with Emulation Package (XDS110 FW) version.

If I debug project in the CCSv9.1.0, the Emulation package 8.2.0.00004 is programed. I found it is the latest version.

But UniFlash v. 5.0.0.2289 request the Emulation package update, and reprogram to the oldest version 8.1.0.00007.

UniFlash is required to clear all onboard Flash memory (e.g. BIM).

And on another use of the CCS, the Emulation package 8.2.0.00004 is programed once again.

CCS automatically detect the Emulation package update. But UniFlash not.

Two closely related applications and no consistent solution.

It is very frustrating.

Best Regards,

Henry