Aster for End Products

The intended use of the Aster Carrier Board is listed as for Evaluation/Development. Why is it not recommended to use this board for End Products?

Related: Is it possible to use the first 40 pins of the Viola Plus extension connector as a Raspberry Pi HAT interface?

Like many others, I am trying to find a replacement for a Raspberry Pi based device that relies on a HAT expansion board. Custom carrier board design is beyond the scope of this project, but custom device tree modifications are not. I have experience working with the device tree in Toradex Embedded Linux, and some minor experience with Torizon. My goal is to keep the hardware components of this project as “off-the-shelf” as possible.



Using the Aster or Iris board in your end products is at your own risk. These boards have not been tested for any certifications, such as EMI, and we are unable to provide any supporting documents if you require certification for your end product.
The pinout of the extension connectors on the Aster and Iris boards are available in their respective datasheets. Therefore, you can compare them with PI HAT and check whether the desired signals are available on the same pins or not