aboutsummaryrefslogtreecommitdiffstats
path: root/firmware/test/Makefile
AgeCommit message (Collapse)AuthorFilesLines
2018-07-01firmware/test: Add more include pathsHarald Welte1-2/+14
Change-Id: I4287fbae6921ed0605265812df5d7243e8857864
2017-05-07migrate from req_ctx to msgbHarald Welte1-1/+2
We now generalize the USB communiction and abandon the 'req_ctx' structure inherited from openpcd. Instead we use the libosmocore 'msgb' structure to handle incoming and outgoing USB tranfers. We also use linuxlist-based msgb-queues for each endpoint.
2017-02-27fix compilation of card_emu_testsHarald Welte1-2/+2
2015-11-09initial commit of more code towards card emulationHarald Welte1-0/+13
I couldn't help but to spend my sunday on working towards card emulation, including * various state machines in the target about ISO7816 states * tc_etu timer import from simtrace1 * req_ctx import from simtrace1 (needs renaming and simplifiation) * USB protocol description as cardemu_prot.h * some host-based testing code to test the state machines The code seems to work fine throughout card reset, sending ATR and receiving the TPDU header of the first APDU, up to the point where it marks the TPDU header as to-be-transmitted over th bulk-in endpoint. Sending the ATR must be done inside the firmware for timing requirements. From that point onwards, the host needs to respond at the very least with a procedure byte, and some indication whether or not the card emulator should continue to transmit data (card->reader), or receive data (reader->card). The code is intentionally not hooked up yet with the USB logic nor with the UART. I want host-based testing completed before doing that.