Difference between revisions of "Clock Card firmware"
From MCEWiki
Line 1: | Line 1: | ||
== Firmware Catalog & To Do List == | == Firmware Catalog & To Do List == | ||
http://www.phas.ubc.ca/~mce/mcedocs/firmware/cc_fpga_programming_file_catalogue.pdf | http://www.phas.ubc.ca/~mce/mcedocs/firmware/cc_fpga_programming_file_catalogue.pdf | ||
+ | |||
+ | |||
+ | == Firmware .sof & .pof Files == | ||
+ | http://www.phas.ubc.ca/~mce/mcedocs/firmware/ | ||
Revision as of 10:46, 13 June 2008
Contents
Firmware Catalog & To Do List
http://www.phas.ubc.ca/~mce/mcedocs/firmware/cc_fpga_programming_file_catalogue.pdf
Firmware .sof & .pof Files
http://www.phas.ubc.ca/~mce/mcedocs/firmware/
Bugs in the Latest Firmware Revision (4.0.9)
- Bug 1: In fast DAS, if I try to issue ‘w cc led 1 2 3 … 58’, the MCE/ DAS will fail at the second command.
- Bug 2: 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)
- Bug 3: When PSUC is not present (or fails), rb psc psc_status comes back as OK with all entries as 0. (comment added by MA)
- Bug 4: fpga_temp readings are way off.
- Bug 5: Switching to Application Config sometimes fails and the red light comes up.
- Bug 6: 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).
- Bug 7: If PSUC is not present and not communicating, CC doesn't report error and instead reports RBOK