issue booting from network with u-boot on RIotBoard

[jyriot]

Hi all,

I am using a Riotboard and I created a complete BSP with buildroot version 2016.05 with success.

I flashed the images (u-boot, the dtb file, kernel image and tarball) successfully with MfgTool2 on eMMC media.

The board startup successfully, at this part the configuration is ok for me.

After that I would like to start in network mode, so I created an NFS server on my virtual machine.

The u-boot version I used is the default version proposed by buildroot -> 2015.10

I set these environment variable for u-boot:

ethaddr, ipaddr, serverip, netmask

=> note the there is a first issue with saveenv because after a reset the u-boot won't start.

when I type run netboot or ping and address I have this message:

ARP Retry count exceeded

I tried many version of the u-boot with the same environment. Finally with u-boot.2013.04 I can ping and start from network. This asserting that my configuration for NFS and network is correct (I use fixed IP addresses). But the version 2013.04 of u-boot make many timeouts during tftp transfers.

My question is: what is missing in the recent version of u-boot, example 2015.10 to let the network functioning?

Thanks for you help, there is a long time I try to resolve this issue, I net to make developments on the Riotboard and flashing each time is not a quick process to me.

Regards,

Jean-Yves.

[gusarambula]

Hello Jean-Yves RIOT,

There is information on NFS booting on the following document:

https://community.nxp.com/docs/DOC-103717

However, I would recommend checking the Element14 Communities on their website in which there may be more resources focused towards the RiotBoard in particular and more users familiar with the board.

https://www.element14.com/community/welcome

Regards,

[jyriot]

Hi,

the question is not about configuration of the system to boot in NFS mode,

the question is the behaviour of the u-boot.2015.10 for example for the

RiotBoard.

I know these two links and I don't found any element to solve the issue.

All I notice is

1 u-boot version 2013.03 can ping my nfs server but tftp transferts

make lot of timeout.

2 newer version of u-boot like 2015.10 don't work with the network: the

ping and tftp transfert abort with "ARP retry count exceded"

So I would like to know if there is nothing forgotten in the u-boot

configuration concerning the RiotBoard to let PHY device working well.

All of the other part of NFS configuration works, and all is ok, the only

problem is with u-boot.

Regards.

2016-10-25 15:49 GMT+02:00 gusarambula <admin@community.freescale.com>:

NXP Community

<https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>

Re: issue booting from network with u-boot on RIotBoard

reply from gusarambula

<https://community.nxp.com/people/gusarambula?et=watches.email.thread> in *i.MX

Community* - View the full discussion

<https://community.nxp.com/message/844645?commentID=844645&et=watches.email.thread#comment-844645>