fw_patch_readme.txt Driver File Contents (framelink_fw_v3_0.zip)

***** Framelink FW Revision 3.0 Patch ***********************************************

This patch will update the FPGA firmware embedded on the Framelink card.

-- changes carried over from patch 1_E
Firmware:	Resolves several issues related to CameraLink serial 
		communications, random 'DMA Timeout' errors ( error 0xff and 
		0x54F ), horizontal pixel jitter, the appearance of snow ( white/
		black ) dots and the occurance of split-images.

-- changes carried over from from patch 1_F
Firmware:	Increases the maximum frame size supported from 2 Mega-pixels to
		8 Mega-pixels.

-- changes carried over from patch 2_0
Firmware:	Changed order of bytes DMA'ed in RGB mode so that only a memory
		copy is required by the software. This improves the performance.

-- changes carried over from patch 2_1
Firmware:	Changed video capture engine to accomodate small FVAL blanking
		period. This prevents extra data from being prepended to the 
		frame buffer.

-- changes carried over from patch 2_2
Firmware:	Changed packing of pixels in 8 bit mode. This improves the DMA
		performance.

-- changes carried over from patch 2_3
Firmware:	Change revoked........no change made in this revision.

-- changes carried over from patch 2_4
Firmware:	Corrected a bug where first frame received by card was not DMA'ed
		into system memory until start of receipt of second frame.
		Also, resolved an anamoly with Panasonic Toughbook laptops where the
		laptop generates a glitch on the Cardbus RST# signal. This glitch
		causes the FrameLink card to get reset. This version of the firmware
		filters out the glitch.

-- changes carried over from patch 2_5
Firmware:	Added line scan support.

-- changes carried over from patch 2_6
Firmware:	Corrected a race condition between a slow camera clock and 66 MHz
		local clock which caused last buffer in a frame to be prepended to
		the next frame. This was discovered with the Siemens camera.

-- changes carried over from in patch 2_7
Firmware:	Fixed a problem where if the last pixel in the frame ended on a 
		1024 byte ( buffer ) boundary then the last buffer ( 1024 bytes )
		in the image would be replaced with the previous buffer.
		Fixed UART 16x clock BAUD rate generator, caused 115.2 Kbps to be
		off. 

-- changes carried over from patch 2_8
Firmware:	Prevent wrap around in SDRAM if frame size exceeds SDRAM size. This
		was required for Imperx 11 Megapixel camera.

-- changes carried over from patch 2_9
Firmware:	Added ability to invert FVAL, LVAL and DVAL strobes

-- changes carried over from patch 2_10
Firmware:	Added 16 character receive FIFO to UART. This was required for 
		SU camera operating at 115.2 Kbps.

-- changes carried over from patch 2_11
Firmware:	Solved problem where if frame ends just after a buffer is closed but before
		it was written into SDRAM, causes last buffer in the image to be replaced with 
		previous buffer.

-- changes carried over from patch 2_12
Firmware:	Solved problem where Tx characters were being overwritten in UART due to 
		race condition in interrupt processing

-- changes carried over from patch 2_13
Firmware:	Fixed random framing anamoly related to fix in v2.11

-- changes carried over from patch 2_14
Firmware:	Fixed DMA inactive occuring due to interrupt conflicts

-- changes carried over from patch 2_15
Firmware:	Added CC(1:4) pulses generator

-- changes made in patch 3_0
Firmware:	Fixed DMA inactive occuring after card insertion or reboot due to
--		SDRAM initialization timing race condition

**********************************************************************************

FPGA programming files:

Jampci.exe 		- a utility that will reprogram the Framelink card's FPGA
vceclcb_rev_3_0.jam 	- the FPGA firmware programming source file
framelink_patch_3_0.bat - the batch file for programming the Framelink FPGA
windrvr.sys		- JamPCI required driver
wdpnp.sys		- JamPCI required driver
loadsys.bat		- the batch file that installs JamPCI drivers
wdreg.exe		- program that registers JamPCI drivers


**********************************************************************************

NOTE: THIS FIRMWARE REQUIRES THAT YOU RUN WITH DRIVER V2.13.2 OR GREATER!

**********************************************************************************


Procedure:

To reprogram FrameLink FPGA firmware: 

1 - create a new folder and unzip all files into this folder
2 - if you haven't previously installed the JamPCI drivers, then using file manager
    or explore, invoke ( double left click ) the loadsys.bat file
3 - wait until "Press any key to continue . . ." message appears
4 - press any key to exit batch file
5 - insert the FrameLink card into the laptop....note that is is important that you 
    install the FrameLink card into the Cardbus slot in which it was placed during
    the original driver installation.

NOTE: DO NOT POWER DOWN OR REMOVE CARD WHILE PROGRAMMING IS IN PROGRESS!

6 - using file manager or explore, invoke ( double left click ) the
    'framelink_patch_3_0.bat' file
7 - wait until "Press any key to continue . . ." message appears
8 - if line above it reads "Exit code = 0...Success" then continue with step 9,
    otherwise contact techsupport@imperx.com or call (561)-989-0006 x106
9 - press any key to exit batch file
10- you must remove and then reinstall the FrameLink card for changes to take effect

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web4, load: 0.91