AVRFreaks.net

Remember this WILL erase the onboard ST-Link software , and afaik there is no way to restore it.
But if you are using Linux/*nix , the ST-Link software isn't supported anyways

SWD pins on the STM8S CN7 plug are like this :

1: VDD (Unused)
2: SWDIO/T_JTMS
3: GND
4: SWCLK/T_JTCK
Remember to connect GND to the target , and you can even "steal" 3v3 for the target , from pin-1 on the JTAG.

STANDALONE Programmer
----------------------
When jumpers/wires are removed from CN3 , in order to use the JTAG as a standalone unit.
The pinout on CN2 is like this :

1: GND via 10K ??? (Unused)
2: SWDIO/T_JTMS
3: GND
4: SWCLK/T_JTCK

ONBOARD Programmer
----------------------
When using the onboard JTAG to program the onboard target chip (the value-line chip) , you can't place the two CN3 jumpers as the manual says.
The CN3 Pins are like this :

1: T_JTMS (From onboard JTAG , differs from schematic)
2: SWCLK (To Onboard value-line chip)
3: T_JTCK (From onboard JTAG , differs from schematic)
4: SWDIO (To Onboard value-line chip)

What i did was connect a jumper on Pin 2-3 , and a short Test-wire on pin 1-4

Modifying the STM8S

HW:
-----
Just solder a standard 0.1" pinheader in the 7 empty holes below the usb connector.
I used a 2x4 block where i pulled out one pin (pin1)

Connect an ARM Jtag to the soldered plug , and "Unlock/Program" it.
I used a signalyzer-lite and OpenOCD (from SVN ... Well actually Simons script) from here http://www.versaloon.com/bbs/viewtopic.php?p=43#p43

I just modified openocd_update , and added --enable-ft2232_libftdi to the "./configure" around line 80 , so i had support for both hw dongles.


You will need "libftdi devel" installed on your distro (>= 1.17 is needed for FT2232H)
http://www.intra2net.com/en/developer/libftdi/
On Ubuntu just use Synaptic , and you'll get >= 1.17




SW:
-----
1: Start OOCD
sudo openocd -f interface/signalyzer-lite.cfg -f target/stm32.cfg


2:
telnet localhost 4444

3 (Once) : stm32x unlock 0

4:
reset halt
flash probe 0
stm32x mass_erase 0

flash write_bank 0 Versaloon_GCC.bin 0

reset run

disconnect & connect the USB cable on the STM8S
You are done

Modifying the STM32VL

This was a bit more difficult (programming) , as the JTAG pins weren't connected to any headers.
But there was access to SWD on the backside of the PCB. Via some Solderbridges (SB)
SB6 is STM_JTCK (SWCLK)
SB10 is STM_JTMS (SWDIO)
So i soldered some thin wires on the part of the solderbridge that was closest to the pinheaders.

At first i had hoped to use my newly build STM8S SWD progger to program the JTAG chip on the STM32 , but no matter what i did i couldb't get
vsprog to do it. vsprog reckognized the chip , but couldn't read/write it. I found out the chip was locked/protected , and as the "OOCD" i build above , using Simons script. Still have some problems with the vsllink hardware , i gave up on that.

I booted into windows , and used a "Genuine ST-Link" to unprotect & flash the JTAG chip.
Now ... I actually wonder if another STM32VL would have worked instead of a "Genuine ST-Link"

When i booted back into Linux the onboard JTAG worked fine , and i now could program the value-line chip on the board from the onboard JTAG.

Note !!!
For both the above solutions , there is another option :
Use the buildin serial bootloader (if you can solder wires on a chip w. 0.5mm spacing)
Serial-Loader program : http://code.google.com/p/stm32flash/
http://gostm32.blogspot.com/2010/09/bet ... oader.html

I am now asking you if there is a tool similar to ST-Link to upload code to the STM32 discovery board, I think that the solution that you posted here will do that, but I dont really want to get the soldering iron near my board, because I know that I will break it.

Unusable/Locked NXP CodeRed debugger