@Fernando , it seems the guide is designed for Aptio IV bios user. However, as more and more board is using Aptio V UEFI bios, perhaps it is better to include a guide for people who is trying to insert a ROM module for Aptio V bios.
For anyone who is interesting to insert the AsMedia 106x AHCI ROM module into Aptio V UEFI BIOS for onboard AsMedia 106x chips, following steps are necessary in order to obtain all the necessary data for all the fields in AMI MMTools 5.x, as the guide on the first page is designed for Aptio IV UEFI BIOS only.
First, open up device manager (devmgmt.msc) under Windows running at the target system (the one that is going to be flashed by the new BIOS), and navigate to ‘Storage Controller’ and find ‘Asmedia 106x SATA Controller’. Double click on it to open up the property dialog.
Then navigate to the ‘Details’ tab of the property dialog, and note the following items by choosing them at the drop box list of ‘Property’.
Hardware IDs: Note the 4 digits at DEV_XXXX, as the AsMedia 106x ROM module can be used for both 0612 and 0611 device manufactured by AsMedia (VEN_1B21)
Location Paths: Note the whole string which started as PCIROOT(X)#PCI(XXXX)#PCI(XXXX) (the second PCI part may not appear as it depends on how the manufacturer connect the chip on the motherboard)
If you have found that the Hardware IDs noted is different from the file that you have downloaded from the repository, you may consider to edit the ROM module via hex editor to update the device ID. To update the device ID in the ROM module, open up hex editor such as ‘HxD’ and load the file. Search the hex string as per the vendor ID, which can be found from the above Hardware IDs (4 digits at VEN_XXXX). For example, the AsMedia vendor ID is 1B21, and you should search the hex string as ‘211B’ in the option ROM file (instead of ‘1B21’ due to its endianess). And the 2 bytes after the first found hex string ‘211B’ from the top of the file should contain the device ID of the option ROM, which should either be ‘1206’ or ‘1106’ (i.e. DEV_0612 or DEV_0611) for AsMedia ROM, and you should modify them such that they matches the actual device ID.
After that, open up MMTools 5.x and load the bios that you want to insert the AsMedia Option ROM Module, and prepare / extract the AsMedia Option ROM Module after downloading it from the repository. Navigate to the ‘Option ROM’ tab of MMTools 5.x, and click on the ‘Browse’ button to load the extracted AsMedia Option ROM.
Choose ‘Insert an Option ROM’ at the radio / button box list, click ‘Apply’, and a box with 3 fields will come up for you to enter.
For the Option ROM File GUID, normally you can choose the existing one by pressing down arrow button, as most Option ROM modules often use the same File GUID within a single BIOS.
For the Option ROM Section GUID, I have generated a Section GUID by pressing the ‘Generates Section GUID’ button, as I cannot find the Section GUID of AsMedia 106x Option ROM module on the internet at all. A randomly generated section GUID should be fine, but perhaps someone with more experience in MMTools can provide some information / explanation about it.
For the Device Path, you have to choose the correct one which matches the ‘Location Paths’ that you have noted down in the device manager. For example, if the ‘Location Paths’ shown was PCIROOT(0)#PCI(1A00)#PCI(0000), then you should select ‘HB0-0:0-0:0-1A:0-0:0’ as the device path, by matching up the last few digits. Another example is that if the ‘Location Paths’ shown was PCIROOT(0)#PCI(1F03) without the second PCI string, you should select ‘HB0-0:0-0:0-1F:3’ as the device path. The prefix / start of the DevicePath string may vary but the number at the middle / at the end must match the ‘Location Paths’ shown in Device Manager.
For anyone interested to know whether the AsMedia AHCI Option ROM Module will work in Aptio V BIOS or not, I will let you know after I have flashed my BIOS, since I have just updated my BIOS with latest ME engine, microcode, RAID driver, etc., but did not flash it yet.