Hi Vincent,

thanks for your quick reply. Unfortunately, the CAPS tool on the ST website does not yet support the STR912FAW47 processor.
RFlasher is not a solution because we need to do a remote control of the flashing application.

Best Regards,

Lars

Hi,

I now realize that STR9_pgm has not been tested for the STR9FW47 and the other 'big' STR9 devices. (it was usually ST who tested it. but it's the first time we support a device in RIDE before they do it in CAPS, so we got a little confused... ;) ) And in fact there are problems in STR9_pgm.exe.

Here is a patch to correct the problems in the executable, and a jci file for the STR9FW47:
ftp://www.raisonance.com/pub/ST/patch_STR9_pgm_STR9FW47.zip

With this I could dump, erase, blank-check, program and verify on a STR9FW47 using STR9_pgm.exe.

Unzip the file and read the readme.txt for instructions.

You have to be careful though, as STR9_pgm only works with obj files, which are normally produced by CAPS. RIDE produces hex files, which are not the same as obj files. And because CAPS does not handle the STR9WF47 for now, you cannot use it for generating the obj file. So here is what you should do:

1. Program the device with your application using RIDE or RFlasher. (and check that it works ;) )

2. Use STR9_pgm to dump the flash to an obj file, with this command:
STR9_pgm.exe STR9FW47.jci UID myapplication.obj

3. Now you have your obj file that you can use to program the Flash in production line / remote control with STR9_pgm.exe:
STR9_pgm.exe STR9FW47.jci UIECPV myapplication.obj

Please give it a try and tell me how it goes, as you'll be the first 'real user' of this feature.

Best Regards,

Vincent

Hi Vincent,

thanks for your quick reply. First tests show that it works as required. Your quick help is appreciated very much.

Best Regards

Lars

Hi,

Some customers complained that the file referenced by the link above disappeared from the server. This is true and unwanted. I could dig the archives, but it would take some time and in any case probably you don't need these files:

First, the changes in the STR9_pgm.exe file itself are included in the versions of the software that have been released after the correction. So you must simply download and install the current versions of Ride and RKit-ARM software from our extranet. And they also include other changes that you probably need (support for Win7 and Vista 64-bits, some bug fixes, etc.)

Second, the jci file is only required if you JTAG-chain the STR9 with some other JTAG device. This does NOT include the several JTAG TAPS that are included in the STR9. It only applies if your board chains the STR9 with another JTAG physical device, like an FPGA, or a second STR9 for example. So if you do not JTAG-chain, you do NOT need a jci file. If you DO JTAG-chain, then in any case you will have to modify the jci file, either using CAPS or by hand. And in this case it's probably easier to have CAPS generate the "chained jci file" as if you were using another STR9, and then edit the file by hand. The other way would be to take the "single STR9xxx47 jci file" from us and add the chaining to it by hand, which is much more complex.

I hope it helps.

Best Regards,

Vincent