I've gotten tired of tftpboot working fine for weeks, then suddenly stop working. I've gotten tired of the Ubuntu nfs working fine for weeks, then on its own independent schedule stop working.
My research into tftpboot says U-Boot doesn't like it when there's other traffic on the network. Well, for two years of development time, I've been connecting my DM6467EVM-derived custom target to my lab's LAN, which is behind a router w/ firewall and has multiple other PC's and MAC's attached. Most times, both tftpboot and nfs work. But then all of a sudden, nothing works well, getting timeouts all the time and totally spoiling my day.
My nfs is hosted by an Ubuntu VM (VMware) on a Windows 7 host. The Windows 7 host has TWO network jacks. I want to try to cable the DM6467EVM target directly to the second, otherwise unused network jack, of the Windows 7 host, then configure the Ubuntu VM to be able to access this in addition to the original network jack, through which it also access files on the Windows 7 host (in and out through the same jack?) such as the CCS codec build.
However, when I move the target's network cable from it's current hub position to the back of my Windows 7 host, it boots U-Boot over and over again, up to 7 times before stopping this repeat. In fact, an earlier trial of plugging the cable into a different network hub did the same thing. WHY MIGHT THIS BE HAPPENING AND HOW DO I STOP IT?
Otherwise, what do I need to do to make this direct connect work? I tried pinging back and forth, but to no avail. I noticed on the Windows 7 host that "ipconfig/all" reported little for that second jack. But when I plugged in a cable to the target, it reported preferred IP address of 192.254.1.40. (This differs from the other jack, with IP address 192.168.xxx.xxx, omitted for security if any). I changed the ipaddr environmental var on the target to be 192.254.1.19. But when I ping 192.254.1.40 from the target, it can't find it. And when I ping 192.254.1.19 from the Windows 7 host I can't find the target. This worked in the past under the other network config. (Of course, I can't get back to that working state now either.)
...confused... tired...