since upgrading to 1.4.0 programing will not work directly from C compiler

[ipestell]

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 Codegrip seem to work fine when I use it standalone, I can read/write etc with no problems, and everything seems to respond as in the manual.
I have tried the three switches below the GLCD display in all positions.
I also presume this is why I cannot Debug.
I have re-installed Codegrip, but no improvement.
Any ideas anyone?

[filip.grujcic]

Hello,

You will have to downgrade the firmware back to 1.3.0:
Here you can download the older version of CODEGRIP Suite, please install it and perform the firmware upgrade procedure inside CODEGRIP Suite, to get the 1.3.0 firmware inside your programmer:
http://help.mikroe.com/CODEGRIP%20Suite ... -win64.zip

I apologize for the inconvenience caused by this.

Regards,

[ipestell]

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

[ipestell]

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

[filip]

Hi,

Please download the 1.3.0 version from the https://s3.us-west-2.amazonaws.com/shar ... -win64.zip, disconnect from the internet, uninstall CODEGRIP Suite 1.4.0 and install 1.3.0 verion.
Then perform debugger firmware downograde from the newly installed 1.3.0 version.

Regards,
Filip.

[ipestell]

Thanks, it is now working again.
Regards
Ian

[Hayato_U]

When will a new version be released that fixes the problem?

[ipestell]

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 click start followed by run/pause many times, it may run, but mostly not.
What I have observed is that if I click start, and then wait maybe 15 - 20 seconds, it will often run, but not always.
Also, if it is going to fail, I notice the blue light on the board goes out when I press the run/pause button.
Overall, the USB link does not appear to be that solid.
This is all quite frustrating.
I have been a Mikroe user for many many years, and have generally found the products to be solid, but since the introduction of CodeGrip, this has not been the case. I also have an issue with the C compiler, but I will deal with that separately.

Regards
Ian.

[filip]

Hi,

We are working on the new version that will solve this issue.

@ipestell
Can you please open a ticket on the HelpDesk regarding this issue, I would like to analyze your issue thoroughly ?

Regards,
Filip.

[ipestell]

Done as requested.

Regards
Ian

[Hayato_U]

Hello,

When is this problem going to be solved?
Give us a roadmap.