MICROCHIP PD77708 Evaluation Board
INSTRUCTION MANUAL
Introduction
The PD77708 device is part of the seventh generation PoE PSE (Power Sourcing Equipment) Integrated Circuit family from Microchip. The PD77708 includes an internal microcontroller, with embedded Flash memory, which allows for in-situ firmware update capability. This document describes the process or flow to update the device firmware. A simplified memory map of PD77708 is as follows:
Table 1. PD77708 Simplified Memory Map
| Memory Sector | START | END |
|---|---|---|
| BOOT | 0 | 1FFF |
| Main Application | 2000 | BFFF |
| Device Testing Utility | C000 | FCFF |
| Calibration area | FD00 | FFFF |
The firmware update is performed over the I2C interface. The I2C interface is a 16-bit, little-endian protocol (LSB sent/received first, then MSB): I2C Read operation. Each read operation is 16-bit long, LSB first.
Figure 1. I2C Read Operation

Figure 2. I2C Write Operation (Including Broadcast-Write)

1. Firmware Update Highlights
- On-board firmware update capability
- Simultaneous firmware update to multiple devices using I2C broadcast commands.
2. Firmware Update Flow Overview
The Firmware update flow overview is as follows:
- The firmware update starts by sending an update request to the PD77708 device(s) while the PD77708 device(s) are running.
- The update request received by the PD77708 instructs the device to jump to the Boot section in update mode, for receiving the updated firmware file.
- Once in firmware update mode, the PD77708 is ready to receive the new firmware data.
- A “start download” command is then sent by the host.
- The “start download” command erases the application and prepares the PD77708 for receiving the new firmware.
- Each download message is 64 bytes long, and the total firmware size is 40960 bytes (40KB), which corresponds to 640 messages to be sent to the PD77708.
- The host prepares each 64-byte message by reading 64 bytes from the firmware update
.hexfile and sends the 64-bytes message in a single I2C transaction. - The 64-byte message may be divided into smaller I2C messages, if required, but the PD77708 waits for the entire 64-bytes message to be received.
- After each 64-byte message is received by the PD77708, the PD77708 automatically programs the received data into the flash.
- Once all messages have been sent (640 messages), a verify flow should be performed to ensure data is received correctly. If verify is successful, a restart command is sent to the PD77708, and the PD77708 starts executing the new firmware.
The following figure shows an overview of the Firmware update flow.
Figure 2-1. Firmware Update and Verify Flowchart-Overview

The following flowcharts depicts the Firmware update flow in detail.
Figure 2-2. PD77708 Firmware Update Flowchart -Detailed



