hey all, I'm just starting with arduino etc. I wanted to use ravedude to flash the arduino. however I'm stuck with:
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00
what board are you using?
using avrdude it works with:
avrdude -C/etc/avrdude/avrdude.conf -v -patmega168 -carduino -P/dev/ttyUSB0 -b19200 -D -Uflash:w:/home/dietrich/Projekte/Source/rust-arduino-blink/target/avr-atmega168/release/rust-arduino-blink.elf:e
so its arduino nano but with atmega168
ravedude nano --open-console --baudrate 57600 -P /dev/ttyUSB0 target/avr-atmega168/release/rust-arduino-blink.elf
Board Arduino Nano
Programming target/avr-atmega168/release/rust-arduino-blink.elf => /dev/ttyUSB0
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00
I get that same error on the arduino IDE when I choose the default atmega328P
Is ravedude automagically expecting arduino nanos to have the atmega328P chip?
and thanks for your instant help!
yes, ravedude expects 328p because that's the only official nano ;)
but I've head of the clones already, we should add proper support for them in ravedude & avr-hal
Hmm, maybe it is the reset signaling that is not working. Try to push the reset button just before running the command
well it does not make sense to try calling avrdude with -patmega328p for an ATmega168 anyway
I'll hopefully get around to adding support in ravedude & avr-hal later this evening. If not, just ping me again enaut
jwagen I think reset is working just fine since the arduino stops the blinking pattern right when I press flash.
enaut: please try Rahix/avr-hal#195 and report if that makes it work (I don't have any such devices on hand to test myself)
I'll quickly add
arduino-hal support as well in the meantime
So if you point the git-revision in
Cargo.toml to e72faada6bb7f67990216525aeb2132bbb3d53e9, you should be able to use it just like you'd do for the Arduino Nano (with ATmega328P)
sorry I'm not sure I can follow here... I installed ravedude from the git version and then I can use it. My current dependency on avr-hal looks like:
[dependencies.arduino-uno]
git = "https://github.com/Rahix/avr-hal"
features=["arduino-nano"]
what should work after that does not work before?
add
rev = "e72faada6bb7f67990216525aeb2132bbb3d53e9" and change the features to features = ["nano168"]
what should work after that does not work before?
as the two chips are almost identical, most likely nothing. But to keep everything clean I'd want to have the 168 version be handled separate, ontop of its own HAL layer. This means if there ever are any differences to care for, it is easy to differentiate the two.
So more than supporting anything new, I just wanted to make sure I did not break anything with my changeset ;)
I fail to be successfull... I added the small blink example to a git repository: https://github.com/enaut/temp-test
```
❯ cargo run
Updating git repository `https://github.com/Rahix/avr-hal.git`
error: no matching package named `arduino-uno` found
location searched: https://github.com/Rahix/avr-hal.git?rev=e72faada6bb7f67990216525aeb2132bbb3d53e9
perhaps you meant: arduino-hal
required by package `rust-arduino-blink v0.1.0 (/home/dietrich/Projekte/Source/rust-arduino-blink)`
what do I do wrong?
ooh, I totally missed that you're still using the old version of
In that case, give me another minute - I'll prepare the new project template for the board, then you can just use that to test
avr-hal... Sorry :(In that case, give me another minute - I'll prepare the new project template for the board, then you can just use that to test
(We did some rather large changes to the crate-architecture of
avr-hal recently... Maybe check https://github.com/Rahix/avr-hal#repository-structure to familiarize yourself with the new layout if you intend to update your own projects)
as that is my only proof of concept project so far no need to upgrade ;)
alright, try generating a project with
cargo generate --git https://github.com/Rahix/avr-hal-template.git --branch wip and then selecting Nano168 as the board. If I didn't mess anything up, cargo run should be enough with that to make your board blink (might need to set a port with cargo run -- -P /dev/ttyFOO).
cargo run --bin test-nano168
Finished dev [optimized + debuginfo] target(s) in 0.02s
Running `ravedude nano168 -cb 57600 -P /dev/ttyUSB0 target/avr-atmega168/debug/test-nano168.elf`
Board Nano Clone (ATmega168)
Programming target/avr-atmega168/debug/test-nano168.elf => /dev/ttyUSB0
and then nothing happens
the weired thing is my other project works now with only
cargo run (after I pasted the code from your example)
Oh I found the difference what does
profile=minimal in toolchain.toml do?
on removing that everything works as expected
it shouldn't have an influence whatsoever... here is relevant documentation: https://rust-lang.github.io/rustup/concepts/profiles.html