Topic : Urgent information required: ST7 pgm used for ST7FLITE25 and ST7FLITES5

Forum : ST7/STM8

Original Post
Post Information Post
June 2, 2016 - 12:37pm
Ruly Sumargo

Dear All

I will need your support, is there any way to restore the RC calibration values for ST7Flite25 and ST7FLITES using ST7_pgm command line?

at the moment when i am using the ST7pgm to perform programming of firmware, but having this condition below:

1) RC calibration values is become corrupted after programming perform

2) Currently I am using software RKit-STM8_2.56.15.0092.exe, is there any issue for this package if we run it under windows 7 64bits?

3) The command that I used during this trial are:

    A) For ST7FLITE25 :   st7_pgm ST7FLITE25 I 07_rm22tg20_V04.hex V 0xA0A2

    B) For ST7Flites5 : st7_pgm ST7FLITE25 I 08_rm22tg00_V03.hex V 0xA0A2

4) If during the scripting the "I" parameter (to select the ICC) is not selected, what would be the issue for the programming?

Hope somebody can help me for this items

Replies
Post Information Post
+1
0
-1
June 9, 2016 - 9:34am
Etienne Cassin

Hello,

We received also your email request but I think is better to answer on the forum. maybe it can helps some other customers ;)

  1. How do you see the calibration is corrupted? did you checked with an oscilloscope or did you controled the value at 0xFFDE? ROM 0xDEE0? Did you tried other hardware/software? do you have an internal or external oscillator? did you set the right option bytes for the oscillator? Could you provide all the information written on the MCU?
  2. The RKit-STM8_2.56.15.0092.exe version is out of dated, please install the latest version at http://support.raisonance.com/content/rkit-stm8
  3. It seems good for me, I checked the option bytes  it saying that you activated an internal RC
  4. The "I" parameter does have effect on the programmed option bytes. it will ignore them or not for the debug. The comunication system between the ST7 target and the Rlink will change.

I hope that can helps.

Best regards,

+1
0
-1
June 9, 2016 - 11:27am
Etienne Cassin

Dear Etienne,

1) I have seen it using the STVP software to view the data, and also check using an oscilloscope for the timing when the MCu run (there are 50% slower when the RC calibration values in 0xFFDE and 0xffdf corrupted) (see picture attached)

2) May I know is there any changes related with the ST7Flite25 and st7flites5 on the latest update? as i didn't see it clearly in the readme files

4) Normally which communication system shall be used by the software to communicate with RLink, once the "I" parameter is not stated?

+1
0
-1
June 9, 2016 - 11:34am
Etienne Cassin

Hello,

It seems that the "I" option need some tests, I will let you know as soon as possible.

Concerning the latest release, it's always better to update it, some bugs are fixed but all are not written in the release note.

Best regards,

+1
0
-1
June 16, 2016 - 3:05pm
Etienne Cassin

hello,

Could you provide us the entire name of the MCU (everything written on top of the device)?

Thanks,