ISH\4.1.0.3364v3_PROD\4.1.0.3364v3_PROD.bin missing in 566285-apollo-lake-soc-fsp-mr5-tgz.zip

[dbur]

Hello,

When trying to stitch the coreboot produced files "coreboot.rom", "coreboot_ibbl.rom" and "coreboot_ibbl.rom" using "BlStitch.bat /stitch" command on Windows 7 Enterprise, the following error is encountered in "Stitch.log" file:

############################################################################
PATH is C:\Devel\\Intel_Atom_E3900\BlStitch
copy ISH\4.1.0.3364v3_PROD\4.1.0.3364v3_PROD.bin CSE\3.1.50.2222\APLI\FIT\input\ISHC.bin
.
Le fichier specifie est introuvable.

------------------------------------------
!!!!!! Stitching FAILED !!!!!!
------------------------------------------
Please check Stitch.log for details

I saw on the Intel forum this issue mentioned twice but not a solution for it.

Where the file "ISH\4.1.0.3364v3_PROD\4.1.0.3364v3_PROD.bin" can be found ?

I searched everywhere  on the "Intel Ressource" but no trace of it.

How can I get it, please ?

Best regards

[CarlosAM_INTEL]

Hello, @dbur:

Thank you for contacting Intel Embedded Community.

You need to address your Firmware Support Package (FSP) consultations as a reference to the channel stated in the following website:

https://github.com/intel/FSP/issues

Best regards,

@CarlosAM_INTEL.

[dbur]

Hello @Mæcenas_INTEL​,

Thank you for the answer.

The problem is not the FSP itself. The problem is the BlStitch.bat utility found in the Intel document #566285-apollo-lake-soc-fsp-mr5-tgz.zip, one can get ONLY from the Intel Resource and Design Center.

As we know, the BlStitch.bat utility is used to create a flashable SPI image using  "coreboot.rom", "coreboot_ibbl.rom" and "coreboot_ibbm.rom" files resulting from coreboot compilation for ApolloLake.

On  https://github.com/intel/fsp neither #566285-apollo-lake-soc-fsp-mr5-tgz.zip nor BlStitch.bat nor BlStitch.7z (the BlStich.bat and associated folders container) exist.

Generally speaking, it seems that BlStitch is something completely unknown to GitHub FSP.

Who wrote BlStitch.bat and who created its associated folders containing an (incomplete) collection of ".bin" files needed to create the flashable SPI image ?  I'm unable to find the answer to that after hours and hours of search.

I can post my issue on https://github.com/intel/fsp/issues as mentioned by you but I'm not sure it's the right place.

Best ragrds,

@dbur 

[CarlosAM_INTEL · Accepted solution]

Hello, @dbur:

Thanks for your reply.

We have sent an email with suggestions that may help you.

Best regards,

@CarlosAM_INTEL.

[dbur]

Hello @Mæcenas_INTEL,

I've got nothing from your part, neither on Intel Community nor on my e-mail except your mail saiyng you sent me something. I checked My Profile as you mentioned and it looks ok. I also pushed the "Save" button to be sure.

Tomorrow I'm out of the office. We'll continue on  thursday.

Best regards,

@dbur

[CarlosAM_INTEL]

Hello, @dbur:

Thanks for your update.

We have sent the emails to the address associated with your profile.

We have sent a new email to the cited address.

Best regards,

@CarlosAM_INTEL.

[ChipsetWr]

Hello Carlos,

I am facing the same issue when trying to stitch firmware for LeafHill CRB. If there is a solution then can I get it as well?

[Adolfo_S_Intel]

Hello, @ChipsetWr 

Please check the RDC document#566285 available here: https://cdrdv2.intel.com/v1/dl/getContent/566285 it should have the latest BSltitch.

Also you can check the RDC document # 574891, Apollo Lake Coreboot Firmware Enabling Application Notes. That can be found here: https://cdrdv2.intel.com/v1/dl/getContent/574891?wapkw=apollo%20lake%20coreboot

And the APL Signing and Manifesting Guide that comes included on the latest TXE kit for Apollo Lake.

Of course, you will need to have access to the RDC to access the document.

I hope this information is useful for your case.

Best regards,

Adolfo S

Intel Customer Support Engineer

[ChipsetWr]

@Adolfo_S_Intel ,

The problem is that ISH and PMC binaries for Apollo Lake are not available in VIP, I cant download it.

[CarlosAM_INTEL]

Hello, @ChipsetWr:

Thanks for your reply.

We sent an email to the address associated with your account with suggestions that may help you to solve the reported inconvenience.

Best regards,

@CarlosAM_INTEL.