Which is the operating system installed? May I know the make and model of smart phone you are trying to connect to computer? Download Audio Song Of Drama Numm.

Download the latest drivers for your OMAP4430 FastBoot USB device. OMAP4430 FastBoot USB device Drivers Download. OMAP4430 FastBoot USB device Driver Installer.

Have you tried to contact the manufacturer of the smart phone for appropriate device drivers? Check the status of the device in device manager. Method 1: Open the Hardware and Devices troubleshooter Method 2:Follow the suggestions mentioned below to update a driver for hardware that isn't working properly. If you are unable to find drivers, you may need to contact the Smart phone Manufacturer, they will help you install the correct drivers for the device. Hope this helps.

Contents • • • • • • • • • • • • • • • • • • • • • • • Applicability This tool can only be used on Sitara AM35x, AM37x devices. This article applies to Sitara SDK 5.0.3.x. For SDK 5.0.2 see archived versions section. This Windows XP-based Flash Tool can be used to program MLO, u-boot and kernel to NAND flash.

As an alternate method, you can use U-Boot to program MLO, u-boot and kernel to NAND flash. File systems must be programmed using Linux kernel commands.

Installation Instructions • Download 'FlashTool for AM35x, AM37x, DM37x and OMAP35x Devices' from here: onto a PC running the Windows XP O/S. Open the downloaded FlashTool_vX.X.X.X zip file and run setup.exe to start the Windows Installer. Follow the installer instructions. The default installation directory is 'C: Program Files Texas Instruments Flash v1.6', but this can be changed when running the installer. The FlashTool software can be uninstalled at any time by accessing the Add/Remove Programs function of Windows (Start ->Control Panel ->Add/Remove Programs).

About Flash v1.6 This page contains a description of a tool – Flash v1.6 – that can be used to transfer binary images from a host PC to certain TI ARM-based target platforms. The tool consists of two main components: - a GUI host application, called Flash v1.6 - a CLI host application, called OMAPFlash. It is recommended to use the GUI for performing flashing functions.

This documentation covers usage of the GUI. Future documentation will cover the CLI interface in more detail. This application has been designed with flexibility and portability in mind. It is now possible to modify target register configurations without rebuilding the tool. This allows for easy modifications to various target peripheral configurations (such as SDRC, GPMC, Pad Control, etc.). This capability makes it possible to support new DDR devices and NAND devices without software changes. Check out the section for more information on this feature.

Internally, the tool makes use of a ROM code mechanism for peripheral boot from UART or USB to transfer compatible drivers to the internal memory of the OMAP device. These drivers provide the mechanism by which the host applications can program binary images into the internal memories (NAND and SDRAM) of the target. All of this operation is hidden from the user.

Release Notes Version 1.6.0.0 (6/24/2011) New Features • Added GUI controls for Target OS and 1-Bit ECC Layout. • Set offset to ECC parity data in spare area based on new GUI controls. • Added support for ECC offsets used with WinCE for 4/8-bit BCH. • Eliminated requirement that image size be a mult of 4 bytes. • Added software NAND unlock command. Limitations • Download and execute can only branch to Thumb code Version 1.5.1.0 (3/25/2011) New Features • Programming flash via UART target connection is now supported. Limitations • Download and execute can only branch to Thumb code Version 1.5 (3/13/2011) New Features • Added support for programming NAND devices with Internal ECC Limitations • Programming flash via UART target connection is not supported • Otherwise, similar functionality to previous releases.

Version 1.4 (2/16/2011) New Features • Added AM35xx and Custom_AM35xx target types • Updated 'What's This?' Help text for UART and USB target connection types • Greyed out 4-bit BCH error correction for OMAP35xx devices (not supported by silicon) Limitations On-chip ECC is not supported • Programming flash via UART target connection is not supported • Otherwise, similar functionality to previous releases. Version 1.3 () New Features • GUI updates, including 'What's This?'

Style help, link to user's guide. • Defined Custom target types for AM37xx and OMAP35xx, to allow customers to more easily make changes for custom boards. • Enhanced NAND capabilities: SW vs. HW ECC Selection, 1b/4b/8b Error Correction, ONFI NAND selection via check box. Limitations • Still no AM35xx support (coming in future release). • Otherwise, similar functionality to previous releases. Version 1.2: New Features • USB Support • Can install over previous versions without manual uninstall • Selectable NAND vs.

ONFI NAND mode Limitations • Same as before Version 1.1: New Features • OMAP35xx Support. Limitations • Same as before Version 1.0: Features • UART support • AM37xx/DM37xx support • Can support new NAND devices via text config file modification. • Can modify target registers via text config file modification (for example SDRC, GPMC, pad config settings) • ONFI NAND Support • Supported operations: Download, Download and Execute (to Thumb mode code), Erase Region, Erase All. • Windows GUI (no Linux yet). • Scriptable Windows CLI (no Linux yet).

