On 23/08/2010 22:21, Peter Stuge wrote:
Spencer Oliver wrote:
ST sent me the api, it is based on mass storage device.
They are happy for openocd to support it.
Any chance of a copy of the API?
The actual api was sent under nda, so i cannot send it on. It
contains a lot more info about the interface (eg. dfu) that they do
not want published.
Then I would personally ignore them and focus on doing business with
companies with a more sane attitude to their documentation.
They just do not want some parts of the stlink to be known.
It is not a problem to publish info on the jtag/swd access layer, just
happens to be all in one document.
The stlink does have dfu capability, it is documented in the info i
was sent.
If it is actually standards compliant DFU (that is a USB class spec)
then maybe you can use the dfu-updater software to reprogram the
firmware.
It is dfu wrapped in a mass storage cmd block.
If you just need to reprogram then any tool can do that, although you
will loose the stlink bootloader.
Of course that doesn't help for debugging.
The problem is that the stlink does not have any low level jtag/swd
access,
What do you want to use openocd for with this device then?
Because it is very low cost (£<15) and supports stm32.
It is supported by higher level cmds, eg. stop, reset, resume etc. This
is why i said to openocd it behaves more like a target.
Cheers
Spen
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
