Tool/software: Linux
Hi,
I have built Linux for the K2HX EVM using Yocto. The SDK version is 05.02.00.10.
I can successfully load U-Boot into RAM using CCS and run it on the board. I can also have U-Boot load files over TFTP. My aim is to load Linux to the board over TFTP/NFS and then run it. I have tried following guides I have found on the internet, but whatever I do, I always run into some problem.
It seems to me that when configured for ramfs boot, U-Boot wants to load four files over TFTP.
First, along with the BOOTP request, it wants a file referred to as "bootfile". What am I supposed to give it at that point? Or should I give nothing and let it just say "file not found"? One interpretation of the guide suggests that I should give it a rootfs image in .gz format, but there is no such file in the Yocto build output.
After that, it apparently wants the monitor, the kernel and the device tree blob.
If I let it load the monitor binary Yocto built, I get a line into the console that looks like a print from the monitor, but then the whole board seems to freeze/crash. If a give it nothing and let it say "file not found", it will proceed to loading the kernel and the dtb file.
If I let it load the zImage Ycto built as kernel, it will say something about starting the kernel and freezes/crashes. If I convert the zImage to uImage, it won't try to start the kernel but instead, gives me the U-Boot prompt.
I have also tried using the prebuilt files that came along with the SDK. U-Boot that came along with the SDK loaded via CSS didn't work at all. Using the U-Boot I had built myself I got to try running the other binaries that came along with the SDK, but they didn't work any better.
What is the detail that I have managed to miss here or is there something bigger that I am doing wrong?
