EKK-LM3S1968 and OpenOCD

This question is answered

Posted by upcom

on Nov 07 2007 04:05 AM

I know that EKK-LM3S811 can be used with OpenOCD. Now, I want to buy EKK-LM3S1968 which is different from EKK-LM3S811 in USB interace.

Can I use EKK-LM3S1968 with OpenOCD?

All Replies

Posted by TI - Eric Hewing

on Nov 07 2007 09:10 AM

Verified Answer

Verified by Michael Cole

Expert4160 points

Yes, all of our evaluation boards can be used with OpenOCD.

Posted by rgl

on Nov 29 2007 09:56 AM

Prodigy165 points

Good to know. But how does it work?
I managed to get the LM3S1968 into 'halt' mode with OCD. After this i get 'unknown did0 version' followed by other errors which basically seem to say: 'Can't identify chip'

Has anybody used OpenOCD with a Stellaris chip different from LM3S811 and can provide some information on this?

Best regards

Posted by jonloveslou

on Nov 30 2007 09:25 AM

Prodigy40 points

Looking at the OpenOCD source, it doesn't look like the LM3S1968 has its part number included (same with LM3S8962).

I've managed to upload code onto a LM3S2110 with a Wiggler using OpenOCD but currently have no luck with the mainboard LM3S8962, despite having added in the board info and re-compiled OpenOCD myself.

Posted by magnuslundinse

on Dec 01 2007 17:51 PM

Intellectual470 points

OpenOCD developers and LMI has friendly but not very frequent contacts :).
We get good answers, some board support but very little advance or update information. My take is that LMI does appreciate OpenOCD but it is low priority. The evaluation boards does work very well with OpenOCD but the configuration info has a tendency to be slightly out of date.
This is of course related to the fact that the demand for this is not very big at the moment.

Regards
Magnus L (OpenOCD developer)

Posted by magnuslundinse

on Dec 03 2007 11:27 AM

Intellectual470 points

Hi

I just checked with the evlm3s6965 evaluation board and OpenOCD can identifythe processor without problems.

If the partnumber is not in the OpenOCD code then the flash info command will give "Unknown part" as the part name, but the chip configuration should be correctly identified anyway.

The "unknown did0 version" message is more serious and it can be that the version of OpenOCD is older than rev 172 or there is a configuration or communication problem.

If you run openocd at debuglevel 3 (with the -d 3 flag) then after the flash info 0 command there will be debug message that shows the information read from the configuration registers. This is what I get:

Debug: target.c:764 target_read_u32(): address: 0x400fe000, value: 0x10010002
Debug: target.c:764 target_read_u32(): address: 0x400fe004, value: 0x1073402d
Debug: target.c:764 target_read_u32(): address: 0x400fe008, value: 0x00ff007f
Debug: target.c:764 target_read_u32(): address: 0x400fe010, value: 0x001133ff
Debug: stellaris.c:348 stellaris_read_part_info(): did0 0x10010002, did1 0x1073402d, dc0 0xff007f, dc1 0x1133ff

/Magnus