Actions
Forum Thread Details
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 336 subscribers
  • Views 378 views
  • Users 0 members are here
Related

generate bootimage

starbright

I successfully created a boot.mcs and boot.bin out of FSBL, bitstream and u-boot.elf. I can flash the mcs file to QSPI - works fine so far.
Board doesn't boot anymore after saving a changed environment (saveenv). Probably it is saved into an area, where boot.mcs is copied to.
So I tried to find out, where are to 3 files are located in flash. But I couldn't find the patterns in mcs file. How to find out (or to set) the addresses of this 3 parts of boot.mcs?

Once I know that, I suppose I have to change the
defines for
CONFIG_ENV_SECT_SIZE
CONFIG_ENV_SIZE
CONFIG_ENV_OFFSET

Is this correct? What are good values for this?

Shouldn't be adapted in devicetree the partitions of the qspi flash according the 4 parts (FSBL, bitstream, uboot, environment)?

---- Edit:

I think I know the answer. Files are appended without space, but with "offset"-param it can be separated (example:

the_ROM_image:
{
t[bootloader]D:XilinxprojectsMicroZedMicroZedsdkFSPLDebugFSPL.elf
t[offset = 0x020000]D:XilinxprojectsMicroZedMicroZed.sdkdesign_1_wrapper_hw_platform_0design_1_wrapper.bit
t[offset = 0x280000]D:u-boot.elf
}

Than at 0x30.0000 are free space.

---- Edit 2:

That doesn't work, environments overwrites important data:

Saving Environment to SPI Flash...
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 16 MiB
Erasing SPI flash...Writing to SPI flash...done

Uboot was configured to:
#define CONFIG_ENV_SECT_SIZEtt0x1000
#define CONFIG_ENV_OFFSETttt0x3000000
#define CONFIG_CMD_SAVEENV

  • 0

    Hi starbright,

    This is what I would have suggested and appears to be what you tried in your edits.  Curious that it did not work as expected.

    Can you confirm that your U-boot config shown is not a typo?

    I see you are planning to place U-boot at 0x28.0000 in flash and plan to place U-boot ENV partition at 0x30.0000 which gives 524288 bytes of space to fit U-boot image.  Hopefully if everything is fitting as expected, then 0x30.0000 in flash does not contain U-boot code.

    You show #define CONFIG_ENV_OFFSET 0x300.0000 (50,331,648 bytes) which is a bit larger than expected.  Is this number correct?

    Regards,

    -Kevin

  • 0

    Also, here is UG821 which has the bootgen command format documentation for anyone else who is following this:

    http://www.xilinx.com/support/documentation/user_guides/ug821-zynq-7000-swdev.pdf

    Regards,

    -Kevin

  • 0

    Thanks Kevin, indeed I had a simple type.
    The environement offset in u-boot 0x300.0000=48MB was far outside the flash (16MB)

    As I can't find the pattern of the origin files in mcs or bin files, I suppose they will be somewhat formatted (stripped?).
    The FSBL.elf is somewhat around 400k, the bitstream 2MB, an u-boot.elf 1.9MB.  This should give offsets of 512k=0x8.0000 and 3MB (512+2M+something) 0x30.0000. The environment than could start at 5MB=0x50.0000. With this values it works! Great!

    The mcs file is somewhat unreadable for me, but the bin file gives me back, that fsbl in boot.bin is much, much smaller, around 100kB. This is just a quarter of size of the elf file. Same for uboot (1.9MB vs 320k). It seems I can save a lot of space in flash. What does make the difference?