3. Registers Used for Firmware Update Flow
The following section describes the various registers used in both the PD77708 application and Boot application during the firmware update process.
3.1. PD77708 Application Registers
These registers are accessible from while the application is running.
Table 3-1. PD77708 Application Registers
| Register Address | Register Name | Width | RW | Description |
|---|---|---|---|---|
| 0x1B | Read_Vendor_ID | 16 | RO | Vendor ID. When in Boot application, returns the value 0x2D2D. |
| 0x43 | Read_Dev_ID | 16 | RO | Device ID. When in Boot application, returns the value 0x2121. |
| 0x90 | SET_BOOT_CTRL | 16 | WO |
Note: This value cannot be read back (Self reset will be generated). Writing other values are ignored and cannot be read back. |
| 0x91 | Read_System_Exe_Status | 16 | RO |
|
3.2. Boot Application Registers
Table 3-2. Boot Application Registers
| Register Address | Register Name | Width | RW | Description |
|---|---|---|---|---|
| 0x1B | Read_Vendor_ID | 16 | RO | Vendor ID. When in Boot application, returns the value 0x2D2D. |
| 0x43 | Read_Dev_ID | 16 | RO | Device ID. When in Boot application, returns the following values:
|
| 0x90 | Set_Boot_Ctrl | 16 | RW |
Notes:
|
| 0x91 | Read_System_Exe_Status | 16 | RO |
|
| 0x92 | Set_Download_Data | 16 | WO | Firmware update data information. The host should write 64 bytes in each I2C transaction. |
Table 3-2. Boot Application Registers (continued)
| Register Address | Register Name | Width | RW | Description |
|---|---|---|---|---|
| 0x95 | Read_Application_Status | 16 | RO | Reports the status of Active Application area (currently running application).
|
| 0x97 | Read_Application_Firmware | 16 | RO | Returns active firmware release version. In case of Application error, returns 0xFFFF. |
4. Revision History
The revision history describes the changes that were implemented in the document. The changes are listed by revision, starting with the most current publication.
Table 4-1. Revision History
| Revision | Date | Description |
|---|---|---|
| A | Feb 2026 | Initial Revision |
Microchip Information
Trademarks
The “Microchip” name and logo, the “M” logo, and other names, logos, and brands are registered and unregistered trademarks of Microchip Technology Incorporated or its affiliates and/or subsidiaries in the United States and/or other countries (“Microchip Trademarks”). Information regarding Microchip Trademarks can be found at https://www.microchip.com/en-us/about/legal-information/microchip-trademarks.
ISBN: 979-8-3371-2853-5
Legal Notice
This publication and the information herein may be used only with Microchip products, including to design, test, and integrate Microchip products with your application. Use of this information in any other manner violates these terms. Information regarding device applications is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. Contact your local Microchip sales office for additional support or, obtain additional support at www.microchip.com/en-us/support/design-help/client-support-services.
THIS INFORMATION IS PROVIDED BY MICROCHIP “AS IS”. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE, OR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE.
IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL LOSS, DAMAGE, COST, OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE INFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW, MICROCHIP’S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION OR ITS USE WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR THE INFORMATION.
Use of Microchip devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless otherwise stated.
Microchip Devices Code Protection Feature
Note the following details of the code protection feature on Microchip products:
- Microchip products meet the specifications contained in their particular Microchip Data Sheet.
- Microchip believes that its family of products is secure when used in the intended manner, within operating specifications, and under normal conditions.
- Microchip values and aggressively protects its intellectual property rights. Attempts to breach the code protection features of Microchip products are strictly prohibited and may violate the Digital Millennium Copyright Act.
- Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code protection does not mean that we are guaranteeing the product is “unbreakable”. Code protection is constantly evolving. Microchip is committed to continuously improving the code protection features of our products.
Troubleshooting
Check update status during/after Boot download:
Read Read_Application_Status in Boot. Reported codes include: 0x0105 NVM Programming in progress; 0x0106 NVM Programming error; 0x0107 NVM Erase error; 0x0108 Update Command Rejected; 0x0103 Match error with calibration structure; 0x0104 CRC error; 0x0109 Image Type error.
If the download command is rejected:
Use the 0x0108 “Update Command Rejected” status as an indicator and confirm that the device is in Boot update mode before issuing the start download / NVM download sequence.
If CRC or match errors occur:
Treat 0x0104 (CRC error), 0x0102 (Match error with Boot), and 0x0103 (Match error with calibration structure) as signs the received image/data did not match expected structures.
Ensure correct Boot exit condition:
The source states that to exit Boot, RESET_IN_N pin must be High.
FAQ
How is the PD77708 firmware updated?
Firmware update is performed over the I2C interface, using a bootloader flow where the host puts the device into Boot update mode, downloads the firmware data, verifies, and restarts the device to run the new firmware.
What is the firmware download block size and total size described?
Each download message is 64 bytes. The total firmware size is 40960 bytes (40KB), which corresponds to 640 messages.
Does the PD77708 program after receiving partial data?
No. The PD77708 waits for the entire 64-byte message to be received before programming the received data into flash.
Which register reports the status of the active application area during Boot?
In Boot, Read_Application_Status reports the status of the active application area (currently running application), with codes such as 0x0105 (NVM Programming in progress), 0x0106 (NVM Programming error), 0x0107 (NVM Erase error), 0x0108 (Update Command Rejected), 0x0104 (CRC error), and others.
Documents / Resources
![]() | PD77708 Evaluation Board |
References
- User Manualmanual.tools
