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.

DM6446 Flashing using Stacked Nor Flash Using SFH_DM644x.eve - Failure to load u-boot

Dear TI Team,

I am not able to flash a DM6446 board with the  PC48F4400POVB00 NOR Flash (Datasheet attached http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/99/1440.306666_5F00_p30_5F00_discrete_5F00_ds-_2800_2_2900_.pdf )

During the serial flashing process, I recieve the following output.  It fails on writing to the flash.  At this point, this appears to be related to not supporting the stacked die.  Do you have any suggestions on things to try?

-------------------------------------------------------------------------------------------------------------------------------------------------------------

sfh_DM644x.exe -flash_noubl -targetType DM6446 -flashType NOR -v -p
COM1 u-boot_develop.bin
-----------------------------------------------------
   TI Serial Flasher Host Program for DM644x
   (C) 2010, Texas Instruments, Inc.
   Ver. 1.67
-----------------------------------------------------


Flashing single boot image: u-boot_develop.bin. the NOR flash device on the DM6446

Attempting to connect to device COM1...
Press any key to end this program at any time.


Waiting for the DM644x...
        Target:  BOOTME
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received. Sending CRC table...
 100% [ ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦ ]
                           CRC table sent.

Waiting for DONE...
        Target:    DONE
DONE received.  Sending the UBL...
 100% [ ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦ ]
                              UBL sent.

        Target:    DONE
DONE received.  UBL was accepted.

Waiting for SFT on the DM644x...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the Application image
Waiting for SENDIMG sequence...
        Target: CFI Query...passed.
        Target: NOR Initialization:
        Target:         Command Set: Intel
        Target:         Manufacturer: INTEL
        Target:         Size: 0x00000020 MB
        Target: SENDIMG
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received.
 100% [ ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦ ]
                  Image data transmitted over UART.

Waiting for DONE...
        Target:    DONE
DONE received.  All bytes of image data received...
        Target: Erasing the NOR Flash
        Target: Erased through 0x02008000
        Target: Erased through 0x02010000
        Target: Erased through 0x02018000
        Target: Erase Completed
        Target: Writing the NOR Flash
        Target: Buffered write failed. Trying normal write
        Target: Normal write also failed
        Target: NOR Write Failed...Aborting!
        Target:         ERROR: Writing NOR failed.
        Target:    FAIL
        Target: BOOTUBL
Command failed, retrying

Waiting for SFT on the DM644x...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the Application image
Waiting for SENDIMG sequence...
        Target: CFI Query...passed.
        Target: NOR Initialization:
        Target:         Command Set: Intel
        Target:         Manufacturer: INTEL
        Target:         Size: 0x00000020 MB
        Target: SENDIMG
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received.
 100% [ ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦ ]
                  Image data transmitted over UART.

Waiting for DONE...
        Target:    DONE
DONE received.  All bytes of image data received...
        Target: Erasing the NOR Flash
        Target: Erase failure at block address 0x02000000
        Target:    FAIL
        Target: BOOTUBL
Command failed, retrying

Waiting for SFT on the DM644x...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the Application image
Waiting for SENDIMG sequence...
        Target: CFI Query...passed.
        Target: NOR Initialization:
        Target:         Command Set: Intel
        Target:         Manufacturer: INTEL
        Target:         Size: 0x00000020 MB
        Target: SENDIMG
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received.
   4% [ ¦¦---------------------------------------------------------- ]
                      Sending image over UART...

 

  • If you have Code Composer Studio (CCS) and an emulator than I would recommend trying the CCS based utility instead, you should be able to find a CCS project within DM644x_FlashAndBootUtils_2_00/DM644x/CCS/NORWriter or a similar directory depending on the version of the utility. The CCS utility project should make it far easier to debug why the flash write is failing since you can more easily see the state of the program when the error happens as well as stepping through.

    Essentially you will probably have to modify the NOR flash driver in the flash and boot utilities package to support your particular NOR device, the CCS project is just the most debug-able means of accessing the code. Note that the CCS utility and the UART boot utility both use the same flash driver source code, so if you can get one working, the other should work as well.

  • Bernie,

    Thanks for the information.  I did try the CCS project in the directory you specified.  When I run that project, I get that the program can not detect my device in the debug window.  I also then ran the .out file that was already compiled and that did work and was able to detect my device.  Unforutnately it failed at writing.  I agree that I need to debug and step through the code, but I need to spend some time to figure out the issue with why the .out works that comes with the download and why my .out from my CCS project doesn't work.

    Can you send me the zip file that you think I should be using (jason.haedt@avnet.com )?  I downloaded the one I have from the Serial Flashing Wiki link. 

    -Jason

  • madtown said:
    When I run that project, I get that the program can not detect my device in the debug window.  I also then ran the .out file that was already compiled and that did work and was able to detect my device.  Unforutnately it failed at writing.

    This is a bit unusual though not out of the question, it sounds like either the original pre built .out file was built using different tools, or that it was from another version of the sources, either way it is a bit concerning but will still require some debugging.

    What version of CCS and code generation tools are you using? Without your custom hardware I cannot do too much to reproduce this, but if I get the exact version of your tools and the flash utility I can try it out on my EVM

    madtown said:
    Can you send me the zip file that you think I should be using (<REDACTED>)?  I downloaded the one I have from the Serial Flashing Wiki link. 

    I don't have a particular recommended version for your purposes, the last time I burned the NOR on a 6446 EVM would have been several years back around DVSDK 1.x and is likely long outdated. In general I would probably just grab the latest version for the device in question from the source forge which appears would be http://sourceforge.net/projects/dvflashutils/files/DM644x/v2.00/ since this is most likely to have the latest improvements in the burning routines (most likely to work with your NOR device easily).

  • Hi,

    I am facing similar problem with serial flasher and NOR flash.

    my NOR part number is PC28F512P30TF.

    Any solutions/pointers how to debug this ?

     

     

  • Hi Harish,

    Did you solve the problem?
    I'm using PC28F256P30TF and facing to the similar problem.

    If you have solved the problem, can you give me an advise?

    best regards,
    g.f.