|
September 21, 2009 - 5:02pm
Guest |
We have 2 new boards using STM8 processors. Board A uses STM8S207K6 and board B uses STM8S207R8.
Using Rlink and the SWIM connector, we connected to board A and tried reading the die ID. "Die ID check failed. Please make sure you have selected the correct target stm8 device" was reported. We then tried board B and got the same response. We went back to board A and forgot to change the processor. Die ID was sucessfully read! Changing the processor back to the 207K6 resulted in failure as before.
We are new to STM8 but very familiar with ST7 processors and are keen to try new firmware for the STM8 boards. Will board A programme succesfully as a 207R8? If so what do we need to define the 207R8 as for board B?
|
Hi,
For sure you should be able to connect to the K6 by selecting K6 and to the R8 by selecting R8... (!)
The first thing to do is to make sure that you are using the latest versions of the kits, because some not-so-old versions had problems with the Die ID definitions. Please tell us the versions of the Ride7 and RKit-STM8 kits that you have installed. Or you can click "help"->"About" and make a screenshot. Check also on our website if there are newer versions. Don't forget to check the version of all the kits you have installed (at least 2: Ride7 and RKit-STM8)
Best Regards,
Vincent
Thanks for your quick response.
We're using Ride7 Ver 7.24.09.0251 and RKit STM* Ver 2.24.09.0238
Hi,
If you can successfully read a device ID with a given setting, then probably the rest (programming, debugging, etc.) should be ok with the same setting.
Now, it's not normal that the device ID does not match the marking on the CPU.
Are your devices prototypes?
Did you get them through the standard distribution process?
Please give me the device ID that is read, when it succeeds.
Please also tell me _everything_ that is written on the chip. With this information I can ask ST to check if it is a special batch or something.
Best Regards,
Vincent
Both lots of chips, STM8S207R8 and STM8S207K6, were supplied by Farnell.
The 207K6 device ID, with processor set as STM8S207R8, reads as 0x37394142.
On the chips is written STM8S207 STM8S207
K6T6C R8T6
99087 VG 2204L VG
MYS 845 MLT22847
ST e4 X ST e4 B
I've not yet identified a specified chip to allow reading die ID of the 207R8 device, but I'll lrt you know if I do.
Best Regards
Brian
Hi,
Thanks for the information.
I will ask ST about your devices. Please tell me if you have issues working on the K6 by selecting the R8. (programming, debugging, etc.)
Sorry, I had not understood that you did not manage to connect to the R8 at all. Please make this test:
1. Close all instances of Ride and RFlasher, make a backup copy of this file:
\bin\STM8_SWIM_ProductInfo.txt
2. Open the original file in a text editor, search it for "" (without the quotes but with the <>) and add this line just after:
DieCheckMask="0x00000000"
Save the file, open Ride or RFlasher, select the STM8S207R8, connect it, perform the target connection test, tell me the result. If the connection succeeded, tell me the value of the Die ID that it reports.
Do NOT try other operations.
3. Restore the original file from the copy, open it in a text editor, search it for "" (without the quotes but with the <>) and add this line just after:
DieCheckMask1="0x00000000"
Save the file, open Ride or RFlasher, select the STM8S207R8, connect it, perform the target connection test, tell me the result. If the connection succeeded, tell me the value of the Die ID that it reports.
Do NOT try other operations.
4. Restore the original file from the copy, in order to be able to work with your K6 without issues.
When I have this information I should be able to help you more.
Best Regards,
Vincent
Hi,
Update on the STM8S207R8 board.
The problem reading that chip was to do with and external reset chip. Removing it solved the problem and the processor device ID is now readable as the correct chip. The device ID is identical to that read from the 207K6 device.
The problem now is only with the STM8S207K6
Best regards
Brian