<re_irc>
<kristoff> I am new to embedded-rust. Can somebody help "decode" this error ?
<re_irc>
<kristoff> what exactly is the problem here?
<re_irc>
<kristoff> and why does it point to a package in "src/03-setup" while I am in src/05-led-roulette ?
<re_irc>
<9names (@9names:matrix.org)> i built it earlier today, just did a clean run through to step 5 from a zip downloaded from git master and it built correctly.
<re_irc>
is microrust a rust project? it might be picking up settings/config from there.
<re_irc>
<kristoff> microrust is the old name of running rust on a microbit . I think it has now been merged in the main embedded-rust repo
<re_irc>
<kristoff> I was trying the old version yesterday, so that is why the name still is there in my folders :-)
<re_irc>
<9names (@9names:matrix.org)> but are there any cargo.toml/etc files in there?
<re_irc>
<kristoff> I will do afull clear try again
<re_irc>
<kristoff> * a full
<re_irc>
<9names (@9names:matrix.org)> cargo looks back up the directory tree when building, can lead to interesting results if you've got another project there
<re_irc>
<kristoff> question .. if you install packages with cargo (I guess that is what it does when you have a "require"), can they "interfere" with other packages ...
<re_irc>
<kristoff> OK, looks like you answered my question while I was tying it :-)
<re_irc>
<kristoff> how can you create multiple projects and be sure that this issue does not happen ?
<re_irc>
<9names (@9names:matrix.org)> you give them their own directory structure, with nothing else below them that can interact:
<re_irc>
<9names (@9names:matrix.org)> kristoff: these crates are in the same workspace, so cargo considers their dependencies while building.
<re_irc>
they shouldn't have any conflicts currently, so i think the error is being caused by something else
<re_irc>
<kristoff> 9names: where does it actually store all the packages?
<re_irc>
<kristoff> it seems to install and compile all kind of libraries .. so I guess they must be stored somewhere
<re_irc>
<kristoff> * cargo
<re_irc>
<kristoff> 9names: I'll first clean up my machine a little bit so I have a fresh slate to start from
<re_irc>
<9names (@9names:matrix.org)> programs installed with "cargo install" end up in $HOME/.cargo/bin, and the libraries/binaries for each project brought in by "cargo build" or "cargo run" end up in [project_root]/target
<re_irc>
<kristoff> ok .. thanks for the info :-)
causal has quit [Quit: WeeChat 3.6]
neceve has quit [Read error: Connection reset by peer]
neceve has joined #rust-embedded
GenTooMan has quit [Read error: Connection reset by peer]
GenTooMan has joined #rust-embedded
<re_irc>
<xldenis> 👋 does anyone have a good way to setup an embedded debugger in VSCode for _non_ Rust projects?
<re_irc>
<newam> for debugging it's the same for C/C++/rust since they all make an ELF
<re_irc>
<xldenis> well... the the difference is probe.rs has an extension which seems to configure it all for you
<re_irc>
<xldenis> and I'm a big idiot when it comes to embedded things, so I have no idea how to properly set up things like openocd etc...
<re_irc>
<newam> probe-rs (the binary, not sure what the extension is) does also work for C/C++
<re_irc>
<newam> Basically you setup openocd to serve a GDB server (default), then you just find a vscode extension that can connect to a GDB server
<re_irc>
<xldenis> newam: does this work with SAMD boards? as I said, I'm incredibly unknowledgeable when it comes to embedded, I'm just trying to figure out why the bootloader isn't jumping to my code
<re_irc>
<newam> xldenis: I don't know anything about SAMD boards, sorry :/
<re_irc>
If the SAMD board has SWD or JTAG, and the probe connected is compatible with OpenOCD then it will work.
<re_irc>
<newam> if setting up vscode is giving you problems you can also just use "gdb", bit of a pain to find the commands for what you want to do, but it is much less finiky than vscode for first-time setup
<re_irc>
<newam> also I think you don't even need OpenOCD these days? There are some probe-rs tools with a gdbserver built in IIRC
<re_irc>
<xldenis> ah, yes it seems like there's a "probe-rs-cli" binary i can install
<re_irc>
<xldenis> I'm able to reset my chip with it, but other commands return "Unexpected DAP response: 0" any idea what that means?
<re_irc>
<xldenis> also able to read memory, but can't run "probe-rs-cli info"
<re_irc>
<xldenis> "probe-rs-cli debug" even works...
<re_irc>
<newam> 🤔
<re_irc>
<xldenis> and I think the gdb server works!
causal has joined #rust-embedded
dc740 has quit [Remote host closed the connection]