mkimage for Windows

[PHJ]

I'm following the instructions in ​Intel® Arria® 10 SoC UEFI Boot Loader User Guide for getting the QSPI UEFI boot loader working.

It has steps to run a tool called mkimage.

Where do I find a windows version of this tool ?

[MuhammadAr_U_Intel]

Hi,

You need to launch SoC EDS command shell to use "mkimage" command in windows.

Thanks,

Arslan

[PHJ]

Thanks MUsman - however this does not work for me -  is it meant to be part of the Quartus 18.0 distribution ?

I just get:

​$ mkimage

bash: mkimage: command not found

[MuhammadAr_U_Intel]

Hi,

No it doesn't come with Quartus installation package.

This is part of Soc EDS package

http://fpgasoftware.intel.com/soceds/18.1/?edition=standard&platform=windows&download_manager=dlm3

You should be able to find "Soc EDS Command shell" different from windows command prompt.

Thanks,

Arslan

[PHJ]

Hi Arslan -

I installed SoCEDSProSetup-18.0.0.219 when I first got the A10 dev kit.

Should this have included the mkimage tool - if so, where is it installed ?

I can run the SoC EDS command shell no problem - it is just mkimage that I cannot find.

Thanks !​

[MuhammadAr_U_Intel]

I attached a screenshot for SoC EDS command shell, using Quartus Standard 17.1

Can you share your screenshot ?

[PHJ]

It looks like I have something missing from my install - I have no mkimage folder in embedded\host_tools\altera....

​

[MuhammadAr_U_Intel · Accepted solution]

Hi,

As a workaround you can install Standard Version of SoC EDS and copy the "mkimage" directory to Pro SoC EDS install directory.

Let me know if you are able to proceed with this.

Thanks,

Arslan

[PHJ]

Thanks Arslan - this has worked for me.....​

[PHJ]

With the new mkimage, I still could not get the instructions from ​Intel® Arria® 10 SoC UEFI Boot Loader User Guide to work correctly.

I tried the following steps:

$ mkimage -A arm -T firmware -C none -O u-boot -a 0 -e 0 -n "RBF" -d

ghrd_10as066n2.rbf ghrd_10as066n2.rbf.mkimage

$ quartus_hps -c1 -oP --addr=0x00720000 ghrd_10as066n2.rbf.mkimage

The boot code reported:

Programmed RBF is not peripheral

The length of the RBF was ~15MB and therefore failed the check against the max 512k size.

I've tried doing the following to program the periph and core RBFs separately and this has got me past this error:

$ mkimage -A arm -T firmware -C none -O u-boot -a 0 -e 0 -n "RBF" -d output_files/ghrd_10as066n2.periph.rbf ghrd_10as06

6n2.periph.rbf.mkimage

$ quartus_hps -c1 -oP --addr=0x00720000 ghrd_10as066n2.periph.rbf.mkimage

$ mkimage -A arm -T firmware -C none -O u-boot -a 0 -e 0 -n "RBF" -d output_files/ghrd_10as066n2.core.rbf ghrd_10as066n

2.core.rbf.mkimage

$ quartus_hps -c1 -oP --addr=0x00820000 ghrd_10as066n2.core.rbf.mkimage

Does this look correct ?

Is this related to the version of mkimage, or are the instructions in the doc wrong ?

[PHJ]

Have read back and I guess that the instructions are assuming Automatically Loaded Combined RBF