• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 98 subscribers
  • Views 743 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.

Using Flash v1.2 on EVM3730

Glenn Wainwright
Expert 1605 points
Other Parts Discussed in Thread: DM3730

I am attempting to use Flash v1.2 on the OMAP3730 EVM using the directions at http://processors.wiki.ti.com/index.php/Flash_v1.0_User_Guide.  My goal is to load U-Boot into SDRAM and then use that U-Boot to flash all the necessary bits over TFTP.

Unfortunately, though it says it downloads the u-boot.bin to SDRAM and branches, I don't see anything coming out of UART1 to indicate that it is running.

App Output:

¯ -stdout
¯ -omap 3
¯ -com 2
¯ -t 60
¯ -p EVM_MDDR_HYNIX_2G
¯ -2
¯ chip_download SDRAM C:\VMShare\u-boot.bin
¯ command branch SDRAM 0x0
¯ Leaving parameter file:temp_script.txt
¯ @temp_script.txt
¯ Looking for device (omap com2)
¯ 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: 11
¯ -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 com2)
¯ Waiting for 2nd
¯ Found 2nd
¯ Looking for a driver for 'SDRAM'
¯ No driver required for 'SDRAM'
¯ Downloading
¯ Downloading 'C:\VMShare\u-boot.bin'
¯ Sending data (274672 bytes) ::.................. [32764]
¯ Sending data (274672 bytes) :::::::::::::::::::: [274672]
¯ Sending data (274672 bytes) :::::::::::::::::::: [274672]
¯ Downloading complete
¯ Elapsed time: 0:23.843 (11942 bytes/s)
¯ branch SDRAM 0x0
¯ Elapsed time: 0:00.000
Console program success, exit code: 0

Setup Details:

I have UART1 on the EVM hooked to COM1 on my PC and UART3 on the EVM hooked to COM2 on my PC. (loading the image using COM2/UART3)
The u-boot.bin image that I am using has been successfully tested on the EVM (by flashing it from the MMC card).
SW4 is set so that just Pin 2 & 4 are on (Peripheral boot from UART)
As mentioned above, it claims to load the image successfully and branch to it, but nothing appears on UART1.

Any idea what I am doing wrong here?

