Thanks Marc, John and David.
I set ROACH board environment same as a working board, now its working.
Thanks & Regards,
Bela
On Sat, May 12, 2018 at 1:13 AM, John Ford wrote:
> Hi Bela.
>
> The non-working one looks to be set up to boot from flash, not the
> network. I
Hi Bela.
The non-working one looks to be set up to boot from flash, not the
network. I think to get it to boot over the network you will have to set
up the environment to have the correct information to be able to find its
NFS mounted root, and the other networking stuff that is needed. You can
Well, bootcmd is what gets run by default, and it differs quite a bit
on the working system - there it specifies the address of an nfs
server.
You could try to run these things manually in parts - first the dhcp,
then the setenv and then the bootm command. Make sure that the
bootargs contain the
Thanks Devid and Marc.
Working ROACH2 not giving "bad CRC" warning.
I tried with printenv command to check environment variable there is
difference between working and non-working board. Please find attached file
of printenv output of working and non-working board.
Thanks & Regards,
Bela
On
As uboot starts up, interrupt the boot to get the uboot prompt. Then
run a printenv command and compare it to the other working roach. If
the configuration is bad, you might not have a useful kernel command
line or mac address available - the latter is need for the network
interface to be
Hi, Bela,
I'm not sure what the problem is, but I can offer a few comments that might be
helpful...
> On May 8, 2018, at 22:50, Bela Dixit wrote:
>
> U-Boot 2011.06-rc2-0-gd422dc0-dirty (Nov 08 2012 - 16:04:14)
>
> CPU: AMCC PowerPC 440EPx Rev. A at 533.333 MHz
Hi CASPERites,
I get a problem when I try to boot ROACH2 via netboot. I tried anther
ROACH2 board with same machine, it successfully booted. The complete log
message dumped on minicom during the boot procedure is reported at the end
of this email.
Kindly help me to fix the problem.
Thanks &
Dear John, Bob and Peter,
I apologize for the belated replay and thanks a lot for your suggestions.
We believe the problem was not related to ownership and permissions but,
instead, related to the xfs file system.
In fact, at boot the ROACH2 nfs client uses by default the NFSv2 protocol
to mount
8 matches
Mail list logo