Omapflash Windows 7

1. Download sp flash tools windows 10 for free. Multimedia tools downloads - Sp Flash tools by SPFlashTool.com and many more programs are available for instant and free download.
2. Windows 7 and flash updates I am having problems with Microsoft internet explorer. I ran a flash update and it said that the update was successful, but nothing runs with it - it is always asking me to run to get the latest version. Now java script is giving me errors also. I run Windows 7.
3. Windows 7 is the only option these days. Is there any direct support for the Flash v1.6 tool in Windows 7, or a direct replacement? I have tried WinXP compatibility mode, but this was no help. Command line script: OMAPFlash.exe ^ -omap 3 -2 -p EVMMDDRMICRON2G -t 20 ^ chiperase NANDINFO1BITBOOT 0 ^.

• Omapflash Windows 7 32-bit
• Windows 10
• Windows 7 Iso
• Omapflash Windows 7 Iso

NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

Flash Player For Windows 7 32 Bit free download - Flash Movie Player, Windows 7 (Professional), Flash Player Pro, and many more programs.

TI Flash and Boot Utilities[edit]

The following software supports the OMAP-L138, C6748, and AM1808 families of devices.

This package contains a set of utilities running from the command-line on Windows for flashing the NAND, NOR, and SPI Flash of the OMAP-L138 EVM via the serial port.

The Serial Flashing Host Utility (which offers the same functionality as a previous program called DVFlasher) executable is called sfh_OMAP-L138.exe.

These programs each encapsulate a distinct binary UBL which is transferred via the UART. This implies that the chip must be operating in the UART boot mode, showing the BOOTME prompt.

NOTE: The assumption is made that the UART of the device operates at 115200, 8N1. If the oscillator used with the device does not match the one used on the EVM (e.g. on a custom platform), the baud rate assumption may be incorrect.

Obtaining the software[edit]

The latest source code and binaries can be download from here.

Omapflash Windows 7 32-bit

Note that for flashing UBLs from PSP releases 03.20.00.13 and earlier, v2.29 of the serial flasher should be used.

For flashing UBLs from PSP releases 3.20.00.14 and later, the latest version of the serial flasher should be used.

Compiling[edit]

A makefile is included for compiling the host and target parts of each utility. The target portions are built first since they are embedded into the the host executables. These target portions are loaded to the OMAP-L138 device via the UART boot mode.

Note that the pre-built executables have been tested to work on the EVMs. It is not necessary to rebuild them unless changes need to be made for a custom board.

Under Windows

Please see the following page for detailed instructions for rebuilding the utilities in included in this package:

Under Linux

The Mono Framework must be installed and in the path. RPMs are available at 'http://www.mono-project.com/Downloads'. The below instructions assume the that GNU ARM cross-compiler tools (arm-arago-linux-gnueabi-gcc, etc.) are in the current PATH.

The C6x Compiler Tools are also required to build some components. These are available free of charge at https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm. You will need to add the bin directory to your PATH and to set the environment variables as directed by the installer. Edit the build.mak file under Common directory and add the paths to ARM and C6x compilers.

Then go to the GNU directory of the package and run:

Running[edit]

Under Windows

This utility can be run from the command line under Windows with the .Net Framework 2.0 or later installed through the following steps:

1. Set the boot pins to UART2 boot mode. This is done by setting switch S7 on the LogicPD OMAP-L138 EVM according to the following table:

Windows 10

For Spectrum Digital EVM:

1. Connect a serial cable from the host computer to the OMAP-L138 EVM
2. Open a command prompt on the host computer and change directory to where the SFH executable is located.
3. Run the flashing utility with this command:
   • ..OMAP-L138gnusfh_OMAP-L138.exe [options]
4. Turn on the board

Under Linux

The serial flasher can be run on a Linux machine with the latest open-source Mono Framework installed. The steps are identical to the Windows environment except the command:

• mono ./sfh_OMAP-L138.exe [options]

Serial Flasher Options[edit]

There are three modes for using the serial flasher:

