DM355 EVM Power up/Boot problem?!

The first thing I would recommend is to get the board level "Target-Content" tests from the Spectrum Digital (board manufacturer) site:  http://c6000.spectrumdigital.com/evmdm355/revd/

There you will find board tests for different peripherals such as Ethernet and so on... if you suspect any part of your hardware in bad, this is a good way to verify.  If you do find bad hardware as a result of these tests (not very common), you can fill out the appropriate form at http://www.spectrumdigital.com/ and return (exchange) EVM.  Otherwise, the image in your NAND flash is likely corrupt (assuming SW7 setting is ON-ON) and we will need to reflash the image; you can do this thru the serial UART port (SW7 setting is OFF-OFF) by using the utility in the following wiki article

http://wiki.davincidsp.com/index.php?title=Serial_Boot_and_Flash_Loading_Utility

Ok, here is my question: How can I get the test software onto the board if it does not respond? I must be missing something...

I also tried sfh_DM35x.exe -nanderase but all I got is the following:

-----------------------------------------------------
   TI Serial Flasher Host Program for DM35x
   (C) 2008, Texas Instruments, Inc.
   Ver. 1.10
-----------------------------------------------------


Platform is Windows.
Globally erasing NAND flash.


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


Waiting for the DM35x...
 Aborting program...


Interfacing to the DM35x via UART failed.
Please reset or power-cycle the board and try again...

I ran the program again and power-cycled but the same thing happened.

Thanks for any help.

Amer

1) I should have mentioned that the board tests software is loaded and executed via CCS/JTAG.  Even if your EVM is not responding, you should be able to put EVM in UART boot mode (via SW7) and connect via CCS / JTAG.

2) If you do not have CCS / JTAG, then you can always try reflashing EVM and see if that helps.  When using the serial utility to do this, you need to make sure your EVM is in serial boot mode (via SW7).

Let us know if you continue to have problems.

Thanks for the reply.  Does the free version of CCS load the software or do I have to buy it?  I ordered the free CD anyway.

Using the serial flash utility, here is what I have done so far:

On a command prompt in windows I typed:

sfh_DM35x.exe -nandflash -v ubl_DM35x_nand.bin u-boot-1.2.0-dm355_evm.bin

and I get the following listing:

-----------------------------------------------------
   TI Serial Flasher Host Program for DM35x
   (C) 2008, Texas Instruments, Inc.
   Ver. 1.10
-----------------------------------------------------


Platform is Windows.
Flashing NAND with ubl_DM35x_nand.bin and u-boot-1.2.0-dm355_evm.bin.


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


Waiting for the DM35x...
        Target:  BOOTME
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received. Sending CRC table...
CRC table sent.  Waiting for DONE...
        Target:    DONE
DONE received.  Sending the UBL...
        Target:    DONE
DONE received.  UBL was accepted.
UBL transmitted successfully.

        Target: Chip initialization passed!
        Target: TI SFT Version: 1.10
        Target: Booting Catalog Boot Loader
        Target: BootMode = UART

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the UBL image
Waiting for SENDIMG sequence...
        Target: NAND_open() failed!Starting UART Boot...
        Target: BOOTUBL

Waiting for SFT on the DM35x...

It keeps refreshing but stays at the same point.

Additionally, my question is, when the above wrinkle is ironed out, will I be able to boot the board the default way ie from nand by simply putting SW7 in ON-ON position?

I know I have ways to go before I get there, but what is the minimal hardware required (to minimize board area) that is needed to program a brand new device?

But first things first, why is the flashing getting stuck as above?

Thank you,

Amer

Amer Abufadel said:

Thanks for the reply.  Does the free version of CCS load the software or do I have to buy it?  I ordered the free CD anyway. 

Yes, free CCS version should allow you to load the software.

Amer Abufadel said:

Additionally, my question is, when the above wrinkle is ironed out, will I be able to boot the board the default way ie from nand by simply putting SW7 in ON-ON position?

Yes, you need to put EVM on UART mode to flash via this serial utility, once it is flashed successfully, then putting EVM in NAND boot mode (via SW7) should allow the board to load u-boot.

Amer Abufadel said:

I know I have ways to go before I get there, but what is the minimal hardware required (to minimize board area) that is needed to program a brand new device?

This is a broad question, if you have a utility such as the one above, all you need is UART; optionally, so long as your u-boot does not get corrupt, you can use ethernet to flash everything else (linux kernel, file system, and even u-boot itself), but this is probrably not the safest.  For ease of flashing file-system, and for ease of development phase, most customers will opt for both ethernet and UART port.  Sometimes, you can build a frew boards with these peripherals and use them for development purposes and remove one or both for production purposes.

Amer Abufadel said:

But first things first, why is the flashing getting stuck as above?

