• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 2181 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.

Question about uboot.env generation

Jeff Wong1
Expert 1305 points

Hi, Kemal and other experts:

I am trying to get uboot.env from the link below:

https://e2e.ti.com/support/arm/sitara_arm/f/791/t/406805


I do see file setupBoard.minicom. Is it correct?

setupBoard.minicom.zip

There are a few questions on the procedures here.

Loading the environment variables from "uEnv.txt" is supported but not preferred in SDK8. It's designed to rely on "uboot.env" instead of "uEnv.txt" therefore setup-uboot-env.sh no more generates "uEnv.txt" and loads it to /boot partition. You can generate "uboot.env" in many ways from U-Boot#, by loading the settings from "setupBoard.minicom" or by using the tool mkenvimage.

You better try to load them from "setupBoard.minicom".

1) first create SDK8 sdcard by # ./create-sdcard.sh and boot-up your board with it.

2) then run ./setup.sh and set-up your tftpboot and NFS preferences, pass 'y' to other choices.

3) when the "bigger 50" message is printed out reboot your board by warm reset button.

Do you mean these message:

Detecting connection to board...
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.


These steps must generate "uboot.env" binary file in your /boot partition.

Do you mean the /boot partition of the SD-card, or some folder in the Ubuntu host PC? I do not find uboot.env generated yet.



It's also still possible to set your variables by "uEnv.txt". You can trim your settings from "setupBoard.minicom" and shape your "uEnv.txt".

Thanks for your replies

  • 0
    TI__Guru 55345 points

    The "bigger 50" message will appear in minicom while your device is waiting to be rebooted. You should have working serial connection with the device in order to perform this. When you reboot the device the setupBoard.minicom script will stop the device in U-Boot stage and import the needed settings for NFS boot like serverip, rootpath etc. The penultimate saveenv command from the script will save these custom environment variables and generate uboot.env in you SD card's boot partition where the MLO and u-boot.img resides. You can set these variables without running ./setup.sh by this command:

    minicom -S <SDK bin dir>/setupBoard.minicom -D /dev/ttyUSB1