Topic : Wrong PID issue

Forum : ST7/STM8

Original Post
Post Information Post
May 19, 2011 - 1:41am
Guest

I am currently using Ride7 with RLink to examine a board which has an ST72F63BK4 device installed. I am getting a wrong PID message when trying to connect to the device with RFlasher (device selected is ST7263BK4).

The Ride details are:-

Ride7 7.30.10.0159
RKit-STM8 for Ride7 2.32.10.0307
Ride7 Patch 7.30.10.0169

The device details are:-

ST72F63BK4M1
M99210344Z
MALAYSIA

The error message is:-

Wrong device detected.
Mismatch of the PID.
PID read: 07A
PID expected: 7B0
Please check target device selection, power and connections.

Any help would be appreciated.

Regards,
Stephen.
Replies
Post Information Post
+1
0
-1
May 19, 2011 - 11:04am
Raisonance Support Team

Hi,

The ST72F63B devices with the 7A PID are prototypes which Raisonance is not supposed to support.

Please contact your ST sales office for replacing them with normal production devices.

You could try to use the ST tools (STVP/STVD), which can drive the RLink and might be able to handle the prototype devices. But this is not guaranteed. And in fact it is not recommended to use prototype devices, because they might be not calibrated or have other similar problems that could prevent your application from working properly.

Best Regards,

Vincent
+1
0
-1
May 19, 2011 - 11:51am
Guest

Thanks Vincent,

These devices are in commercial products (USB interface for UPS) which I am attempting to repair. The USB interface no longer works (Windows reports Unknown Device). I am trying to determine if the USB interface has been damaged (possibly from ESD) but I can't even try since the issue with PID.

I have purchased new replacement components (non prototype), so I need to copy over the flash contents. It is possible that these devices have readout protection which will mean I am wasting my time, but again I won't know until I can access the device.

I will have a look at STVP/STVD tools you mentioned.

Any other help would be appreciated.

Regards,
Stephen.
+1
0
-1
May 25, 2011 - 4:43am
Guest

I managed to solve the problem by modifying the file used by RFlasher:-
(note that you will need to run your text editor in administrator mode to modify the file if running Vista or Windows 7)

C:\Program Files\Raisonance\Ride\bin\ST72ICC_ProductInfo.txt

This is a text file and has a warning against modifying the file, which I'm glad I ignored. I found the PID reference of 0x7B0 in the file under the ST72F63BK section ("Product_Type_Identifier_ST7PID=0x7B0") and changed it to 0x07A (after making a backup of the file). RFlasher now reads the option bytes and the flash contents, since the device was not read-protected.

I can now proceed with burning the flash+option bytes into new ST72F63BK devices to repair the boards (I will restore the original ST72ICC_ProductInfo.txt file first).

I had looked at the possibility of using STVP/STVD, however this solution worked out the best. This information may be useful for anyone else who comes across this issue.

Regards,
Stephen.
+1
0
-1
May 25, 2011 - 4:56am
Raisonance Support Team

Hi Stephen,

Good work concerning the reerse Engineering of the ProductInfo file!
As Vincent explained the chips in use in your UPS are not following the guidelines for commercial chips (early fab, which we are considering as prototypes).

I am glad that you enjoy so much our products so much that you preferred to hack it through instead of using STVP!

Best Regards,