This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Ti flash tool on 64 bit windows

Other Parts Discussed in Thread: FLASHTOOL, OMAP3530

Hi,

I am unable to erase and flash the bootloader from Ti flash tool on windows 7 64 bit machine.

This was fine on 32 bit , but on 64 bit the device is not identified from the host and even supplied with modified "csstusb.inf" file for 64 bit.

The modificatons are device entry for 64 bit.

[TI.NTamd64]

%USB_OMAP3430%     = CSSTUSBInstall, USB\VID_XXXX&PID_XXXX

 

Any inputs on 64 bit modifications for inf file and corresponding driver is greatly appreciated.

 

rgds,

Shar T 

 

 

  • Hi Shar,

    I wonder have you tried running the FlashTool installer in compatibility mode? There is a post which reports success on Win 7 64bit using this method:

    http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/416/t/197870.aspx

    Please report back if this helps with the issue.

    Regards,

    Garry

  • Hi Garry,

    Thanks for the reply.

    I followed the process and still I could not fix the issue.

    Installation was never problem and UART connection works fine.

     

    rgds,

    Shar

  • Hi Shar,

    There is an alternative flash tool called OMAPFlash in which the CSST USB driver was replaced by a WinUSB based driver, so the application can run on Windows7 (32 and 64 bit) platforms. This tool is available on request through your local TI Representative.

    This is a pretty complex and powerful low-level command line utility  that you may need help in configuring for your hardware (hence the restricted access) but it should fit your requirements.

    I will contact you with further details offline so hopefully this will close off this post as resolved.

    Regards,

    Garry

  • Hi Garry,

    I get the same problem.

    I have used the OmapFlah tool but it still fails.

  • Cleiton,

    there is a particular version of OMAPFlash (v4.11) which worked for some users with OMAP35 based devices on Win7 64 platforms. 

    Important: This tool is no longer supported by TI however I have attached it for your experiments and regret it comes with discalimer of no support or warranty so use at your own discretion. 

    The limited usage I had was with an original BeagleBoard (OMAP3530).

    0537.OMAPFlash4.11-with-win7.zip

    Usage:

    1. Unzip the file
    2. Install the appropriate OMAP USB driver for the OMAP device
    3. [For Beagle using the command file to do SDRAM ] OMAPflash @OMAP35_sdram_1k_Beagle.txt, see below
    C:\TI\OMAPFlash4.11-with-win7\OMAPFlash4.11-with-win7>OMAPflash @OMAP35_sdram_1k_Beagle.txt
    
    » OMAPFlash v4.11 (Apr  6 2011)
    
    »     -v
    »     -stdout
    »     -omap 3
    »     -t 60
    »     -p CUSTOM_OMAP35XX_BOARD
    »     -2
    »     chip_download SDRAM .\test_data\pattern_1K.bin
    » Leaving parameter file:OMAP35_sdram_1k_Beagle.txt
    » @OMAP35_sdram_1k_Beagle.txt
    » Looking for device (omap usb)
    » Please turn on device
    » Waiting for device (omap usb)
    » Found device (omap usb)
    » Awaiting ASIC id
    » AsicId items 05
    » AsicId id             01 05  01  34 30 07 54
    » AsicId secure_mode    13 02  01  00
    » AsicId public_id      12 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    » AsicId root_key_hash  14 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    » AsicId checksum       15 09  01  D6 D8 80 68 00 00 00 00
    » Searching 2nd for: CUSTOM_OMAP35XX_BOARD 343007 54 GP
    » Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_512m.2nd
    » Entering parameter file:omapflash2nd.txt at line: 5
    »     -pheriphalboot_reopen
    » Reading board configuration file Targets\Configurations\configuration_evm35xx_micron_512m.txt
    » Reading definition file .\targets\definitions\definitions_omap3.txt
    »     -board_config Targets\Configurations\configuration_evm35xx_micron_512m.txt
    » Leaving parameter file:omapflash2nd.txt
    » Sending size of second file (0x00006804 bytes)
    » Transferring second file to target (0x6804 bytes)
    » Closing boot connection
    » Found device (omap usb)
    » Waiting for 2nd
    » Found 2nd
    » Looking for a driver for 'SDRAM'
    » No driver required for 'SDRAM'
    » Downloading
    » Downloading '.\test_data\pattern_1K.bin'
    » Sending data (1024 bytes) :::::::::::::::::::: [1024]
    » Downloading complete
    » Elapsed time: 0:00.010 (102400 bytes/s)

    Regards,

    Garry