Another odd error
Alan Adams (2486) 1125 posts |
I’m now getting the following error: Does it indicate there is a % sign in the title, or is it an unexpanded wildcard chracter – and given the headers below, WHY?
|
Steve Drain (222) 1620 posts |
AFAIK this means that the module chain is broken and the only resort is to reset the machine. Something has written to memory it should not have. ;-( It is not to do with the title of your particular module. The ‘%’ is normally used for instantiated module names, so it cannot be used in a title. |
Alan Adams (2486) 1125 posts |
Thanks. It seems to occur very early in the initialisation, so should be fairly easy to find. |
Alan Adams (2486) 1125 posts |
Now traced to unmatched stmfd and ldmfd pairs. The result was that R13 wasn’t the same when unstacking at the end of Initialise, so the stacked registers were altered too. Messy. |
Rick Murray (539) 13385 posts |
Whoa… You did that in module code and it didn’t stiff the machine solid? I’m impressed.
It’s why we use compilers these days. Writing in assembler means remembering all that rubbish. Which gets more fun if different things were stacked at different points, and it all has to be correctly unwound for every possible exit scenario. |
Alan Adams (2486) 1125 posts |
So we’re making progress. It now initialises and finalises almost correctly. Almost, because *help modules doesn’t show the module name or addresses, but does list the help string. *modules shows the module name in the same way as all the others.
Hmm, I’m not checking that – maybe I’m just lucky with the SWIs in use. Something else for tomorrow then.
|
Rick Murray (539) 13385 posts |
Module title string pointing to the wrong thing? |
Alan Adams (2486) 1125 posts |
|
Stuart Swales (8827) 1237 posts |
Better, but change “Show file system activity various ways” to “Blinker” |
Steve Drain (222) 1620 posts |
I think Alan may be following my style, which is to give ‘helpful’ help. This is idiosyncratic. ;-) |