Request: Centralized collection OpenOCD ARM scripts

Hi,

First, I think OpenOCD is great! I’m so happy that it exists, thanks to everyone for their contributions. I think for those of use who are trying to get started with OpenOCD, it is confusing coming up with the right “script” for our respective ARM processor.

Since others have gone through this trouble for almost all (if not all) variants supported by OpenOCD, can we collect an example script per processor (or processor family if it works across the variants) and put them up at the OpenFacts page?

It would be nice if we documented any caveats or interesting issues per config file / family. There are some examples around, but, for example, it took me some Googling to find one for the LPC2103 that I’m using. I’m still not sure if the LPC 2xxx families are all the same, and what options differ for the flash programming, etc.

Instead of relying on users’ pages for information on how to get this going, we should try to fold this information back into OpenOCD itself.

I would be happy to contribute my part – I can help write English documentation and/or correct grammar and spelling issues. Can we get something going here?

This would be a great addition to the OpenCircuits Wiki. Maybe a section on OpenOCD scripts?

Instead of moving to yet another Wiki, it should be possible to add this information to the existing OpenOCD Wiki at http://openfacts.berlios.de/index-en.ph … p_Debugger

If there’s a problem with plain ascii files in the Wiki I can easily put them on the OpenOCD homepage at http://openocd.berlios.de/web/

If you want, feel free to add a new page to the Wiki and put the .cfg file you’re using up.

Regards,

Dominic

this is a great idea. This is the main problem from newbie like me to get thoses script working.

I will put mine for sure on this webpage

dumarjo

Hello,

I have make the first step and create a new wiki page with

examples for the STR710 and LPC2294 cpu which was

working here.

http://openfacts.berlios.de/index-en.ph … CD_scripts

I hope this examples will work for you too :smiley:

Dominic, please can you take a look at it?

It was the example from the OpenOCD windows installer.

Best regards,

Michael

I think it is time to add the following lines in each .cfg we give as example:

#nTRST and nSRST delay [milliseconds]

jtag_nsrst_delay 250

jtag_ntrst_delay 50

Many new boards are coming with on-board reset supervisors.

Adding this two lines will remove many issues and support !!!

… and if you do not have supervisor, you only lose some ms starting OpenOCD server!

We already add these lines in the examples coming with the sdk4arm !

Regards,

Laurent

Hello Laurent,

I have think about these options too.

But what are the correct delay values?

What does the other think, should we add it to the examples?

Regards,

Michael

I put mine too.

Cumarjo

Hello Cumarjo,

Could you please explain us why CFI in your .cfg ?

Regads,

Laurent Gauch

http://www.amontec.com

Hello Laurent,

oops, I have the cfi in the LPC2294 example too. Why?

Because the cfi was in the example from Dominic too.

Regards,

Michael

Heh, guess Laurent’s point is that while it makes sense for the LPC2294 with its external bus to have an external flash configured, there’s little or no use for an external flash on the LPC2129 which doesn’t have an external bus.

Regards,

Dominic.

Yes Dominic, this is what I mean !

OK, the Cumarjo one is not wrong, but adding CFI configuration for LPC2129 is not possible since the LPC2129 does not provide any external bus ! This will just generate troubles to the other users!

It is important to provide correct .cfg examples !

Laurent

http://www.amontec.com

Hi all,

I have only take the generic lpc from the yagarto and modify it to use it on flash based. But i’m not an expert at thoses thing. If this should not be there, i will remove it.

Dumarjo