所遇到的问题：
1. 脚本要求清除EMMC中的MLO文件，请问清除后am335x从何处加载MLO和u-boot呢？
2.按照脚本使用说明清除MLO文件后，配置TFTP NFS模式，最终执行minicom脚本，串口没有任何信息打印，板子无法启动
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.
所遇到的问题：
1. 脚本要求清除EMMC中的MLO文件，请问清除后am335x从何处加载MLO和u-boot呢？
2.按照脚本使用说明清除MLO文件后，配置TFTP NFS模式，最终执行minicom脚本，串口没有任何信息打印，板子无法启动
1、需要重新烧写MLO和UBOOT，BBB板中擦除的是预烧写好的Angstrom distribution.
2、是重新烧写后仍然无法启动吗？请问参考的是哪部分内容？
-------------------------------------------------------------------------------
TISDK setup script
This script will set up your development host for SDK development.
Parts of this script require administrator priviliges (sudo access).
-------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 18.04 LTS is being used, continuing..
--------------------------------------------------------------------------------
Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group.
A user must be apart of this group to have the proper permissions to access a serial device.
User 'user' is already apart of the 'dialout' group
-------------------------------------------------------------------------------
setup package script
This script will make sure you have the proper host support packages installed
This script requires administrator priviliges (sudo access) if packages are to be installed.
-------------------------------------------------------------------------------
System has required packages!
--------------------------------------------------------------------------------
Package verification and installation successfully completed
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /home/user/ti-processor-sdk-linux-am335x-evm-08.02.00.24/targetNFS ]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/user/ti-processor-sdk-linux-am335x-evm-08.02.00.24/targetNFS
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/user/ti-processor-sdk-linux-am335x-evm-08.02.00.24/targetNFS already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r] s
Skipping filesystem extraction
WARNING! Keeping the previous filesystem may cause compatibility problems if you are upgrading the SDK
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
This step will set up the SDK to install binaries in to:
/home/user/ti-processor-sdk-linux-am335x-evm-08.02.00.24/targetNFS/home/root/am335x-evm
The files will be available from /home/root/am335x-evm on the target.
This setting can be changed later by editing Rules.make and changing the
EXEC_DIR or DESTDIR variable (depending on your SDK).
Press return to continue
Rules.make edited successfully..
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
This step will export your target filesystem for NFS access.
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/user/ti-processor-sdk-linux-am335x-evm-08.02.00.24/targetNFS already NFS exported, skipping..
[sudo] password for user:
Stopping nfs-kernel-server (via systemctl): nfs-kernel-server.service.
Starting nfs-kernel-server (via systemctl): nfs-kernel-server.service.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Which directory do you want to be your tftp root directory?(if this directory does not exist it will be created for you)
[ /tftpboot ]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
This step will set up the tftp server in the /tftpboot directory.
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/tftpboot already exists, not creating..
Successfully copied *Image-am335x-evm.bin to tftp root directory /tftpboot
Successfully copied am335x-bone-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-boneblack-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-boneblack.dtb to tftp root directory /tftpboot
Successfully copied am335x-boneblack-wireless-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-boneblack-wireless.dtb to tftp root directory /tftpboot
Successfully copied am335x-boneblue-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-boneblue.dtb to tftp root directory /tftpboot
Successfully copied am335x-bone.dtb to tftp root directory /tftpboot
Successfully copied am335x-bonegreen-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-bonegreen.dtb to tftp root directory /tftpboot
Successfully copied am335x-bonegreen-wireless-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-bonegreen-wireless.dtb to tftp root directory /tftpboot
Successfully copied am335x-evm-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-evmsk-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-evmsk.dtb to tftp root directory /tftpboot
Successfully copied am335x-icev2-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-icev2.dtb to tftp root directory /tftpboot
Successfully copied am335x-pocketbeagle-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-pocketbeagle.dtb to tftp root directory /tftpboot
Successfully copied am335x-sancloud-bbe-am335x-evm.dtb to tftp root directory /tftpboot
Successfully copied am335x-sancloud-bbe.dtb to tftp root directory /tftpboot
ls: cannot access '*.dtbo': No such file or directory
/etc/xinetd.d/tftp already exists..
/tftpboot already exported for TFTP, skipping..
Restarting tftp server
Stopping xinetd (via systemctl): xinetd.service.
Starting xinetd (via systemctl): xinetd.service.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------"
This step will set up minicom (serial communication application) for
SDK development
For boards that contain a USB-to-Serial converter on the board such as:
* BeagleBone
* Beaglebone Black
* AM335x EVM-SK
* AM57xx EVM
* K2H, K2L, and K2E EVMs
the port used for minicom will be automatically detected. By default Ubuntu
will not recognize this device. Setup will add a udev rule to
/etc/udev/ so that from now on it will be recognized as soon as the board is
plugged in.
For other boards, the serial will defualt to /dev/ttyS0. Please update based
on your setup.
--------------------------------------------------------------------------------
NOTE: If your using any of the above boards simply hit enter
and the correct port will be determined automatically at a
later step. For all other boards select the serial port
that the board is connected to.
Which serial port do you want to use with minicom?
[ /dev/ttyS0 ] /dev/ttyUSB0
Copied existing /home/user/.minirc.dfl to /home/user/.minirc.dfl.old
Configuration saved to /home/user/.minirc.dfl. You can change it further from inside
minicom, see the Software Development Guide for more information.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
This step will set up the U-Boot variables for booting the EVM.
Autodetected the following ip address of your host, correct it if necessary
[ 192.168.70.16
192.168.6.1
192.168.7.1 ] 192.168.70.16
Select Linux kernel location:
1: TFTP
2: SD card
[ 1 ] 1
Select root file system location:
1: NFS
2: SD card
[ 1 ] 1
Available kernel images in /tftproot:
am335x-bone-am335x-evm.dtb
am335x-bone.dtb
am335x-boneblack-am335x-evm.dtb
am335x-boneblack-wireless-am335x-evm.dtb
am335x-boneblack-wireless.dtb
am335x-boneblack.dtb
am335x-boneblue-am335x-evm.dtb
am335x-boneblue.dtb
am335x-bonegreen-am335x-evm.dtb
am335x-bonegreen-wireless-am335x-evm.dtb
am335x-bonegreen-wireless.dtb
am335x-bonegreen.dtb
am335x-evm-am335x-evm.dtb
am335x-evm.dtb
am335x-evmsk-am335x-evm.dtb
am335x-evmsk.dtb
am335x-icev2-am335x-evm.dtb
am335x-icev2.dtb
am335x-pocketbeagle-am335x-evm.dtb
am335x-pocketbeagle.dtb
am335x-sancloud-bbe-am335x-evm.dtb
am335x-sancloud-bbe.dtb
zImage-am335x-evm.bin
Which kernel image do you want to boot from TFTP?
[ zImage-am335x-evm.bin ] am335x-boneblack.dtb
--------------------------------------------------------------------------------
Would you like to create a minicom script with the above parameters (y/n)?
[ y ] y
Successfully wrote /home/user/ti-processor-sdk-linux-am335x-evm-08.02.00.24/bin/setupBoard.minicom
No BeagleBone (Black) or StarterKit detected. Assuming
general purpose evm is being used. Is this correct?
(y/n) y
Would you like to run the setup script now (y/n)? For the general purpose evm
you must now connect the RS-232 cable to your evm now. For the Beaglebone (Black)
or StarterKit this step should of already have been done. Also connect the ethernet
cable as described in the Quick Start Guide.
**Important**
Once answering 'y' on the prompt below you will have 300 seconds to turn on the
board or if it was already on reboot the board before the setup times out
After successfully executing this script, your board will be set up. You will be
able to connect to it by executing 'minicom -w' or if you prefer a windows host
you can set up Tera Term as explained in the Software Developer's Guide.
If you connect minicom or Tera Term and power cycle the board Linux will boot.
[ y ] y
minicom: cannot open /dev/modem: No such file or directory
/home/user/ti-processor-sdk-linux-am335x-evm-08.02.00.24
You can manually run minicom in the future with this setup script using: minicom -S ./bin/setupBoard.minicom
--------------------------------------------------------------------------------
-------------------------------------------------------------------------------
TISDK setup completed!
Please continue reading the Software Developer's Guide for more information on
how to develop software on the EVM
-------------------------------------------------------------------------------