Codegrip 1.7.0 will not verify

[ipestell]

Since updating with Codegrip 1.7.0, whenever I program a device, it fails verification.

It does this with all devices I have tried, I am currently using PIC18F45K22 and PIC18F46K22.

However after programming, despite the verification error, the device/program seems to work OK.

Anyone have any ideas or suggestions.

Cheers
Ian

[faeton]

Most likely, the check fails because the compiler does not erase the old firmware, and does not program the new one.
Try to erase the firmware in CodeGrip window manually first, and then write a new one form compiler.

At the same time, in CodeGrip window all works fine and using the Chinese programmer ST (whistle), everything works fine in compiler to.



This update is very crooked.
mikroPascal is now unable to write firmware to STM32.
The erase function doesn't work seem.

CodeGrip has become a useless beautiful box.
I do not know how to restore the previous version now and will never make updates in the future.

I contacted support recently, there is no response yet.

[ipestell]

Thanks for your reply.

I did try erasing the firmware in the device manually, and then read it back to see if it was all 0xFF, and it was, but the problem remained. Also, I did a blank check, and it said it was blank.

I have since tried a PIC18F26K22, and it is still the same.

I agree with your comment about 1.0.7.0, and in general I have found that Mikroe stuff is not as rock solid as it was in the past.

Thanks
Ian

[IvanJeremic]

Hi,

The issue is being investigated at the moment, I have already requested your project in our ticket since we can not reproduce this issue with our projects.

You can also share the project here if you want.

Regards,

Ivan.

[ipestell]

After much trial and error, some without any real logic, I believe I may have resolved this.
It appears that the start address for the EEPROM was set to 0x0008, and once I set this to 0x000 it started to verify OK.

One for the archives I guess.

Cheers
Ian

[ipestell]

OK, a bit quick off the mark there.

The problem is with the EEPROM data, and the message about failed verification has returned.

When the device is programmed, it does not load the EEPROM data correctly (hence the verification error) however within the operational program, it is able to update (write to) the EEPROM correctly.

Any ideas?

Cheers
Ian

[IvanJeremic]

Hi,

Can you send us a HEX file that was causing the original issue so we can try to reproduce the issue?

Maybe there is a problem with the CODEGRIP Suite that we are not aware of.

Regards,

Ivan.

[ipestell]

Hi,
I do not seem to be able to send a message with attachments of any type.

I have also tried pasting the contents of the Hex file, but that will not send either.

Is there another way

Regards
Ian

[IvanJeremic]

Hi,

Place this dll file into the folder where your CODEGRIP is installed. See if it helps with your original HEX code.

codegrip-dll-core.zip

(479.51 KiB) Downloaded 8 times

Regards,

Ivan.

[ipestell]

Hi Ivan,
Thanks for that, it does appear to have resolved the issue. I have tried it a few times now.

One other small issue, which you may want to look at, although it is not causing me a problem, when I do a blank check, I get the message in the attached file.

Cheers
Ian

PS I still do not seem to be able to send attachments, so I have sent the image to support for you.

[IvanJeremic]

Hi,

Let's continue the conversation in the ticket you made since you cannot post pictures here.

Regards,

Ivan

[IvanJeremic]

Hi,

For everyone who has a similar issue, the problem is with the CODEGRIP Suite.

The memory for PIC18F46K22 is set to be larger than it actually is, so when you erase the chip you do erase the entire MCU, but because the CODEGRIP Suite thinks there is more memory than it actually is when you click on Blank it will say that it is not empty when the MCU actually is empty.

This issue will be fixed in the next update of the CODEGRIP Suite.

Regards,

Ivan.

[ipestell]

Thanks.