Thanks.

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 b...

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

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 (writ...

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

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 comm...

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 ...

filip wrote: ↑

15 Sep 2021 15:40

Hi,

Currently interrupts are not implemented in the mikroSDK, I suggest using legacy project for the interrupt based code.

We have in plans to implement this in some of the future updates of the mikroSDK.

Regards,
Filip.

When will this happen?

Regards
Ian

Hi, I am transferring a program from PICPROC, which runs fine. When I transfer the code to Necto, I get various problems with the program hanging. Using the debugger it would seem the program is hanging on a delay statement. If I remove the delay statement, the program will run. After further develo...

Done as requested.

Regards
Ian

I said above it was working OK, which turns out not to be quite true. Whilst all the basic functions are working, I am having problems with the debugger. Whenever I go into the debugger, and then press run/pause it will almost always fail to run, quickly going from 'real time' to 'paused'. If I clic...

Thanks, it is now working again.
Regards
Ian

Also I keep getting a virus message when I install the program from your link.
Regards
Ian

Thank you for your reply, I have followed your instructions and link, and I can only get version 1.4.0
regards
Ian

Since I upgraded Codegrip to 1.4.0, I have not been able to program my devices 18F45K22 or 18F46K22 directly from the Program or Compile and program buttons. The dialog at the bottom of the screen remains at Erase chip..., and I have to kill the program to get out of it. All other functions of Codeg...