This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LM3S6965: LM3S6965 ethernet eval board / LMFLASH. *ERROR* unable to find target

Part Number: LM3S6965
Other Parts Discussed in Thread: SEGGER

I need to program a couple of dozen LM3S6965 boards, and it appears that the eval board we've used as the hardware interface in the past has failed. LMflash just returns the message  "**ERROR** unable to find target". I'm not sure exactly what that means. The "Target" that it can't find could be either the LM3S6965 on the eval board, or the LM3S6965 on my product. In any case, the message is the same if the eval board (used as interface) is attached (USB) to the host computer or not.

I do get a power light on the eval board, and the USB interface is working. At least to the extent that it recognizes a virtual com port, and "Stellaris Evaluation Board A" and "Stellaris Evaluation Board B" usb controllers. No other devices though. Are these older boards supposed to identify as anything else?

Is there anything else I can do?  Is there anyway to reset the eval board?  I've got no documentation, and when I look, I see slightly confusing information about more recent products.

  • Part Number: LM3S6965

    I've got to program some stallaris LM3S6965 parts this week. It's an obsolete part (even the named forum has been closed), and I don't know what tools/hardware are suitable. Specifically I need to write the MAC into this ethernet-interface part. In the past, we've used LMflash and the LM3S6965 ethernet eval board, but that seems to have stopped working (and seems to be irreplacable) What's out there that works?

  • You state that "couple of dozen" 3S6965 boards need to be programed - and thus far that fails. Have you attempted this across "more than one such 3S6965 board?"

    Have any "changes or alterations" been made to your, past, "Program capable, Eval board?" Has it been safely (ESD safely) stored & safeguarded?

    I'd check for any/all "past" documentation which may have "fully/properly" described "all of the details" which enabled your (past) success. Should you happen to have a past "3S811 eval board" (included the small oled) we have used that to program "3S6965" w/success.

    Vendor's newer "ICDI" devices (may) not accommodate the (retired) LM3S series - you may inquire in that regard. If such proves true - you may "graduate to Segger's "J-Link" (available at educational discount) and which my firm has LONG employed to program (both) LM3S and TM4C123 devices...
  • The LM Flash Programmer does support programming the LM3S6965 ethernet evaluation board. Here is a link to the LM3S6965 Evaluation Board User's Guide. When you put the cable on the 20 pin connector and connect to your target system, is the red "Debug Out" LED (upper right corner) on?

  • The red "Debug Out" LED does NOT come on. I'm still not sure if that indicates a USB failure or a SWD failure.

  • I've tested with new boards and known working boards. The eval board is safely packaged, but the package has been left connected to the PC for several years. We have a documented process. We don't have a 3S811 eval board, yes, I would like to know if the vendors newer ICDI devices accommodate the (retired) LM3S series, and thank you for the recommendation of the JLINK. Can you confirm that it understands MAC programming on the 3S6965 ethernet part? The way that is implemented is, I think, unique to that part?
  • Is pin 18 on the connector pulled to ground?

  • Thankyou to everyone who responded. Identified as a USB fault, and board is working now.

    I was able to reset the FTDI USB chip (which turned it into a standard 6010/6011 usb device). I don't understand USB well enough to understand why a FT2232 dual channel USB chip was used instead of a single channel chip (USB 6001) , nor how exactly a USB composite device works, but I got lucky, and when I reprogrammed the original PID, serial number /and informational text strings/ LMFlash recognized it again.

    **ERROR**. Unable to find a target!

    Means that LMFlash couldn't see a USB device with the expected text strings.

    **ERROR** Unable to initialize target -0!

    Means that LMFlash found the USB device, and the debug port is loaded with a second external device, which didn't initialize correctly.

    MAC Address: FF-FF-FF-FF-FF-FF

    Means that LMFlash read the MAC from the second external device.

    MAC Address: 00-1A-B6-nn-nn-nn

    Means that no secondary external device is loading the debug port, so LMFlash is reporting the MAC from the eval board....

    Not the way our software is written: we don't return indistinguishable signals for qualitatively different outcomes, and we don't depend on English language text strings to identify our devices, but hey, I guess it works for TI.