This design differs from the RX888mk2 in many ways, and the key to being able to bring the board up among all of the developers is ensuring that the design choices or component placements made here allow the latest known-good Firmware to run. This way, the firmware gets out of the way of hardware testing and bring up. Else if the design was CONTINGENT on firmware development to run, this would serialize the development and cause a firmware designer a lot of grief.
These functions will NOT be supported by the latest known-good firmware (0.1.0 of rx888-firmware):
- EXT Ref Active
- SI5351 Disable
- SPI Flash
@ringof to perform a detailed FW review to ensure that either that HW does not demand immediate FW support (thru DNI resistors, etc), or if unable, to spin a new release of rx888-firmware ASAP for rx888mk2 validation to ensure it can drop-into the TAPRx888 without issues.
This is a MUST as there is risk of issues with the first board and we need to control for the one variable we can.
This design differs from the RX888mk2 in many ways, and the key to being able to bring the board up among all of the developers is ensuring that the design choices or component placements made here allow the latest known-good Firmware to run. This way, the firmware gets out of the way of hardware testing and bring up. Else if the design was CONTINGENT on firmware development to run, this would serialize the development and cause a firmware designer a lot of grief.
These functions will NOT be supported by the latest known-good firmware (0.1.0 of rx888-firmware):
@ringof to perform a detailed FW review to ensure that either that HW does not demand immediate FW support (thru DNI resistors, etc), or if unable, to spin a new release of rx888-firmware ASAP for rx888mk2 validation to ensure it can drop-into the TAPRx888 without issues.
This is a MUST as there is risk of issues with the first board and we need to control for the one variable we can.