How to use ftdi2232d jtag for tm4c1294

So, do programming .bin from LM flash to the target board via EK LM3S and sending debug messages from the target board to my pc use different routes? one is Jtag connection the other is usb cable?

HI Amit,

Is that the correct layout of what you said?

                                                                                                              FT2232

PC(LM Flash, terminal program...) ----- USB ------------ CH A (JTAG/SWD) ---------|      T      |

                                                                                        |                                                          |      M     |

                                                                                        |-------CH B(Virtual Com Port) ---|      4     |

                                                                                                                                                    |      C     |

I found that the previous guy connected LM3S to another target board by the mode of ICDI out to JTAG header.  If I want to use the above mode with TM4C, I need to physically wire up PA0 ~PA7(TCK,TDI,TDO...) with the target board. Is that right?

Hi Amit,

Here is a schematic,which is same as LM3S9B, for ft2232d on the new custom board based on TM4C.

According to the schematic, Ch A is for JTAG/SW and Ch B is for Virtual Com port.

I have tried to set up FTDI2232d on the new custom board using FT_Frog, but it has not worked so far.

How I configure using FT_Prog is:

I have tried on D2XX Direct and VCP but nothing works.

For the Port B, I select Virtual Com Port for Driver and 232 UART for the hardware.

As I program .bin into the custom board it still says "Unable to find a target"

I am not sure if you can help since this is more likely to be FTDI side.

Thanks,

Jin

Hi Amit

I chose Custom VID/PID  as a FTDI default and chose self-power since an external 5V power supply is connected.

I have changed it as you suggest but it is still same "unable to find a target".

Thanks,

Jin

Hi Amit,

Here is my FT prog .xml file, which is mostly same as LM3S9B96

Thanks,

Jin

<?xml version="1.0" encoding="utf-16"?>
<FT_EEPROM>
  <Chip_Details>
    <Type>FT2232D</Type>
  </Chip_Details>
  <USB_Device_Descriptor>
    <VID_PID>1</VID_PID>
    <idVendor>0403</idVendor>
    <idProduct>BCD9</idProduct>
    <bcdUSB>USB 2.0</bcdUSB>
  </USB_Device_Descriptor>
  <USB_Config_Descriptor>
    <bmAttributes>
      <RemoteWakeupEnabled>false</RemoteWakeupEnabled>
      <SelfPowered>true</SelfPowered>
      <BusPowered>false</BusPowered>
    </bmAttributes>
    <IOpullDown>false</IOpullDown>
    <MaxPower>500</MaxPower>
  </USB_Config_Descriptor>
  <USB_String_Descriptors>
    <Manufacturer>LMI</Manufacturer>
    <Product_Description>Stellaris Evaluation Board</Product_Description>
    <SerialNumber_Enabled>true</SerialNumber_Enabled>
    <SerialNumber />
    <SerialNumberPrefix>0A</SerialNumberPrefix>
    <SerialNumber_AutoGenerate>true</SerialNumber_AutoGenerate>
  </USB_String_Descriptors>
  <Hardware_Specific>
    <Port_A>
      <Hardware>
        <UART>false</UART>
        <_245FIFO>true</_245FIFO>
        <CPUFIFO>false</CPUFIFO>
        <OPTO>false</OPTO>
        <HighIO>true</HighIO>
      </Hardware>
      <Driver>
        <VCP>false</VCP>
        <D2XX>true</D2XX>
      </Driver>
    </Port_A>
    <Port_B>
      <Hardware>
        <UART>true</UART>
        <_245FIFO>false</_245FIFO>
        <CPUFIFO>false</CPUFIFO>
        <OPTO>false</OPTO>
        <HighIO>false</HighIO>
      </Hardware>
      <Driver>
        <VCP>true</VCP>
        <D2XX>false</D2XX>
      </Driver>
    </Port_B>
  </Hardware_Specific>
</FT_EEPROM>

Hi Amit,

The reason why I chose the "self-powered" is the custom board is powered by an external 5V supply. Anyhow I changed as you said and tried.

After programming config into eeprom, I did "cycle ports" in FT Prog(Program devices).

Then, unlock the device using LM flash

Here is what the device manager shows:

Then I was trying to program MAC address, but LM flash says "unable to initialize target -0".

Thanks,

Jin

Hi Amit,

I guess you were talking about LM Flash. As you see the below capture I tried to erase flash, but it says "unable to initialize target -0"

Thanks,

Jin

Hi Amit,

I checked pin 1(TDI),5(TMS),9(TCK) in JTAG/SWD header since the custom board has 2*10 jtag header.
I could see some signal go through, but not TDO and SRSTN.

The one thing I wonder is TDI stays high(3.37v) although any signals(actions) do not go out of the LM Flash. Still  TDI corresponds with JTAG signals come out of LM Flash but it just stays high all the time.

Thanks,
Jin

Hi Amit,

First thing I did was unlock the debug port under other utilities in LM Flash. It seemed to work ok as it showed captured message above like "power cycle board to complete~~"
Then testing erase Flash and Flash black check gave me a same error like "unable to initialize target -0"

Thanks,
Jin

Hi Amit,

After unlocking debug ports, I turned off the power on the custom board, then executed hardware reset through LM Flash.

Now I can program MAC address as well as .bin into the custom board.

I wonder turning off the custom board's power and hardware reset through the LM Flash once the unlock sequence is done are necessary processes?

Thanks,
Jin

Hi Amit,

The one thing that I have noticed from the custom board is that the below schematic from LM3S9B96 is designed as for "BUS POWERED", but the previous guy disconnected pin 1(5v) of J13(USB interface) with +5v since an external 5v power supply is connected.

I guess he thought the custom board is sourced by the external 5 v power ,so disconnecting 5V from pin1 of USB interface by modifying LM3S9B's ICDI schematic.

Every time I change the configuration of FT Prog to test something and go back to the config that worked well before, I still hit the "unable to initialize target -0" error although I did power cycled several times.

It ends up working after rebooting computer and power cycles a couple of times. I am suspicious about the hardware configurations(schematic) of the custom board.

The custom board uses the external 5V power but its schematic seems not to go along with "SELF POWERED". It is more likely "BUS POWERED" except disconnection of 5V from Pin1 of USB interface

Is that the reason working erratically?

Thanks,

Jin

Jin