mmm,  not sure, but since source code is provided, I would look at the source code for serial utility and determine what step is trying to do when it displays that error.

OK, I got a little further but not much... here is what I am at now:

sfh_DM35x.exe -nandflash ubl_DM35x_nand.bin u-boot-1.2.0-dm355_evm.bin

I get the following:

-----------------------------------------------------
   TI Serial Flasher Host Program for DM35x
   (C) 2008, Texas Instruments, Inc.
   Ver. 1.10
-----------------------------------------------------


Platform is Windows.
Flashing NAND with ubl_DM35x_nand.bin and u-boot-1.2.0-dm355_evm.bin.


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


Waiting for the DM35x...
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received. Sending CRC table...
CRC table sent.  Waiting for DONE...
DONE received.  Sending the UBL...
DONE received.  UBL was accepted.
UBL transmitted successfully.

        Target: Chip initialization passed!
        Target: TI SFT Version: 1.10
        Target: Booting Catalog Boot Loader
        Target: BootMode = UART

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the UBL image
Waiting for SENDIMG sequence...

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the UBL image
Waiting for SENDIMG sequence...

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the UBL image
Waiting for SENDIMG sequence...

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the UBL image
Waiting for SENDIMG sequence...

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the UBL image
Waiting for SENDIMG sequence...

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the UBL image
Waiting for SENDIMG sequence...

Waiting for SFT on the DM35x...

It keeps repeating it over and over..

If I quit the utility without restarting the board, and connect via hyperterminal I see the following:

Starting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBL

Once I reset the board, I see the BOOTME message over and over...

I switch into NAND flash boot which is the default, but no avail...

Any ideas?

Thanks a bunch..

Amer

Which UBL are you using? you should be using the YBL that came with the utility (as opposed to DVSDK); you can use the u-boot that came with DVSDK.  Also, please make rue you do a nanderase first. 

The following command should work

1) sfh_DM35x.exe -nanderase

2) sfh_DM35x.exe -nandflash ubl_DM35x_nand.bin u-boot.bin

Thats what I have been doing, using ubl that came with  the utility and the u-boot from the DVDSK. 

When I issued the nanderase command I got the following:

sfh_DM35x.exe -nanderase

-----------------------------------------------------
   TI Serial Flasher Host Program for DM35x
   (C) 2008, Texas Instruments, Inc.
   Ver. 1.10
-----------------------------------------------------


Platform is Windows.
Globally erasing NAND flash.


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


Waiting for the DM35x...
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received. Sending CRC table...
CRC table sent.  Waiting for DONE...
DONE received.  Sending the UBL...
DONE received.  UBL was accepted.
UBL transmitted successfully.

        Target: Chip initialization passed!
        Target: TI SFT Version: 1.10
        Target: Booting Catalog Boot Loader
        Target: BootMode = UART

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
        Target: NAND_open() failed!Starting UART Boot...
        Target: BOOTUBL

Waiting for SFT on the DM35x...

I never get a prompt to issue the flash command...

What am I doing wrong?

Amer

PS. I got the utility from http://sourceforge.net/project/showfiles.php?group_id=233754

I just tried this myself successfully on my DM355 EVM. Please note that you must use UBL included with utility. Steps below

1) go to wiki site and download utility http://wiki.davincidsp.com/index.php?title=Serial_Boot_and_Flash_Loading_Utility

2) open DOS prompt and go to ...\DM35x_FlashAndBootUtils_1_10\DM35x\GNU

3) copy u-boot file from DVSDK to this directory (e.g. u-boot-1.2.0-dm355_evm.bin from DVSDK 1.30.00.41)

4) With EVM powered off, set SW7 switch on EVM to OFF-OFF, and turn on EVM.

5) Type the following command

  % sfh_DM35x.exe -nanderase

6) if step 5 completes sucessfully (message printed out), power cycle EVM and type the following command

  % sfh_DM35x.exe -nandflash ubl\ubl_DM35x_nand.bin u-boot-1.2.0-dm355_evm.bin   (note we use UBL included w/ utility)

7) power off EVM, set SW7 on EVM to ON-ON.

8) Open serial terminal utility (e.g. teraterm, hyperterm...) and power ON EVM. You should see u-boot loading. At this point, you can use u-boot to flash Linux Kernel.

Thanks for trying to help.

I had been doing what you told me and I redid what you said. 

Step 5 in your post gives me the following:

-----------------------------------------------------
   TI Serial Flasher Host Program for DM35x
   (C) 2008, Texas Instruments, Inc.
   Ver. 1.10
-----------------------------------------------------


Platform is Windows.
Globally erasing NAND flash.


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


