MCU to TDA8035 to smartcard flow chart

2026-05-31

Stack Overflow: View Question

Tags: embedded, flowchart, mcu, nuvoton

Score: 0 | Views: 40

The asker is integrating a Nuvoton MCU with the NXP TDA8035 smart card interface IC. They've stitched together reference code from Nuvoton, MCUXpresso, and Arduino, but the card never returns an ATR (Answer To Reset) — the very first byte sequence a card emits after activation. Without an ATR, no further ISO 7816-3 communication is possible.

Why this is interesting: The ATR failure mode is deceptively rich. The TDA8035 is an analog front-end that does level shifting, VCC sequencing, clock generation, and ISO 7816 activation/deactivation timing for you — but only if you drive its control lines in the right order and your UART-style I/O is configured correctly for the bizarre half-duplex, open-drain, inverse-convention world of smart cards. There are at least a dozen places for a beginner to go wrong silently.

A debugging flow chart, in priority order:

Gotchas: Many TDA8035 dev boards omit the 1.8 µF VCC tank cap → unstable activation. The SAM_VCC level select pin must match the card class. And if the MCU's UART can't do 2 stop bits natively, you must emulate them or the card will see a framing error and never reply.

The challenge: A "no ATR" failure spans analog activation timing, ISO 7816 frame format, and the TDA8035's specific control pin choreography — any one wrong, and the card stays silent with no diagnostic output to guide you.

All newsletters