• State Answer Suggested
  • Locked Locked
  • Replies 16 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 2860 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

uEnv.txt for SD-Card; TFTP BootUp Sequence for v07.00 SDK

Naum Grutman
Prodigy 240 points

I am using the AM335x StarterKit...

I have a couple of issues:

1. I am interested to put together an uEnv.txt to provide the following BootUp sequence:

SD-Card and if that fails to fall back to TFTP ( no NAND; no Flash; nothing extra

if all else fails the CCCC for Serial I/O is just fine but that is gonna come up as a default anyhow )

Using v07.00 SDK with ALL of its components...
via SD-Card BootUp works...
via TFTP it was failing...
so I tried the virgin out the box v07.00 TFTP boot up setup via ./setup-uboot-env.sh
to see that it works sure enough I see that there is a problem

Just for sanity check I tried same exact procedures and setups
on v05.05 result TFTP BootUp works fine
on v06.00 result TFTP BootUp works fine

Same AM335x StarterKit... same cables... same everything in fact hardware is not being touched...
there must be something about v07.00

2. If there is already a proven uEnv.txt for SD-Card; TFTP setup available
it would be appreciated....

I am attaching three traces for v07.00; v06.00; v05.05
and three uEnv.txt built by corresponding ./setup-uboot-env.sh  version scripts.

Thanks,

Naum

