package hw.trezor.messages.debug

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message DebugLinkDecision

messages-debug.proto:20

* Request: "Press" the button on the device @start @next DebugLinkLayout

enum DebugLinkDecision.DebugButton

messages-debug.proto:37

* Structure representing button presses

Used in: DebugLinkDecision

enum DebugLinkDecision.DebugPhysicalButton

messages-debug.proto:47

TODO: probably delete the middle_btn as it is not a physical one

Used in: DebugLinkDecision

enum DebugLinkDecision.DebugSwipeDirection

messages-debug.proto:27

* Structure representing swipe direction

Used in: DebugLinkDecision

enum DebugLinkDecision.DebugTouchEventType

messages-debug.proto:63

* Explicit touch event type, used to separate TOUCH_START and TOUCH_END If not set, defaults to full click behavior (TOUCH_START + optional hold + TOUCH_END)

Used in: DebugLinkDecision

message DebugLinkEraseSdCard

messages-debug.proto:238

* Request: Erase the SD card @start @next Success @next Failure

message DebugLinkFlashErase

messages-debug.proto:228

* Request: Erase block of flash on device WARNING: Writing to the wrong location can irreparably break the device. @start @next Success @next Failure

message DebugLinkGcInfo

messages-debug.proto:281

* Response: GC heap information details. @end

message DebugLinkGcInfo.DebugLinkGcInfoItem

messages-debug.proto:287

* Key-value pair.

Used in: DebugLinkGcInfo

message DebugLinkGetGcInfo

messages-debug.proto:275

* Request: Get GC heap information. @start @next DebugLinkGcInfo

(message has no fields)

message DebugLinkGetPairingInfo

messages-debug.proto:156

* Request: Host asks for device pairing info @start @next DebugLinkPairingInfo

message DebugLinkGetState

messages-debug.proto:105

* Request: Host asks for device state @start @next DebugLinkState

enum DebugLinkGetState.DebugWaitType

messages-debug.proto:107

/ Wait behavior of the call.

Used in: DebugLinkGetState

message DebugLinkLayout

messages-debug.proto:76

* Response: Device text layout as a list of tokens as returned by Rust @end

message DebugLinkLog

messages-debug.proto:184

* Response: Device wants host to log event @ignore

message DebugLinkMemory

messages-debug.proto:204

* Response: Device sends memory back @end

message DebugLinkMemoryRead

messages-debug.proto:195

* Request: Read memory from device @start @next DebugLinkMemory

message DebugLinkMemoryWrite

messages-debug.proto:215

* Request: Write memory to device. WARNING: Writing to the wrong location can irreparably break the device. @start @next Success @next Failure

message DebugLinkOptigaSetSecMax

messages-debug.proto:268

* Request: Set Optiga's security even counter to maximum @start @next Success

(message has no fields)

message DebugLinkPairingInfo

messages-debug.proto:166

* Response: Device pairing info @end

message DebugLinkRecordScreen

messages-debug.proto:95

* Request: Start or stop recording screen changes into given target directory @start @next Success

message DebugLinkReseedRandom

messages-debug.proto:86

* Request: Re-seed RNG with given value @start @next Success

message DebugLinkResetDebugEvents

messages-debug.proto:259

* Request: Remove all the previous debug event state @start @next Success

(message has no fields)

message DebugLinkSetLogFilter

messages-debug.proto:298

* Request: Set logging filter string. @start @next Success

message DebugLinkState

messages-debug.proto:134

* Response: Device current state @end

message DebugLinkStop

messages-debug.proto:178

* Request: Ask device to restart @start

(message has no fields)

message DebugLinkWatchLayout

messages-debug.proto:248

* Request: Start or stop tracking layout changes @start @next Success