RfidResearchGroup/proxmark3
1
1
Fork 0
mirror of https://github.com/RfidResearchGroup/proxmark3.git synced 2025-12-18 22:20:26 +08:00
Code Issues Projects Releases Packages Wiki Activity
proxmark3/uart
History
Philippe Teuwen 21be6d4400 FPC: got RX working, got client over usart somehow working..., see detailed commit msg 
* using WITH_FPC:
  * activate basic usart
  * no double buffer for now, no interrupt
  * usart_dataavailable/usart_readbuffer/usart_writebuffer, to demo it:
    * pm3 client over USB, minicom over usart
    * analyse a d 414243
* using WITH_FPC_HOST:
  * it implies WITH_FPC as it's based on it
  * control pm3 with client over usart
  * EXPERIMENTAL! still some frame desync issues
  * you can connect both from usart & USB with two pm3 clients
    * actually you *have* to connect USB for the moment because
      it's used to send debug messages about buggy usart... See Dbprintf_usb below
  * "sessions": msgs are directed to the latest client to have sent a cmd
  * Dbprintf_usb macro to send msgs to USB client to help debugging usart...
  * We now have an option to run client at different speed as usart is 115200:
    client/proxmark3 /dev/ttyUSB0 -b 115200
  * Consequently, argc,argv handling is a bit revamped, it was so messy...
  * USB and flashing are still at 460800, don't try flashing over usart yet ^^
2019-04-02 22:06:10 +02:00
..
README.md part of monstermerge... 2017-07-27 20:48:49 +02:00
uart.h FPC: got RX working, got client over usart somehow working..., see detailed commit msg 2019-04-02 22:06:10 +02:00
uart_posix.c FPC: got RX working, got client over usart somehow working..., see detailed commit msg 2019-04-02 22:06:10 +02:00
uart_win32.c FPC: got RX working, got client over usart somehow working..., see detailed commit msg 2019-04-02 22:06:10 +02:00

README.md

uart

This contains functionality for talking to UART/Serial devices on different platforms. The official client will build either uart_posix.c and uart_win32.c. Build targets for these files are contained in client/Makefile.

If you want to implement support for other platforms, you need to implement the methods provided in uart.h.

Implementing a new driver

Each driver is called with a string, typically containing a path or other reference to a serial port on the host. The methods outlined in uart.h need to be implemented.

The hardware uses common/usb_cdc.c to implement a USB CDC endpoint exposed by the Atmel MCU.