5852.AM335x-SK_TFTP_BootUp_v07.00.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
root@Latitude3540:~/ti-sdk-am335x-evm-07.00.00.00/bin# ./setup-uboot-env.sh
--------------------------------------------------------------------------------
This step will set up the u-boot variables for booting the EVM.
Becuase the not all AM335x devices have a NAND, the u-boot variables will
be stored in uEnv.txt on the boot partition. U-boot will read this
file on boot.
Autodetected the following ip address of your host, correct it if necessary
[ 10.5.5.86 ]
Select Linux kernel location:
1: TFTP
2: SD card
[ 1 ] 1
Select root file system location:
1: NFS
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
0576.uEnv_for_v07.00.txt
Fullscreen
1
2
3
4
5
6
serverip=10.5.5.86
rootpath=/home/ngrutman/ti-sdk-am335x-evm-07.00.00.00/targetNFS
bootfile=zImage-am335x-evm.bin
ip_method=dhcp
tftp_nfs_boot=run findfdt; setenv autoload no;dhcp; tftp ${loadaddr} zImage-am335x-evm.bin; run findfdt; tftp ${fdtaddr} ${fdtfile}; run netargs; bootz ${loadaddr} - ${fdtaddr}
uenvcmd=run tftp_nfs_boot
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
7028.AM335x-SK_TFTP_BootUp_v06.00.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
0
mmc0 is current device
SD/MMC found on device 0
reading uEnv.txt
260 bytes read in 3 ms (84 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
Booting from network...
cpsw Waiting for PHY auto negotiation to complete. done
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 10.5.5.93
Using cpsw device
TFTP from server 10.5.5.86; our IP address is 10.5.5.93
Filename 'uImage-am335x-evm.bin'.
Load address: 0x80200000
Loading: #################################################################
#################################################################
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
7028.uEnv_for_v06.00.txt
Fullscreen
1
2
3
4
5
6
serverip=10.5.5.86
rootpath=/home/ngrutman/ti-sdk-am335x-evm-06.00.00.00/targetNFS
bootfile=uImage-am335x-evm.bin
ip_method=dhcp
tftp_nfs_boot=echo Booting from network...; dhcp ${loadaddr} ${bootfile}; run netargs; bootm ${loadaddr}
uenvcmd=run tftp_nfs_boot
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
1643.AM335x-SK_TFTP_BootUp_v05.05.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
U-Boot SPL 2011.09 (Jul 26 2012 - 17:18:20)
Texas Instruments Revision detection unimplemented
No daughter card present
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.09 (Jul 26 2012 - 17:13:38)
I2C: ready
DRAM: 256 MiB
WARNING: Caches not enabled
No daughter card present
NAND: HW ECC Hamming Code selected
No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
0184.uEnv_for_v05.05.txt
Fullscreen
1
2
3
4
5
6
serverip=10.5.5.86
rootpath=/home/ngrutman/ti-sdk-am335x-evm-05.05.00.00/targetNFS
bootfile=uImage-am335x-evm.bin
ip_method=dhcp
tftp_nfs_boot=echo Booting from network...; dhcp ${loadaddr} ${bootfile}; run net_args; bootm ${loadaddr}
uenvcmd=run tftp_nfs_boot
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0
    TI__Guru**** 393215 points

    Hi Naum,

    I will ask the SW team to look at this.

  • 0 in reply to Biser Gatchev-XID
    TI__Expert 4475 points
    Hi Naum,

    1. Boot order is depend how are the SYSBOOT[4:0] pins are powered. For more information please see the Table 26-7. SYSBOOT Configuration Pins from the "AM335x Sitara™ Processors" TRM. From this table I didn't see exactly what you are looking for, but the closest are:
    - SYSBOOT[4:0] - 10101b (NANDI2C -> MMC0 -> EMAC1 -> UART0). This mean that on the Nand should never have a MLO, because the boot ROM first will look for MLO on the NAND.
    - SYSBOOT[4:0] - 11001b (SPI0 -> MMC0 -> EMAC1 -> UART0). Here the same situation, but if you have SPI0, you should never have a MLO.

    2. I'm looked at attached uEvm.txt files and I think that these files are correct.

    BR
    Ivan
  • 0 in reply to Ivan Matrakov
    Prodigy 240 points

    First of all let me reiterate that I am using AM335x Starter Kit

    The point of my forum message is a simple fact that TFTP transfer using the components provided within v07.00 does not work:

    I perform the following steps:

    1. Out of the box installation of v07.00 SDK

    2. Build bootable SDcard using ./create-sdcard.sh.

    3. Booting the AM335x Starter Kit using the SDcard created in above step 2… Boot up works beautiful…

    4. Now I utilize a script provided by TI within ti-sdk-am335x-evm-07.00.00.00/bin called

    ./setup-uboot-env.sh to set up future BootUps via TFTP and that is where the problem is…

    BootUps via TFTP get initiated but do not complete… Boot Up chokes up…

    I gave you a benefit of the doubt and reinstalled v07.00 again from scratch performed above 4 steps again from scratch and the problem still repeats…

    Now I will reiterate again… I do the same exact above 4 steps with v05.05 SDK or v06.00 SDK

    and everything works fine…  

    Boot via TFTP gets setup and works fine using v05.05 Boot Up does not choke up… I get Linux Arago prompt

    Boot via TFTP gets setup and works fine using v06.00 Boot Up does not choke up… I get Linux Arago prompt

    Please review and compare the trace provided for v07.00 and for v06.00 Boot Up at around 3.8 seconds mark…!!!!

    Remember there is no intervention of any kind on my part... I use components as they are provided... within ZIPed SDK

    and images and scripts within those... Again this process works the way I perform it within v05.05 and also within

    v06.00... My logic says it should perform in the same fashion within v07.00

    v07.00_Trace_of_BootUp.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    U-Boot SPL 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
    reading args
    spl: error reading image args, err - -1
    reading u-boot.img
    reading u-boot.img
    U-Boot 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
    I2C: ready
    DRAM: 256 MiB
    NAND: 0 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    *** Error - No Valid Environment Area found
    *** Warning - bad CRC, using default environment
    Net: <ethaddr> not set. Validating first E-fuse MAC
    cpsw, usb_ether
    Hit any key to stop autoboot: 0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    v06.00_Trace_of_BootUp.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    USB Host mode controller at 47401800 using PIO, IRQ 0
    OMAP SD/MMC: 0
    reading u-boot.img
    reading u-boot.img
    U-Boot 2013.01.01 (Jun 25 2013 - 16:42:52)
    I2C: ready
    DRAM: 256 MiB
    WARNING: Caches not enabled
    NAND: No NAND device found!!!
    0 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    *** Warning - readenv() failed, using default environment
    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Naum Grutman
    TI__Guru**** 155911 points

    Naum,

    Do you connect the board to the tftp server through a Ethernet hub/switch? If so, can you please remove the hub and directly connect the board to the PC to see if the DHCP request go through?

  • 0 in reply to Biser Gatchev-XID
    Prodigy 240 points

    I need somebody within your SW team to look at and respond to the heart of the problem  which is TFTP Boot Up chokes up under v07.00

    TFTP Boot Up works fine with v05.05 and 06.00....!!!! Please review traces provided at approx 3.8 seconds mark....

    First of all let me reiterate that I am using AM335x Starter Kit

    The point of my forum message is a simple fact that TFTP transfer using the components provided within v07.00 does not work:

    I perform the following steps:

    1. Out of the box installation of v07.00 SDK

    2. Build bootable SDcard using ./create-sdcard.sh.

    3. Booting the AM335x Starter Kit using the SDcard created in above step 2… Boot up works beautiful…

    4. Now I utilize a script provided by TI within ti-sdk-am335x-evm-07.00.00.00/bin called

    ./setup-uboot-env.sh to set up future BootUps via TFTP and that is where the problem is…

    BootUps via TFTP get initiated but do not complete… Boot Up chokes up…

    I gave you a benefit of the doubt and reinstalled v07.00 again from scratch performed above 4 steps again from scratch and the problem still repeats…

    Now I will reiterate again… I do the same exact above 4 steps with v05.05 SDK or v06.00 SDK

    and everything works fine…  

    Boot via TFTP gets setup and works fine using v05.05 Boot Up does not choke up… I get Linux Arago prompt

    Boot via TFTP gets setup and works fine using v06.00 Boot Up does not choke up… I get Linux Arago prompt

    Please review and compare the trace provided for v07.00 and for v06.00 Boot Up at around 3.8 seconds mark…!!!!

    Remember there is no intervention of any kind on my part... I use components as they are provided... within ZIPed SDK

    and images and scripts within those... Again this process works the way I perform it within v05.05 and also within

    v06.00... My logic says it should perform in the same fashion within v07.00

    1754.v07.00_Trace_of_BootUp.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    U-Boot SPL 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
    reading args
    spl: error reading image args, err - -1
    reading u-boot.img
    reading u-boot.img
    U-Boot 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
    I2C: ready
    DRAM: 256 MiB
    NAND: 0 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    *** Error - No Valid Environment Area found
    *** Warning - bad CRC, using default environment
    Net: <ethaddr> not set. Validating first E-fuse MAC
    cpsw, usb_ether
    Hit any key to stop autoboot: 0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    4478.v06.00_Trace_of_BootUp.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    USB Host mode controller at 47401800 using PIO, IRQ 0
    OMAP SD/MMC: 0
    reading u-boot.img
    reading u-boot.img
    U-Boot 2013.01.01 (Jun 25 2013 - 16:42:52)
    I2C: ready
    DRAM: 256 MiB
    WARNING: Caches not enabled
    NAND: No NAND device found!!!
    0 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    *** Warning - readenv() failed, using default environment
    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Bin Liu
    Prodigy 240 points

    Yes, the AM335x is connected via J6 to the Ethernet switch

    Disconnecting Ethernet cable from the switch and connecting

    it directly to PC does not make sense to me, but since you asked

    I have performed exactly that... connected J6 to PC's ethernet port..

    Here is the resulting trace:

    .

    v07.00_Trace_ConnectedDirect.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    U-Boot SPL 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
    reading args
    spl: error reading image args, err - -1
    reading u-boot.img
    reading u-boot.img
    U-Boot 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
    I2C: ready
    DRAM: 256 MiB
    NAND: 0 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    *** Error - No Valid Environment Area found
    *** Warning - bad CRC, using default environment
    Net: <ethaddr> not set. Validating first E-fuse MAC
    cpsw, usb_ether
    Hit any key to stop autoboot: 0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Naum Grutman
    TI__Guru**** 155911 points

    I asked to test without the switch, because I heard that some cheap switches cause failures, and wanted to narrow down if that was the issue.

    ftfp boot & nfs always works for me. Here is my uEnv.txt for sdk7.0 for your reference.

    svrip=192.168.2.108
ipaddr=192.168.2.103
image=zImage.am335x

rootpath=/home/lb/am335x/filesys

netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},nolock rw ip=${ipaddr}:::::eth0

