Dear "Bedia, Vaibhav",
In message FCCFB4CDC6E5564B9182F639FC356087035FBED5FB@dbde02.ent.ti.com you wrote:
In that case how can network boot be supported in U-Boot? Is the expectation that the SPL image which gets downloaded to internal RAM inits SDRAM, relocates to it and then download any other image like a larger U-Boot or the OS image?
Can you please restrict your line length to some 70 or so characters?
At the moment, U-Boot it self assumes that it somehow got started as a whole - either executing from reset (like when booting from NOR flash or similar bootable memory regions), or by being loaded by some secondary loader. So far, we support NAND and OneNAND in such a mode. Especially with NAND the restrictions may be severe - quite often the SPL code has to fit in as little as 4 KiB, sometimes even in 2 KiB.
If you want SPL support for network booting, this needs to be added. I am not sure if this really makes sense, though. Many devices today have ROM code capable of reading boot images from USB or SDCard etc., so these are the "naturally supported" boot modes for such systems. I haven't seen network boot in such a configuration yet.
If you add it, I guess the next steps will be support for WLAN booting and IPv6.
Best regards,
Wolfgang Denk