Hi Frans, I have tryed what Marcelo said and it is right... sometimes it is enough just one additional byte in the program to make it fail or pass...
This is really strange...
Could you test it by yourself?
I really need to use this chip in my design... is it possible to fix the programmer or is it a hardware issue that can´t be solved by software?
Thanks, Pablo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am still puzzling with this. I wanted to work on it last week (in the evenings during my Cern work visit), but things got more hectic than I thought.
I have added the device to low voltage programming mode entry this morning while in the train. I will try and test it but if you can't wait you could try the new firmware yourself. https://raw.githubusercontent.com/fransschreuder/usbpicprog/master/trunk/uc_code/uc_code.hex
Frans
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Frans, I tryed this new firmware but the problem is still there. Furthermore, with this new firmware the code that works ok before, now it doesn't get programmed.
Pablo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get more failures, I mean, some .hex files that I was able to program without troubles now are failing. I reinstalled the last firmware and they are working again, but the problem is still there with some of them as I told you before.
Is something wierd, in those files that fails to program it is enough to change a couple of bytes as Marcelo told and they get programmed ok...
Pablo.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Frans, as I really needed to program those 16f1825 for a project in which I am working on, I ended buying a CCS Mach X programmer. Using this programmer I realized that the problem with yours is that after it programs the pic, the pic starts to execute the code, so when it tries to verify, it fails.
The Mach X programmer doesn't let the pic starts before performing the verification.
The solution goes by not letting the pic starts after programming...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Alright, usbpicprog releases VPP after every phase (erase / program code / data / verify / program config)
I will make a version that doesn't release VPP and keeps it in programming mode.
Although I don't understand why it starts executing code, as we bring it into programming mode, not in run mode.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Frans, I have tryed what Marcelo said and it is right... sometimes it is enough just one additional byte in the program to make it fail or pass...
This is really strange...
Could you test it by yourself?
I really need to use this chip in my design... is it possible to fix the programmer or is it a hardware issue that can´t be solved by software?
Thanks, Pablo
Hi Pablo,
I am still puzzling with this. I wanted to work on it last week (in the evenings during my Cern work visit), but things got more hectic than I thought.
I have added the device to low voltage programming mode entry this morning while in the train. I will try and test it but if you can't wait you could try the new firmware yourself.
https://raw.githubusercontent.com/fransschreuder/usbpicprog/master/trunk/uc_code/uc_code.hex
Frans
Hi Frans, I tryed this new firmware but the problem is still there. Furthermore, with this new firmware the code that works ok before, now it doesn't get programmed.
Pablo
Hi Pablo,
Ok, so does this mean that the new firmware doesn't do anything? Or do you get more failures.
Frans
I get more failures, I mean, some .hex files that I was able to program without troubles now are failing. I reinstalled the last firmware and they are working again, but the problem is still there with some of them as I told you before.
Is something wierd, in those files that fails to program it is enough to change a couple of bytes as Marcelo told and they get programmed ok...
Pablo.
Frans, as I really needed to program those 16f1825 for a project in which I am working on, I ended buying a CCS Mach X programmer. Using this programmer I realized that the problem with yours is that after it programs the pic, the pic starts to execute the code, so when it tries to verify, it fails.
The Mach X programmer doesn't let the pic starts before performing the verification.
The solution goes by not letting the pic starts after programming...
Alright, usbpicprog releases VPP after every phase (erase / program code / data / verify / program config)
I will make a version that doesn't release VPP and keeps it in programming mode.
Although I don't understand why it starts executing code, as we bring it into programming mode, not in run mode.