Difference between revisions of "MCE firmware"
From MCEWiki
Line 3: | Line 3: | ||
* [[ MCE Untested features ]] | * [[ MCE Untested features ]] | ||
* [[ MCE bugs ]] | * [[ MCE bugs ]] | ||
+ | |||
== MCE How-To Guide == | == MCE How-To Guide == | ||
Line 9: | Line 10: | ||
* [[ High rate acquisition ]] | * [[ High rate acquisition ]] | ||
* [[ Fast SQ2 Feedback and TES Biasing with an Address Card ]] | * [[ Fast SQ2 Feedback and TES Biasing with an Address Card ]] | ||
+ | |||
== Procedures for keeping DAS/MCE healthy during firmware upgrades, power cycles, etc. == | == 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. | 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. | ||
+ | |||
== Hardware Peripherals == | == Hardware Peripherals == | ||
Line 17: | Line 20: | ||
* [[ USB Blaster ]] | * [[ USB Blaster ]] | ||
* [[ Sync Box ]] | * [[ Sync Box ]] | ||
+ | |||
== Software Tools == | == Software Tools == |
Revision as of 11:53, 18 June 2008
Contents
MCE Firmware
MCE How-To Guide
- 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.
Hardware Peripherals
Software Tools
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