Linux on Zynq

rdoost

unread,

Jun 4, 2016, 7:10:34 PM6/4/16

to connectal

Hi,

I just came across this project and it looks like it solves a lot of problems I had in Zynq development. Just a question, why not support for Linux on Zynq and only android. How much implementation effort it takes to port this to Linux? Any insights on this is very much appreciated.

Thanks!

John Ankcorn

unread,

Jun 4, 2016, 7:54:14 PM6/4/16

to rdoost, connectal

Hi,

We support both (android+linux) and (ubuntu+linux) on zynq. (Jamey recently added the ubuntu support. Yeah!)

In each case, the linux kernel is used. In user space, the android suite of applications and the ubuntu suite are currently available options.

To me, the android group is quite tidy, easy to do static analysis on and perfect for building embedded devices (both with or without Java). In contrast, the Ubuntu suite matches closely the operation of normal developer desktop machines, so the learning curve to get started is close to zero.

I am not sure that I understood your original question correctly; does this help?

Thanks very much for your questions!

jca

--
You received this message because you are subscribed to the Google Groups "connectal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to connectal+...@googlegroups.com.
To post to this group, send email to conn...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jamey Hicks

unread,

Jun 4, 2016, 8:17:51 PM6/4/16

to j...@alum.mit.edu, rdoost, connectal

Here are the steps to run connectal on ubuntu on zedboard:

1) Install Raspberry Pi 2 Ubuntu 16.04 root image on an SD Card. There will be a vfat and a ext4 partition. You can ignore the stuff that gets installed in the vfat partition.

https://wiki.ubuntu.com/ARM/RaspberryPi

2) git clone git://github.com/cambridgehackers/zynq-boot

cd zynq-boot; make OS=ubuntu zImage zynqdrivers bootbin.zedboard

Install the boot.bin in the vfat partition of the SD Card. It contains the zImage and device tree.

3) Insert the card into the zedboard and it should boot.

4) Copy zynqportal.ko and portalmem.ko to /lib/modules/4.4.0 something and run depmod. insmod zynqportal.ko; insmod portalmem.ko

On your host, cd connectal/examples/simple; make build.zedboard_ubuntu

That will build an arm linux ubuntu.exe which contains a bitstream and which you can run on the zedboard.

rdoost

unread,

Jun 4, 2016, 9:57:57 PM6/4/16

to connectal, j...@alum.mit.edu, d.moh...@gmail.com

Great! thanks for your responses. I have a rather large application codebase working with Xilinx Linux on Zynq that could use PL acceleration. And based on latency results in your paper, connectal could be great for this.

Given the current state of my platform, I guess I just need to make the proper boot files and do the tests you pointed out. One more question, in case I want to use my own PL reference design (not accelerators, I will do those with connectal), do I just need to replace my own tcl and xdc files (and system wrapper) in /bitfiles? I am not sure if I fully understand the relation between the base board bitfile generated in step 2 and the bsv hardware modules we generate in connectal.

Jamey Hicks

unread,

Jun 6, 2016, 1:05:00 PM6/6/16

to rdoost, connectal, j...@alum.mit.edu

We do not include PL bitstreams in boot.bin. We load the bitstream when the application runs. Also, we embed application bitstreams in the "fpgadata" section of the application executable.

An exception to this is the zybo, which requires a bitstream to connect some pins which are required for booting.

Reply all

Reply to author

Forward