Mantis Bug Tracker

View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000061FirmwareInit & Configpublic2008-11-16 15:032011-06-28 13:04
Assigned ToFred 
PlatformOSOS Version
Product Version0.0.17-SpudEchoes 
Target VersionFutureFixed in Version 
Summary0000061: Go Through ALL ISR Code And Check For References To TablesA-D RAM Locations
DescriptionI've realised the potential for issues reading from that global ram space from an ISR while the math routine has the RPAGE value swapped out. I need to go through all ISR code and ensure there are no references to that present there and keep it that way into the future.
TagsNo tags attached.
Issue TypeTask
Risk of Breakagemedium
Attached Files

- Relationships
child of 0000011assignedFred Define And Reorganise Header Structure 

-  Notes
User avatar (0000095)
Fred (administrator)
2008-11-25 13:38

This has been done, however the next step is to remove the references to these items from headers above the ISRs such that it can't happen in future. This task can stay open until that is done.
User avatar (0000186)
Fred (administrator)
2011-06-15 11:31

Or make access to them through a function that also sets and restores page in a consistent way such that they CAN be used for this as it *might* be nice for the rpm dependent dynamic acceleration tolerance stuff in 0000118
User avatar (0000206)
Fred (administrator)
2011-06-28 13:04

Risk updated. I'm favouring accessing through functions at this time. For things requiring direct access, for speed, copies of settings data could be made at init time, and after serial writes, possibly through some callback mechanism or similar. Worth considering.

Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker