AVR avrdude stk500v2_ReceiveMessage(): timeout, Bootloader Huh?
up vote
0
down vote
favorite
I am using stk500v2bootloader
that I have modified to accomodate RS485 to my electronic device.
When I program a .hex file via avrdude.exe, it programs one of my .hex files successfully. But if program another similar but larger .hex file, it programs the .hex file for a few seconds and then stops giving message:
R.00V2....BOOTLOADER HUL?....
stk500v2_ReceiveMessage(): timeout.
avr avrdude
add a comment |
up vote
0
down vote
favorite
I am using stk500v2bootloader
that I have modified to accomodate RS485 to my electronic device.
When I program a .hex file via avrdude.exe, it programs one of my .hex files successfully. But if program another similar but larger .hex file, it programs the .hex file for a few seconds and then stops giving message:
R.00V2....BOOTLOADER HUL?....
stk500v2_ReceiveMessage(): timeout.
avr avrdude
The "Huh" message that AVRDUDE is receiving from your bootloader makes it seem like your bootloader is using some kind of non-standard ASCII-based protocol, and also it doesn't understand the messages that AVRDUDE is sending to it. You need to find a bootloader that is compatible with AVRDUDE, or if this one is, then carefully read its documentation to understand what options to pass to AVRDUDE so that AVRDUDE will use the right protocol when talking to the bootloader.
– David Grayson
2 days ago
Thanks. That is the weird thing. I did not change anything except add control for RS485 Tx/Rx control pin. The bootloader is working fine for all RS232 comms (before adding RS485 comms) and the RS485 version works for .hex file for similar project to the one that gives this error. The one that does not work is just a larger .hex file but still no where close to maximum flash size etc for ATmega2560V. Baffled...
– user10552007
2 days ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using stk500v2bootloader
that I have modified to accomodate RS485 to my electronic device.
When I program a .hex file via avrdude.exe, it programs one of my .hex files successfully. But if program another similar but larger .hex file, it programs the .hex file for a few seconds and then stops giving message:
R.00V2....BOOTLOADER HUL?....
stk500v2_ReceiveMessage(): timeout.
avr avrdude
I am using stk500v2bootloader
that I have modified to accomodate RS485 to my electronic device.
When I program a .hex file via avrdude.exe, it programs one of my .hex files successfully. But if program another similar but larger .hex file, it programs the .hex file for a few seconds and then stops giving message:
R.00V2....BOOTLOADER HUL?....
stk500v2_ReceiveMessage(): timeout.
avr avrdude
avr avrdude
edited 2 days ago
lagom
3,31651736
3,31651736
asked 2 days ago
user10552007
1
1
The "Huh" message that AVRDUDE is receiving from your bootloader makes it seem like your bootloader is using some kind of non-standard ASCII-based protocol, and also it doesn't understand the messages that AVRDUDE is sending to it. You need to find a bootloader that is compatible with AVRDUDE, or if this one is, then carefully read its documentation to understand what options to pass to AVRDUDE so that AVRDUDE will use the right protocol when talking to the bootloader.
– David Grayson
2 days ago
Thanks. That is the weird thing. I did not change anything except add control for RS485 Tx/Rx control pin. The bootloader is working fine for all RS232 comms (before adding RS485 comms) and the RS485 version works for .hex file for similar project to the one that gives this error. The one that does not work is just a larger .hex file but still no where close to maximum flash size etc for ATmega2560V. Baffled...
– user10552007
2 days ago
add a comment |
The "Huh" message that AVRDUDE is receiving from your bootloader makes it seem like your bootloader is using some kind of non-standard ASCII-based protocol, and also it doesn't understand the messages that AVRDUDE is sending to it. You need to find a bootloader that is compatible with AVRDUDE, or if this one is, then carefully read its documentation to understand what options to pass to AVRDUDE so that AVRDUDE will use the right protocol when talking to the bootloader.
– David Grayson
2 days ago
Thanks. That is the weird thing. I did not change anything except add control for RS485 Tx/Rx control pin. The bootloader is working fine for all RS232 comms (before adding RS485 comms) and the RS485 version works for .hex file for similar project to the one that gives this error. The one that does not work is just a larger .hex file but still no where close to maximum flash size etc for ATmega2560V. Baffled...
– user10552007
2 days ago
The "Huh" message that AVRDUDE is receiving from your bootloader makes it seem like your bootloader is using some kind of non-standard ASCII-based protocol, and also it doesn't understand the messages that AVRDUDE is sending to it. You need to find a bootloader that is compatible with AVRDUDE, or if this one is, then carefully read its documentation to understand what options to pass to AVRDUDE so that AVRDUDE will use the right protocol when talking to the bootloader.
– David Grayson
2 days ago
The "Huh" message that AVRDUDE is receiving from your bootloader makes it seem like your bootloader is using some kind of non-standard ASCII-based protocol, and also it doesn't understand the messages that AVRDUDE is sending to it. You need to find a bootloader that is compatible with AVRDUDE, or if this one is, then carefully read its documentation to understand what options to pass to AVRDUDE so that AVRDUDE will use the right protocol when talking to the bootloader.
– David Grayson
2 days ago
Thanks. That is the weird thing. I did not change anything except add control for RS485 Tx/Rx control pin. The bootloader is working fine for all RS232 comms (before adding RS485 comms) and the RS485 version works for .hex file for similar project to the one that gives this error. The one that does not work is just a larger .hex file but still no where close to maximum flash size etc for ATmega2560V. Baffled...
– user10552007
2 days ago
Thanks. That is the weird thing. I did not change anything except add control for RS485 Tx/Rx control pin. The bootloader is working fine for all RS232 comms (before adding RS485 comms) and the RS485 version works for .hex file for similar project to the one that gives this error. The one that does not work is just a larger .hex file but still no where close to maximum flash size etc for ATmega2560V. Baffled...
– user10552007
2 days ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53344447%2favr-avrdude-stk500v2-receivemessage-timeout-bootloader-huh%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The "Huh" message that AVRDUDE is receiving from your bootloader makes it seem like your bootloader is using some kind of non-standard ASCII-based protocol, and also it doesn't understand the messages that AVRDUDE is sending to it. You need to find a bootloader that is compatible with AVRDUDE, or if this one is, then carefully read its documentation to understand what options to pass to AVRDUDE so that AVRDUDE will use the right protocol when talking to the bootloader.
– David Grayson
2 days ago
Thanks. That is the weird thing. I did not change anything except add control for RS485 Tx/Rx control pin. The bootloader is working fine for all RS232 comms (before adding RS485 comms) and the RS485 version works for .hex file for similar project to the one that gives this error. The one that does not work is just a larger .hex file but still no where close to maximum flash size etc for ATmega2560V. Baffled...
– user10552007
2 days ago