Hi,
Can i help me
it's impossible to upgrade my Easypic V8 with codegrip suite to the firmware 1.1.2
How it's possible, the codegrip suite when i click on the help/update button, i see available firmware version 1.1.2. but i don't kwon how it's possible
Can you help me
Jean-michel
Update code grip 1.1.2
Re: Update code grip 1.1.2
My guess is that you do not need to upgrade firmware at all...
You are probably already using v 1.1.2 firmware on your EasyPIC v8
To check firmware versions:
1) Run Codegrip with EasyPIC v8 connected by USB and scanned, and found
2) "Codegrip" - "Scanning"
3) Select "device control" tab
4) You should see grey text for Hardware version 1.00 and firmware version 1.1.2
5) ONLY if you see firmware version earlier than 1.1.2 should you update the firmware
ONLY IF FIRMWARE UPDATE IS NEEDED...
This works for me.....
1) Run Codegrip Application
2) Connect EasyPIC v8 via USB but leave power off
3) Help
4) updates
5) select "codegrip" tab
6) "scan devices"
7) power on EasyPIC v8
8 ) check that your board is listed with serial number and firmware version
9) if firmware version shows as 1.1.2 then there is no need to update - skip to step 12
10) if firmware is earlier than 1.1.2 then click "update firmware" button
11) note the advice to re-connect
12) select "codegrip" scanning tab at left
13) click on usb icon to change it from grey to blue
Do this at your own risk - if update fails, I will not buy you a new board!
If you want to avoid risk, wait for a reply from mikroE support, just in case they know something that I do not.
I am just a hobby user, not an expert.
You are probably already using v 1.1.2 firmware on your EasyPIC v8
To check firmware versions:
1) Run Codegrip with EasyPIC v8 connected by USB and scanned, and found
2) "Codegrip" - "Scanning"
3) Select "device control" tab
4) You should see grey text for Hardware version 1.00 and firmware version 1.1.2
5) ONLY if you see firmware version earlier than 1.1.2 should you update the firmware
ONLY IF FIRMWARE UPDATE IS NEEDED...
This works for me.....
1) Run Codegrip Application
2) Connect EasyPIC v8 via USB but leave power off
3) Help
4) updates
5) select "codegrip" tab
6) "scan devices"
7) power on EasyPIC v8
8 ) check that your board is listed with serial number and firmware version
9) if firmware version shows as 1.1.2 then there is no need to update - skip to step 12
10) if firmware is earlier than 1.1.2 then click "update firmware" button
11) note the advice to re-connect
12) select "codegrip" scanning tab at left
13) click on usb icon to change it from grey to blue
Do this at your own risk - if update fails, I will not buy you a new board!
If you want to avoid risk, wait for a reply from mikroE support, just in case they know something that I do not.
I am just a hobby user, not an expert.
Start every day with a smile...... (get it over with)
- filip.grujcic
- Posts: 822
- Joined: 14 May 2018 08:34
Re: Update code grip 1.1.2
Hello,
I can confirm that the steps Hexreader provided are correct.
However, there is no risk of damaging the board or the programmer, or having a corrupt firmware, therefore you do not need to worry about that.
Thank you, Hexreader.
Kind regards,
I can confirm that the steps Hexreader provided are correct.
However, there is no risk of damaging the board or the programmer, or having a corrupt firmware, therefore you do not need to worry about that.
Thank you, Hexreader.
Kind regards,
Filip Grujcic
-
- Posts: 2780
- Joined: 25 Dec 2008 15:22
- Location: Scotland
Re: Update code grip 1.1.2
Standalone codegrip for STM32
Fails to erase the flash during upgrade
that leaves me stuck with no ability to do anything
5th time lucky!
Fails to erase the flash during upgrade
that leaves me stuck with no ability to do anything
5th time lucky!
- Attachments
-
- UpdateGood.jpg (6.08 KiB) Viewed 2163 times
Best Regards
Mince
Mince
Re: Update code grip 1.1.2
Hi,
I apologize for the issue, does the CODEGRIP now run correctly ?
Regards,
Filip.
I apologize for the issue, does the CODEGRIP now run correctly ?
Regards,
Filip.
-
- Posts: 2780
- Joined: 25 Dec 2008 15:22
- Location: Scotland
Re: Update code grip 1.1.2
Hi filip,
Thanks for your interest. I really should have started a new thread.
i can operate the unit using codegrip suite and i can scan for it in Necto setup no issue, but within Necto it wont program the board so it can't enter debug mode either.
codegrip all good scan in Necto during creation of a setup. All good settings which i pref to use
Thanks for your interest. I really should have started a new thread.
i can operate the unit using codegrip suite and i can scan for it in Necto setup no issue, but within Necto it wont program the board so it can't enter debug mode either.
codegrip all good scan in Necto during creation of a setup. All good settings which i pref to use
Best Regards
Mince
Mince
-
- Posts: 2780
- Joined: 25 Dec 2008 15:22
- Location: Scotland
Re: Update code grip 1.1.2
doing a debug session in Necto
fails to connected to the target, blue light does one super short on pulse and then stays off and flashing fails I should say, i am using wired (USB-C) connection. Not WiFi
fails to connected to the target, blue light does one super short on pulse and then stays off and flashing fails I should say, i am using wired (USB-C) connection. Not WiFi
Best Regards
Mince
Mince
-
- Posts: 2780
- Joined: 25 Dec 2008 15:22
- Location: Scotland
Re: Update code grip 1.1.2
yey solution provided by the MikroE team
the issue was that the Clicker 4 for STM32 originally arrives with demo code and i assume now that it also has a protected bootloader for people who do not have a codegrip JTAG hardware. Soooo the unit arrives with flash protection enabled and this was the root of my issues.
I tested that the codegrip JTAG unit was working by switching to using a uni clicker fitted with an STM32F407ZG, worked perfectly with both codegrip app and full Necto. So i then knew that my codegrip JTAG hardware was all good.
to remove the locked flash, setup your codegrip app as shown below.
huge thank you to MikroE
the issue was that the Clicker 4 for STM32 originally arrives with demo code and i assume now that it also has a protected bootloader for people who do not have a codegrip JTAG hardware. Soooo the unit arrives with flash protection enabled and this was the root of my issues.
I tested that the codegrip JTAG unit was working by switching to using a uni clicker fitted with an STM32F407ZG, worked perfectly with both codegrip app and full Necto. So i then knew that my codegrip JTAG hardware was all good.
to remove the locked flash, setup your codegrip app as shown below.
huge thank you to MikroE
Best Regards
Mince
Mince