Waiting for the DM35x...
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received. Sending CRC table...
CRC table sent.  Waiting for DONE...
DONE received.  Sending the UBL...
DONE received.  UBL was accepted.
UBL transmitted successfully.

        Target: Chip initialization passed!
        Target: TI SFT Version: 1.10
        Target: Booting Catalog Boot Loader
        Target: BootMode = UART

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
        Target: NAND_open() failed!Starting UART Boot...
        Target: BOOTUBL

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
        Target: NAND_open() failed!Starting UART Boot...
        Target: BOOTUBL

Waiting for SFT on the DM35x...

And I have to press any key to abort because it gets stuck Waiting for SFT.

What message does it give you after nanderase succeeds? 

Thank you.

I'm also having the same exact issue with the "Waiting for SFT on the DM35x.." (I'm using the u-boot ubl from the DVSDK CD, which is 1.30.00.23 and not 1.30.00.41 and the current ubl_DM35x_nand.bin from the Utility.) Not sure if that is a potential issue?

Juan - Could you expand on the compiling procedure for the makefile's? I never used the csc.exe or the cygwin environment make command  for these host executables. Could this be the issue?

Nathan Evans

Nathan,

I believe you only need to compile if you are using the loader.   Since I was only interested in flashing new u-boot on the EVM, I used the flasher part of the utility.  I did not rebuilt anything, but used the pre-built binaries included in the ...\DM35x_FlashAndBootUtils_1_10\DM35x\GNU

I hope this helps.

It only helps in the fact that I don't need to look into compiling the makefile with cygwin.

It seems that we are following the same procedure then, but I'm still having an SFT error. Would Brad Griffis have any insight into this SFT issue?

This would almost suggest that either RBL or UBL (provided by utility) residing on EVM side is not responding correctly.  What silicon version do you have (may have different RBL version)? WIth regards to UBL, it should be the same since it comes from the same utility, unless your NAND flash is bad.

