Difference between revisions of "Clock Card firmware"
From MCEWiki
(→Firmware) |
(→Latest Stable Release) |
||
| Line 1: | Line 1: | ||
== Latest Stable Release == | == Latest Stable Release == | ||
'''v 4.0.9 (cc_v04000009)''' | '''v 4.0.9 (cc_v04000009)''' | ||
| − | * | + | |
| − | * | + | Features: |
| − | * | + | * Header Version 6 |
| − | * | + | * Integrated a bug fix for the sram_ctrl block |
| − | * | + | * Integrated new all_cards block of code which was causing a synthesis warning in ModelSim |
| − | * | + | * Two new commands added: card_type, scratch. |
| − | * | + | Bugs: |
| + | * In fast DAS, if I try to issue ‘w cc led 1 2 3 … 58’, the MCE/ DAS will fail at the second command. | ||
| + | * Cards with no firmware loaded are treated as ‘not present’ and therefore replies come back as OK as oppose to ER. (comment added by MA) | ||
| + | * When PSUC is not present (or fails), rb psc psc_status comes back as OK with all entries as 0. (comment added by MA) | ||
| + | * fpga_temp readings are way off. | ||
| + | * Switching to Application Config sometimes fails and the red light comes up. | ||
| + | * If the FPGA on a card is not programmed, it does not report an error (it treats the card as the not-present card and therefore the error is masked). | ||
| + | * If PSUC is not present and not communicating, CC doesn't report error and instead reports RBOK | ||
== Firmware Links == | == Firmware Links == | ||
Revision as of 14:31, 14 July 2008
Latest Stable Release
v 4.0.9 (cc_v04000009)
Features:
- Header Version 6
- Integrated a bug fix for the sram_ctrl block
- Integrated new all_cards block of code which was causing a synthesis warning in ModelSim
- Two new commands added: card_type, scratch.
Bugs:
- In fast DAS, if I try to issue ‘w cc led 1 2 3 … 58’, the MCE/ DAS will fail at the second command.
- Cards with no firmware loaded are treated as ‘not present’ and therefore replies come back as OK as oppose to ER. (comment added by MA)
- When PSUC is not present (or fails), rb psc psc_status comes back as OK with all entries as 0. (comment added by MA)
- fpga_temp readings are way off.
- Switching to Application Config sometimes fails and the red light comes up.
- If the FPGA on a card is not programmed, it does not report an error (it treats the card as the not-present card and therefore the error is masked).
- If PSUC is not present and not communicating, CC doesn't report error and instead reports RBOK
