1. Create and boot off a DOS bootable USB flash drive (or similar)
2. Copy the sas2flsh DOS utility to the drive
3. Copy both the IT firmware and the BIOS file to the same folder
   1. Firmware should be '2114it.bin'
   2. BIOS should be 'mptsas2.rom'
4. Use this command to erase the existing flash firmware and BIOS
   • sas2flsh -o -e 6
   • DO NOT REBOOT at this point. Rebooting would cause the HBA to cease functioning completely (RMA required).
5. Use this command to flash the new firmware and BIOS
   • sas2flsh -o -f 2114it.bin -b mptsas2.rom
6. After flashing is complete you can verify the version using this command.
   • sas2flsh -listall

If you get an error: “ERROR: Failed to initialize PAL. Exiting program.” it means your motherboard has option ROM limitations. The easiest solution is to use a different system. Alternately, you can use the UEFI installer (it is a different download from LSI website).

1. Boot UEFI Shell (press F11 on Supermicro boards to invoke boot menu, then select UEFI: Built-in EFI Shell)
2. Issue command 'mount fs1:' assuming fs1: was the USB flash drive (use map command to list the device tree) -- TIP #3: this command/step may not be needed if the EFI shell has already mapped the flash drive (usually fs0:)
3. Issue command 'fs1:' to change directory
4. The utility should be sas2flash.efi (get it from LSI website, UEFI installer), so use these commands to complete the flash process.
   1. sas2flash.efi -o -e 6
   2. sas2flash.efi -o -f 2114it.bin -b mptsas2.rom

For further reading, check SAS2Flash_ReferenceGuide.pdf found in the downloaded ZIP files from LSI. Alternatively here is another example case: http://brycv.com/blog/2012/flashing-it-firmware-to-lsi-sas9211-8i/

END

This article discusses 3 levels of intelligence for detecting Left Objects which could be a threat to public safety or an aid to identifying the original owner by jumping back to the video recording when the event was detected.
  
IQ-100 

• This is an entry level application and applies to empty space only and certainly not for any busy environment.  It can detect an object left in an empty scene up to a period which is shorter than the predefined Motion Retention time (MRT).  In case the object is blocked from the camera, the application will reset the timer and start counting again. In case we set the period to be longer than MRT, all left objects will be ignored. MRT pre-definition is required to eliminate various transient or illumination changes.
  

• For false alarm reduction, it requires the size of potential objects to be predefined. This helps to eliminate falling leaves on the ground, or a big dog lying down.  
  

• It can detect one object at a time. Other objects that are left at the same time would be ignored.
  
  

• IQ-140 can detect objects as small as 8*8 pixels and IQ-180 can detect very small objects of 4*4 pixels in busy scenes. The application needs to be told to expect the level of business of the scene and to relearn the scene if it has changed beyond a certain percentage. Default parameter is 50% for business of scene and an additional 10% change (that is 60% business) for triggering relearning of the scene.   These parameters are different for each site and tuning is essential to improve accuracy.  The point is that the application will take time to relearn the scene.  If the business level hits 70% in the meantime, the application will miss certain changes (including left objects). A message will be displayed on the screen in case someone is monitoring in real time.    

• Both applications are capable of detecting multiple left objects.
  

• A left object that has a similar colour to the background is the worst case scenario for detection (such as a black bag in a shadowed background).  The applications are able to detect an object that is the same colour as the background with 50% difference in luminance. That ratio comes down when there is significant difference in colour.  A white object against a black background will require 0% difference in luminance.
  

• The false alarm rate depends heavily on the amount of moving traffic and changing environment. If we deploy this in an indoor environment with minimal traffic (with 2 to 3 persons through traffic per minute) we would be looking at close to 0 false alarms. If we deploy this in an outdoor environment with foot traffic density similar to a busy city street, we are probably looking at around 1 false alarm per camera per 3 to 4 hours.

END