|Anonymous | Login | Signup for a new account||2019-05-24 13:57 UTC|
|Main | My View | View Issues | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000069||Firmware||General Features||public||2008-11-25 11:47||2014-03-27 03:46|
|Target Version||0.2.0||Fixed in Version|
|Summary||0000069: Add Useful COP Monitor Function|
|Description||Add a COP ISR handler that packages up the registers states, sends them out using the serial code and when done resets the device.|
This shouldn't take a significant amount of time at all, but is low priority.
An addition to this at a later date could be to fill the free code space with jump instructions to run this code, however the chance of hitting such space is currently around 50% and dropping daily. It will approach zero in the medium term, so I deem that change ineffectual and a waste of time. (nice idea for a lightweight unreliable app though).
|Tags||No tags attached.|
|FirmwareVersion||unknown at this time, but current HEAD as of today|
|Issue Type||New Feature|
|Risk of Breakage||medium|
More info on this issue here ^
Also, it is unlikely that we have access to this interrupt with the standard bootloader, however we will in future modify the boot loader to pass these interrupt types back to us so the engine keeps running except for genuine forced resets.
vector02: .word ColdStart ; /* vector 02 */
vector01: .word uvector01 ; /* vector 01 */
vector00: .word ColdStart ; /* Reset vector */
So currently COP resets are swallowed and identical to the genuine resets once they arrive at the firmware. It'd be quite nice to record the source and pass them on faithfully to the firmware so they could be handled there.
|This issue is now to simply add a normal COP reset as per the above linked thread. Fancy recognition of COP reset requires SM work and firmware work to be in harmony and fairly sophisticated.|
|Copyright © 2000 - 2011 MantisBT Group|