This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Booting Linux image via Ethernet on EVMK2H board



Hello,

I've been around with questions in another topic, but it went a bit askew so I thought I'd clarify my intentions and make a new thread.
I would like to test the EVMK2H's (Board Rev 3.0.) ability on booting up Linux via Ethernet on ARM core0. From the KeyStone II Architecture User Guide (Literature Number: SPRUHJ3) I've learnt that the RBL is capable of booting up Linux via Ethernet by setting the bootstrap pins accordingly.
When connecting to the BMC, I select ARM RBL ENET as boot source, configure the TFTP server (TFTPD64) boot file with u-boot-keystone-evm.bin. But when I reboot the board and observe network traffic with Wireshark I can see no requests from the EVMK2H board whatsoever, although the RBL should start the the BOOTP sequence automatically.
My questions regarding these would be:

1. Is setting the BMC boot source to "ARM RBL ENET" equivalent to setting the Keystone II bootstarp pins on Ethernet boot? What are the default boot parameters that can not be set through BMC? (SYS PLL Config, ARM PLL Config, PA clk, etc.)

2. Is it possible with the EVMK2H board to boot up the provided u-boot-keystone-evm.bin U-Boot image?

3. Is .bin the runnable BLOB format and is it run automatically by RBL once the image transfer is finished?

4. After the U-Boot is started (and it is in MCMS), how do I proceed loading a Linux image specifically into DDR memory?

Sorry for not being specific enough on these earlier. Thanks for the help, I appreciate it a lot!

Janos