Smallest configuration memory for Cyclon V SE SoC

[Altera_Forum]

Hi, I am currently designing a product(well, not me, I am just a student in an internship that was put on a project), and one of our option is to use a Cyclon V SE so we get an ARM cortex running linux for some network task. 

 But its currently unclear if the smallest configuration memory we could use is the EPCQ64 or the EPCQ32.  According to the Cyclone V Device datasheet page 78 (https://www.altera.com/content/dam/altera-www/global/en_us/pdfs/literature/hb/cyclone-v/cv_51002.pdf) : The smallest Cyclone V SE, A2, has a Configuration .rbf Size (bits) of 33,958,560 bits.  According to this page : https://documentation.altera.com/#/00021046-AA$AA00050621 EPCQ64 is 67,108,864 bits EPCQ32 is 33,554,432 bits  According to the number, the EPCQ32 is too small of about 404,128 bits. But since the number are pretty close, 33,958,560 bits VS 33,554,432 bits, I was wondering if the extra 404,128 bits is just some sort of header for the file for quartus or the programmer to do its job correctly, or if that extra data is really stored inside the memory.  Strangely, posting reply doesn't seem to work.  My current project need to gather many LVDS and transmit those data over ethernet. My plan: FPGA do data acquisition, HPS do ethernet thing. About memory, what would be the cheapest option for Linux + gcc + ethernet? Which memory size do i need? Which memory medium shall I use? SD card or emmc or some sort of flash? Does this one may work? : http://www.digikey.ca/product-search/en?mpart=s25fl128sagnfi000&v=1274

[Altera_Forum]

The Cyclone V SoC chips are configured by default from the same SD card or serial flash that holds the Linux kernel and file system image. There is no need for a separate configuration chip unless you want it to boot a few seconds faster. If you do decide to use a separate configuration chip, you will need the bigger one. Note that some (but not all) non Altera serial flash chips can also be used to hold Cyclone V configuration images.

[Altera_Forum]

--- Quote Start ---  The Cyclone V SoC chips are configured by default from the same SD card or serial flash that holds the Linux kernel and file system image. There is no need for a separate configuration chip unless you want it to boot a few seconds faster. If you do decide to use a separate configuration chip, you will need the bigger one. Note that some (but not all) non Altera serial flash chips can also be used to hold Cyclone V configuration images.  --- Quote End ---    Thanks, its what i realized yesterday, after work, that i could just let linux boot it. This poppout another question ; What would be the cheapest way to boot the board (linux side) Should i use SD card? Can this flash be used to hold linux and the bitstream? (http://www.digikey.com/product-search/en?lang=en&site=us&wt.z_cid=ref_findchips_standard&mpart=ksz9021gq). It is the chip used on a digilent board with a zynq.  What is the expected size for a linux distro with gcc + network stack?  My current application is to acquire many LVDS channel, transfer the data to HPS, and from there, use the easy to use Linux network stack to send data trough either UDP or TCP/IP. I am trying to keep cost low.

[Altera_Forum]

This is what i tough after work, that i could use the HPS to boot Linux and bypass the configuration memory. It then open up the door to another question: 

 The final product need to be able to convert multiple LVDS stream into an Ethernet stream (still not sure if UDP or TCP). So i could do the data acquisation with the FPGA side, then share it to the HPS side, and let the Linux stack network handle the ethernet. What would be the cheapest option for this? Linux + GCC + Bitstream + small network application? SD card? Emmc? some sort of flash memory? Which size? Would this memory work? : http://www.digikey.ca/product-search/en?mpart=s25fl128sagnfi000&v=1274 (The same one as used on the Zymbo board from digilent)

[Altera_Forum]

Simplest would be a micro SD. If you use an on board serial flash, you will need to program each of your boards which is slow. With an SD or micro SD, you can program several at the same time on a PC and just slot them into the board. The default software is set up to boot that way so no engineering hoops to jump through to configure everything differently to boot from serial flash. Also, SD cards hold much more data than serial flash and are much faster.