• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 3360 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Flash V1.6 OMAP flash error

Nick Velado
Prodigy 190 points


Hi,

We're using a DM3730 on a Variscite SOM, and attempting to reflash the EBoot sector to correct some display issues using the Flash Tool v1.06/1.05.  When attempting to erase the EBOOT region, on a Windows 7 machine (running app as admin), the program gives a crash error code of -1073741819 about 3 seconds after reading the asic ID.  On two Windows XP machines, the application crashes alltogether after the same time period.  We've attempted to use a true UART from an older XP machine, as well as FTDI USB serial adapters.  Using the params AM37XX (Hynix), HWECC, ONFI Compliant, 1 bit ECC, Erase Region Offset 0x80000, size: 0x40000.

What are the hardware requirements in order for this to succeed?  The Flash Wiki indicates different switches for different carrier boards, however, would like to know more details on the exact hardware signals and states required, as we don't have schematics for the carrier boards listed, ie: Mistral.  Also, what are the EBoot requirements in order for this to succeed? 

Here is the output from Version 1.6, Win7, USB-Serial:

 

 

¯ -stdout

¯ -omap 3

¯ -no_force_package_alignment

¯ -com 25

¯ -t 60

¯ -p EVM_MDDR_HYNIX_2G

¯ -2

¯ chip_erase NAND1BITBOOT 40000

¯ Leaving parameter file:temp_script.txt

¯ @temp_script.txt

¯ Looking for device (omap com25)

¯ Please turn off device, then turn it on again

¯ Awaiting ASIC id

¯ AsicId items 04

¯ AsicId id 01 05 01 36 30 07 07

Console program aborted or crashed, exit code: -1073741819

 

The DDR populated appers to be Samsung K4X1G163PE (x2), so 256MB total.

 

The NAND populated appears to be Micron NW194. I think this is a 512MB part.

Variscite has confirmed the memory is clocking at 400MHz

Thanks,

