PASD Improvement
pjv
Posts: 1,903
Hello Andy;
I am using your debugger, and find it a very useful tool, so thanks for that.
I do have a requirement where I wish to park certain pieces of assembler code at specific cog memory locations, and I do that with inserting a group of zero longs in my code such as:
Code
instr
instr
Here instr
long 0[There-Here]
There instr
instr
/Code
and it seems that the debugger cannot handle such spaces. Could this possibly be fixed?
Also, I cannot seem to get the debugger to "remember" a change to the default font size setting eventhough I ask it to remember. Am I doing something wrong ?
Thanks for your help.
Cheers,
Peter (pjv)
I am using your debugger, and find it a very useful tool, so thanks for that.
I do have a requirement where I wish to park certain pieces of assembler code at specific cog memory locations, and I do that with inserting a group of zero longs in my code such as:
Code
instr
instr
Here instr
long 0[There-Here]
There instr
instr
/Code
and it seems that the debugger cannot handle such spaces. Could this possibly be fixed?
Also, I cannot seem to get the debugger to "remember" a change to the default font size setting eventhough I ask it to remember. Am I doing something wrong ?
Thanks for your help.
Cheers,
Peter (pjv)
Comments
PASD parses the source code only very rudimentary. All it does is to try to find out how many longs a source line occupies in the cog and use that number to match the source with the cog code read from the cog memory. There is no Assembler in PASD, so it does not know the values of "Here" and "There". In case of a "long" line it just counts the number of commas and adds 1 to get the number of longs for this source line. So maybe you can use some tricks like: to reserve a number of longs. But a calculation by PASD is not possible with the current way it works.
I have added the "Font size remembering" to my todo list, for the next updates, whenever this may bee
Andy
Cheers,
Peter