Tags:
view all tags
Please log AMC13 test activity below, blog style (new entries at top) ---+++2012-05-24, rohlf Sucessfully updated Spartan firmware from v3 to v6 at point 5. This was accomplished remotely in Bat. 40 at CERN with AMC13Tool by first writting Spartan v6 to flash at 0x000000 (its old location) as if programming the Header, power cycling the AMC13 module with the NAT tool, reprogramming the flash Header (0x000000), Golden (0x100000), Spartan (0x200000), and Virtex (0x400000), and then issuing the software command to reconfigure from flash. ---+++2012-05-24, rohlf Update firmware in cDAQ lab at CERN using python software. Older software (now named amc13_python_backup-23-may2012) was used to program Spartan firmware v6 into 0x0, power cycle crate, program Header (0x000000), Golden (0x100000), Spartan (0x200000), and Virtex (0x400000) where in the process a bug was discovered in programming the header due to incorrect erase of a single page, power cycling again, and verifying the configuration. ---+++2012-04-27, hazen Install HCAL xDAQ 11.4.0 (as daqowner) per instructions: <pre> To install on a teststand (as daqowner) : wget http://cmshcalweb01.cern.ch/hcalsw/release/installDAQ_11_4_0.perl perl installDAQ_11_4_0.perl --mode=teststand ~daqowner/common/bin/pickRelease.sh (choose 11.4.0) You can make a code-development area on a teststand or USC using perl installDAQ_11_4_0.perl --mode=[teststand|usc] --ownsource=${HOME}/src/11_4_0 --packages=hcalUpgrade --cvsuser=[your afs id] You can list multiple packages, separated by commas. </pre> ---+++2012-01-10, hazen Trying to program a new AMC13 MMC. Plug in to crate, connect JTAG ICE 3 cable to JTAG connector. Fails to program. Try to force power on with "pwr_on 9" (it's in AMC slot 4) but doesn't help. Note: <pre> pwr_on [fru #] pwr_off [fru #] where [fru #] is the fru number starting with 5 to16. That means if you want to switch on e.g. AMC2 use the command "pwr_on 6". </pre> Remembering wisdom of Tom Gorski: <ul> Maybe grasping at straws here, but if you look at the reset circuit for the AVR on the MMC schematic page, you see that it is important for the IPMI_ENABLE# line to be driven low, in order to release reset. You didn't say what your power situation was to the card. If you had it in a rig with an MCH trying to talk to the card, then the IPMI_ENABLE# line would indeed be zero, and the FET would not be pulling reset low, and the problem is probably somewhere else. On the other hand, if you have the card in a rig with a dumb power supply, then AVR reset will be pulled low *unless* a shunt is installed at JMP4. Since reset goes to the JTAG connector you might be able to check this with a voltmeter. </ul> This should be taken care of by the uTCA backplane, no? Meanwhile, trying to program the thing in Wu's test fixture. Doesn't work. Checking to be sure jumpers are installed. *AHA* ... the required ECO (soldered wire) on the T3 board was missing. Now all is OK. One can indeed program the MMC on a new board in a MicroTCA crate. Another observation: an AMC won't power up fully without the front panel hardware installed, as the handle switch must be depressed for the negotiation with the MMC to complete. ---+++2011-12-06, heister cms2: SLC5 updated, installation fine tuned, PyChips and microHAL installed for the "daq" user, all tested and works ---+++2011-12-06, hazen Install 2nd NIC on cmssun2 (old Dell computer, Ubuntu 10.04 OS). Cable to AMC13 in uTCA crate. Install IPBus test firmware from Wu. Install PyChips. Works! (I think). Added [[http://bucms.bu.edu/twiki/bin/view/BUCMSPublic/AMC13FlashProgramming][AMC13FlashProgramming]] page. ---+++2011-12-02, hazen Started this log. One dead NAT-MCH at Boston. 2nd NAT-MCH shipped from MN by Jeremy. Reset I/P address to 192.168.1.11 and connect to CMS1. One can now do =cms1> telnet 192.168.1.11=. But, this MCH has firmware v2.0 which doesn't work with AMC13 (symptom is both red/green LEDs blink forever on AMC13 with MMC firmware V1.2). Updating MCH firmware to V2.10 received from NAT on 9/20/11. Briefly, the procedure is: <pre> unzip the e-mail attachement somewhere copy the "bin" file to /tftpboot/mch on cms1.bu.edu connect to the MCH using the USB console and type "update_firmware" and follow the prompts type "reboot" to load the new firmware </pre> It works! Now the AMC13 seems to be up and running with the MCH. -- Main.EricHazen - 02 Dec 2011
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r163
|
r12
<
r11
<
r10
<
r9
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r10 - 26 May 2012
-
JimRohlf
Home
Site map
BUCMSPublic web
Main web
Sandbox web
TWiki web
Main Web
Users
Groups
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Register User
Edit
Attach
Copyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback