Difference between revisions of "Programming over Fibre"
From MCEWiki
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
= Using Remote Firmware Update = | = Using Remote Firmware Update = | ||
* Load Clock Card v5.0.6+ Firmware in the Clock Card Factory Configuration Device (.pof file). | * Load Clock Card v5.0.6+ Firmware in the Clock Card Factory Configuration Device (.pof file). | ||
Line 26: | Line 19: | ||
sudo ./jam -u -v -f100000 -aprogram -dDO_VERIFY=0 cc_rcd_jic.jam // For Programming EPCS64's (Step 2 of 2) | sudo ./jam -u -v -f100000 -aprogram -dDO_VERIFY=0 cc_rcd_jic.jam // For Programming EPCS64's (Step 2 of 2) | ||
− | = Remote Firmware Update Development Notes = | + | = Porting to DAS = |
+ | The following C-code will need to be ported to DAS to enable Remote Configuration. You will need to convert the MCE WB and RB commands in the code to use DAS libraries and compile the code with the included Makefile: | ||
+ | *[http://www.phas.ubc.ca/~scuba2/sc2mce/system/mce_jam/mce_jam_r16.zip MCE Jam Player -- SVN revision 16 (~/jp_25/mce_jam/trunk)]. | ||
+ | ** '''jam_mce.c''': contains low-level MCE routines used during programming | ||
+ | ** all other files should be fine. | ||
+ | * [[ Remote Firmware Update | How to use Remote Firmware Update]] | ||
+ | |||
+ | = Development Notes = | ||
* http://e-mode.phas.ubc.ca/intmcewiki/index.php/Remote_Firmware_Update | * http://e-mode.phas.ubc.ca/intmcewiki/index.php/Remote_Firmware_Update |
Revision as of 13:19, 21 June 2010
Using Remote Firmware Update
- Load Clock Card v5.0.6+ Firmware in the Clock Card Factory Configuration Device (.pof file).
- Clock Card firmware descriptions are available here: Clock Card (CC).
- Clock Card firmware is available here: http://www.phas.ubc.ca/~mce/mcedocs/firmware/.
- Flip the SW1p1 "BB_EN" Dip Switch on the Clock Card to 'OPEN'.
- On a MAS PC, get the version of JAM Player software from SVN that is compatible with the version of Clock Card firmware you just loaded in the Factory Configuration Device (i.e. SVN revision 16 is compatible with cc_v0500006).
cd ~/jp_25/mce_jam/trunk svn update -r16
- Compile the SVN software with the following commands:
make clean make
- The read_idcode.jam file is included in SVN as a test script to help you determine whether you have set up the system correctly.
sudo ./jam -u -v -f8000000 -aread_idcode read_idcode.jam // For Querying ID Codes
- If you can run the read_idcode script, then you are ready to re-configure FPGA's, EPC16's and EPCS64's. For these devices, you will need to generate .jam files that are specifically suited to your JTAG chain's topology. You will need Quartus II software to do this. Instructions on generating .jam files are here: MCE Programming File Conversions. If you do not have access to Quartus II software, send the output of the read_idcode.jam script to UBC, and configuration .jam files can be generated for you.
sudo ./jam -u -v -f800000 -aprogram -dDO_VERIFY=0 cc_xfpga_rc_pof.jam // For Programming EPC16's sudo ./jam -u -v -f8000000 -aconfigure cc_xfpga_rc_sof.jam // For Configuring FPGA's
- Note that programming an EPCS64 is a two-step process:
sudo ./jam -u -v -f8000000 -aconfigure cc_rcd_jic.jam // For Programming EPCS64's (Step 1 of 2) sudo ./jam -u -v -f100000 -aprogram -dDO_VERIFY=0 cc_rcd_jic.jam // For Programming EPCS64's (Step 2 of 2)
Porting to DAS
The following C-code will need to be ported to DAS to enable Remote Configuration. You will need to convert the MCE WB and RB commands in the code to use DAS libraries and compile the code with the included Makefile:
- MCE Jam Player -- SVN revision 16 (~/jp_25/mce_jam/trunk).
- jam_mce.c: contains low-level MCE routines used during programming
- all other files should be fine.
- How to use Remote Firmware Update