# Building BOOT.BIN for Zedboard to use with gnuradio-dev-image **URL:** \ **Category:** GNU Radio\ **Created:** [December 9, 2014, 4:29pm UTC](https://www.ruby-forum.com/t/building-boot-bin-for-zedboard-to-use-with-gnuradio-dev-image/233383 "2014-12-09T16:29:14Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\ **Post date:** [December 9, 2014, 4:29pm UTC](https://www.ruby-forum.com/t/building-boot-bin-for-zedboard-to-use-with-gnuradio-dev-image/233383/1 "2014-12-09T16:29:14Z")
I’d like to use the gnuradio openembedded SDK and image that are available here [1] to reproduce the work here [2] without building my own openembedded image. I’m having trouble getting a working boot.bin for Zedboard without doing a full openembedded build. I know that there are licensing issues that may prohibit distributing an FSBL file, but I’ve gone ahead and done that using the directions in [2]. I’d like to compile boot.bin with the zynq\_fsbl.bit I created with Xilinx 14.6, uImage, and the device tree binary distributed in [1]. However, in order to use the build script in zynq-acp, I need u-boot.elf, and [1] only provides u-boot.bin. Is there another way to compile these without doing a full openembedded build? [1] [http://gnuradio.org/data/sdk/zedboard\_armv7a-sf-vfp-neon/](http://gnuradio.org/data/sdk/zedboard_armv7a-sf-vfp-neon/) [2] [http://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq](http://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq) Thanks, Sean ---
**Author:** ![NowlanS\_Sean](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/f05b48/32.png) [@NowlanS\_Sean](https://www.ruby-forum.com/u/NowlanS_Sean)\ **Post date:** [December 9, 2014, 6:17pm UTC](https://www.ruby-forum.com/t/building-boot-bin-for-zedboard-to-use-with-gnuradio-dev-image/233383/2 "2014-12-09T18:17:49Z")
A number of different distributions include a u-boot.elf suitable for the Zedboard. I’m not a linux boot expert, but u-boot seems pretty platform-agnostic when paired with a suitable FSBL. The images here include a u-boot.elf that works with Zedboard, ZC702, ZC706, etc. [http://wiki.analog.com/resources/tools-software/linux-software/zynq\_images](http://wiki.analog.com/resources/tools-software/linux-software/zynq_images) Email me directly and I’ll just send you the .elf if you’re interested. –n On Tue, Dec 9, 2014 at 7:27 AM, Nowlan, Sean [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) ---
**Author:** ![NowlanS\_Sean](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/f05b48/32.png) [@NowlanS\_Sean](https://www.ruby-forum.com/u/NowlanS_Sean)\ **Post date:** [December 9, 2014, 8:00pm UTC](https://www.ruby-forum.com/t/building-boot-bin-for-zedboard-to-use-with-gnuradio-dev-image/233383/3 "2014-12-09T20:00:53Z")
On 12/09/2014 12:16 PM, Nick F. wrote: > A number of different distributions include a u-boot.elf suitable for the > Zedboard. I’m not a linux boot expert, but u-boot seems pretty > platform-agnostic when paired with a suitable FSBL. > > The images here include a u-boot.elf that works with Zedboard, ZC702, > ZC706, etc. > [Analog Devices Kuiper Linux [Analog Devices Wiki]](http://wiki.analog.com/resources/tools-software/linux-software/zynq_images) > > Email me directly and I’ll just send you the .elf if you’re interested. A pox on people using ancient stuff. I think Sean wants to load an fpga image early in the boot process. Try the image I posted a few days ago and drop a file called fpga.bin in the FAT partition. U-boot SPL will load that fpga.bin file then load u-boot. You can now build the fsbl directly from u-boot but dropping the ps7\* files in the right place. (See the OE recipe for how that is done there, and copy if you are building u-boot from Xilinx git) My understanding is the current release of Xilinx tools will give you ps7 files with a license that is compatible with the GPL. Philip ---
**Author:** ![NowlanS\_Sean](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/f05b48/32.png) [@NowlanS\_Sean](https://www.ruby-forum.com/u/NowlanS_Sean)\ **Post date:** [December 9, 2014, 8:22pm UTC](https://www.ruby-forum.com/t/building-boot-bin-for-zedboard-to-use-with-gnuradio-dev-image/233383/4 "2014-12-09T20:22:22Z")
> On 12/09/2014 12:16 PM, Nick F. wrote: > > > A number of different distributions include a u-boot.elf suitable for > > the Zedboard. I’m not a linux boot expert, but u-boot seems pretty > > platform-agnostic when paired with a suitable FSBL. A lot of u-boots I’ve found point to a ramdisk filesystem instead of a partition. > > The images here include a u-boot.elf that works with Zedboard, ZC702, > > ZC706, etc. > > [http://wiki.analog.com/resources/tools-software/linux-software/zynq\_im](http://wiki.analog.com/resources/tools-software/linux-software/zynq_im) > > ages > > > > Email me directly and I’ll just send you the .elf if you’re interested. > A pox on people using ancient stuff. > I think Sean wants to load an fpga image early in the boot process. Not trying to do anything fancy; just trying to reproduce Jonathan Pendlum’s FFT filter example, which was written back when that ancient stuff was current. I think it’d be good for that to be updated for people who want to run GNU Radio on Zynq. I know RFNoC will change how that’s done with E310, but we don’t need RFNoC for MicroZed/ZedBoard/ZC70x. I’m happy to help with the writeup if/when I figure all this out. > Try the image I posted a few days ago and drop a file called fpga.bin in the FAT > partition. U-boot SPL will load that fpga.bin file then load u-boot. > You can now build the fsbl directly from u-boot but dropping the ps7\* files in > the right place. (See the OE recipe for how that is done there, and copy if you > are building u-boot from Xilinx git) I’ll try your newer image. > My understanding is the current release of Xilinx tools will give you > ps7 files with a license that is compatible with the GPL. > Philip > > > for Zedboard without doing a full openembedded build. I know that > > > there are licensing issues that may prohibit distributing an FSBL > > > file, but I’ve gone ahead and done that using the directions in [2]. > > > I’d like to compile boot.bin with the zynq\_fsbl.bit I created with > > > Xilinx 14.6, uImage, and the device tree binary distributed in [1]. > > > However, in order to use the build script in zynq-acp, I need > > > u-boot.elf, and [1] only provides u-boot.bin. Is there another way to compile > > > these without doing a full openembedded build? > > > .\>\> ---
**Author:** ![NowlanS\_Sean](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/f05b48/32.png) [@NowlanS\_Sean](https://www.ruby-forum.com/u/NowlanS_Sean)\ **Post date:** [December 9, 2014, 9:13pm UTC](https://www.ruby-forum.com/t/building-boot-bin-for-zedboard-to-use-with-gnuradio-dev-image/233383/5 "2014-12-09T21:13:18Z")
On 12/09/2014 02:21 PM, Nowlan, Sean wrote: > > On 12/09/2014 12:16 PM, Nick F. wrote: > > > > > A number of different distributions include a u-boot.elf suitable for > > > the Zedboard. I’m not a linux boot expert, but u-boot seems pretty > > > platform-agnostic when paired with a suitable FSBL. > > A lot of u-boots I’ve found point to a ramdisk filesystem instead of a > partition. Modern ones let us use the uEnv.txt file to control u-boots behavior. Philip ---
**Author:** ![NowlanS\_Sean](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/f05b48/32.png) [@NowlanS\_Sean](https://www.ruby-forum.com/u/NowlanS_Sean)\ **Post date:** [December 9, 2014, 8:40pm UTC](https://www.ruby-forum.com/t/building-boot-bin-for-zedboard-to-use-with-gnuradio-dev-image/233383/6 "2014-12-09T20:40:10Z")
On Tue, Dec 9, 2014 at 11:21 AM, Nowlan, Sean [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > On 12/09/2014 12:16 PM, Nick F. wrote: > > > > > A number of different distributions include a u-boot.elf suitable for > > > the Zedboard. I’m not a linux boot expert, but u-boot seems pretty > > > platform-agnostic when paired with a suitable FSBL. > > A lot of u-boots I’ve found point to a ramdisk filesystem instead of a > partition. That option should be pulled in from the devicetree, at least for sane u-boots! The one I linked appears to be a sane u-boot. > Hey, if it loads the kernel and FPGA it does everything I need it to do. The linked one is used in ADI’s FMCOMMS distro and loads an FPGA image before the kernel boots, if you put the bitfile into the compiled boot.bin created by the Xilinx SDK. Is there anything a newer u-boot buys me? If so I’ll go through the legwork of rebuilding from recent sources. If not I’ll keep on keepin’ on. 😉 –n