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.
PhilTilson Newbie Joined: 15/11/2015 Location: United KingdomPosts: 35
Posted: 01:09pm 15 Nov 2015
Copy link to clipboard
Print this post
Hi -
As a newcomer to the MicroMite I have to express my appreciation and admiration for Geoff for creating this resource. It has made my life so very much easier!
However, I do have one problem. On several occasions now, having successfully saved - and used - a number of routines to Library, I have found them suddenly gone without trace. Doing a Library List shows nothing stored and a Memory command shows no memory allocated to Library.
If I then load the routines again and re-store them with a Library Save, everything works fine - until the next time. Is there something obvious that I may be doing wrongly, or is this a problem that anyone else has experienced?
Phil
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9643
Posted: 02:57pm 15 Nov 2015
Copy link to clipboard
Print this post
WELCOME!
I use the library for the stereo project I am developing with jman, and it is being used constantly for the fonts, and I have never had a single glitch since the fonts were saved in the library, and it's probably been more then 100 power cycles now.
Which MM are you using?
170 or 470?
If 470 module, it has on-board regulation and supervisory, so your power should be pretty good. If you have hooked up your own circuit and PSU, perhaps there is something not quite right on the PSU - the 470 especially is very sensitive to the PSU, and it must be clean and stable, or odd things can and do happen. The 170 is not such an issue, as it runs slower. There have been reports of odd things happening with the 470 over the months of development, hence the addition of the supervisory IC on MCLR to ensure a clean startup of the core.
Watching this thread with interest - we'll see what others say.Smoke makes things work. When the smoke gets out, it stops!
WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2948
Posted: 09:15pm 15 Nov 2015
Copy link to clipboard
Print this post
I have recently had some 'strange' behaviour with LIBRARY DELETE and LIBRARY SAVE on a 100pinner.
With an existing LIBRARY (that contained matherp's BackLight code i.e. code in 'continuos' use), whenever I do a LIBRARY DELETE (so I can update my library with a newer improved version) I get a CPU exception error message. I then perform a second LIBRARY DELETE to ensure all is wiped cleanly. Then I perform the LIBRARY SAVE with the 'newer' code which then works ok - so all as expected . . . .
However, I repeated the above several times as I continued to 'improve' the code. But on one occasion ALL my OPTIONS somehow got deleted!!! It was no problem to re-enter them all, but if it happened to me, then it is sure likely going to happen to others too.
Another time, I had several CFunctions/CSubs in the library, yet on just one occasion, all the 'CFunction numbers' got 'removed' from one of the CSub's (I noticed this when doing a LIBRARY LIST but thought let's just see what happens); so when that command got called, it just hung the MM+ with no way out. I had to re-flash the MM+ firmware. The end result was kind of expected, but the unknown is what actually caused the 'CSub numbers/code' to get wiped? The original code still contained them (I am using using MMEdit to keep 'master' versions of all my code') so it was definitely a 'strange' thing that happened here.
@PhilTilson - Is it always the 'same' library code that causes your issue? If so, then would you be able to post the code so that others can test it?
I will be playing with LIBRARY SAVE & DELETE a lot over the coming week so will highlight any other issues or 'patterns' that I come across for others to test.
WW
matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10406
Posted: 11:01pm 15 Nov 2015
Copy link to clipboard
Print this post
That is a feature
When you delete the library you delete the routine that is being called in the firmware's interrupt routine - hence the crash. To do this properly I should have provided a "turn-off" call to be used before deletion but as I assumed you wanted it permanently running didn't bother. It is possible that bad things could happen e.g. "ALL my OPTIONS somehow got deleted!!!" as a result but this is probably unrelated to Phil's problem depending on what was in his library.
This is what is supposed to happen. Any Cfunction when saved as a library will show as empty with library list - it saves memory by removing the ascii Basic code representation but the actual binary is still there in flash.Edited by matherp 2015-11-17
WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2948
Posted: 11:29pm 15 Nov 2015
Copy link to clipboard
Print this post
PhilTilson Newbie Joined: 15/11/2015 Location: United KingdomPosts: 35
Posted: 11:57pm 15 Nov 2015
Copy link to clipboard
Print this post
To answer a couple of questions that have been raised...
I am at the other end of the scale! I am using the 28-pin version of the 170 chip.
I could post the code, but there's quite a lot of it and it's nothing special - just user-defined functions - and all the routines perform perfectly when loaded.
The power is pretty well decoupled and seems stable.
I, too, will be interested to see if others have had any problems in this area.
Phil
MicroBlocks Guru Joined: 12/05/2012 Location: ThailandPosts: 2209
Posted: 04:55am 16 Nov 2015
Copy link to clipboard
Print this post
Are you using a breadboard?
Microblocks. Build with logic.
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.
Print this post