Nick

  • 0
    TI__Expert 6735 points

    Nick:

    This tool needs to run on Win XP.  Best to use a real COM port if available.  The error code is Windows

    Access Violation error (C0000005).   Did you have to change your bootloader to support the Samsung

    memory?   Micron NW194 is decoded as MT29F4G16ABBDAH4:D.   The board configuration you are

    using is for a Hynix POP LPDDR + NAND device with DDR at 200 MHz. 

    You would need a modified version of this file ported to your DDR:

    C:\Program Files\Texas Instruments\Flash v1.6\Targets\Configurations\configuration_evm37xx_hynix_2g.txt

     

    Regards,

    Michael T

  • 0 in reply to Michael T
    Prodigy 190 points

    Hi Michael,

    So just confirming, I need a configuration file that matches the Samsung memory populated?  I had suspected this early on, but was told that the config file you're referring to was working on their end.  I just want to make sure my understanding of this is correct before I go back and request this.  Thanks,

    Nick

  • 0 in reply to Nick Velado
    TI__Expert 6735 points

    Nick:

    Usually if the board configuration is an issue OMAPFlash will run to the point where the status text has "Waiting for 2nd".

    If the Clocks / SDRAM / GPMC register setups are wrong the downloaded 2nd loader target binary will not start up.

    What you are seeing is an access violation, which seems like the program is not able to access some file on

    the hard drive.

    Is this happening on WinXP with a physical COM port?

    You can run OMAPFlash from command line and have it run the generated temp_script.txt file from your last run.

    Modify this file to include the "-rxtx_trace" command line arg - that will give you more output status:

     \Program Files\Texas Instruments\Flash v1.6\temp_script.txt

    //Open a command window

    Start -> Run -> cmd

    cd \Program Files\Texas Instruments\Flash v1.6

    OMAPFlash @ temp_script.txt

    Regards,

    Michael T

  • 0 in reply to Michael T
    Prodigy 190 points

    Hi Michael,

    Have rerun it without the access violation.  Here's the output from the GUI:

    ¯ -stdout

    ¯ -omap 3

    ¯ -no_force_package_alignment

    ¯ -com 7

    ¯ -t 60

    ¯ -p EVM_MDDR_HYNIX_2G

    ¯ -2

    ¯ chip_erase NAND1BITBOOT 40000

    ¯ Leaving parameter file:temp_script.txt

    ¯ @temp_script.txt

    ¯ Looking for device (omap com7)

    ¯ Please turn off device, then turn it on again

    ¯ Awaiting ASIC id

    ¯ AsicId items 04

    ¯ AsicId id 01 05 01 36 30 07 07

    ¯ 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

    ¯ Searching 2nd for: EVM_MDDR_HYNIX_2G 363007 07 GP

    ¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_2g.2nd

    ¯ Entering parameter file:omapflash2nd.txt at line: 18

    ¯ -pheriphalboot_reopen

    ¯ Reading board configuration file Targets\Configurations\configuration_evm37xx_hynix_2g.txt

    ¯ Reading definition file .\targets\definitions\definitions_omap3.txt

    ¯ -board_config Targets\Configurations\configuration_evm37xx_hynix_2g.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 com7)

    ¯ Waiting for 2nd

    ¯ Unknown status message '??Texas Instruments Windows CE NAND X-Loader for EVM 3730??Built Jun 4 2011 at 21:59:54??Version VAR-SOM-OM37 CE6 v2.3???Initializing....??Jumping to bootloader at 0x87E00000????Microsoft Windows CE Bootloader Common Library Version 1.4 Built Jun 4 2011 ' during peripheral boot (waiting for 2nd)

    Then, here's the output from the command line, after adding the arg you mentioned:

    C:\Program Files\Texas Instruments\Flash v1.6>OMAPFlash.exe @ temp_script.txt

    » OMAPFlash v4.2 (Jun 24 2011)

    »     -v
    »     -stdout
    »     -omap 3
    »     -no_force_package_alignment
    »     -rxtx_trace
    »     -com 7
    »     -t 60
    »     -p EVM_MDDR_HYNIX_2G
    »     -2
    »     chip_erase NAND1BITBOOT 40000
    » Leaving parameter file:temp_script.txt
    » @ temp_script.txt
    » Looking for device (omap com7)
    » Please turn off device, then turn it on again
    » Awaiting ASIC id
    » AsicId items 04
    » AsicId id             01 05  01  36 30 07 07
    » 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

      00130-000-TX 4 raw bytes: 02 00 03 F0 '????'
    » Searching 2nd for: EVM_MDDR_HYNIX_2G 363007 07 GP
    » Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_2g.2nd
    » Entering parameter file:omapflash2nd.txt at line: 18
    »     -pheriphalboot_reopen
    » Reading board configuration file Targets\Configurations\configuration_evm37xx_hynix_2g.txt
    » Reading definition file .\targets\definitions\definitions_omap3.txt
    »     -board_config Targets\Configurations\configuration_evm37xx_hynix_2g.txt
    » Leaving parameter file:omapflash2nd.txt
    » Sending size of second file (0x00006804 bytes)

      00130-001-TX 4 raw bytes: 04 68 00 00 '?h??'
    » Transferring second file to target (0x6804 bytes)

      00130-002-TX 26628 raw bytes: 00 00 0F E1 1F 00 C0 E3 13 00 80 E3 C0 00 80 E3 '????????????????' ...
    » Closing boot connection
    » Found device (omap com7)
    » Waiting for 2nd
      00454-003-TX ACK

      00562-004-RX: 256 raw bytes: 0D 0A 54 65 78 61 73 20 49 6E 73 74 72 75 6D 65 '??Texas Instrume' ...
    » Unknown status message '??Texas Instruments Windows CE NAND X-Loader for EVM 3730??Built Jun  4 2011 at 21:59:54??Version VAR-SOM-OM37 CE6 v2.3???In
    itializing....??Jumping to bootloader at 0x87E00000????Microsoft Windows CE Bootloader Common Library Version 1.4 Built Jun  4 2011 ' during periphera
    l boot (waiting for 2nd)

    C:\Program Files\Texas Instruments\Flash v1.6>

    In both cases, the string shown at the bottom of the trace is what appears from the bootloader under a normal boot condition.  Thanks,

    Nick

  • 0 in reply to Nick Velado
    Prodigy 190 points

    Hi Michael,

    Confirming using XP with real serial port worked.  Previously, I had problems with this, which may or may not have had something to do with version 1.5 of the flash tool, and/or opening the COM port prior to using the flash tool creating issues.  When using V1.6 on a clean boot, this succeeds.  Thanks for your help, there were no configuration changes required,

    Nick

  • 0 in reply to Nick Velado
    TI__Expert 6735 points

    Nick:

    UART mode was broken on the Flash Tool v1.5.

    Regards,

    Michael T

  • 0 in reply to Michael T
    Prodigy 110 points

    Hi

    Im having a similar problem to what you describe above. I'm using a Micron 16 bit memory (with an AM37x) and I want to flash the MLO. The tool hangs right after it prints "downloading 2nd". Im using the AM37x micron config file that comes with the tool.

    Could anybody give me a hand?

    Rodolfo

  • 0 in reply to Rodolfo Solera
    TI__Expert 6735 points

    Rodolfo:

    Are you using WinXP?  UART or USB?   Could I get the DDR and NAND part numbers?  2K or 4K NAND page size?

    Could you post your log from Flash v1.6?  The AM37x/micron target configuration is for a POP memory that has

    NAND + LPDDR.  LPDDR is at 166MHz.  You may need a custom configuration if your memory has different timing requirements.

    Regards,

    Michael T

     

  • 0 in reply to Michael T
    Prodigy 110 points

    Hi Michael, thanks for your prompt answer

    We're running XP, the flash part # is MT29F4G16ABBDAH4 and the DDR's part# is MT46H128M32L2.

    Rodolfo


  • 0 in reply to Rodolfo Solera
    Prodigy 160 points

    Rofoldo,

    We are running into similar problems, and using devices similar to what you listed.  Were you able to get your problem resolved?

    Thanks,

    -jesse-

  • 0 in reply to Jesse
    Prodigy 110 points

    We modified the HW because of another requirement and one of the parts that we changed was an oscillator. After the change we didn't have that problem anymore so I guess it has to do with the timing of the memory.