UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Adventurer
Adventurer
4,864 Views
Registered: ‎01-21-2014

Unable to create image: FATAL: Exception: Section offset overlaps with prior section

I followed the document given here to boot from flash:

 

http://www.wiki.xilinx.com/Zc702+Boot+From+Flash

 

When I am clicking create image after selecting various files as mentioned in the link above, I get the following error in the console:

 

 

 

bootgen -image system.bif -o i \
/home/suheb/petalinux-v2013.10-final/Xilinx-ZC702-14.7/pre-built/linux/images/output.bin 
-- Dump of Binary cache ----
00000000 Len: 000008a0 Res: 00000000 "BootHeader"
000008c0 Len: 00000014 Res: 00000000 "ImageHeaderTable"
00000900 Len: 00000024 Res: 00000000 "ImageHeader zynq_fsbl.elf"
00000940 Len: 00000020 Res: 00000000 "ImageHeader u-boot.elf"
00000980 Len: 00000020 Res: 00000000 "ImageHeader zImage.bin"
000009c0 Len: 00000024 Res: 00000000 "ImageHeader devicetree.dtb"
00000a00 Len: 00000028 Res: 00000280 "ImageHeader uramdisk.image.gz"
00000c80 Len: 00000040 Res: 00000000 "PartitionHeader zynq_fsbl.elf.0"
00000cc0 Len: 00000040 Res: 00000000 "PartitionHeader u-boot.elf.0"
00000d00 Len: 00000040 Res: 00000000 "PartitionHeader zImage.bin.0"
00000d40 Len: 00000040 Res: 00000000 "PartitionHeader devicetree.dtb.0"
00000d80 Len: 00000040 Res: 00000000 "PartitionHeader uramdisk.image.gz.0"
00000dc0 Len: 00000040 Res: 00000940 "PartitionHeader Null"
00001700 Len: 0001800c Res: 00000000 "zynq_fsbl.elf.0"
00080000 Len: 0003bf0c Res: 00000000 "u-boot.elf.0"
00100000 Len: 005986c8 Res: 00000000 "zImage.bin.0"
00600000 Len: 000010f8 Res: 00000000 "devicetree.dtb.0"
00800000 Len: 005024a0 Res: 00000000 "uramdisk.image.gz.0"
-- End of Dump
FATAL: Exception: Section "devicetree.dtb.0" offset of 0x600000 overlaps with prior section end address of 698700

 

  I took these files from Xilinx pre-built image folder, except uramdisk.image.gz, and devicetree.dtb which I took from ug873-design-files downlodable from xilinx website

 

This is my .bif file (system1.bif):

the_ROM_image:
{
    [bootloader]/home/suheb/petalinux-v2013.10-final/Xilinx-ZC702-14.7/pre-built/linux/images/zynq_fsbl.elf
    [offset = 0x80000]/home/suheb/petalinux-v2013.10-final/Xilinx-ZC702-14.7/pre-built/linux/images/u-boot.elf
    [offset = 0x100000]/home/suheb/petalinux-v2013.10-final/Xilinx-ZC702-14.7/pre-built/linux/images/zImage.bin
    [offset = 0x600000]/home/suheb/petalinux-v2013.10-final/Xilinx-ZC702-14.7/pre-built/linux/images/devicetree.dtb
    [offset = 0x800000]/home/suheb/petalinux-v2013.10-final/Xilinx-ZC702-14.7/pre-built/linux/images/uramdisk.image.gz
}

 


 

 

 

0 Kudos
4 Replies
Adventurer
Adventurer
4,863 Views
Registered: ‎01-21-2014

Re: Unable to create image: FATAL: Exception: Section offset overlaps with prior section

Additionally:

 

I chose the partition options as below:

 

bootloader

fsbl.elf

 

datafile

 u-boot.elf 

zimage.bin 

zynq-zc702.dtb 

ramdisk8M.image (ram disk file system) 

 

And the offsets exactly as given in the link above. 

0 Kudos
Xilinx Employee
Xilinx Employee
4,849 Views
Registered: ‎03-13-2012

Re: Unable to create image: FATAL: Exception: Section offset overlaps with prior section

Is it possible that your zimage.bin exceeds the partition size of the partition you assign it to?

0 Kudos
Explorer
Explorer
4,827 Views
Registered: ‎02-27-2014

Re: Unable to create image: FATAL: Exception: Section offset overlaps with prior section

Can you please tell me where did you find that my zImage.bin file is exceeding the partition size ?
0 Kudos
Xilinx Employee
Xilinx Employee
4,818 Views
Registered: ‎03-13-2012

Re: Unable to create image: FATAL: Exception: Section offset overlaps with prior section

Yours? I was talking to somebody else? Or are you using two different accounts?

 

Anyway, that was just my suspicion, you still need to confirm whether it is correct. But look at the output:

It says, the DT partition overlaps with its preceeding partition, which is the zImage partition. So, my guess is, the tools move the zImage into the zImage partition and record where that partition would end based on the zImage size. Then the next command tells to put the DT at some fixed offset and an overlap is detected.

(As I said, mostly speculating here)

0 Kudos