Difference between revisions of "MCE firmware"
From MCEWiki
| Line 18: | Line 18: | ||
It is good practice to do an MCE reset ("mce_reset" command or "mce_reset_clean" shell script) after any firmware upgrades or power cycles. | It is good practice to do an MCE reset ("mce_reset" command or "mce_reset_clean" shell script) after any firmware upgrades or power cycles. | ||
| − | == | + | == Firmware source code and its version-control system (CVS) == |
| + | All that you need to know about logging into our CVS repository can be found here: | ||
| + | * [[ CVS Firmware Repository ]] | ||
| + | |||
We decided (sadly) NOT to migrate from CVS to SVN, if we ever do here are some guidelines: | We decided (sadly) NOT to migrate from CVS to SVN, if we ever do here are some guidelines: | ||
| − | svn manual: http://svnbook.red-bean.com/en/1. | + | svn manual: http://svnbook.red-bean.com/en/1.4/ |
* [[ Firmware Accessing the svn repository | Accessing the svn repository ]] | * [[ Firmware Accessing the svn repository | Accessing the svn repository ]] | ||
Revision as of 14:21, 16 June 2008
Special Features
- Flux jumping
- Raw-mode readout
- High rate acquisition
- Fast SQ2 Feedback and TES Biasing with an Address Card
Procedures for keeping DAS/MCE healthy during firmware upgrades, power cycles, etc.
It is good practice to do an MCE reset ("mce_reset" command or "mce_reset_clean" shell script) after any firmware upgrades or power cycles.
Firmware source code and its version-control system (CVS)
All that you need to know about logging into our CVS repository can be found here:
We decided (sadly) NOT to migrate from CVS to SVN, if we ever do here are some guidelines:
svn manual: http://svnbook.red-bean.com/en/1.4/
- Accessing the svn repository
- svn commit guidelines
- svn basic operations
