<eZioPan[m]>
hi, does probe-rs have some commandline interface to interact with target MCU’s memory and registers(like telnet interface of OpenOCD)?
<eZioPan[m]>
VSCode is great, but if I just want to read a few bytes from MCU, then write down a config file, and start a debug session just be too heavy for me :)
duderonomy has joined #rust-embedded
GenTooMan has quit [Ping timeout: 248 seconds]
GenTooMan has joined #rust-embedded
crabbedhaloablut has joined #rust-embedded
barafael[m] has joined #rust-embedded
<barafael[m]>
You could do this using a USB-to-serial converter (also calls am 'ftdi'). This would require a free serial port on the device. The advantage would be that you would not be bound to a debugger, but your firmware would have to know how to receive serial commands. If you want to do it via debugger, then I would say reserve a page of memory for your config data and use sth. like
<barafael[m]>
`probe-rs download 43439A0.bin --format bin --chip RP2040 --base-address 0x10100000`
<barafael[m]>
`probe-rs download 43439A0.bin --format bin --chip RP2040 --base-address 0x10100000`
<barafael[m]>
* eZio Pan: you could do this using a USB-to-serial converter (also referred to as an 'ftdi'). This would require a free serial port on the device. The advantage would be that you would not be bound to a debugger, but your firmware would have to know how to receive serial commands. This might be something you need anyway. If you want to do it via debugger, then I would say reserve a page of memory for your config data and use sth.
<barafael[m]>
like
GenTooMan has quit [Ping timeout: 248 seconds]
<eZioPan[m]>
thanks! I might not make myself clearly, I want to halt the MCU, then read/modify some bytes from SRAM/peripheral register. I think I will need to use a debugger to access these bytes. Currently I try move from OpenOCD workflow to probe-rs one, thus I’d like to know a simple way with probe-rs.