Lpc2000

Hello Bruce,

On Friday 24 March 2006 01:32, Bruce Paterson wrote:
> Hi Jim,
>
> Just attempted to get OpenOCD going using the new bits of your tutorial
> so thought you might like some feedback.
> Any experts on Chameleon with OpenOCD also appreciated (it's not
> working....) !
>
> 1/ You make no mention of the need to also install the DX22 FTDI
> drivers. According to the OpenOCD wiki you can use --disable-"whatever"
> with openocd but it isn't clear if this is for configure, making or
> running (my guess is configure ?). Anyway I couldn't seem to get around
> needing the DLL to use openocd.exe version as specified. Since I didn't
> actully have an FTDI to plug into a USB port to kick off the recommeded
> Windows Add-New-Hardware procedure, I simply copied the dll file from
> the downloaded driver zip to c:\windows. That got rid of that error !
>
I supposed you've downloaded the preview-cygwin-ftd2xx-20060213 release. This 
one has been prebuilt for use with the FT2232. If you don't have such a 
device, you should have used preview-cygwin-20060213.
Please note that these versions are rather outdated, and many things have been 
fixed since mid-february.
It's probably best to get the current sources from svn:
svn checkout http://svn.berlios.de/svnroot/repos/openocd/
or use the graphical svn client of your choice.
In current versions, the ./configure options have been changed to opt-in, i.e. 
you have to --enable-XXX the interfaces you want.
Build instructions and usage notes are available at the OpenFacts Wiki:
http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger
Let me know if you're missing something, or if something is unclear.

> 2/ I got errors about not being able to find cygwin1.dll, even though
> c:/cygwin/bin is in my path. I've got around this by running from a
> cygwin bash shell rather than a DOS prompt. Not sure how I tell Windows
> the DLL search paths. Have I missed a step somewhere ?
>
Haven't experienced this problem yet, but then I rarely test on Windows. Maybe 
someone else is more knowledgeable as far as Cygwin is concerned.

> 2/ I added the ioperm -i to run everytime I start debugging. Harmless
> if already installed. Just one less thing to go wrong/forget. I note
> that WinARM uses giveio instead to allow user level access, but that was
> an older openocd version.
>
I'm considering adding GiveIO to the OpenOCD, together with changes that allow 
OpenOCD to be built for native-windows, i.e. without Cygwin. I'm still 
undecided whether that's worth the trouble of additional code and build 
management complexity.

> 3/ I wrote my chameleon.cfg file for openocd using Dominic's wiki.
> Unfortunately, the openocd version compiled for cygwin doesn't seem to
> have some of the options given in the wiki. 'daemon startup' isn't
> supported, nor the arm7tdmi reset option "run_and_halt". I'll attach the
> file below for reference.
>
The "chameleon.cfg" included in doc/configs/ is for configuring the chameleon 
(OpenOCD can be used to program the .amtsvf files), not for use of the 
chameleon with an ARM target.
Use one of the config files matching your target (like arm7_wig.cfg), and 
modify the JTAG configuration to match your interface. For use with an 
Chameleon in its JTAGAccelerator configuration, use the following lines:
interface amt_jtagaccel
parport_port 0x378 (or whatever your parport is configured to use)

The parport_cable line isn't necessary for the JTAGAccelerator (but shouldn't 
do any harm either).

> 4/ Worst of all, I couldn't actually get the thing to work :(  Just got
> a JTAG chain error. I tried various JTAG delay settings. Since I'm
> attempting the Chameleon Accelerator (I believe I do have my port set to
> EPP mode) , I should possibly also backtrack and try very basic wiggler
> mode (reprogram the chameleon). I have in the past used this PC with
> ocdremote and the Chameleon in Raven mode though, but it was a bit
> dodgy. Suggestions welcome !
>
A JTAG chain error (Error validating JTAG scan chain, IR mismatch) suggests 
that you're using a wrong configuration file (see above). The OpenOCD 
verifies that the connected devices match the description of the jtag_device 
entries from the config files.

> 5/ Just using Insight at this stage. I'll give Eclipse a go when I get
> the underlying basics all working. My gdb.ini file has been setup as you
> suggest (plus a heap of other stuff, mainly source paths, I had from
> before). I'll attach the file below for reference.
>
> 6/ In the PC BIOS, there is no option to set the parallel port into EPP
> mode only. There is (EPP and SPP) or (EPP and ECP) and I think one
> other. Obviously all hysterical. I know you haven't gone into the
> Chameleon Pod, but it would be good if there was some sort of guide
> about Parallel Ports somewhere (maybe the Chameleon site ?). Could be
> useful for plain wiggler people too.
>
In your case, use EPP and SPP. The one thing you shouldn't use is ECP, as it's 
often not possible to switch to EPP from ECP (and OpenOCD doesn't attempt to 
do that switch, either ;))

>
> Cheers,
> Bruce

Kind regards,

Dominic