You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prior to ch. 7 on Registers, each chapter by default uses the overall project's default src/.cargo/config.toml, which some chapters suggest modifying to use your platform's specific gdb.
This is overridden for the first time in Ch 7 by an unmentioned src/07-registers/.cargo/config with a default assumption that arm-none-eabi-gdb is to be used. In my case, no such gdb exists, and cargo run fails. Editing as follows allowed me to continue, but some may not understand the resulting error from Cargo well enough (or realize that you can have a multitude of .cargo/config or .cargo/config.toml files) to fix the issue:
Hmm, I guess those are left overs not removed in #308. @winksaville is there any reason why those config files other than ./src/.cargo/config.toml should stay?
I deleted the .cargo directory under f3discovery/src/07-registers, and now cargo run is successfully using the appropriate config from f3discovery/src/.cargo.
Prior to ch. 7 on Registers, each chapter by default uses the overall project's default
src/.cargo/config.toml
, which some chapters suggest modifying to use your platform's specificgdb
.This is overridden for the first time in Ch 7 by an unmentioned
src/07-registers/.cargo/config
with a default assumption thatarm-none-eabi-gdb
is to be used. In my case, no suchgdb
exists, andcargo run
fails. Editing as follows allowed me to continue, but some may not understand the resulting error from Cargo well enough (or realize that you can have a multitude of .cargo/config or .cargo/config.toml files) to fix the issue:Maybe it's worth adding a helpful note in chapters where a custom config exists so users know exactly what to modify to get back to a working state?
The text was updated successfully, but these errors were encountered: