 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 : CPU exception #7 at address 0x9D02EF05...
Page 1 of 2   |
|||||
| Author | Message | ||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9755 |
This seems to happen when I try to VAR SAVE. Anyone got any ideas? The code falls over with the same error, in the line of the code above, when I try to save the VOLUME variable with VAR SAVE. If I END or comment that VAR SAVE line out, the code proceeds to the next part of code as it should. MMBASIC version 5.0501 on a 170 Micromite 44-pin chip. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9755 |
Seems to be a problem:  I think I am using the latest MMBASIC, but I will check. Smoke makes things work. When the smoke gets out, it stops! |
||||
| PeterB Guru  Joined: 05/02/2015 Location: AustraliaPosts: 655 |
G'Day Grogster That is the original VAR SAVE problem from a couple of months ago. It is caused by V5.05.01 Peter EDIT The original was VAR RESTORE I think but VAR SAVE was part of it. P |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9755 |
Oh, so I must have an outdated MMBASIC then. There are so many to keep track of!  Thanks, I will update. Smoke makes things work. When the smoke gets out, it stops! |
||||
| PeterB Guru Joined: 05/02/2015 Location: AustraliaPosts: 655 |
As you say, "there are so many to keep track of" so what is the latest and does it fix the above problem? Peter |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9755 |
Well, according to Geoff's website, 5.0501 IS the latest. So that means we still have a problem with VAR SAVE.... Smoke makes things work. When the smoke gets out, it stops! |
||||
| PeterB Guru Joined: 05/02/2015 Location: AustraliaPosts: 655 |
At the time I was trying to sort it all out, you supplied me with V5.04.08 which did the trick and made a bloke in the UK very happy. Can't remember his name  Peter |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9755 |
Yeah, I seem to vaguely remember that whole issue now, so I will downgrade and see if the problem goes away. I will keep the thread updated.  Smoke makes things work. When the smoke gets out, it stops! |
||||
Turbo46 Guru Joined: 24/12/2017 Location: AustraliaPosts: 1646 |
PeterB and Grogster, PeterB's problem was different, it required a freshly programmed chip and OPTION AUTORUN ON before a VAR RESTORE. If a NEW was issued before the program was run the error is eliminated. It did not occur if MMEdit was used to load the program because as part of the download it issues a NEW command. The error it gave was: Error: Variable name see here, it may be related but it is different. Bill Keep safe. Live long and prosper. |
||||
| PeterB Guru Joined: 05/02/2015 Location: AustraliaPosts: 655 |
Sorry Bill but it is the same problem. If you read through the early posts from Jan 24 you will find reference to Grogsters problem. It got lost in the following discussion. That problem is going to take me to my grave. Peter |
||||
| Turbo46 Guru Joined: 24/12/2017 Location: AustraliaPosts: 1646 |
No, I'm sorry Peter. I'd forgotten about Panky's error it did get a bit lost. It's a bit strange because MMEdit hid your problem from me but Grogster is using MMEdit by the look of his listing and it (or a different form of it) is still occurring for him. Bill Keep safe. Live long and prosper. |
||||
| PeterB Guru Joined: 05/02/2015 Location: AustraliaPosts: 655 |
That, MMEDIT, worried me. Peter |
||||
disco4now Guru Joined: 18/12/2014 Location: AustraliaPosts: 1044 |
Grogster, If you comment out the line above the VAR SAVE does it make any difference.i.e Text mm.hres/2,165,STR$(VOLUME),CM,2,1,rgb(Green) I am thinking along the lines of the text to the LCD is written in the background, so might be still happening and the VAR SAVE sort of interrupting it. Gerry F4 H7FotSF4xGT |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10572 |
All graphics commands are blocking and complete before the next statement. The only non-blocking command is PRINT so it is worth trying removing that statement. Where in the program is VOLUME defined? Make sure it is DIMmed at the top of the main program |
||||
| Turbo46 Guru Joined: 24/12/2017 Location: AustraliaPosts: 1646 |
I'd forgotten also that I had trouble with Com2 messages that were corrupted by a VAR SAVE command. Geoff wrote: I wouldn't have thought this would cause an exception error - but then I wouldn't know either. Maybe a pause after the VAR SAVE is worth a go? Bill Keep safe. Live long and prosper. |
||||
| JohnS Guru Joined: 18/11/2011 Location: United KingdomPosts: 4133 |
I suppose this means the h/w watchdog could be used as well. John |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9755 |
VOLUME is DIM'ed as an Integer at the top of the code - before the main loop starts. VOLUME defined as an integer inside the SELECT CASE routine. I use MMEDIT to write the code, but I use GFXterm to copy the code across - I don't use the RUN button in MMEDIT. This is just how I have come to do it. EDIT: I get the code to where I want it in MMEDIT, then CTRL-A copy-all, right-click/Copy. Go to GFXterm window, type AUTOSAVE, then paste from clipboard. I commented out the PRINT line directly below the VAR SAVE - Still get the same exception. The fact that once the processor has restarted, if I just define any variable at the command prompt and then try to save it(as in the GIF image I added), this also generates the same error suggests something is wrong.... EDIT: Like this.....  Smoke makes things work. When the smoke gets out, it stops! |
||||
| PeterB Guru Joined: 05/02/2015 Location: AustraliaPosts: 655 |
Good morning All Does that mean GFXterm modifies the code and deletes NEW? Geoff's cure was start with NEW if I remember correctly. Peter |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9755 |
My GUESS is that AUTOSAVE performs a NEW, but until that is confirmed, that is just my assumption. I will try loading the code again, but issuing NEW first before the AUTOSAVE. I plan to down-grade back to 5.04.08 which has been rock-solid, and see if the problem goes away. I will do that later today to allow for any more new suggestions members might have for me to try. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Turbo46 Guru Joined: 24/12/2017 Location: AustraliaPosts: 1646 |
When you transfer a program with MMEdit it interacts with the Micromite. Stops the program if running (^C I suppose), sends a "NEW" command and transfers the program using XMODEM. Maybe more - I don't know. I've not used GFXterm but I doubt that it modifies the program. @Grogster, Maybe if you try MMEdit to transfer your program you may avoid the problem. If it is the same as that which caused Peter's then hopefully Geoff will fix it in the next version. Bill Keep safe. Live long and prosper. |
||||
| Page 1 of 2 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
