1. Omapflashinstaller-4.10 2 .zip

(through ) has made the Flash Recovery Utility available. This is an unsupported utility.

Is happy to answer email questions about it, but does not support it at present. Add comments here. you need to have an older OSK.

Nowadays the Internet has reached a level where it is, in huge proportions, accessed for entertainment. This is mainly found in the form of media, with most websites relying on special tools in order to get the video, audio and even games more info. Adobe Flash Player Plugin 20.0.0.286 Download.

Rev D1 and later have been reported to not work Please contact and/or and request an updated Flash Recovery Utility if you have a newer board. Unfortunately, no longer works at, so it's not likely that he will be able to provide an updated version.:(. 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. get the untility:. unpack it on a windows XP host (other windows hosts might work). set JP3 to the left (pins 1-2).

disconnect any serial or jtag cables from the OSK (thanx dave). connect the USB cables to the XP host. power up the OSK. windows should prompt for a driver. install it from the ' USB Windows Driver' folder in extracted from the zip file. To recover a dead OSK:.

run the Flash Recovery Utility from which is ' FlashRecoveryUtility OSK Flash Recovery.exe' 1, choose ' Connect and Download'. reset the OSK. 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: - Original Message - Subject: Re: Flash Recovery Utilityfor OSK Date: Sun, 3 Apr 2005 16:16:35 -0700 From: David Brownell To: linux-omap-open-source@linux.omap.com I just used this FRU to load U-Boot 1.1.3, and the essential undocumented trick seems to be disconnecting the serial line. With a serial line connected, nothing works. Contrary to the documentation, you must do more than change JP3. If it's disconnected, the USB enumeration behaves (on either Windows or Linux) and Windows will see the IDs listed in that INF file. Then the driver install can work.

(Needs some hand-holding to find the driver file in same directory as that INF file, but it can work.) And then you can follow the other instructions. Dave Software Design Solutions licenses FRU The OMAP Flash Recovery Utility was licensed to Software Design Solutions, 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 Luis Recuerda has made a new program, called OMAP Flash Loader , 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.

(through ) has made the Flash Recovery Utility available. This is an unsupported utility. Is happy to answer email questions about it, but does not support it at present. Add comments here. you need to have an older OSK.

Rev D1 and later have been reported to not work Please contact and/or and request an updated Flash Recovery Utility if you have a newer board. Unfortunately, no longer works at, so it's not likely that he will be able to provide an updated version.:(. 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. get the untility:. unpack it on a windows XP host (other windows hosts might work). set JP3 to the left (pins 1-2).

disconnect any serial or jtag cables from the OSK (thanx dave). connect the USB cables to the XP host. power up the OSK. windows should prompt for a driver. install it from the ' USB Windows Driver' folder in extracted from the zip file. To recover a dead OSK:. run the Flash Recovery Utility from which is ' FlashRecoveryUtility OSK Flash Recovery.exe' 1, choose ' Connect and Download'.

Omapflashinstaller-4.10 2 .zip

reset the OSK. 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: - Original Message - Subject: Re: Flash Recovery Utilityfor OSK Date: Sun, 3 Apr 2005 16:16:35 -0700 From: David Brownell To: linux-omap-open-source@linux.omap.com I just used this FRU to load U-Boot 1.1.3, and the essential undocumented trick seems to be disconnecting the serial line.

With a serial line connected, nothing works. Contrary to the documentation, you must do more than change JP3. If it's disconnected, the USB enumeration behaves (on either Windows or Linux) and Windows will see the IDs listed in that INF file. Then the driver install can work. (Needs some hand-holding to find the driver file in same directory as that INF file, but it can work.) And then you can follow the other instructions. Dave Software Design Solutions licenses FRU The OMAP Flash Recovery Utility was licensed to Software Design Solutions, 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 Luis Recuerda has made a new program, called OMAP Flash Loader , 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.