kerms
/
wireless-proxy-esp32
0
0
Fork 0
Code
wireless-proxy-esp32/README.md

6.5 KiB
Raw Blame History

Wireless ESP8266 DAP

Build Status master Build Status develop

PRs Welcome %e2%9d%a4

Introduce

Wireless debugging with only one ESP8266 !

Realized by USBIP and CMSIS-DAP protocol stack.

👉 5m distance, 100kb size firmware flash test:

Feature

  1. Debug Communication Mode

    • SWD
    • JTAG

  2. USB Communication Mode

    • USB-HID (Default)
    • WCID & WinUSB (Experimental)

  3. Debug Trace

    • UART Serial Wire Output(SWO)
    • SWO Streaming Trace

  4. More..

    • Custom maximum debug clock (40MHz, SWD only)
    • SWD protocol based on SPI acceleration
    • ...

Link your board

WIFI

The default connected WIFI SSID is DAP , password 12345678

You can change WIFI_SSID and WIFI_PASS in wifi_configuration.h

Debugger

SWD
SWCLK GPIO5
SWDIO GPIO4
LED_CONNECTED GPIO2
LED_RUNNING GPIO15
TVCC 3V3
GND GND
JTAG
TCK GPIO5
TMS GPIO4
TDI GPIO13
TDO GPIO12
nTRST optional GPIO0*
nRESET GPIO14
LED_CONNECTED GPIO2
LED_RUNNING GPIO15
TVCC 3V3
GND GND

You can modify these pin definitions in DAP_config.h

Tips: Try to avoid using GPIO0(working mode switch) and GPIO16(RTC)

Build

You can build locally or use Github Action to build online

Build with Github Action Online

See: Build with Github Action

General build

  1. Get ESP8266 RTOS Software Development Kit

    For now, use the 3.3-rc1 version of the SDK (this is a known issue) See: ESP8266_RTOS_SDK

  2. Build & Flash

    Build with ESP-IDF build system. More information can be found at the following link: Build System

The following example shows a possible way to build on Windows:

# Build
python ./idf.py build
# Flash
python ./idf.py -p /dev/ttyS5 flash

We also provided sample firmware quick evaluation. See Releases

Usage

  1. Get USBIP project

The pre-compiled version on SourceForge is also available, for HID mode only, but it may be faster.

  • Linux: Distributed as part of the kernel

  1. Start esp8266 and connect it to the device to be debugged

  2. Connect it with usbip:

# HID Mode only
# for pre-compiled version on SourceForge
# or usbip old version
.\usbip.exe -D -a <your-esp8266-ip-address>  1-1

# HID Mode Or WinUSB Mode
# for usbip-win 0.3.0 kmdf ude
.\usbip.exe attach_ude -r <your-esp8266-ip-address> -b 1-1

If all goes well, you should see your device connected.

image

Then test it under MDK:

target

Develop

  1. Check other branches to know the latest development progress.

  2. Use WinUSB Mode:

    change USE_WINUSB macor in USBd_config.h

Credits to:

In this repo you can find the complete implementation of the USB protocol stack including USB-HID, WCID, WinUSB. Although WinUSB-based mode currently does not work on USBIP 😥 . They are very easy and can help you quickly build your own DAP on other hardware platforms.

Currently TCP transmission speed needs to be further improved, If you have any ideas, welcome:

Issue

2020.12.1

TCP transmission speed needs to be further improved.

2020.11.11

Winusb is now available, but it is very slow.

2020.2.4

Due to the limitation of USB-HID (I'm not sure if this is a problem with USBIP or Windows), now each URB packet can only reach 255 bytes (About 1MBps bandwidth), which has not reached the upper limit of ESP8266 transmission bandwidth.

I now have an idea to construct a Man-in-the-middle between the two to forward traffic, thereby increasing the bandwidth of each transmission.

2020.1.31

At present, the adaptation to WCID, WinUSB, etc. has all been completed. However, when transmitting data on the endpoint, we received an error message from USBIP. This is most likely a problem with the USBIP project itself.

Due to the completeness of the USBIP protocol document, we have not yet understood its role in the Bulk transmission process, which may also lead to errors in subsequent processes.

We will continue to try to make it work on USB HID. Once the USBIP problem is solved, we will immediately transfer it to work on WinUSB

License

MIT LICENSE