• Fully open source, BSD-style license. Limitations • Download and execute can only branch to Thumb code. • Storing images to NAND uses HWECC. Therefore, you cannot use a standard xloader to load uboot from NAND.

Xloader uses SWECC when reading from NAND. The workaround is to use the uboot provided on the SD card to flash itself into NAND memory. • GUI support does not yet exist to define new platforms.

However, two memory choices are supplied, Hynix and Micron. For experimenting with modifications to the configuration text file (for instance, to port to a new platform) it is recommended that you modify the Micron files (and save a copy if you need the originals). Accessing Online Help There are two methods to get help from the user interface: 1. Click the 'What's This Do?' This changes the cursor type. Move the cursor over a widget until you see the cursor change to a question mark.

Then, you may click and get context sensitive help. Click the 'Open User's Guide' Button. This will open your normal HTML browser to the Flash User's Guide Page (this page). Setup for USB Peripheral Boot Mode 1. Ensure that your EVM is set up for peripheral boot from USB. For Mistral OMAP EVM (AM37x, DM37x or OMAP35xx devices) • Set SW4 switches #2 and #3 to the ON position and all others OFF.

• Connect a USB cable from the board's USB 'On the Go' port to a USB port on the PC. • Power on the EVM or press the reset pushbutton (labelled 'OMAP_RST') For LogicPD AM3517EVM: • Set SW7 switches #1 and #4 to the ON position and all others OFF. • Connect a USB cable from the board's USB 'On the Go' port to a USB port on the PC. • Power on the EVM 2. If this is the first time to connect the EVM to your PC via USB you will need to perform the following steps to install the required USB driver: • You will see the 'Found New Hardware Wizard' dialog box. Select 'No, not this time', then 'Next'. • Select 'Install from a list or specific location (Advanced)'.

• Use the browse box to select the following folder: usb_drv_windows. Normally, the full path will be: C: Program Files Texas Instruments Flash vX.X usb_drv_windows. • Make sure the box 'search removable media' is unchecked. • Make sure the box 'Include this location in the search' is checked.

• Click Next. The driver should install correctly without error messages. • Click Finish to exit the Found New Hardware Wizard. Setup for UART Peripheral Boot Mode 1. Ensure that your EVM is set up for peripheral boot from UART. For Mistral OMAP EVM (Rev G): • Set SW4 switches #2 and #4 to the ON position and all others OFF. • Connect a 9-pin serial NULL-MODEM cable, from your host PC to the “UART3” port on the target board.

• Power on the EVM or press the reset pushbutton (labelled 'OMAP_RST') For LogicPD AM3517EVM: • Set SW7 switches #1 and #4 to the ON position and all others OFF. • Connect a 9-pin serial NULL-MODEM cable, from your host PC to the “UART” port on the target board. • Power on the EVM. Making Binary Images Accessible to the Windows XP O/S The binary images for XLOADER, U-Boot and the Linux Kernel must be made accessible to the Windows XP O/S. There are a few methods for doing this: 1) If you are running your Linux Host as a virtual machine (using VMWare or using Sun Virtual Box) you can setup a shared folder that can be accessed by both the Linux Host and the Windows O/S.

(You can also create sub-folders below that as needed - the resulting directory tree will be accessible to both Linux and Windows.) See or for details. OR 2) You can setup a Samba server that makes a designated location in your Linux Host file system appear as a drive to the Windows O/S.

The binary images can be copied to the shared folder or be accessed directly via a Samba drive. 1) Pre-built images can be found in the./psp/prebuilt-images subdirectory of the Sitara SDK installation. OR 2) Rebuilt images would be found where they were rebuilt under the./psp subdirectory of the Sitara SDK installation. Starting the Flash Application To start the Flash application under Windows XP: • Double click the 'Shortcut to Flash.exe' icon on the desktop OR • Use the Windows Start menu: 'Start ->All Programs ->Texas Instruments ->Flash v1.6 ->Flash.exe'.

Below is a screen capture of Flash_v1.6.0.0 upon startup. Details about the Flash GUI 1. CHOOSE TARGET (drop-down box) This allows selection of pre-defined target configuration files for the different EVM boards. The target configuration files contain register initialization code that mimics what is performed by XLOADER to initialize clocks and memory interfaces prior to flash programming.

The following pre-defined EVM configurations and custom configurations are provided. Choose a a custom target configuration and click the 'Edit Config File' button to view or modify the target configuration for your custom design. See the section for more information on how to design a custom target configuration file. Pre-Defined EVM Target Board Configurations Target Board Target Configuration Description AM35xx (Micron) LogicPD AM3517EVM with AM3517A SOM and Micron discrete NAND and DDR2 memories AM37xx (Hynix) Mistral OMAP3 EVM with AM37x or DM37x SOM containing Hynix POP Memory AM37xx (Micron) Mistral OMAP3 EVM with AM37x or DM37x SOM containing Micron POP Memory OMAP35xx (Micron) Mistral OMAP3 EVM with OMAP35x SOM containing Micron POP Memory Custom Target Board Configurations Target Board Configuration Description Custom AM35xx Board Same as AM35xx (Micron) - Modify for your custom AM35xx design. Custom AM37xx Board Same as AM37xx (Hynix) - Modify for your custom AM37x/DM37x design. Custom OMAP35xx Board Same as OMAP35xx (Micron) - Modify for your custom OMAP35xx design.

