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.

setup.sh problem

Source and document URL:

http://software-dl.ti.com/dsps/dsps_public_sw/am_bu/sdk/AM335xSDK/latest/index_FDS.html

 

After setting the ti-sdk-am335x-evm-05.03.00.00, I tried to run "sudo ./setup.sh" and I had a problem:

According to the sitara-linuxsdk-sdg-05.03.00.00.pdf (page 29), after asking kernel image in /tftpboot, the script will ask if the user wants to create a minicom script, etc...

The setup.sh stopped short after getting the boot image file name and immediately asking user to flash the NAND ?

======================================================================
Select Linux kernel location:
 1: TFTP
 2: SD card

[ 1 ]

Select root file system location:
 1: NFS
 2: SD card

[ 1 ]

Available kernel images in /tftproot:
    uImage-am335x-evm.bin

Which kernel image do you want to boot from TFTP?
[ uImage-am335x-evm.bin ]
--------------------------------------------------------------------------------
The NAND on the AM335x EVM will be flashed with the previous settings. Please
press enter to begin the flashing process.

 

 

  • Hi Binh,

    The AM335x setup script is slightly different from the previous ones; it assumes that you do want to setup a minicom script and pressing enter will create the script and flash the NAND using the minicom script. The SDG will be updated accordingly to clarify the confusion. When you pressed enter did the NAND flash as expected?

  • Hi Michael,

    I don't have the eval kit.  I'm trying to set up environment to build Linux kernel.

    After I hit Enter, the minicom will stay there since there is no flash to program.  I had to break out the process.

    In my opinion, the set up script should not try to program the flash since this step should be done later when needed.

    Thanks,

    Binh

  • That's fair. I agree with your assesment. The script was created with the expectation the board is connected, but that isn't always valid. We will discuss changing this. Thanks for your feedback.