Talk:GSG: DM6467 DVEVM Additional Procedures

Comments on GSG: DM6467 DVEVM Additional Procedures

---

Rabler said ...

Had trouble getting it to work with the rootpath as a variable, perhaps because my dhcp returned a blank "rootpath="? Embedding the actual rootpath directly in the bootargs solved the problem.

--Rabler 14:52, 18 February 2011 (CST)

HelmutForren said ...

I agree with Rabler. It's clear as day. My system wouldn't boot to root on NFS when I had the macros. It does when I hard code the values. Note that in the middle of my console log, there was an output:

IP-Config: Complete:

    device=eth0, addr=192.168.123.15, mask=255.255.255.0, gw=192.168.123.33,
    host=192.168.123.15, domain=domain.invalid, nis-domain=(none),
    bootserver=192.168.123.33, rootserver=192.168.123.33, rootpath=

That has rootserver pointing to my LAN router (.33). After removing the macros, I instead got:

IP-Config: Complete:

    device=eth0, addr=192.168.123.19, mask=255.255.255.0, gw=192.168.123.33,

    host=192.168.123.19, domain=domain.invalid, nis-domain=(none),

    bootserver=192.168.123.33, rootserver=192.168.123.18, rootpath=

Where bootserver still points to the router, but more importantly rootserver is correct. rootpath blank doesn't enter in the equation, I guess, if there are no macros used in bootargs.

P.S. Could be use of curly braces instead of round braces that was the problem

--HelmutForren 17:08, 28 February 2011 (CST)

Tom.gerardy said ...

I'm having trouble with the section Booting via TFTP Using the EVM’s Hard Drive File System The problem seems to be with the bootcmd setting and in particular the dhcp piece. Dhcp on my network is setup to tell windows machines how to boot from the network which is totally the wrong thing here! We either need instructions to setup a private network with its own DHCP server setup the way we need or we need to change that command. Unfortunately, I'm not a uboot expert (yet), but a little searching on the web suggested tftpboot was the right thing to use. So my suggestion for the bootcmd setting is: EVM # setenv bootcmd 'tftpboot <tftp server ip address>:<kernel image>; bootm'

This seems to work although it still behaves differently than the flash image using the image built during setup.

--Tom.gerardy 10:16, 25 April 2013 (CDT)