Greetings,

Try debugging your problem using PROG12Z. Are you able to replicate the issue?
If you are able to program in PROG but not in CPROG, then we can start looking into the BAT or CFG file you are using.


Takao Yamada

Greetings,

If you have CPROG12Z, then you have PROG12Z. Check your C:\pemicro\prog12z directory and you will find the software I need you to use. 

Inconsistent errors are difficult to debug and right now there are not enough information to fix this issue. 

One thing you may want to try is program the exact same board 30 or more times and see if the issue occurs. If not, then the issue is not in software or drivers. It is most likely hardware when you are switching between boards. You may want to check your ribbon cable for problems.


Takao Yamada

Good Morning Takao,

  I try to locate on C:\pemicro\prog12z and there's nothing there, on it't folder was only CPROG12Z.EXE and some other files.I try to program one good board that was my "Gold Board". It just erase the loaded program and "Error 18 come out". try it again on the same board, Failed ..try it again failed..and keep on trying until it pass (maybe 30 or more times).After it pass I try to load the program on the same board again and it Failed,and I had to do it the same thing again until it pass.I'm just testing only one known good board. I checked my cable and it was ok. Try on the other interface adapter and it failed the same "Error 18 "

I do appreciate for taking your time on this matter

Thanks
Dhing

Greetings,

That means someone gutted your PROG12Z folder to only have the CPROG software. Which is unfortunate. 

You may want to change the IO_DELAY_CNT setting within CPROG. Right now you have it set to 14. Try a higher number like 50. See if this gives you better results:

C:\PEMICRO\PROG12Z\CPROG12Z.EXE ? IO_DELAY_CNT 50 C:\pemicro\veltron2c\v2ctest\v2ctest.cfg Interface=USBMULTILINK PORT=USB1


Takao Yamada

Hello.
 I change the IO_DELAY_CNT from 14 to 50, it get an error #34 "Can't enter on background mode. Change it back to 14 and it goes on the same problem "Error 18.
I edit the cfg script file and add another command VM (verify module) before PM command..Look like this

RE
CM c:\pemicro\prog12z\9s12dt128_128k.12p
EM
BM
SS c:\pemicro\veltron2c\v2ctest\v2ctest110.phy
VM
PM

It flash me an error on the screen like this.
CMD> VM
Checking range of S record . Checked
Verifying Address $0E0000. Verify Error at Address $0E0000
Byte in Module is $FF and should be $34
Error 3 during the script

I don't know if these make sense to you.

Thanks again
Dhing

Greetings,

VM should be at the end. VM indicates you want to verify that the programming was done correctly. You have it set before the programming, so it will fail. The chip has not been programmed yet.


Takao Yamada