# Update Local Host (INT6000/INT6300/INT6400)

The Update Local Host operation transfers a firmware image and/or PIB image from the device to the local host for permanent storage. After the firmware and PIB are stored, the local host will reset the device and the device will retrieve parameters and firmware using the Boot from Host operation described in the next section.

The firmware may initiate this operation after a remote host has downloaded new firmware or PIB and issued a `VS_MOD_NVM.REQ` to the device, the device has been asked to restore factory default settings or the firmware has dynamically altered the runtime PIB in some way. Consequently, the device will be reset by the host in each case.

The device initiates this operation to complete an Upgrade Device operation when the device has no dedicated flash memory onboard. This operation requires running Atheros firmware on the device and custom software on the local host.

## Update Local Host (INT6000/INT6300/INT6400)

          INT6300/INT6400                           LOCAL-HOST
            [01] |-------- VS_HOST_ACTION.IND ------->| [01]
            [03] |<------- VS_HOST_ACTION.RSP --------| [02]
                 |                                    |
            [04] |<------- VS_RD_MOD.REQ -------------| [04]
            [04] |-------- VS_RD_MOD.CNF ------------>| [04]
            [04] |<-----------------------------------| [04]
            [04] |----------------------------------->| [04]
                 |                                    |
            [05] |<------- VS_RD_MOD.REQ -------------| [05]
            [05] |-------- VS_RD_MOD.CNF ------------>| [05]
            [05] |<-----------------------------------| [05]
            [05] |----------------------------------->| [05]
                 |                                    |
            [06] |<------- VS_RS_DEV.REQ -------------| [06]
            [07] |-------- VS_RS_DEV.CNF ------------>| [07]

1. The runtime firmware initiates this operation by broadcasting `VS_HOST_ACTION.IND` messages every 500 milliseconds. The `HOST_ACTION_REQ` field of the message can be either `0x01`, `0x02` or `0x03` to indicate that a firmware image, a parameter block image or both are ready for upload by the local host.

2. The local host sends a `VS_HOST_ACTION.RSP` message to the device to indicate the ability and willingness to upload the information. The `MSTATUS` field is set to `0x00` for affirmative and `0x01` for negative.

3. Assuming an affirmative response, the device stops broadcasting and will wait indefinitely for local host action.

4. Optionally, the local host reads the firmware image from the device by sending a series of VS_RD_MOD.REQ messages to the device and waiting for a `VS_RD_MOD.CNF` message after each one. The message `MODULEID` field is set to `0x01` for this operation.

5. Optionally, the local host reads the PIB from the device by sending a series of `VS_RD_MOD.REQ` messages to the device and waiting for a `VS_RD_MOD.CNF` message after each one. The message `MODULEID` field is set to `0x02` for this operation.

6. The local host sends a `VS_RS_DEV.REQ` message to the device to initiate a firmware reboot.

7. The device sends a `VS_RS_DEV.CNF` to the host and performs a software reset. This forces a Boot from Host.