We are using EasyPIC v7a with PIC18F14K50.
We have a problem that CODEGRIP Ver.1.4.2 (Firmware is the same) always fails to verify.
However, the written code appears to be working correctly.
Any suggestions how to fix this problem?
There are too many bugs in CODEGRIP.
PIC18F14K50 Verification Failed (Ver.1.4.2)
- filip.grujcic
- Posts: 822
- Joined: 14 May 2018 08:34
Re: PIC18F14K50 Verification Failed (Ver.1.4.2)
Hello,
I will notify our development team regarding this.
There's nothing you can do about this at the moment, however it shouldn't cause you any issues, you are still able to program the MCU without problems.
Regards,
I will notify our development team regarding this.
There's nothing you can do about this at the moment, however it shouldn't cause you any issues, you are still able to program the MCU without problems.
Regards,
Filip Grujcic
- filip.grujcic
- Posts: 822
- Joined: 14 May 2018 08:34
Re: PIC18F14K50 Verification Failed (Ver.1.4.2)
Hello,
Could you please provide the hex file you are trying to program?
Regards,
Could you please provide the hex file you are trying to program?
Regards,
Filip Grujcic
Re: PIC18F14K50 Verification Failed (Ver.1.4.2)
Hello,
Please confirm.
Please confirm.
- filip.grujcic
- Posts: 822
- Joined: 14 May 2018 08:34
Re: PIC18F14K50 Verification Failed (Ver.1.4.2)
Hello,
The reason why verification is failing in this MCU is because one unimplemented bit in CONFIG2L register that, according to datasheet is supposed to be read as 0, is actually read as 1, causing the verification to fail. Our development team is aware of this and will address this in one of the future updates, however like I said previously, this won't hinder your development in any way and you can continue using the programmer without any concerns.
Regards,
The reason why verification is failing in this MCU is because one unimplemented bit in CONFIG2L register that, according to datasheet is supposed to be read as 0, is actually read as 1, causing the verification to fail. Our development team is aware of this and will address this in one of the future updates, however like I said previously, this won't hinder your development in any way and you can continue using the programmer without any concerns.
Regards,
Filip Grujcic