Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/jtag-swdMobile, firmware e hardware

jtag-swd

⁨Non-destructive JTAG/SWD pin identification, OpenOCD configuration, CPU halting, and runtime memory dumping.⁩

v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 Stellesincronizzato 11 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/jtag-swd

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
clqBlT6T3S…niiWLwDg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettof7d2ba46…6fc57b00
f7d2ba46a5d3…ba3c6fc57b002 file · ⁦2.4 KB⁩
ScansioneMedio2 segnalazioni
  • Nessuna licenza trovata
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-hardware/jtag-swd@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

Use when firmware extraction is needed but direct SPI flash reading is physically impossible (BGA chips, eMMC), or live debugging/execution flow control is required.

1. Interface identification

  • Standard JTAG: TCK, TMS, TDI, TDO, nTRST, nSRST, GND, VCC.
  • ARM SWD: Compact 2-wire alternative (SWDIO, SWDCLK, GND, VCC).
  • Use tools like JTAGulator or JTAGenum on unknown pin headers to automatically scan for TDO responses without manual probing.

2. Electrical and target preflight

Before connecting, confirm the target's I/O voltage, probe voltage compatibility, supported transport (JTAG or SWD), pinout, and any required level shifting from the target and probe documentation. Do not assume VTref powers the target or has the same function on every probe; check that probe's manual before wiring or powering anything. See the OpenOCD adapter guidance.

For the original ESP32, use JTAG, not SWD. ESP-IDF v6.1 documents JTAG I/O on VDD_3P3_RTC (normally 3.3 V); ensure the adapter supports the target's I/O level. Do not generalize this pin, voltage, or transport note to other ESP32-family chips; check the exact device documentation. See ESP-IDF v6.1 JTAG debugging.

ESP-IDF v6.1 documents a configuration-dependent case where flash-encryption setup disables JTAG by burning the relevant eFuse on first boot. Check the project's flash-encryption configuration and actual eFuse state for the specific original ESP32 before expecting debug access; flash encryption alone is not evidence that this eFuse was burned. See ESP-IDF v6.1 flash encryption.

3. OpenOCD connection

Map the physical interface (e.g., FTDI-based programmer like Olimex or TIAO) and the target MCU architecture.

bash
# Example: Connect to an STM32F4 via an Olimex ARM-USB-OCD-H programmer
openocd -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -f target/stm32f4x.cfg

4. Execution control & dumping

Connect to OpenOCD's telnet control interface (localhost:4444).

text
> telnet localhost 4444
# Halt the CPU execution cleanly
> halt

# Inspect CPU state and registers
> reg

# Dump specific memory region (e.g., 1MB starting from flash base 0x08000000)
> dump_image firmware.bin 0x08000000 0x100000

# Resume normal execution
> resume

5. Risks & Considerations

  • Watchdog Timers: Halting via JTAG may trigger hardware watchdogs, causing abrupt resets.
  • Read-out Protection (RDP): Microcontrollers (especially STM32/NRF) often set internal fuses disabling JTAG debug access or flash reads. Bypassing requires chip-specific glitching workflows.

References

  • references/stm32-rdp-bypass.md — Load when an STM32 Read-Out Protection (RDP) prevents memory extraction in OpenOCD.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaLicenza · Nessuna licenza trovata
  2. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd568f7d2ba46Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login