All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Understanding Hard-Float vs Soft-Float Implementations on Cortex-M Processors

By

hasheddan

1mo ago· 10 min readenInsight

Summary

The article discusses floating-point operations on Cortex-M processors, focusing on the differences between hard-float and soft-float implementations. It references a previous post about the PSA Crypto API and how ECDSA signature operations are handled on nRF52840 MCUs through closed-source libraries that interface with Arm TrustZone CryptoCell 310. The author explores the implications of floating-point variants in embedded systems libraries and their impact on performance and compatibility.

Key quotes

· 4 pulled
Readers that ventured down the rabbit hole of links in the post may have noticed that there are variants of the nrf_cc310_mbedcrypto libraries for hard-float and soft-float.
In the case of the former, the ECDSA signature operation was eventually executed in a closed source library that manages communication between the Arm Cortex-M4 processor and the Arm TrustZone CryptoCell 310 security subsystem.
If you have ever hit an error from your linker of the type...
The article discusses floating-point operations on Cortex-M processors, focusing on the differences between hard-float and soft-float implementations.
Snippet from the RSS feed
In my recent post on the PSA Crypto API, I demonstrated the use of the API on two different MCUs: the nRF52840 and the ESP32-S3. In the case of the former, the ECDSA signature operation was eventually executed in a closed source library that manages commu

You might also wanna read