Glenn Wainwright

  • 0
    TI__Intellectual 1585 points

    I believe there may be a problem with the branch command - the problem I believe is that the processor needs to be in ARM mode in order to execute u-boot, but the Flash tool leaves the processor in Thumb mode.  This problem has not yet been resolved and probably won't be very soon, it is a low priority problem at the moment.

    Do you have another way to load u-boot?  Perhaps by booting it from an SD card or directly from NAND?

  • 0 in reply to Greg Guyotte
    Expert 1605 points

    Unfortunately, I won't have access to the SD card slot on our custom board - which is why I was trying so hard to get this method working.  If the SDRAM load on this app is broken, then we can try writing the x-loader and u-boot directly into NAND.  However, when I try this using the Flash app, the written data fails ECC checks.  There may be something wrong with the NAND configuration - do you know what the correct settings are for the Rev G DM3730 EVM?  

    I have tried the following so far:

    memory NANDINFO driver Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin parameters gpmc 0x6E000000 cs 0 address 0x28000000 bberase 0 onfi 0 bpp 1024 sbpp 32 ppb 64 bpl 4096 l 1 acv 0x23 f 0x0019

    memory NANDINFO driver Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin parameters gpmc 0x6E000000 cs 0 address 0x0 bberase 0 onfi 0 bpp 2048 sbpp 64 ppb 64 bpl 2048 l 1 acv 0x23 f 0x0019

    The first config fails entirely.  The second successfully writes data to the NAND, but that data does not pass ECC checks.

     

  • 0 in reply to Glenn Wainwright
    TI__Intellectual 1585 points

    The second NAND configuration is likely correct, however I can't be certain without knowing what NAND device you have on your custom board.

    Further, what do you mean by "does not pass ECC checks"?

    I'm guessing that perhaps you were able to burn x-loader to NAND, but it fails when it tries to load u-boot?  If that's the case, I have a solution for you.  There is a Flash v1.3 now available on the GForge site.  It contains the ability to burn images with both HWECC and SWECC.  So you would select HWECC when loading x-loader to address 0x0, and SWECC when loading u-boot to address 0x80000.  In each case, you would select 1-bit ECC correction.  Also, under the target selection, select AM37xx.  The default configuration file should contain the proper NAND configuration.  If not, you can easily modify it to suit your needs.  I have provided a "Custom AM37xx" target option which gives you a configuration file that you can freely modify without concern for messing up the original config file that works with stock EVMs.

    Hopefully, this solution will get you to a u-boot prompt.

  • 0 in reply to Greg Guyotte
    Expert 1605 points

    Great, that should be exactly what I need!

    ...once I can get this new version operational.  So I'm on the same hardware setup (using 3730 EVM, not a custom board) with the new Flash v1.3 with the base "AM37xx (Hynix)" config.  My first step is to just run an Erase Region on the NAND space containing U-Boot, and it's timing out "waiting for 2nd".

  • 0 in reply to Glenn Wainwright
    TI__Intellectual 1585 points

    Glenn,

     

    I haven't yet seen issues when using the stock 3730 Mistral EVM.  If you could, I would need to get a dump of the output.  Also, did you select the "ONFI" checkbox or not?

    -Greg

  • 0 in reply to Greg Guyotte
    Expert 1605 points

    Here is the log dump, as well as a screenshot of the app before executing the command.  ONFI is not selected.

    0871.flash1_3_log.txt

    Hope that helps,

    Glenn Wainwright

  • 0 in reply to Glenn Wainwright
    TI__Intellectual 1585 points

    Glenn, if you are able to try flashing over USB, please try that.  We have identified an issue with flashing over UART on AM37xx devices and are working to fix it.

  • 0 in reply to Greg Guyotte
    Expert 1605 points

    That method seems to work well on the EVM board.  We'll need to swap out some resisters on the SYSBOOT pins on our custom boards, but this should definitely get us up and running right now.  Thank you very much for your assistance, and please keep in touch when you find a solution to the other modes.

    Glenn

  • 0 in reply to Greg Guyotte
    Expert 1130 points

    Hi Greg/All,

    I believe this therd is still active, I,m also facing an issue in write Eboot into nand falsh using Flash tool (Flashv1.4) in my AM37xx EVM. The following are my setup

    1. Processor Board: EVM3530/3730 0.4MM Processor Module RevD

    2. Main Board: EVM Main Board REV G

    3. Memory: Hynix 256MB DDR/512MB nand Flash

    4. BSP: bspsource_omapwince_06_15_00

    5. Flash tool: Flash v1.4 and log atatched

    (0358.log_37xx_hynix.txt)

    From the above log it showing writing nand flash is success but device is not booting and debug messages are also not printing. I had tried SD boot and it is working.

    Plz help me how to download eboot using Falsh v1.4.

     

    Thanks in Advance

    Jethin


  • 0 in reply to Jethin Sekhar
    TI__Genius 9190 points

    Hello Jethin,

    do you have the correct sysboot setting for booting from NAND (SW4)?  Also, here is a link to the Flash tool user's guide if you haven't seen it:

    http://processors.wiki.ti.com/index.php/Flash_v1.4_User_Guide

     

  • 0 in reply to Jeff Culverhouse
    Expert 1130 points

    Thanks Jeff,

    I have configured sysboot setting as specified in the user manual (SW4 switches #2 and #3 to the ON position and all others OFF).

  • 0 in reply to Jeff Culverhouse
    Expert 1130 points

    Thanks Jeff,

    I had configured sysboot setting already as specified in the user manual (SW4 switches #2 and #3 to the ON position and all others OFF).

    Regards

    Jethin

  • 0 in reply to Jethin Sekhar
    Expert 1130 points

    Hi Jeff,

    I had not seen any nand flash support for hynix in 6.15 BSP, will this be an issue in booting from nand falsh(No single debug message).

    Regards

    Jethin

  • 0 in reply to Jethin Sekhar
    TI__Genius 9190 points

    Hi Jethin,

    the Hynix part is ok to use.  Once you have the NAND flashed, you need to change the SW4 to have 2 and 4 on and the rest off.  This will allow the ROM code to look at the NAND for booting.  The other boot option (2 and 3 on)  is for USB boot. 

    Once you do that you should boot from the NAND.