netboot=run findfdt; tftp ${loadaddr} ${bootfile}; tftp ${fdtaddr} ${fdtfile}; run netargs; bootz ${loadaddr} - ${fdtaddr}

uenvcmd=setenv serverip ${svrip}; setenv ipaddr ${ipaddr}; setenv bootfile ${image}; run netboot
  • 0 in reply to Bin Liu
    Prodigy 240 points


    Hello Bin,

    Everybody that is responding to my concern seems to be missing my point...

    The TFTP Boot and NFS works for me with v05.05 SDK and with v06.00 SDK thru
    1. the same switch;
    2. same cables;
    3. same PC;
    4. same AM335x etc...etc...

    it is the v07.00 SDK release that looks like is having an issue... it is either:
    1. the script that whatever ./setup-uboot-env.sh spits out into uEnv.txt has an issue
    ( even though it looks pretty much the same same as the script from v06.00 ) or
    2. the zImage that v07.00 is OK for SDcard Boot up but when it comes to TFTP there is something internally within zImage a screwed up...

    To me it looks like more like the zImage since TFTP gets initiated but chokes up...
    Look at the traces for v07.00 and v06.00 at around 3.8 seconds mark within attached trace/text files...

    Would it be possible for you to ZIP up your zImage.am335x and either email or make it available on some cloud for me to download and try with it...

    Thanks,

    Naum

    4834.v07.00_Trace_of_BootUp.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    U-Boot SPL 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
    reading args
    spl: error reading image args, err - -1
    reading u-boot.img
    reading u-boot.img
    U-Boot 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
    I2C: ready
    DRAM: 256 MiB
    NAND: 0 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    *** Error - No Valid Environment Area found
    *** Warning - bad CRC, using default environment
    Net: <ethaddr> not set. Validating first E-fuse MAC
    cpsw, usb_ether
    Hit any key to stop autoboot: 0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    3386.v06.00_Trace_of_BootUp.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    USB Host mode controller at 47401800 using PIO, IRQ 0
    OMAP SD/MMC: 0
    reading u-boot.img
    reading u-boot.img
    U-Boot 2013.01.01 (Jun 25 2013 - 16:42:52)
    I2C: ready
    DRAM: 256 MiB
    WARNING: Caches not enabled
    NAND: No NAND device found!!!
    0 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    *** Warning - readenv() failed, using default environment
    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Naum Grutman
    TI__Mastermind 30416 points

    Naum,

    I'm sorry you are having trouble with SDK 7.0. We have a known issue, pointed to below, with solution, that I believe is your problem.

    http://processors.wiki.ti.com/index.php/Cpsw_3_12_dhcp_lease_fail_dual_emac

    Please give this a try and let us know if it solves your problem.

  • 0 in reply to RonB
    Prodigy 240 points
    Ron,

    Thanks for your response... Out of all the previous responses yours looks more to the point...
    Looking and comparing the traces between 6.0 and 7.0 felt like ethernet issue...
    Looking at the proposed patch it seems that this some kind of input to automated process...
    Do you have a pointer or a link to what are the steps of applying proposed patch or any future patches...?

    Thanks,

    Naum
  • 0 in reply to Biser Gatchev-XID
    Prodigy 240 points
    Hello Biser,

    There was a reply from RonB with proposed patch...
    Do you have a pointer or a link to what are the steps of applying proposed patch or any future patches...?

    Thanks,
    Naum
  • 0 in reply to Biser Gatchev-XID
    Prodigy 240 points

    Hello Biser,

    I have narrowed it down to be actually not the TFTP issue

    It is the  targetNFS issue

    If you utilize the  ./setup-uboot-env.sh to setup the uEnv.txt in the form of 2 and 1:

    i.e.

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

    [ 1 ] 2

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

    [ 1 ] 1

    the same issue occurs BootUp chokes up at that same point... again only in v07.00

    the previous versions v06.00 and v05.05 work fine

    Trace is atached:

    AM335x_v07.00_BootUp_with_uEnv_set_as_SDcard_to_NFS.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    root@Latitude3540:~/ti-sdk-am335x-evm-07.00.00.00/bin#
    root@Latitude3540:~/ti-sdk-am335x-evm-07.00.00.00/bin# ./setup-uboot-env.sh
    --------------------------------------------------------------------------------
    This step will set up the u-boot variables for booting the EVM.
    Becuase the not all AM335x devices have a NAND, the u-boot variables will
    be stored in uEnv.txt on the boot partition. U-boot will read this
    file on boot.
    Autodetected the following ip address of your host, correct it if necessary
    [ 10.5.5.86 ]
    Select Linux kernel location:
    1: TFTP
    2: SD card
    [ 1 ] 2
    Select root file system location:
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Bin Liu
    Prodigy 240 points

    Hello Bin,

    I have narrowed it down to be actually not the TFTP issue

    It is the  targetNFS issue

    If you utilize the  ./setup-uboot-env.sh to setup the uEnv.txt in the form of 2 and 1:

    i.e.

    Select Linux kernel location:

    1: TFTP

    2: SD card

    [ 1 ] 2

    Select root file system location:

    1: NFS

    2: SD card

    [ 1 ] 1

    the same issue occurs BootUp chokes up at that same point... again only in v07.00

    the previous versions v06.00 and v05.05 work fine...

    Bin,

    I am curious  Have you applied the patch that RonB mentioned in his reply to your SDK7... ???

    Trace is atached:

    8132.AM335x_v07.00_BootUp_with_uEnv_set_as_SDcard_to_NFS.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    root@Latitude3540:~/ti-sdk-am335x-evm-07.00.00.00/bin#
    root@Latitude3540:~/ti-sdk-am335x-evm-07.00.00.00/bin# ./setup-uboot-env.sh
    --------------------------------------------------------------------------------
    This step will set up the u-boot variables for booting the EVM.
    Becuase the not all AM335x devices have a NAND, the u-boot variables will
    be stored in uEnv.txt on the boot partition. U-boot will read this
    file on boot.
    Autodetected the following ip address of your host, correct it if necessary
    [ 10.5.5.86 ]
    Select Linux kernel location:
    1: TFTP
    2: SD card
    [ 1 ] 2
    Select root file system location:
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Naum Grutman
    TI__Guru**** 155911 points

    Naum Grutman said:
    I am curious  Have you applied the patch that RonB mentioned in his reply to your SDK7... ???

    To apply the patch, please copy and paste the patch from the wiki Ron provided, then use Linux patch command.

    The alternative is if you have checked my uEnv.txt, I use static IP in bootargs to avoid this issue: ip=${ipaddr}:::::eth0.

  • 0 in reply to RonB
    Prodigy 240 points

    Looks like others had similar issues targetNFS with SDK7 way before I got into this subject

    see the following links...

    http://e2e.ti.com/support/arm/sitara_arm/f/791/p/347641/1218748

    http://e2e.ti.com/support/arm/sitara_arm/f/791/t/338842 

    As a help to anybody that has similar issues with SDK7 based zImage-am335x-evm.bin and  targetNFS while

    booting via TFTP the solution is to use portions of SDK8 now that it got released...

    I end up using images: u-boot-spl.bin and u-boot.img  from SDK7 the uEnv.txt that is being built by scripts from SDK7

    and zImage-am335x-evm.bin and targetNFS from SDK8, which is Linux Kernel 3.14 based, and now it works

    like it was supposed to be working within SDK7 and Linux Kernel 3.12  in a first place.

  • 0 in reply to Biser Gatchev-XID
    Prodigy 240 points

    Looks like others had similar TFTP / targetNFS  BootUp issues with SDK7 way before I got into this subject

    see the following links...

    http://e2e.ti.com/support/arm/sitara_arm/f/791/p/347641/1218748

    http://e2e.ti.com/support/arm/sitara_arm/f/791/t/338842 

    As a help to anybody that has similar issues with SDK7 based zImage-am335x-evm.bin and  targetNFS while

    booting via TFTP the solution is to use portions of SDK8 now that it got released...

    I end up using images: u-boot-spl.bin and u-boot.img  from SDK7 the uEnv.txt that is being built by scripts from SDK7

    and zImage-am335x-evm.bin and targetNFS from SDK8, which is Linux Kernel 3.14 based, and now it works

    like it was supposed to be working within SDK7 and Linux Kernel 3.12  in a first place.