v1.6.0

Notes

This release brings a lot of improvements over the previous release, the highlights are:

• Clock switch configuration is not hard-coded anymore, you can change it via IPMI;
• AFCv3.1 Timing and BPM now uses the same firmware binary;
• Proper support for RTM-LAMP for AFCv4.0.

Upgrade notes

• Before upgrading the firmware via HPM from v1.5.0, make sure to use a patched ipmitool as described in the README.md file. This will not be necessary in future releases;
• After upgrading, you will need to configure the clock switch for each AFC card via IPMI, these configurations are not hardcoded anymore. Check the 'Clock switch configuration' section in the README.md file;
• AFCv4.x.x boards produced before this release have a generic FRU written to the EEPROM that will not work with RTM-LAMP due to the Zone3 compatibility record been incorrect. Use the set-fru-info.py to generate a new FRU image based on the generic image and use ipmitool to update the FRU EEPROM.

What's Changed

• Add script to automate generating binaries for all targets by @augustofg in #162
• Add instructions to update firmware via serial port using nxpprog by @gustavosr8 in #164
• Fix IPMI FRU Write command returning invalid data by @gustavosr8 in #170
• Implement EEPROM 24xx02 interface module by @gustavosr8 in #167
• Clock switch config by @gustavosr8 in #165
• Remove deprecated code for clock switch configuration by @gustavosr8 in #174
• Unifies the firmware for afcv3 bpm and timing by @gustavosr8 in #175
• Changes to use the correct i2c function by @gustavosr8 in #173
• Fix the real size of tx_len by @gustavosr8 in #172
• Add suport for xvc probe by @gustavosr8 in #177
• Add script for decoding and encoding clock configuration for AFCv3.1 and AFCv4 by @augustofg in #168
• Separate the I2C chip_id map for AFC devices and RTM devices by @gustavosr8 in #180
• Read i2c address from i2c_chip_rtm_map instead of i2c_chip_map by @gustavosr8 in #183
• Change the fru runtime info to AFC v3 instead of AFC Timing by @gustavosr8 in #184
• Move to rtm_check_presence function to board specific directory by @gustavosr8 in #182
• Only set the clock switch configuration when Payload Power is ON by @gustavosr8 in #187
• Move the count check to be done after the fru_write call by @gustavosr8 in #188
• Check if the clock configuration is successfully applied before FPGA_ON by @gustavosr8 in #189
• Rename error librarie to avoid conflicts by @gustavosr8 in #193
• Always write fru info in eeprom by @gustavosr8 in #195
• Add script to set the Serial Number and standardize the other AFCv4 fields by @gustavosr8 in #178
• Modify adn4604 config functions to return error codes by @gustavosr8 in #191
• Fix the if statement for correctly use the standalone mode by @gustavosr8 in #198
• Fix FRU reading / writing operations by @gustavosr8 in #197
• Change lpc17 i2c driver to accept any size of command in MasterCmdRead by @gustavosr8 in #201
• [RTM] Move 12V turn on/off to AFC specific code by @gustavosr8 in #205
• Rtm presence detection by @gustavosr8 in #202
• Set RTM-LAMP ADC CNV retiming clock PLL config to AMC_CLK1 1:1 by @augustofg in #206
• Change delay counts from ticks to ms by @gustavosr8 in #199
• Remove unnecessary functionality from the Watchdog module by @gustavosr8 in #209
• Improve i2c eeprom write functions to only incremend addr if success by @gustavosr8 in #208
• Increase block_data size to allocate the uploaded firmware block by @gustavosr8 in #210
• Handle FMC power good signals by @gustavosr8 in #213
• Add support to bootloader self-update by @gustavosr8 in #212
• Dummy handler to receive the I2CSlaveAddr when don't match the IPMBAddr by @gustavosr8 in #215
• Change the TARGET_BOARD_NAME from AFC Timing to AFC v3.1 by @gustavosr8 in #216
• Update README preparing for v1.6.0 release by @gustavosr8 in #217
• Fix incorrect clock switch configuration for AFCv3.1 Timing by @augustofg in #214
• Fix clock configuration readback when start on M1 after reset by @augustofg in #218
• Enable voltage and current sensors for AFCv4 by @augustofg in #219
• Better wording of the workaround needed when upgrading from v1.5.0 by @augustofg in #220

Full Changelog: v1.5.0...v1.6.0