K900 has quit [Quit: Idle timeout reached: 172800s]
AtleoS has quit [Ping timeout: 272 seconds]
AtleoS has joined #rust-embedded
haobogu[m] has quit [Quit: Idle timeout reached: 172800s]
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #rust-embedded
norineko has quit [Remote host closed the connection]
norineko has joined #rust-embedded
norineko has quit [Remote host closed the connection]
norineko has joined #rust-embedded
slinkee[m] has joined #rust-embedded
<slinkee[m]>
heys guys and girls I'm learning how to code html and css and eventually wanna learn other coding languages too so ya lol
<slinkee[m]>
I would love to learn all I can
K900 has joined #rust-embedded
<K900>
#rust:matrix.org might be a better room for beginner questions unless you're specifically doing embedded
<slinkee[m]>
i can check that too, thanks!
dngrs[m] has quit [Quit: Idle timeout reached: 172800s]
RockBoynton[m] has quit [Quit: Idle timeout reached: 172800s]
diondokter[m] has quit [Quit: Idle timeout reached: 172800s]
adamhott[m] has joined #rust-embedded
<adamhott[m]>
If I'm sending out over UART, does anyone have any good experiences with a good UART to USB converter so I can "talk" to an rp2040 via the converter?
<JamesMunns[m]>
any reason not to just use the native USB on the device itself?
<adamhott[m]>
I'm a bit needing help, I'm making a glitch target for a rp2040 that I want to crack with another rp2040. I was thinking to make UART the protocol for that, but don't know exactly what to use, like a converter or if it can be done over native USB
<JamesMunns[m]>
probably depends what "protocol" you're looking to write, and how timing sensitive it is and stuff. Never written glitching code tho!
<adamhott[m]>
I basically want to create a simple example where I prompt a user for a password, and I want to glitch it to jump past the verification instruction and unlock the secret.
<adamhott[m]>
I thought it would be a good experiment in light of the rp2350 hacking challenge
<JamesMunns[m]>
gotcha! I know what you mean, but I've never done glitching, let alone building tools for doing it :)
<adamhott[m]>
gotcha!
jannic[m] has joined #rust-embedded
<jannic[m]>
<adamhott[m]> "If I'm sending out over UART..." <- The raspberry pi debug probe contains a USB/UART converter.
<adamhott[m]>
Does the rusty-probe allow for bi-directional communication in the same way as the raspberry pi debug probe?
<jannic[m]>
Via RTT? I think there's no difference. This is a software feature, the probe only provides access to the swd interface.
<adamhott[m]>
It seems like using usb-device and usbd_serial actually would make this a lot simpler