Error Message in Bootwizard V 1.0.401.0
Hi,
I have Hitex Hitop V 5.3 and create a *.elf file.
When I would create a *.bin file with the bootwizrad (Click on load elf/binay and select the file) following error is shown:
The extracted image is to large (1342167188 bytes)
Please check your linker
But the file is only 1604252 bytes great.
Can someone help me
Br,
Rainer
Hi,
we have a similar problem: For performance reasons we devided our application in SDRAM and TCM. Since both memory regions are far apart bootwizard tries to build an almost 2GB binary file.
How can we build a small binary that uses SDRAM and TCM at the same time?
Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
Hello Thyron,
please read the previous post from Chris Frickel and follow his recommendations.
Regards
AJ
M T
Hilscher Gesellschaft für Systemautomation mbH
For performance reasons we devided our application in SDRAM and TCM. Since both memory regions are far apart bootwizard tries to build an almost 2GB binary file.
How can we build a small binary that uses SDRAM and TCM at the same time?
First of all you should read and understand what Chris has written about the differences of .ELF and .bin files, as AJ proposed.
As the netX can only start special prepared .bin files (not .ELF files), you will need to relocate data and code yourself. This is done via the Linker Script (.ld) by telling the linker that this code / data has different load (LMA) and execution addresses (VMA).
See LD documentation http://sourceware.org/binutils/docs-2.21/ld/Output-Section-Attributes.html#Output-Section-Attributes for more information.
NOTE: If LMA and VMA is different, the application needs to copy this region from LMA to VMA at startup for correct execution, any may only call relocated functions after they have been copied to their destination adress.
Regards,
MT
Chris Frickel
Hilscher
Hi Rainer,
The Bootwizard tries to convert an elf image to a binary file. So lets take a closer look at both file formats first:
Converting an elf file to a binary file takes all the sections and fills the gaps between them. Depending on the sections addresses the result can get quite big. Just imagine one section in the internal ram at 0x00008000 and one section in SDRam at 0x80000000. The gap between both sections is almost 2 gigabyte! This means almost 2 gigabyte of fillup bytes will be written to the binary file. Whoa, that's a bit to much for a bootable image.
Sooo... your problem boils down to a huge gap between two sections in your elf file. Please check your project and especially your linker description file. There must be some data or code section which is far away from the rest. Do not worry, the linker can help you to find the problem. Add this to your linker options:
Rebuild your elf file and there will be a "mapfile.txt" with a lot of useful info about what goes where in the memory. The file will be not small, but with some digging you will get all the information you need to identify your problem.
Good luck!
[/]