-
fallback-7z014s-v0.9.6 Release: fallback v0.9.6 for 7z014s
fallback v0.9.6 for 7z014s This release includes the EEPROM Fault Log feature in the fallback image. This feature records significant IPMI or fault related events. While there are no sensors or events to log in fallback, the ability to read out this log from a fallback mode, even without SDR information, can be valuable.
-
fallback-7z020-v0.9.6 Release: fallback v0.9.6 for 7z020
fallback v0.9.6 for 7z020 This release includes the EEPROM Fault Log feature in the fallback image. This feature records significant IPMI or fault related events. While there are no sensors or events to log in fallback, the ability to read out this log from a fallback mode, even without SDR information, can be valuable.
-
CDB-v1.0.4 Release: CDB v1.0.4 for 7z020
CDB v1.0.4 for 7z020 This release integrates various fixes related to the initialization of the EEPROM boottarget field on fresh cards, as well as the `image_tag_lock` command.
-
fallback-7z014s-v0.9.5 Release: fallback v0.9.5 for 7z014s
fallback v0.9.5 for 7z014s This release fixes a bug in the firmware update procedure where the Image Tag Lock feature would automatically be enabled when uploading a firmware image tagged e.g. "fallback-7z014s" to the primary partition, because it did not match "fallback". This will no longer occur. The current image tag lock setting can be manipulated with the `image_tag_lock` command. This issue affects only fallback images applied to the primary (operational) partition. It is considered a low priority update on RevB IPMCs. The help text for the `image_tag_lock` command has also been improved.
-
fallback-7z020-v0.9.5 Release: fallback v0.9.5 for 7z020
fallback v0.9.5 for 7z020 This release fixes a bug in the firmware update procedure where the Image Tag Lock feature would automatically be enabled when uploading a firmware image tagged e.g. "fallback-7z020" to the primary partition, because it did not match "fallback". This will no longer occur. The current image tag lock setting can be manipulated with the `image_tag_lock` command. This issue affects only fallback images applied to the primary (operational) partition. It is considered a low priority update on RevB IPMCs. The help text for the `image_tag_lock` command has also been improved.
-
fallback-7z014s-v0.9.4 Release: fallback v0.9.4 for 7z014s
fallback v0.9.4 for 7z014s This release fixes a bug with the handling of the boot target field in uninitialized EEPROM (such as on fresh boards).
-
fallback-7z020-v0.9.4 Release: fallback v0.9.4 for 7z020
fallback v0.9.4 for 7z020 This release fixes a bug with the handling of the boot target field in uninitialized EEPROM (such as on fresh boards).
-
fallback-7z014s-v0.9.3 Release: fallback v0.9.3 for 7z014s
fallback v0.9.3 for 7z014s This release restores some IO testing routines and functionality that were lost in prior refactors.
-
fallback-7z020-v0.9.3 Release: fallback v0.9.3 for 7z020
fallback v0.9.3 for 7z020 This release restores some IO testing routines and functionality that were lost in prior refactors.
-
CDB-v1.0.3 Release: CDB v1.0.3
CDB v1.0.3 This update blocks firmware updates when the card is not in an M1 state, and will not allow the card to leave M1 until the IPMC has been restarted if an update is applied.
-
fallback-7z014s-v0.9.2 Release: fallback v0.9.2 for 7z014s
fallback v0.9.2 for 7z014s This release includes significant upgrades to the image management and verification facilities of the IPMC. The "A" and "B" partitions have been replaced with "primary" and "backup" partitions containing the most recent, and second most recent image applied. This design prevents confusion with regard to whether A or B is current, and allows updates to be done in a uniform manner without assuming (possibly incorrectly) the partition configuration of the card. Updates automatically program the next image slot, and boottarget can be used to undo an update. In addition to this change, images are now validated by reading the ZYNQ part out of the bitstream, as well as the ZYNQ device ID register to ensure that an IPMC based on a 7z020 part will not accept e.g. a 7z014s based image. Images are now also validated by confirming that the git tag in the embedded version information matches the expected git tag, if configured, to limit exposure to instances of confusion where an IPMC running on one type of carrier board is programmed with an image for a different type of carrier board which is not electrically safe for it. Images are also validated when switching boot target as well as at upload time, so it is not possible to accidentally select an unprogrammed or invalid boot target. This release also includes a 2 second delay in early boot, for power-on resets only, to allow for JTAG recovery of boot loops.
-
fallback-7z020-v0.9.2 Release: fallback v0.9.2 for 7z020
fallback v0.9.2 for 7z020 This release includes significant upgrades to the image management and verification facilities of the IPMC. The "A" and "B" partitions have been replaced with "primary" and "backup" partitions containing the most recent, and second most recent image applied. This design prevents confusion with regard to whether A or B is current, and allows updates to be done in a uniform manner without assuming (possibly incorrectly) the partition configuration of the card. Updates automatically program the next image slot, and boottarget can be used to undo an update. In addition to this change, images are now validated by reading the ZYNQ part out of the bitstream, as well as the ZYNQ device ID register to ensure that an IPMC based on a 7z020 part will not accept e.g. a 7z014s based image. Images are now also validated by confirming that the git tag in the embedded version information matches the expected git tag, if configured, to limit exposure to instances of confusion where an IPMC running on one type of carrier board is programmed with an image for a different type of carrier board which is not electrically safe for it. Images are also validated when switching boot target as well as at upload time, so it is not possible to accidentally select an unprogrammed or invalid boot target. This release also includes a 2 second delay in early boot, for power-on resets only, to allow for JTAG recovery of boot loops.
-
CDB-v1.0.2 Release: CDB v1.0.2
CDB-v1.0.2 This release includes significant upgrades to the image management and verification facilities of the IPMC. The "A" and "B" partitions have been replaced with "primary" and "backup" partitions containing the most recent, and second most recent image applied. This design prevents confusion with regard to whether A or B is current, and allows updates to be done in a uniform manner without assuming (possibly incorrectly) the partition configuration of the card. Updates automatically program the next image slot, and boottarget can be used to undo an update. In addition to this change, images are now validated by reading the ZYNQ part out of the bitstream, as well as the ZYNQ device ID register to ensure that an IPMC based on a 7z020 part will not accept e.g. a 7z014s based image. Images are now also validated by confirming that the git tag in the embedded version information matches the expected git tag, if configured, to limit exposure to instances of confusion where an IPMC running on one type of carrier board is programmed with an image for a different type of carrier board which is not electrically safe for it. Images are also validated when switching boot target as well as at upload time, so it is not possible to accidentally select an unprogrammed or invalid boot target.
-
CDB-v1.0.1 Release: CDB-v1.0.1
Improve FSBL functionality on RevA boards with single-image flash configurations.
-
fallback-v0.9.1 Release: fallback-v0.9.1
Improve FSBL functionality on RevA boards with single-image flash configurations.
-
-
fallback-v0.9.0 Release: fallback-v0.9.0
A hopefully-stable fallback image for distribution and standard use.
-