Multiple target debugging in CCS5.1 - Concerto and Piccolo

Hi Ki,

Thanks for so rapid answer. I run your file configuration with my serial numbers: SD28DOCK for concerto and TIVHUIIA for Piccolo.

VID/PID    Type            Serial #    Description
0403/a6d0  XDS100v1/v2     TIVHUIIA    Texas Instruments XDS100+RS232 V1.0
0403/a6d0  XDS100v1/v2                 Texas Instruments Inc.XDS100 Ver 2.0
0403/a6d0  XDS100v1/v2     SD28DOCK    Texas Instruments XDS100+RS232 V1.0

Piccolo is connecting, but concerto - not. I get error connection always:
 IcePick_C_0: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.569.0)

It seems that it is serial number problem , because the Concerto connect properly with EmulationSelection=OnlyOneZDS100Installed.

Thanks, Sabina

Is the serial number the only difference between the two (TCLK frequency is the same)?

Sounds like you plugged the Concerto into a dock and using the onboard emulation on the dock. is that correct?

Is the serial number the only difference between the two (TCLK frequency is the same)?
[sg]Yes, the difference is in the serial number. The frequesncy is the same - default 1.0Mhz frequency.

Sounds like you plugged the Concerto into a dock and using the onboard emulation on the dock. is that correct?
[sg]Yes, I plugged the Concerto into a dock and using the onboard emulation on the dock. Piccolo also plugged into a dock (the same as Concerto)

Sabina Greenberg101872 said:

[sg]Yes, I plugged the Concerto into a dock and using the onboard emulation on the dock. Piccolo also plugged into a dock (the same as Concerto)

I think the onboard emulation on the dock is an XDS100v1 (SD28DOCK), which doesn't support the M3 of the concerto. Do you also have the mini-USB cable plugged in on the concerto card itself when you got it to work with just the Concerto debug session only?

 I have the mini-USB cable plugged in on the concerto card itself. this cable is connected to PC during debug session.

We perform Concerto debugging on the dock(SD28DOCK) XDS100v1 , but without serial number using.  So it is not so clear why do you think  that the onboard emulation on the dock XDS100v1 (SD28DOCK) doesn't support the M3 of the concerto. 

Sabina Greenberg101872 said:

 I have the mini-USB cable plugged in on the concerto card itself. this cable is connected to PC during debug session.

The mini-USB port on the card allows you to use the onboard XDS100v2 on the card. 

XDS100v1 does NOT support any ARM device:

http://processors.wiki.ti.com/index.php/Xds100#XDS100v1_Features

You need an XDS100v2 (or greater). 

When you ran xds100serial, it detected THREE xds100 emulators.

Sabina Greenberg101872 said:

VID/PID    Type            Serial #    Description
0403/a6d0  XDS100v1/v2     TIVHUIIA    Texas Instruments XDS100+RS232 V1.0
0403/a6d0  XDS100v1/v2                 Texas Instruments Inc.XDS100 Ver 2.0
0403/a6d0  XDS100v1/v2     SD28DOCK    Texas Instruments XDS100+RS232 V1.0

The first is the piccolo. The second is the XDS100v2 on the card itself (plugged in via mini-USB cable). The third is the XDS100v1 on the dock.

You need to use the second one with your concerto. The issue is that the XDS100v2 on the concerto does not have a serial number. Sometimes they ship without a serial number. You can program it:

http://processors.wiki.ti.com/index.php/Xds100#Q:_Can_I_change_the_serial_number_on_my_XDS100v2.3F

When you used CCS with the concerto only, it worked since you didn't have to specify a serial number. With the multi-target setup, you have to pass in serial numbers and you passed in the serial number for the dock which will not work since it looks to be a v1.

Thanks

ki

Hi Ki,

Does TI provide FTDI MProg utility for changing Serial number? Could you send me link to it.

Thanks,Sabina

You can obtain the utility from the main FTDI page:

http://www.ftdichip.com/Support/Utilities.htm

Search for 'Mprog'

Thanks

ki

Hi Ki,

Thanks for the link.

Device->Scan give me : 

Number Of Blank Devices = 0
Number Of Programmed Devices = 1

But during Device->Program I get: "No device found' error".  

May be this device could not be reprogrammed?

Thanks,Sabina 

Try using FT_Prog. Looks like MProg is being deprecated in favor of FT_Prog. The interface is different but the interface is pretty east to use. Do a scan and you can find the devices and serial numbers.

Forgot to mention that FT_Prog is available on the same site as MProg

Thanks, I've programmed serial number for Concerto board and managed to connect both: Concerto and Piccolo. Now the problem is in the downloading program. downloading Concerto (M3 and C28) program and running work properly. But I can not download Piccolo program.

C28xx_0: Flash Programmer: Missing Flash Programming Settings.
C28xx_0: Flash Programmer: Error erasing Flash memory.
C28xx_0: Flash Programmer: Missing Flash operation option. Operation cancelled.
C28xx_0: Trouble Writing Memory Block at 0x3e1230 on Page 0 of Length 0x5b5
C28xx_0: GEL: File: C:\ViewStore\sabina.greenberg_Decathlon_V1_00\Decathlon\Decathlon_Emb\PMCU_Emb\Debug\PiccoloApp.out: Load failed.

The same program with the same gel file (another configuration file without serial number using) load to the target successfully.

Our serial number are:
VID/PID Type Serial # Description
0403/a6d0 XDS100v1/v2 TIVHUIIA Texas Instruments XDS100+RS232 V1.0
0403/a6d0 XDS100v1/v2 SDVPXMZY Texas Instruments XDS100+RS232 V1.0
0403/a6d0 XDS100v1/v2 FTVPXODL Texas Instruments Inc.XDS100 Ver 2.0

Piccolo work with TIVHUIIA serial number, and concerto - with FTVPXODL.

What could be the problem here?

Thanks,Sabina

Hi Sabina,

I think what is going on is that normally the flash programmer can figures what device it is programming by querying the target. Then it picks the correct algo for the target and tries to flash it. In this multi-target configuration I bet the flash programmer is getting confused, it is finding multiple targets. Let me see if there is a workaround for the issue.

ki

Hi Ki,

Did you find the workaround for the issue?

Thanks,Sabina