Topic : Unable to verify ST72324 after Programming

Forum : ST7/STM8

Original Post
Post Information Post
July 23, 2007 - 12:40pm
Guest

Hi,

When I am trying to verify ST72324J2 MCU on board after programming it, there is an error message "Error resetting ICC mode; no response from the device" on Reflasher S/W.

The programming device I am using is RLink.

I am able to erase, check blank and program the MCU but I am not able to verify it.

Please help.

Please also let me know if maore info required.

Thanks,
kea

Replies
Post Information Post
+1
0
-1
August 13, 2007 - 1:34pm
Guest

Hello, can you please answer the questions on this FAQ : http://www.raisonance.com/Forum/punbb/viewtopic.php?id=2231 and send me the answers at ?

Best regards,
Lionel

+1
0
-1
December 18, 2008 - 1:27pm
Guest

Hello,

My problem is I use command prompt to program ST72324 but when I verify the checksum it shows 0xE000 which is the same checksum without programming. The command line I type : st7_pgm st72324j2 himid_st7ost.s19 0x7FA4 F. The option byte is same as what I have set which is 0x7FA4. Please advise me if I miss out something?

Thanks.
JOYCE

+1
0
-1
December 18, 2008 - 2:19pm
Raisonance Support Team

Hi JOYCE,

For now ST7_pgm can only read hex files, not s19. That is very probably the source of your problem.

Please try to convert your s19 file to hex and try to give the hex file to ST7_pgm.

Best Regards,

Vincent

+1
0
-1
December 19, 2008 - 3:13am
Guest

Hi VincentC,

Thanks for your reply.

I have actually simply change the .*s19 to *.hex and have the same result where checksum returned is 0xE000. However, if I programe the device by using RFLASHER interface, both *.hex and *.s19 file can return the correct checksum. I am very curious why this cannot be done through command prompt. Maybe you can enlighten me with some idea?

Thanks...

Regards,
JOYCE

+1
0
-1
December 19, 2008 - 10:21am
Raisonance Support Team

Hi,

Changing the file name is not enough: hex and s19 are different formats and the contents of the files are not the same! So you really need to _convert_ the file. For that you can use a free converter, there are several on the internet. (personnally I use objcopy from gcc) But the best is to have your linker generate a hex file directly. All decent linkers can do that if you ask them.

The part of the software that reads the input file is not factorized between RFlasher and ST7_pgm. That explains why RFlasher can read s19 files and ST7_pgm cannot. (yet)

Best Regards,

Vincent

+1
0
-1
December 22, 2008 - 1:33pm
Guest

Hi Vincent,

I use BINCVT to convert s19 to bin file and then from bin file to hex file but still fail to program by using command prompt. The checksum return is still 0xE000. I do not have the source code of this file so I may not use the linker to generate a hex file directly. Can you please advise any method that I can try? Thanks.

Regards,
JOYCE

+1
0
-1
December 22, 2008 - 1:52pm
Raisonance Support Team

Hi,

There is probably a problem in your conversion.
(bin files are bad for devices like ST7 that don't have the start of flash at zero.)

I suggest you use RFlasher for converting. (you know that RFlasher reads your s19 correctly) For this, open RFlasher, load the s19 file, and then save the content of the memory in a hex file. (right-click in the data dump view)

Or you can send your s19 file to us (support@raisaonance.com) and we will convert it. (include a link to this post in the message)

Please also tell me which version of the Ride7 and STM8-ST7 kits you are using, and the command line you use for launching ST7_pgm.exe.

Best Regards,

Vincent

+1
0
-1
December 23, 2008 - 10:17am
Guest

Hi Vincent,

Really thanks for your helpful info. I can now program by using command prompt with the *.hex file generated by RFlasher.

Thanks a lot.
JOYCE

+1
0
-1
December 24, 2008 - 10:17am
Guest

Hi Vincent,

I have another question here. Is it possible for me to check for the checksum by using command prompt as well? Any command line to execute this checksum verification?

Thanks,
JOYCE

+1
0
-1
January 2, 2009 - 11:38am
Guest

Hi

All the possibilities of ST7_pgm.exe can be seen from the help menu.
If you run ST7_pgm.exe without argument you will get this help.
I do not know if this is exactly expect but I think the parmeter "V" after file name can be used to do a verication ( it has to be written first after the file name).

Matloub

+1
0
-1
January 5, 2009 - 3:31am
Guest

Hi matloub,

The command line I am using now is: st7_pgm st72324j2 c:\ file.hex 0x7FA4 F

I observe that if I put V after the file name which is :st7_pgm st72324j2 c:\ file.hex V 0x7FA4 F, I cannot write the option byte correctly( the option byte is set as default = FFE7) and I also do not get the reading of checksum. By using RFLASHER, I will only need to click on the Statistics button to verify the checksum. Please advise if I did wrongly.

Thanks,
JOYCE

+1
0
-1
January 5, 2009 - 11:16am
Raisonance Support Team

Hi,

ST7_pgm does not allow to read the checksum. (not for now, at least)
But if you verify, you don't need the checksum...

About the option bytes, I will need some clarification:
You say that you want to program the value 0x7FA4, which selects the internal oscillator as main clock source and activates the PLL.
This seems wrong to me, because the datasheet from ST says this (page 151 in the version I have):

ST72324 datasheet Rev.4 page 151 wrote:
The PLL must not be used with the internal RC oscillator.
The PLL is guaranteed only with an input
frequency between 2 and 4MHz.

And also this:

ST72324 datasheet Rev.4 page 151 wrote:
CAUTION: the PLL can be enabled only if the
“OSC RANGE” (OPT3:1) bits are configured to
“MP - 2~4MHz”. Otherwise, the device functionality
is not guaranteed.

This could very well explain that you are unable to program and/or verify the option bytes that you mention.

Please check the value that you want in your option bytes.

Best Regards,

Vincent