1. Erase the target flash type - This will erase the entire contents of the flash.
   • ..sfh_OMAP-L138.exe -erase
2. Flash the memory with a single application image - This will place an application image at address 0x0 of the flash. This must be an AIS format binary, which can be created with the AISgen utilities bundled with the Bootloader User Guide and associated files.
   
   • ..sfh_OMAP-L138.exe -flash_noubl
3. Flash the memory with a UBL and application image - This will place a UBL at address 0x0 of the flash and an application image, such as u-boot, at address 0x10000. In general, a UBL is not required, and this mode is only used when restoring the default flash contents, as explained in the following section.
   
   • ..sfh_OMAP-L138.exe -flash

For C6748 devices, use the following option: '-targetType C6748'

For AM1808 devices, use the following option: '-targetType AM1808'

Note: Only the UBL found in the OMAP-L138/GNU/UBL directory can be used with the serial flasher. Other UBLs are not compatible with the serial flasher format.

Note: 'The 'flash_noubl' and 'flash' options will automatically erase the necessary amount of memory in order to fit the UBL and/or application image.

Currently, the only supported flash types are NAND, NOR, and SPI.

Additional options are shown below:

Once any command is run, the 'Waiting for BOOTME...' prompt shows. Power cycle the board or press the reset button to continue.

Restoring the OMAP-L138 EVM SPI Flash[edit]

If the contents of the OMAP-L138 SPI flash become corrupted, they can be restored through the following steps:

1. Set the boot pins to UART2 boot mode. This is done by setting switch S7 on the OMAP-L138 EVM according to the following table:

For Spectrum Digital EVM:

1. Obtain the UBL and u-boot binary files and place them in the same directory as the SPI flashing utility.
   • A pre-built UBL bin file is located in the OMAP-L138/GNU/ubl/ directory of this serial flashing project. The UBL bin file from the PSP installation will also work, located at images/u-boot/.
   • A pre-built u-boot image is located in the images/u-boot/ directory of the PSP installation.
2. Run the following command to flash the UBL and u-boot binary files:
   • ..sfh_OMAP-L138.exe -flash
   • Note that if the serial port is not on COM1, the correct port must be specified using the '-p' option. To determine which COM port to use, open HyperTerminal, connect to one of the ports, and make sure the word 'BOOTME' appears when the EVM is reset.
   • Note: If you are using a device other than OMAP-L138, such as C6748, you must use the '-flashType' option and specify the device you are using.
     
3. Turn on the board
4. After the UBL and u-boot files have been flashed, set the boot pins to SPI boot mode and reboot the board. This is done by setting switch S7 on the OMAP-L138 EVM according to the following table:

For Spectrum Digital EVM:

1. Once u-boot has loaded, follow the instructions in the Getting Started Guide to copy the Linux kernel and filesystem to the SPI flash.
   • Note: This step requires that the setup procedures in the Getting Started guide have been followed:

Modifications for Custom Boards[edit]

The default settings used by the tools apply only to the EVMs. For custom boards, changes will most likely be required, and the tools must be rebuilt. The custom changes should be made to the files in the OMAP-L138/Common/src and OMAP-L138/Common/include directories. Common changes include:

• DDR Configuration
  • OMAP-L138/Common/src/device.c: Modify the parameters passed to the function DEVICE_ExternalMemInit to match the DDR timing requirements for the custom board

• UART Settings
  • OMAP-L138/Common/include/device_uart.h: Modify the #define DEVICE_UART_PERIPHNUM to set which UART is connected to the host PC.
  • Note that flow control is not used, so only the RX and TX lines need to be connected for boot and flashing purposes.

• SPI Settings
  • OMAP-L138/Common/include/device_spi.h: Modify the global macros to select the appropriate peripheral and chip select numbers.
  • OMAP-L138/Common/src/device_spi.c: Modify the flash organization in DEVICE_SPI_MEM_params.
  • The SPI flash on the EVM does not need to be unlocked in order to erase or write. Some SPI flashes may need to set the BL bits before writing. Check the device datasheet to see if this step needs to be added to the initialization.

