FPGA Reference Design Linux Image

iulia  Hi Julia, the last update to this page came from you. Is there any other update in another link?

ForrestGumpCa what aspect is missing? If you are looking for the rootfs generation its linked in the page and points here https://wiki.analog.com/resources/tools-software/linux-build/generic/buildroot 

-Travis

 Hi ForrestGumpCa ,

My update was just adding the warning that the page has been moved at a different address, and that guide is outdated. Please note as well the big warning at the beginning of the page.

Still, even with the old guide, you should still be able to generate it, as the steps are the same.

Best regards,
Iulia

Existing steps generates the "elf" file and leave it there. SD Card Image is a collection of files and "elf" file is not one of them. 

Existing steps generates the "elf" file and leave it there. SD Card Image is a collection of files and "elf" file is not one of them.

I'm under the assumption you are using VCU118 as you are pointing to the microblaze doc which has no SD card. ELF files are loaded as demonstrated on the page.

Am I missing something?

-Travis

How can a Linux system function without a root file system?

At the bottom of the referenced page, there’s a request for help in creating a Linux image—but this raises some important questions that need clarification.

What exactly is running in this setup?
Is it just the Linux kernel on its own?
Is it handling only a single interrupt?
Is there just one driver performing all the required tasks?

If so, and the driver is doing everything expected without user space or a full system stack—then what’s the point of using Linux at all?

ForrestGumpCa said:

How can a Linux system function without a root file system?

It does have one and runs out of memory. This is primarily why loading the system takes a while over JTAG. This is what the "rootfs.cpio.gz" file does.

ForrestGumpCa said:

What exactly is running in this setup?

The ADI Kernel but a buildroot userspace.Look at the microblaze_adi_rootfs_defconfig configuration within the buildroot repo to see what exactly is enabled.

ForrestGumpCa said:

Is it just the Linux kernel on its own?

No

ForrestGumpCa said:

Is it handling only a single interrupt?

If you want detailed information about the interrupt handling of Microblaze you will need to go to AMD.

ForrestGumpCa said:

Is there just one driver performing all the required tasks?

No. There are many drivers enabled that not only manage the AD9082-FMC but also the HDL IP and components within the microblaze. For example the networking stack.

ForrestGumpCa said:

If so, and the driver is doing everything expected without user space or a full system stack—then what’s the point of using Linux at all?

Without a userspace there is nothing really to interact with the system once running. If you purely interacted with the system through say the FPGA logic side then in theory that would be fine. But any runtime control you need through the AD9082 API or similar drivers would not be possible.

-Travis