Hi,
I have been working with the concerto F28M35H52C1 on a custom board for a while. I had always used the XDS100v2. Unfortunately, I don't have the XDS100v2 programmer anymore. I have been trying, unsuccessfully, to use the XDS110 programmer included in the launchpad F280049C.
Can someone please tell me if It is possible to program the F28M35H52C1 using the XDS110 programmer included in the Launchpad F280049C?
This is the current configuration that I had tried.
1) Connection: I made an adapter to connect the 10Pin-Jtag of the Launchpad F280049C to the 14Pin-Jtag used in my custom F28M35H52C1 board.
|
JTAG(10) Pin # |
JTAG(14) Pin # |
function |
|
1 |
5 |
3v3 |
|
3,5,9 |
4,8,10,12 |
GND |
|
2 |
1 |
TMS |
|
4 |
9,11 |
TCK |
|
6 |
7 |
TODO |
|
8 |
3 |
TDI |
|
10 |
2 |
RESET (2k2Ω pull-up) |
|
7 |
6 |
NC |
|
-- |
13 |
EMU0 (5kΩ pull-up) |
|
-- |
14 |
EMU1 (5kΩ pull-up) |
2) CCS: I had tried using CCS Version: 9.1.0.00010, and CCS version 10.1.1.00004.
3) Target configuration: I had tried several configurations and clk frequencies, but this is the current one.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
<instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
<connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
<instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
<instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
<instance XML_version="1.2" href="drivers/tixds510cortexM.xml" id="drivers" xml="tixds510cortexM.xml" xmlpath="drivers"/>
<instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
<instance XML_version="1.2" href="drivers/tixds510c28x.xml" id="drivers" xml="tixds510c28x.xml" xmlpath="drivers"/>
<property Type="choicelist" Value="1" id="The JTAG TCLK Frequency (MHz)">
<choice Name="Fixed with user specified value" value="SPECIFIC">
<property Type="stringfield" Value="1.0MHz" id="-- Enter a value from 100.0kHz to 2.5MHz"/>
</choice>
</property>
<property Type="choicelist" Value="0" id="SWD Mode Settings"/>
<platform XML_version="1.2" id="platform_0">
<instance XML_version="1.2" desc="F28M35H52C1_0" href="devices/f28m35h52c1.xml" id="F28M35H52C1_0" xml="f28m35h52c1.xml" xmlpath="devices"/>
<device HW_revision="1" XML_version="1.2" description="" id="F28M35H52C1_0" partnum="F28M35H52C1" simulation="no">
<router HW_revision="1.0" XML_version="1.2" description="ICEPick_C router" id="IcePick_C_0" isa="ICEPICK_C">
<subpath id="C28x">
<property Type="numericfield" Value="0x11" desc="Port Number_0" id="Port Number"/>
</subpath>
</router>
</device>
</platform>
</connection>
</configuration>
</configurations>
4) connection test result:
[Start: Texas Instruments XDS110 USB Debug Probe_0]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\ELETRON\AppData\Local\TEXASI~1\
CCS\ccs1011\0\0\BrdDat\testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Nov 8 2020'.
The library build time was '17:25:15'.
The library package version is '9.2.1.00042'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.
-----[Print the reset-command hardware log-file]-----------------------------
The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.
The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.
[End: Texas Instruments XDS110 USB Debug Probe_0]
5) CLK signal:
Best regards,
Jorge Caicedo