• NAND Settings
  • OMAP-L138/Common/include/device_async_mem.h: Modify the #define DEVICE_ASYNC_MEM_NANDBOOT_BUSWIDTH to match the bus width of your NAND

• PLL Settings (for non 24 MHz input clocks)
  • OMAP-L138/Common/src/device.c: Modify the parameters passed into the function DEVICE_PLL0Init and DEVICE_PLL1Init to set the proper PLL output frequencies
  • OMAP-L138/Common/src/device_uart.c: Modify the 'divider' field in DEVICE_UART_config to achieve 115200 baud rate

Known Issues[edit]

The software provided has no known issues on TI supported evaluation platforms. The software may need modifications in case of custom hardware.

License[edit]

These tools are provided as freeware, with no guarantee.

Texas Instruments (through Tim Riker) has made the OSKFlash Recovery Utility available. This is an unsupported utility. Tim Riker is happy to answer email questions about it, but Texas Instruments does not support it at present. Add comments here.

1. you need to have an older OSK. Rev D1 and later have been reported to not work Please contact Spectrum Digital and/or Texas Instruments and request an updated Flash Recovery Utility if you have a newer board. Unfortunately, Tim Riker no longer works at Texas Instruments, so it's not likely that he will be able to provide an updated version. :(
2. you need a USB-A-male to USB-A-male cable. This can be done with a common USB-A-male to USB-B-male cable and a USB-B-female to USB-A-male adapter.
3. get the untility: Media:OSK5912FlashRecoveryUtility.zip
4. unpack it on a windows XP host (other windows hosts might work)
5. set JP3 to the left (pins 1-2)
6. disconnect any serial or jtag cables from the OSK (thanx dave)
7. connect the USB cables to the XP host
8. power up the OSK
9. windows should prompt for a driver
10. install it from the 'USB Windows Driver' folder in extracted from the zip file.

To recover a dead OSK:

1. run the Flash Recovery Utility from which is 'FlashRecoveryUtilityOSK Flash Recovery.exe' 1, choose 'Connect and Download'
2. reset the OSK
3. is should connect, download the reflash code, and bootloader: 'u-bootbinOSK' and run the reflash code when unprotects the NOR flash and does the writes the bootloader to flash.

Note that you can replace the file 'u-bootbinOSK' with a different copy of uboot or any other loader if you like.

There have been some failures reported. This might be a useful comment: http://linux.omap.com/pipermail/linux-omap-open-source/2005-April/003491.html

Software Design Solutions licenses FRU

The OMAP Flash Recovery Utility was licensed to Software Design Solutions, Inc. Software Design Solutions. SDS Inc. now sells a Flash Recovery Utility that supports the OSK5912 revision C and revision D hardware.

How Does it Work?

Many OMAP chips support a 'full boot' mode. There is an internal ROM in the chip that the ARM CPU boots from. The ROM tries to talk over the serial port to an external application. It can also support the USB port in client mode. When you set JP3 on the OSK you are telling the OMAP to boot in 'full boot' mode. The ROM code is started and the device enumerates on the SCSI bus. The FRU looks for this enumeration, and sends a small app over USB which then runs. In this case the small app will have u-boot attached to it as data, and the small app just contains code to flash the data payload into NOR flash. Other applets can be developed, but this FRU is just the basic feature. This FRU does not support flashing over serial, though the hardware could do that too.

As an FYI: this internal ROM is also what is used to support 'secure boot'. In 'secure boot' the OMAP verifies a signed binary in some external flash/ROM before running the code. If an OMAP is setup for 'secure boot' it will only run signed code. Contact TI for more information on 'full boot' or 'secure boot' modes of the various OMAP chips.

OMAP Flash Loader

Windows 7 Iso

Luis Recuerda has made a new program, called OMAP Flash Loader (Media:omapfl-1.0.tar.gz), that runs under Linux or other Unixes with libusb support.It is a GPL program (with sources) that can be expanded easily to use diferent flash chips (for new boards) and, perhaps, other OMAP processors.

Omapflash Windows 7 Iso