Home › Forums › TinyG › TinyG Support › TinyG Updater App Problems
Tagged: TinyG Updater App, TinyG Updater App Crash
- This topic has 14 replies, 6 voices, and was last updated 9 years, 4 months ago by travelphotog.
-
AuthorPosts
-
June 26, 2015 at 3:11 am #7869akfreakMember
Ok.. I got my hands on some TinyG boards a V8 and V9.
Starting with the V8 I wanted to update the FW. Installed is 384.04 (confused at the build numbers vs the release numbers on the GitHub pages, nit not the issue: )
http://gyazo.com/0901b33b3cf56ca2090c91acac52fdfbSo I am fully speaking to the board via CoolTerm, and I have set some of the Parameters (flow control). Does this matter for FW updating, I think no.
So when I run the Updater App, this is the connected screen
http://gyazo.com/96ba4284a6fb610a61036cca799af583Then it talks for a few, and I get a Verify Failed error (see screen cap below)
http://gyazo.com/36c9129b6185b599ac08357ff64f7cb4I till try some of the other FW updating options. Do I need to buy a programmer to push FW to a TinyG?
- This topic was modified 9 years, 5 months ago by akfreak.
June 26, 2015 at 3:57 pm #7880cmcgrath5035ModeratorThomas – Lets continue on the CP Community, since you and Kurt ( and probably others) have the same issues there.
July 10, 2015 at 11:32 am #7966AndrakondraMemberHello,
I need help with updater too.
I purchased Tinyg v8 controller recently. Made all connections to my router.
Board worked correctly for one day and then it started to stop in the middle of the work, so I decided to update the firmware.
Downloaded last version of the updater, started update to master 380.08 version. The update started and seemed to be finished. And from this point the board is not accessible not to Chilipeppr and not to Updater.
Now I only hear the sound when usb is connected.What can I do to bring the board back to work?
(As I understand I need now to purchase in addition to my new board original AVRisp mk2 programmer 🙁 and the price of this unit is close to new tinyg board… so I don’t know what to do)
Thanks in advance for any help.
Dan.
P.S. Picture of current attempt to reupdate the board.
http://i.gyazo.com/44003fb5da2d3463bcb02aeb13bf1c5b.pngJuly 10, 2015 at 12:48 pm #7969cmcgrath5035ModeratorDo you know what version you were upgrading from?
When you hit reset on the tinyG, does the Spin/Dir led flash one per second or so For 5 seconds or so(sorry, away from my tinyG, going from memory)?
That is the bootloader running (good), while the led is flashing, the bootloader will accept a connection from Avrdude.You should use the Avrdude method, outlined here:
Additionally, I use the “-e” option, discussed here:
You should flash with Edge release 440.14, NOT 380.08.
- This reply was modified 9 years, 4 months ago by cmcgrath5035.
July 10, 2015 at 2:17 pm #7972AndrakondraMemberThanks for reply,
The Spin/Dir is flashing,
Already tried the avrdude method (with 440.14 version)
I don’t have an expensive programmer board, I have 2 simple ones (Usbtinyisp and usbasp) so I tried them.For both of them I disabled Vcc output and used this schematics to protect 3.3 tinyg logic inputs.
http://i.gyazo.com/ed2418484edd1f843a237eaeefe58020.pngBoth programmersare giving the same result (sometimes with some small variations)
http://i.gyazo.com/fb9fdc771276cbb07aed31c3ac1b585d.png*Connections and scematic checked at least 10 times. Flat wires are checked and other wires in the logic level converter are very short so there are no possibility of a signal loss. All the parts and breadboard are completely new.
- This reply was modified 9 years, 4 months ago by Andrakondra.
July 11, 2015 at 4:49 pm #7974cmcgrath5035ModeratorI’m a bit confused, the Avrdude method does not use a programmer, it sends the file over USB if initiated correctly while Spin/Dir flashing(accepting connections from Avrdude.
Are you saying Avrdude method did not work either?
What OS and what version of avrdude do you have?
July 12, 2015 at 4:20 pm #7987AndrakondraMemberHello,
Sorry for confusion, I will explain step by step from the beginning.
The first problem was: after configuration and calibration the controller started to stop in the middle of the work. After resetting started to work again.
So I wanted to update the firmware using Updater ver 0.5 to solve the problem.
(System is Windows 7 x64bit)Steps:
1. Trying to use last version of updater – updating to version 440.142. Updating process starts and seem to be complete.
3. After using the updater the board becomes unresponsive to coolterm, Chillipepr, and to updater.
4. Trying the Avrdude metod (without programmer) – result is … no result, many error lines in avrdude.
5. Trying to add -E function, no success. Board still non responsive.
6. Trying to use updater again – Verification error, lookup button doesn’t show the version number.
***(of course in the process restarting the computer, reinstalling drivers etc, using different computer to be sure there no problem with computer itself)
7. Getting to plan B with direct chip programming .
8. Trying to use Usbtinyisp and usbasp (witout Vcc output to tinyg and with logic level converter)
9. No sucsess.
10. Starting to write here 🙂
——————————————————————————-
11. Today I tried once again the avrdude (without programmer)12. Some sort of success – board became responsive for Chillipepr with firmware version 380.08 (if updating to 440.14 with avrdude board is not responsive)
13. Trying to update from 380 to 440 with updater instead of avrdude – works.
14. Board becomes responsive to Chillipepr until I hit first command (like Jog x) and then board is offline.
15. Chillipepr gives advice to update to 440.15
16. Updating with avrdude to 440.15
17. Board responsive for some short time now (only in chillipepr) when I try to enter settings in chillipepr (axis and motors) and hit Save, the board gets offline (resetting the board, resetting the JSON, and again it works for some time).
Still not responsive to Coolterm.
So those are steps for now.
Thanks for help.July 12, 2015 at 10:45 pm #7988cmcgrath5035ModeratorHmmm, wild ride.
Particularly strange that not responsive CoolTerm, that is a very basic interface.
Update to 440.15 was not absolutely necessary, but OK to stay there.My current guess is that you have some limit switch issues that stop your machine(maybe).
So you see fast flashing of Spin/Dir when the machine stops?Try to post your parameter set (results of a $$) to a cloud drive so we can have a look. Here is a how to:
July 13, 2015 at 6:25 am #7989cmcgrath5035ModeratorAnother thought – are you sure that when you start up Chilipeppr, you are choosing the tinyG buffer manager option in the SPJS widget(lower right) for your connection?
That of course would have nothing to do with CoolTerm.
Also, a reminder to be sure SPJS is not still running when you exit CP and try CoolTerm or avrdude from command line.
You are running Windows – use Alt-Ctl-Del to open the Task Manager to double check. SPJS can be restarted as a background process by a restart of SPJS.July 13, 2015 at 6:25 pm #7994Larry DeackMemberI’m having similar problems with TWO boards as No. 17) above. I can jog and send G code but save setting stalls with dialog still open, appears to save but the board goes dead until reboot. Buffer seems to load slowly when connecting in Chilipeppr and stalls during save.
One worked fine a week ago when I last had it running. The other is brand new. I can connect with coolterm and change things but even though I change $1tr= to any value and it shows that value with $m or $$ the motor still acts like it’s set to something else and moves way too far for G0 X.1.
I upgraded the old board to 440.15 and left the new one as is. I thought I was doing something wrong but judging from the above post I’m guessing it’s no me, this time. 🙂 This is not good as we have a couple of CNC machines we made for other folks by convincing them this is as reliable as our Mach3 run machine.
July 13, 2015 at 10:35 pm #7996cmcgrath5035ModeratorI can jog and send G code but save setting stalls with dialog still open, appears to save but the board goes dead until reboot. Buffer seems to load slowly when connecting in Chilipeppr and stalls during save.
The behavior you describe here would suggest a failure of the tinyG config widget to receive a success acknowledgement while writing the parameter set to tinyG.
But then you have the same issue with Coolterm, so perhaps CP is not involved.
Anything change on your PC OS? Perhaps a driver update or, or?
Perchance a bad USB cable?July 14, 2015 at 12:23 pm #7999Larry DeackMemberNothing changed that I can tell other than when I logged into Chilipper and it asked for the .15 upgrade, which I did but it did not help. I need to do more work on them do narrow it down. Already tried two different boards and two USB cables, both worked fine before. I was hoping you knew something because of the similarity to the other guy with the board going down after saving in Chilipeppr, buffer frozen. It also seems like when it connects the buffer takes longer to show “ready”. Thanks for the quick response. It’s a bit frustrating at this point.
July 14, 2015 at 2:42 pm #8004jorgeMemberhaveing similar issues, any news on this?
July 15, 2015 at 9:19 am #8006cmcgrath5035ModeratorI have bumped it over to the CP side for a look
July 15, 2015 at 1:55 pm #8011travelphotogMemberAlso having issues with the app not working. Hope we find ot more info and get it working shortly so the needed 440.15 can be flashed and the TinyG will be stable with Chilipeppr again.
-
AuthorPosts
- You must be logged in to reply to this topic.