i2c-vr: fix xdpe1x2xx bugs

1.Due to the lack of a null character, debug messages become abnormal
during file parsing.

2.When performing “Reset the configuration”,
writing more memory than the length declared by data[MaxSectDataCnt] may
cause the program to exit abnormally.

issue log:
```
<7> parsing package header
<7> parsing package, pkg header size: 178
<7> Yosemite5_MB_VR_CPU0_1794: set version 1009
09Z 0x140B21B9/XV0 Config
0000000sing: //XV0 PMBus LoopA User
643C5088ing: //XV0 PMBus LoopB User
07> Parsing: //XV0 FW SVI3 LoopA
07> Parsing: //XV0 FW SVI3 LoopB
00000000ing: [End Configuration Data]
<7> Scratchpad Address: 0x2005f000
<7> CRC before programming: 0x140b21b9
<7> CRC of configuration: 0x140b21b9
```

```
<6> Successfully updated VR Yosemite5_MB_VR_CPU0
corrupted size vs. prev_size
Aborted (core dumped)
root@bmc:~#

<7> Yosemite5_MB_VR_CPU0_1794: creating 'activating' association to /xyz/openbmc_project/inventory/system/board/Yosemite5_MB
free(): invalid pointer
Aborted (core dumped)
root@bmc:~#
```

Change-Id: I7cba7cc5373612d79da641b2e764fa4985377e8b
Signed-off-by: Leo Yang <Leo-Yang@quantatw.com>
1 file changed
tree: 53a7c90db3c2fc25ac0388f03d83bf580eac9de4
  1. bios/
  2. bmc/
  3. common/
  4. cpld/
  5. eeprom-device/
  6. i2c-vr/
  7. subprojects/
  8. test/
  9. tpm/
  10. .clang-format
  11. .clang-tidy
  12. .gitignore
  13. .shellcheck
  14. LICENSE
  15. meson.build
  16. meson.options
  17. OWNERS
  18. README.md
README.md

phosphor-bmc-code-mgmt

Phosphor BMC Code Management provides a set of system software management applications. More information can be found at Software Architecture

To Build

To build this package, do the following steps:

  1. meson build
  2. ninja -C build

To clean the repository run rm -r build.