Have you tried running the target content tetst on SD site ( http://c6000.spectrumdigital.com/evmdm355/revd/ ) to ensure the hardware is working properly.

My silicon version is D.  I will be getting a blank nand flash by the end of the week and will test it.

How do I run the target content tests when I am getting the SFT error?  Mind you I do not have CC yet.

Thank you,

a

The Chipset I have on the EVM (Which is on demo to us from our local AvNet Office) is:

TMX320           DM355ZWK          $4A-78AD3EW       E1

From the Silicon Errata, I believe that the silicon revision is $4A and the TMX indicates this is a prototype DM355 chipset. I have not tested the board hardware with the target content tests, as it seems I need CCS and an emulator. I'm downloading the eval version of CCS 3.3 and tracking down an XDS510 USB emulator to conduct these tests this morning.

I noticed from other posts that another person had a similar issue and the flash socket was this issue. When I opened the TSOP48 socket to verify the orientation and condition of the flash I also noticed the locking mechanism side was loose at the hinge. I will troubleshoot this with the target content tests, but I cannot find a guide on how to execute these tests. There is nothing from Spectrum Digital available. Have you run these tests on your EVM?

Thanks,

The Target Content tests are essentially CCS projects; you need CCS and a JTAG to run them.

Nathan Evans said:

The Chipset I have on the EVM (Which is on demo to us from our local AvNet Office) is:

TMX320           DM355ZWK          $4A-78AD3EW       E1

It appears I have the same silicon as you and I was able to flash u-boot successfully; maybe this does have to do with loose sockets on some boards.... Does your log show sucessful completion and you simply cannot see anything in the serial terminal after flashing new u-boot, or do you get failures during the boot process?

Amer Abufadel said:

What message does it give you after nanderase succeeds? 

Platform is Windows.
Globally erasing NAND flash.

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

Waiting for the DM35x...
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received. Sending CRC table...
CRC table sent.  Waiting for DONE...
DONE received.  Sending the UBL...
DONE received.  UBL was accepted.
UBL transmitted successfully.

        Target: Chip initialization passed!
        Target: TI SFT Version: 1.10
        Target: Booting Catalog Boot Loader
        Target: BootMode = UART

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
        Target: Unprotecting blocks 0x00000001 through 0x00000031.
        Target: Erasing block 0x00000001 through 0x00000031.
        Target: Erase completed successfully.
        Target: Protecting the entire NAND flash.
        Target:    DONE
        Target:    DONE

Operation completed successfully.

I do have a loose socket door.  Essentially, the "longer" door comes out of the hinge when I open it.  Is this what you mean by loose socket?

I get successful transmission of UBL but then it fails like the following

BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received. Sending CRC table...
CRC table sent.  Waiting for DONE...
DONE received.  Sending the UBL...
DONE received.  UBL was accepted.
UBL transmitted successfully.

        Target: Chip initialization passed!
        Target: TI SFT Version: 1.10
        Target: Booting Catalog Boot Loader
        Target: BootMode = UART

Waiting for SFT on the DM35x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
        Target: NAND_open() failed!Starting UART Boot...
        Target: BOOTUBL

Its as if the nand chip is not there....

Sucess!!!!

It has everything to do with the flash socket. Simply add pressure (with a finger) to the hinge side opposite from the processor and the "Waiting for SFT" hold up is eliminated. I was able to nand erase and re-flash sucessfully.

Nathan Evans

Nathan Evans said:

Sucess!!!!

It has everything to do with the flash socket. Simply add pressure (with a finger) to the hinge side opposite from the processor and the "Waiting for SFT" hold up is eliminated. I was able to nand erase and re-flash sucessfully.

This is great news!  I was beginning to wonder why some customers where having trouble with this.  This certainly helps explain why many of us are not seeing the wainting for SFT issue.

Juan - I was getting the "Waiting for SFT" repeated message exactly like Amer was. I was unable to even execute and -nanderase operation, let alone try and re-flash the NAND flash. The symptom was nothing in the terminal window when the SW7 was booting from NAND (normal operation). When the SW7 was booting from UART, the NAND flash was not communicating with the sfh_DM35x.exe host terminal program because of the loose socket connection of the Flash.

Can you boot from the flashed device?

Alex said:

Can you boot from the flashed device?

I have been able to boot successfully after flashing via this utility (I know other colleages that have as well).  It would be great if Nathan can confirm is he is able to boot via newly flashed u-boot.

Yes, I can confirm that as well! 

It was so frustrating for a beginner like me to try to figure out if it were my fault or something else.

I guess I will be sending the board to SD for repair, unless there is another suggestion.  If thats the case, does anyone know the turnaround time for something like this?

Thank you!!

Amer

do you use a custom flash or the flash provied with the board?
Can somebody confirm if my 29F16G08MAA Flash will work with shipped u-boot and ubl from flashtool?
afiak is there only another temperature range to the flash provied with the board.

i have 0-70°C and the boards original flash had -40°C - 85°C

Also pressure to the Flash didnt work while booting. Cause i can erase and flash it without any finger at to door...
I also switched SW7 back to NandBoot. DS22 is lit but nothing to see in hyper terminal...

Alex,

If you are using a different NAND part, the first thing I would do is refer to the ARM subsystem Guide (http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&familyId=1446&abstractName=sprufb3) for the list of NAND devices supported by the RBL to make sure your device ID is listed there. 

If it is supported, there is still the question of whether the software tools support that particular NAND part.  Although the utility sypports a few NAND devices, we only test with the NAND device present on our EVM; we provide the source code as-is so customers can modify it to suit their particular needs.  Therefore, it is certainly a possibility that your NAND device may not be supported by this utility; maybe looking at the source code could offer some insights.

Amer Abufadel said:

I guess I will be sending the board to SD for repair, unless there is another suggestion.  If thats the case, does anyone know the turnaround time for something like this?

Amer,

I am not sure how long SD will take to return a board to you; but you can send them a quick e-mail before shipping the board if you are concerned.

I was able to succesfully boot after flashing with this utility, but I'm getting a "bad CRC of NAND, using default environment" error when the auto-boot executes. So I'm going to restore the bootloader and kernel image using U-boot, becasue that functionality works and verify the environmental variables. I would assume this is only my issue as this is a shared demo board.

I'm planning on placing a piece of Kapton tape over the flash socket for the time being to hold it down, but this is because my board is only on demo to me.

I am also getting the bad CRC of NAND error....  I will be sending it to Spectrum for repair.

Amer Abufadel said:

I am also getting the bad CRC of NAND error....  I will be sending it to Spectrum for repair.

I believe the bad CRC is always displayed initially aftar flashing new u-boot; however, after you 'saveenv' once within u-boot, this error should go away.

Juan Gonzales said:

If you are using a different NAND part, the first thing I would do is refer to the ARM subsystem Guide (http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&familyId=1446&abstractName=sprufb3) for the list of NAND devices supported by the RBL to make sure your device ID is listed there. 

Hm anotehr difference i have noticed is the fact, the the TI Board uses a SLC Flash Device. My new one is a MLC Device, i could imagine this is the point why the Board wont boot?
I will order now some SLC Devices, such es the TI Board uses and try again.

Alex

Hm OK
its very difficult to find a place where i can buy those Chip...
Do you have any idea where to order those?

Alex

Alex,

I believe you are correct that most, if not all, the device IDs listed in the table in ARM Subsystem Guide are SLC devices.  The safest thing is to go by the device IDs listed. 

That said, I would not know where to purchase SLC devices; there is a B.O.M. document in the Spectrum Digital site (http://c6000.spectrumdigital.com/evmdm355/revd/), but I do not belive it lists supplier.  Perhaps you can send an e-mail to spectrum digital support (they manufacture these boards for us) and they may be able to point you in the right direction.