by i-Bot » Wed Aug 06, 2008 8:22 am
by i-Bot
Wed Aug 06, 2008 8:22 am
I have not further developed the code, though I have used parts of it elsewhere and found some of the bugs. I did not make a structured testing and fixing though.
The bugs are in the bits of code I used to make the C calling interface. Usually where I changed registers to reflect the calling and return values. I also changed some used registers to avoid registers that should be preserved. The core of the code is orginal, so I would not expect errors deep into the routines.
If you want to make a structured testing, I can help you to fix any parts. I just don't have time to test and fix it all.
The reason I stopped with these routines was that although they have the function of the existing C3024, they also have many of the limitations. This is mainly in the large amount of time taken in the motion interrupt routine, and the heavy processor load of some of the background functions. These mean that I still could not use the serial port on interrupt.
I have not further developed the code, though I have used parts of it elsewhere and found some of the bugs. I did not make a structured testing and fixing though.
The bugs are in the bits of code I used to make the C calling interface. Usually where I changed registers to reflect the calling and return values. I also changed some used registers to avoid registers that should be preserved. The core of the code is orginal, so I would not expect errors deep into the routines.
If you want to make a structured testing, I can help you to fix any parts. I just don't have time to test and fix it all.
The reason I stopped with these routines was that although they have the function of the existing C3024, they also have many of the limitations. This is mainly in the large amount of time taken in the motion interrupt routine, and the heavy processor load of some of the background functions. These mean that I still could not use the serial port on interrupt.