Artesyn MOTLoad Firmware Package User's Manual (February 2015) - Manual (Page 254)

Remote Start
MOTLoad Firmware Package User’s Manual (6806800C24D) 254
unsigned char class;
unsigned char subClass;
unsigned char unused[6];
}pciPopulation_t;
/*
*This structure defines the organization of board payload *information
that's returned by the Remote Start Firmware *Query command.
*/
typedef struct bdPayload {
char processorType[16]; /*offset0 */
char boardType[32]; /* offset 9x10 */
char boardAssy[32]; /* offset 0x30 */
double memTotal; /* offset 0x50 */
double memAvail; /* offset 0x58 */
char os_major; /* offset 0x60 */
char os_minor; /* offset 0x61 */
char fw_major; /* offset 0x62 */
char fw_minor; /* offset 0x63 */
unsigned short numCPU; /* offset 0x64 */
unsigned short numPciDevs; /* offset 0x66 */
unsigned char unused[8]; /* offset 0x68 */
/*
* Assuming all busses are 33mhz, allow room for 10 devices,
* 8 func per device, on each PCI bus on board.
*/
} bdPayload_t;
Note In the bdPayload structure, the NUM_PCI_INSTANCES value should be set to the number
of PCI Bus Instances on the target board to match the generous estimate of the number of
possible pciPopulation_t entries used by MOTLoad. A PCI bus instance is an independent PCI
bus, not to be confused with a PCI subbus, which could exist as a child of a PCI bus instance.
(Sub-bus devices are not reported by the Firmware Query / Payload command.) The actual
number of pciPopulation_t entries is very likely to be fewer than the generous estimate; the
actual number is dynamically determined and provided by the target firmware in the
numPciDevs element.