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/renodeReverse engineering e fuzzing

renode

⁨Auth/lab ref: Renode board and SoC simulation for MCU/RTOS firmware, UART/GPIO/peripheral modeling, GDB remote debugging, REPL platforms, and RESC scripts.⁩

v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 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/renode

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

FirmaFirmato, ed25519
B5lX+w5ZXq…jG5gcCDg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettob93625da…f7992cb7
b93625da6f17…aadcf7992cb71 file · ⁦1.8 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/renode@21cd568

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

Renode is the first public tool to try when firmware behavior depends on a modeled MCU board, RTOS peripherals, UART, GPIO, timers, storage, or multi-core SoC state.

Use Renode when

  • the artifact is MCU/RTOS firmware and a board or close SoC model exists
  • UART/GPIO/timer/storage/network peripheral behavior matters
  • QEMU lacks the exact board, or CPU-only emulation hangs on MMIO
  • you need deterministic virtual time and GDB remote debugging
  • you can write or adapt a .repl platform description for the minimum needed peripherals

Do not treat CPU stepping as board parity. Prove the peripheral behavior relevant to the objective.

Core objects

  • .repl: platform description; CPUs, memory maps, buses, UARTs, GPIOs, timers, and peripherals.
  • .resc: Renode monitor script; creates machines, loads platforms, loads binaries, configures analyzers, starts emulation.
  • Monitor: interactive command surface for machines, sysbus, peripherals, memory, UART analyzers, and GDB server.
  • Robot Framework: useful for validation harnesses that assert UART/peripheral output; keep it as test infrastructure, not the only evidence.

Minimal monitor flow

text
mach create
machine LoadPlatformDescription @platforms/boards/<board>.repl
sysbus LoadELF @firmware.elf
showAnalyzer sysbus.uart0
machine StartGdbServer 3333
start

Useful commands:

text
peripherals
sysbus WhatPeripheralIsAt 0x40000000
sysbus ReadDoubleWord 0x40000000
sysbus WriteDoubleWord 0x40000000 0x1
sysbus.cpu Step
pause
quit

For raw binaries, set load address and reset vector deliberately; ELF is safer when available because it carries sections and entry point.

Custom platform guidance

When no board exists:

  1. Build the smallest .repl from known CPU, RAM/flash, and MMIO ranges.
  2. Add UART first if console output is needed.
  3. Add timers/interrupt controller before assuming RTOS scheduler failure.
  4. Stub unknown peripherals only enough to pass non-target checks.
  5. Label the result as partial parity and list unmodeled peripherals.

Sources for modeling clues: vendor datasheet, SVD, linker script, map file, DTB, SDK headers, strings, disassembly xrefs to MMIO addresses, and logic/UART captures.

GDB

text
machine StartGdbServer 3333

Then connect with the matching toolchain:

bash
arm-none-eabi-gdb firmware.elf
(gdb) target remote :3333

Use GDB to prove reset handler, RTOS task creation, peripheral driver paths, memory state, and breakpoints on fault handlers.

Evidence

  • exact .repl/.resc or monitor command sequence
  • board/profile source and any custom modeled/stubbed devices
  • UART transcript, GPIO/peripheral read/write, memory state, or GDB breakpoint
  • whether proof is instruction execution, runtime boot, peripheral parity, or system parity

Failure pivots

  • no UART: wrong UART instance, firmware uses semihosting/RTT, clocks not modeled, or boot never reaches init
  • stuck in default handler: missing IRQ/timer/peripheral model
  • fault after reset: wrong load address, vector table, stack pointer, Thumb bit, or memory map
  • GDB oddities on multicore boards: start/select the correct CPU-specific GDB server

File di questa versione

Permessi

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

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

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 202621cd568b93625daFirmata–

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