[OpenOCD-user] parport dongle

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

 Since I didn't manage to make my olimex dongle work, I designed a
parport one so that I could have something to compare with. Design
and patch attached, design files available at [1], comments are
welcome.

 My openocd.cfg now contains:

interface parport
#parport_port 0x378
parport_port 0
parport_cable aspo
reset_config trst_and_srst
#parport_toggling_time 10000
#adapter_khz 500
parport_write_on_exit on

 Test run:

Open On-Chip Debugger 0.7.0-dev-00204-g1da9e59 (2013-03-25-19:11)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.sourceforge.net/doc/doxygen/bugs.html
Warn : Adapter driver 'parport' did not declare which transports it allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
parport port = 0x0
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 500 kHz
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
cortex_m3 reset_config sysresetreq
Info : clock speed 500 kHz
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x06420041 (mfg: 0x020, part: 0x6420, ver: 0x0)
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x06420041 (mfg: 0x020, part: 0x6420, ver: 0x0)
target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x0800061c msp: 0x20001000
Info : device id = 0x10016420
Info : flash size = 32kbytes
stm32x mass erase complete
wrote 1660 bytes from file hasselby_feig.hex in 0.237011s (6.840 KiB/s)
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x06420041 (mfg: 0x020, part: 0x6420, ver: 0x0)
shutdown command invoked

///

Page 46 in doc/openocd.pdf (section 8.2 / parport ) says:

> parport_toggling_time 1000
> adapter_khz 500

But having parport_toggling_time in openocd.cfg made openocd complain:

 Error: BUG: unknown jtag clock mode

Have I misunderstod something?

///

Some notes.

 I could not use a standard wiggler one since I didn't have any '244
chips handy and I wanted it to behave differently.

 I wanted that no signal from pc or disconnected cable from pc should
result in mcu default values (page 645 of [2] says that there are
pullups on all jtag pins except TCK which have a pulldown).
Then I could attach/disconnect cables without changing the pin state.

Regards,
/Karl Hammar

[1] http://turkos.aspodata.se/git/openhw/isp/pp_jtag_arm20.sch
    http://turkos.aspodata.se/git/openhw/isp/pp_jtag_arm20.pcb

[2] http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/REFERENCE_MANUAL/CD00246267.pdf


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