This table lists all of the scores uploaded by members or licensees. It is not required that members or licensees upload scores, and in many cases the scores they create are for internal use only. However, EEMBC requires that before any license holder can use a score publicly (i.e., not under NDA) it must first be uploaded to the EEMBC website.
Scores that are certified have undergone a rigorous analysis by the EEMBC Certification Lab. Certification is a benefit only available to members, and guarantees the score adheres to the official run-rules for that benchmark.
Vendors who certify their scores may use the "EEMBC Certification Logo" () on their press release, product packaging, etc.
The energy score is the sum of the micro-Joules-per-iteration multiplied by a weighting factor, inverted and scaled by 100. The weighting array is [1,1,1,1,1,1,1,2,3,1,1,3,4,10] for the order of the scores listed in the detailed view. This array aligns the component scores to match the TLS handshake, plus a little extra AES traffic. Inverting the score ensures lower-is-better, and scaling by 100 moves the score into a suitable integer range. We only report three significant figures in the final score to avoid excess noise.
The performance calculation uses micro-seconds of execution time per iteration, and changes the final scale factor to 1000, but uses the same weights and inverse of weighted sum.
If the score was submitted by the manufacturer of the device hardware, the vendor field is type "dev". If the score was submitted by the vendor of the crypto library, the vendor field is "clib". This is to differentiate between platforms that are used as vehicles for software technology, as opposed to hardware vendors demonstrating a particular hardware feature. A blank in this field means the score was submitted by a licensee who is neither the device nor library vendor.