SELECT TARGET CONNECTION TYPE (Radio Buttons) This allows selection of the target connection. Select USB or UART for communication between the Host PC and the target board (and also the peripheral boot mode that will be used). For the UART connection, also select the PC COM port that will be used (typically 1 for COM1). CHOOSE THE DESIRED MEMORY TYPE This selects the destination memory type. Selecting NAND enables Erase and Download operations. Selecting SDRAM allows Download and Download and Execute operations. SELECT MEMORY OPTIONS If you have selected SDRAM, there are no other memory options to select.

If you have selected NAND, choose from the following group of options: • ECC STYLE (Radio Buttons) This selects the method used to generate, check and correct ECC data in the NAND spare area. Choose HWECC, SWECC or NAND ECC. HWECC uses the GPMC controller to calculate ECC parity and uses software error detection and correction. SWECC uses software to calculates ECC parity and to detect and correct errors. NAND ECC uses Internal ECC controller on the NAND device to calculate ECC parity and to perform error detection and correction.

Before NAND is programmed using NAND ECC mode, the Internal ECC of the NAND device is activated. When programming XLOADER, always choose HWECC and 1-bit ECC, as this is required by the ROM Boot Loader. When programming U-Boot or the Linux Kernel the ECC style must be set to be compatible with the software that will read the downloaded image from NAND.

• ONFI COMPLIANT NAND? (check box) Check this box for operations on an ONFI-compliant NAND device. When checked, data specifying NAND memory geometry and features are read from the NAND device. Otherwise, this data is taken from the header in the Target Configuration file.

• ERROR CORRECTION (Radio Buttons) Select the error correction algorithm that will be used to program the ECC data into the OOB area. For SWECC ECC format, only 1-Bit ECC (Hamming Code) is allowed. For HWECC ECC format, 1-bit ECC, 4-bit BCH or 8-bit BCH algorithms can be selected.

(4-bit BCH is not available for the OMAP35xx device due to silicon limitations). For NAND ECC mode, the ECC algorithm provided by the NAND Internal ECC is used. • TARGET OS (drop-down box) This GUI control shows only when HWECC 4-bit BCH or 8-bit BCH is selected. Change Serial Number Phoenix Bios. The ECC Offset in spare area is changed to 2 if the WinCE Target OS is selected. • 1-Bit ECC Layout (drop-down-box) This GUI control shows only when HWECC 1-bit ECC is selected.

Choose 'X-Loader/U-Boot' when programming XLOADER or U-Boot into NAND. For Linux kernel 2.6.37 or later, you must change this setting to Kernel when programming the Linux kernel into NAND.

This changes the ECC offset in spare area from 2 to 40, as is needed to be compatible with the JFFS2 NAND file system. For earlier Linux kernels, 'X-Loader/Uboot' setting should be used for programming the Linux kernel into NAND. CHOOSE OPERATION PARAMETERS (Radio Buttons) Select the operation to be performed: • DOWNLOAD Choose this to download a binary image to either NAND or SDRAM. Before downloading an image to NAND, you must first erase the region where the image will be downloaded (or Erase All NAND). Set OFFSET (hexadecimal value) to the offset from the beginning of NAND or SDRAM where the image will be downloaded. • DOWNLOAD AND EXECUTE Choose this to download a binary image and execute it. Applies to SDRAM as destination only.

Supports Thumb Mode ARM code only. Set OFFSET (hexadecimal value) to the offset from the beginning SDRAM where the image will be downloaded. • ERASE REGION Choose this to erase a region in NAND flash. Set OFFSET (hexadecimal value) to offset from beginning of NAND device where erasing begins. Set SIZE (hexadecimal value) to the number of bytes which will be erased.

Use a multiple of the NAND BLOCK size. • ERASE ALL Choose this to erase the entire NAND flash.

IMAGE SELECTION (Edit Box) For download operations, you must specify the binary image to be downloaded. Click the BROWSE button to select an XLOADER, U-Boot, Linux Kernel. File systems cannot be programmed to NAND flash using this Flash Tool. U-Boot should be used to program file systems to NAND flash.

GO (Button) Once you have successfully made your selections, the GO button will be enabled. Click the GO start execution of the specified operation. ABORT (Button) Once the operation is in progress, you will have the option of clicking the ABORT button to cancel it. This would be used if communication with the target device fails or if the target board fails to complete the peripheral boot process. OUTPUT (Text Window) While the operation is in progress, status information is output to the OUTPUT text window. First a message will be displayed to 'Please turn off device' (if powered on) and then 'Please turn on device'.