STM32 PN532 AES Reader Firmware -- 2
£750-1500 GBP
Posted 1 minute ago
•
Ends in 6 days
£750-1500 GBP
Paid on delivery
I have a PN532 NFC front-end wired to an STM32 and now need complete firmware that turns this hardware into a reliable MIFARE Ultralight AES reader/writer. The reader must perform AES-128 authentication and CMAC generation/verification, then expose read- and write-protected memory commands once the card is authenticated. What I expect from you • Fully commented STM32 firmware (CubeIDE or compatible GCC project) that drives the PN532 in ISO14443-A mode, implements the Ultralight AES security flow, handles errors, and outputs clear status codes. • A simple, documented UART command interface: human-readable commands such as AUTH, READ <page>, WRITE <page> <data>. • A reference host script or small desktop console app that exercises every command so I can test the reader immediately after flashing. Please keep the design portable across the common STM32 families (F1/F4/L4). If you rely on third-party crypto libraries, include them under a permissive license or point to a readily obtainable source. Acceptance criteria will be the ability to: 1. Power up, select a card, run AES authentication, and output a valid CMAC over UART. 2. Read and write a protected page while the session key is active. 3. Recover gracefully from failed authentications or missing cards. Let me know your preferred STM32 part for development, any extra hardware you might require, and the timeline for first test firmware.
Project ID: 40809123
About the project
18 proposals
Open for bidding
Remote project
Active 2 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
18 freelancers are bidding on average £1,100 GBP for this job


Hi, I understand you need reliable STM32 firmware for a PN532-based MIFARE Ultralight AES reader/writer, including card selection, AES-128 authentication, CMAC handling, protected page access, error recovery, and a clear UART command interface. I will build this as a portable C Programming project for STM32 F1/F4/L4, with practical Software Development structure, Microcontroller drivers, and the needed Electronics interface checks. The CubeIDE/GCC project will be fully commented, with status codes and a small host console for testing AUTH, READ, and WRITE immediately after flashing. I will also document the crypto source and confirm the preferred STM32 part and hardware setup before implementation. Could you share the exact STM32 part, PN532 connection details, and Ultralight AES card configuration so I can confirm the firmware plan and test setup? Please start the chat and let’s discuss your exact PN532 wiring, card security settings, and first test target.


Hello, STM32 embedded development combined with practical electronics and hardware troubleshooting makes me well suited to turn your PN532 hardware into a dependable reader/writer. I have over 10 years of experience in embedded systems, STM32, microcontrollers, UART, and industrial electronics, with hands-on involvement across prototyping, testing, debugging, and commissioning. I can develop a portable CubeIDE/GCC firmware structure for STM32 F1, F4, or L4, including PN532 ISO14443-A communication, AES-128 authentication, CMAC handling, protected read/write commands, UART status reporting, and graceful recovery from missing cards or failed authentication. My experience with STM32, embedded control systems, and UART interfaces directly matches the reader firmware and documented command-console requirements. I will also provide clear source comments and a reference host-side test utility so the complete command flow can be exercised after flashing. I am ready to develop and validate the first firmware around a practical STM32 target and coordinate the required PN532/card test hardware. Choose me for a hardware-aware embedded implementation focused on reliable testing and integration. Thanks!


STM32 embedded firmware development and hardware bring-up are central to my work, making this PN532 reader project a strong match. I develop production-ready embedded C/C++ systems on STM32 and work directly with device drivers, communication protocols, UART, SPI, and I²C—covering the interfaces needed for a portable PN532 implementation across F1, F4, and L4 families. My background in embedded systems, electronics, RF hardware, and validation supports the complete reader solution: reliable ISO14443-A communication, AES-128 authentication, CMAC processing, protected memory access, clear UART status reporting, and graceful handling of missing cards or failed authentication. I can also provide a CubeIDE/GCC-compatible project with commented source, a documented UART command interface, and a reference host console for exercising AUTH, READ, and WRITE commands. I would be glad to develop the initial target around an STM32 family already suitable for your hardware and deliver a robust, portable firmware foundation.


SUPER MATCH, "MAKE AES-AUTHENTICATED NFC ACCESS RELIABLE ON STM32" - The critical part is implementing the PN532 communication and MIFARE Ultralight AES security flow correctly, including authentication, CMAC verification, and protected memory access. I can develop a documented STM32 firmware project with PN532 communication, AES-128 authentication, CMAC handling, protected READ/WRITE commands, and a UART interface. I'll also include a host-side test script, clear error codes, and recovery handling for missing cards or failed authentication. I recommend STM32F4 with STM32CubeIDE as the initial development target, keeping the code portable to F1 and L4. Which exact STM32 part and PN532 communication interface are you using, and can you provide the card type and AES protocol documentation? Looking forward to working with you.


