The commands you have mentioned are only meant to be used locally using the Manageability Engine Interface (MEI) driver. Please remember that MEI driver is also referenced as HECI driver.
Section B.28 in the developers guide to sample configuration application document talks about the watch dog(WD) client. Intel AMTfirmware and other firmware executing on the Intel Management Engine are divided into clients. Each client responds to a subset of commands.The commands in appendix B.28 are part of two different clients:
The document currently only lists out the API's that are needed for Remote Configuration Local Agent and is not the complete list of API's supported by the driver.
Regarding the communication to the Intel AMT device through BIOS codes, I need to check on that. Can you tell me more on what you would like to achieve with this?
Hope this helps.
I also would like to see availability via bios. I have asked about this and local storage admin in the past and the explaination was it was documented that way and supporting use cases... non of which were applicable to me... were articulated.
We seem to have created a remote only managed unit in this regard, IMHO. One that can only be managed by ISVs. We bought the chips, however, we cannot utilize them... only the ISVs, which we are not one of (we make the PCs) can utilize the technology after we hand off to the os.
It would be nice for example to include a amt nvram storage diagnostic with our PCs, however, we would have to ask the owner to find an apprpriate PC to connect up to in order to accomplish this task. Not the most desirable IMHO.
We would like to manage nvram storage to add value to our products at bios start up that other manufactures do not have, however, we cannot manage storage locally, much less via bios, so any value add will have to come from a ISV... which they can turn around and sell to other manufactures of course which leaves us with no real advantage at all.
Ok... you are free to flame me at will ;) I just could not resist this.