Re: [OpenOCD-user] Test/debugging jtag interface

[<ka...@as...>]

Spencer Oliver:
> On 26 March 2013 12:21, Karl Hammar <ka...@as...> wrote:
> >> that looks fine.
> >> The next step is to enable debug log, so add -d3 to the OpenOCD args.
> >
> > $ cat olimex.cfg
> > source [find interface/olimex-arm-usb-ocd-h.cfg]
> > source [find target/stm32f1x.cfg]
> >
> > init
> > reset init
> > stm32f1x mass_erase 0
> > flash write_image hasselby_feig.hex
> > reset
> > shutdown
> > $ cat pp.cfg
> > interface parport
> > parport_port 0
> > parport_cable aspo
> > reset_config trst_and_srst
> > #adapter_khz 500
> > parport_write_on_exit on
> > source [find target/stm32f1x.cfg]
> >
> > init
> > reset init
> > stm32f1x mass_erase 0
> > flash write_image hasselby_feig.hex
> > reset
> > shutdown
> > $
> >
> > Running openocd -f pp.cfg works fine.
> >
> 
> strange, does the new ftdi driver work ? It requires libusb-1.0 or libusbx
> build with --enable-ftdi and slight tweak of your config - note the
> added ftdi in the path.
> source [find interface/ftdi/olimex-arm-usb-ocd-h.cfg]

Same thing (using the libusb-1.0).

> I will run a check to see if it is working for me with your setup.

Don't forget that the setup used to work, something must have
happened between to flashing runs, since it worked and then tree
minutes later I consistently gets "Error: timed out while
waiting for target halted".

So my guess is that the olimex dongle is faulty. And I feel I more or
less have confirmed it now that the parport one works.

Regards,
/Karl Hammar

-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57