 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Var Save issue...
| Author | Message | ||||
| viscomjim Guru  Joined: 08/01/2014 Location: United StatesPosts: 925 |
Has the Var Save issue been fixed? If not, which is the latest firmware that does not have this problem. I have a few boards going out where the end user does not have access to the console so they can not do the var clear on the command line. Thanks! |
||||
Quazee137 Guru Joined: 07/08/2016 Location: United StatesPosts: 600 |
I had a problem with Var Save on a test mite until I saved program did a NEW and reloaded. Then its been working fine. Not sure why it broke. At first I though it may have been because is it one of my first 170's and its gone through a lot of flashing. Using 5.0501 Took a 2nd mite and went through the same paces I did with the 1st but can not get Var Save to fail. With the 1st one it would not get past Var restore with out it getting cpu restart. Even tried on error skip but luck. |
||||
Turbo46 Guru Joined: 24/12/2017 Location: AustraliaPosts: 1646 |
If you issue a NEW command after loading the MMBasic firmware the VAR SAVE problem will not occur. If you use MMEdit to load your program then you will never have the problem because MMEdit issues a NEW command as part of the download. It will not re-occur after a reset. Bill Keep safe. Live long and prosper. |
||||
Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3308 |
That bug will be fixed in the next beta. It is low priority because it has an easy workaround (a NEW after flashing the firmware). Geoff Graham - http://geoffg.net |
||||
| viscomjim Guru Joined: 08/01/2014 Location: United StatesPosts: 925 |
Ah! New works perfectly! Thanks for the input! Long live mmbasic! |
||||
| PeterB Guru Joined: 05/02/2015 Location: AustraliaPosts: 655 |
Good morning Viscomjim et al You did ask what is the firmware that does not have the problem. These young blokes never listen. V5.05.01 has the bug. V5.04.08 is rock solid and still used by some people. I think V5.04.09 is good but I have never used it. Peter |
||||
| Turbo46 Guru Joined: 24/12/2017 Location: AustraliaPosts: 1646 |
Good morning blokes of all ages, I learned during my working life, when seeking information from other departments, that if I asked more than one question in one email then 9 times out of 10 only one would be answered. I found it less frustrating to only ask one question at a time. Sorry Jim and thanks Peter - I didn't know the answer to the second question anyway. Bill Edit: Sorry to omit sheilas of all ages. Keep safe. Live long and prosper. |
||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9755 |
PeterB is not being curt, he is just being sarcastic when he said: "These young blokes never listen." He forgot to add the smilies again.  I got caught by one of his similar replies to me in another thread, and with no smilies, I thought he was angry at me. Haha! Gotcha again, Pete!  I concur with PeterB - 5.0408 was the last stable release that did not have the VAR SAVE issue. But as you can issue a NEW command on the later firmware BEFORE loading and running your code, that also gets around the problem as stated. The only real problem, is if you use 5.0501 as the basis of your project, and then READ the entire chip back with a PK3 and the Microchip IPE, so you have a self-contained HEX file. When you program THAT into your project - complete with the autorun set etc, this will promptly fall over with the VAR SAVE or VAR RESTORE error when first run. I THINK you can get around THAT by making sure that you have issued a NEW, then load your current code, THEN read the chip into a self-contained HEX file. If you then program THAT, I would expect that should also get around the issue, but I have not actually put that to the test myself. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Turbo46 Guru Joined: 24/12/2017 Location: AustraliaPosts: 1646 |
At 73 I don't take offence at being called a young bloke.  I expect that you are correct Grogster. If you issue a NEW and prove the program works then reading the whole chip would clone the working firmware and should be OK. Bill Keep safe. Live long and prosper. |
||||
| PeterB Guru Joined: 05/02/2015 Location: AustraliaPosts: 655 |
Good morning / afternoon Grogster I'm sorry that my humor confuses you. Most of my attempts at humor are meant to be self depreciating and I did used to say to the young blokes "I've taught you all I know and you still know nuthin"! however, "you young bloke never listen" is just me saying "I wish I was still young". I hope most blokes just say "silly old f..rt".  It is interesting that people still trip over this problem. Peter edit. The next time I say "you young blokes never listen" perhaps you could respond with "we would if you had anything worth saying" That's the response I would have got back when I worked with all sorts of repulsive people. And we are still mates. |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