I can deliver a robust STM32 firmware solution for your PN532 MIFARE Ultralight AES reader, mirroring the successful implementation of secure authentication and data handling in similar embedded NFC projects I've completed. My expertise includes precisely interfacing with NFC front-ends and implementing cryptographic protocols. My approach will involve leveraging the STM32CubeIDE and its HAL libraries for efficient peripheral management, focusing on I2C communication with the PN532. I'll integrate a well-tested AES-128 library and implement the CMAC generation and verification logic as per the MIFARE Ultralight C standard. The firmware will manage state transitions for authentication, secure read/write operations, and robust error handling, exposing a clear, documented UART interface for command control and status reporting. How do you envision the error reporting mechanism for authentication failures, and are there specific memory regions you prioritize for read/write protection configuration? I'm eager to discuss these details and how I can quickly bring this project to completion.


CORE REQUIREMENT - Reliable STM32 firmware that handles PN532 communication, AES authentication, CMAC verification, and protected card read/write operations. Hi - Adelman here from Texas. This needs careful separation between the PN532 communication layer, card security protocol, and UART command handling. I would structure the firmware into portable modules so the STM32-specific hardware code stays separate from the NFC and cryptographic logic. Before implementation, the exact MIFARE Ultralight AES variant and its authentication sequence need to be confirmed. Those details determine the command flow, session-key handling, CMAC rules, and protected memory behavior. I can also plan the UART test interface and host-side test script around the acceptance criteria. I want to be transparent that I don't have a verified portfolio example of PN532 or MIFARE Ultralight AES firmware, so I won't claim prior hardware validation. Which STM32 board and PN532 interface are you currently using, SPI or I2C? Looking forward to work with you.


Hi, Melih here >> "STM32 PN532 MIFARE ULTRALIGHT AES FIRMWARE" - you need secure card authentication, verified CMAC operations, and reliable protected memory access. I would build this in portable C, keeping the PN532 communication, AES-128 authentication, CMAC handling, and UART commands in separate modules. I'd prioritize getting the complete authentication flow working first, then add protected READ/WRITE operations and recovery for missing cards or failed authentication. The project will include a test script and clear firmware documentation. I suggest starting with an STM32F4. Which exact STM32 board and MIFARE Ultralight AES card revision are you using? Looking forward to work with you.


Hi there, Which STM32 family do you want to use for the first build, and do you already have a PN532 breakout with proven SPI or I2C wiring? Does the host script need to stay cross-platform in Python, or is a small desktop app on one OS enough for your test setup? The main task is to make the PN532 talk cleanly in ISO14443-A mode, then layer the Ultralight AES flow on top with clear UART status replies. A portable CubeIDE project can keep the low-level driver separate from the card logic, so the same code stays usable on F1, F4, or L4 parts. One risk is timing and state handling around auth failures, card removal, and CMAC checks. That is best handled with a strict command state machine, timeout recovery, and a small crypto wrapper so the firmware never mixes transport errors with security errors. The firmware can be structured for easy testing: UART commands for AUTH, READ, and WRITE, plus a host tool that exercises the full sequence right after flashing. If helpful, the first step can be a minimal bring-up on one STM32 part, then the portable layers can be expanded once the card exchange is stable. Best, Hlib


The key part here is the Ultralight AES flow: the AES-128 mutual authentication, then session-key CMAC on every protected read and write. I'll build it on a small PN532 driver over your link (SPI, I2C or UART), with a thin HAL layer so F1, F4 and L4 all build. You'll get commented CubeIDE/GCC firmware, the AUTH/READ/WRITE UART commands, and a Python test script. I've done a lot of STM32 firmware and Modbus/industrial work. I'd start on an F4 or L4 Nucleo, and first test firmware can be ready in about 4 days. Which PN532 interface and STM32 part are you wired to?


Hello, You've got the PN532 and STM32 hardware set up and need firmware that handles MIFARE Ultralight AES authentication, CMAC, and protected memory operations reliably. The tricky part here is ensuring the AES-128 flow and CMAC verification are robust, especially with edge cases like failed authentications or missing cards, while keeping the design portable across STM32 families. I'd start by setting up the PN532 in ISO14443-A mode and implementing the Ultralight AES security flow, focusing on error handling and clear status codes. Next, I'd build the UART command interface with human-readable commands like AUTH, READ, and WRITE, followed by a simple host script to test every command. For crypto, I'd use a lightweight library like TinyCrypt or LibTomCrypt, ensuring it's permissively licensed and easy to integrate. I'd aim for initial test firmware within 7-10 days. I recently delivered a project involving secure hardware communication and crypto integration, so this is familiar territory. Which STM32 part would you prefer for development, or should I proceed with the F4 series as a default?
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