Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arduini Nano Every avrdude EEPROM writing issue. #120

Closed
mcuee opened this issue Aug 17, 2022 · 3 comments
Closed

Arduini Nano Every avrdude EEPROM writing issue. #120

mcuee opened this issue Aug 17, 2022 · 3 comments

Comments

@mcuee
Copy link

mcuee commented Aug 17, 2022

Ref: avrdudes/avrdude#1069 (comment)

For my official Arduini Nano Every board, it does not work with EEPROM writing, using latest avrdude git. I also tried different binaries (including Arduino version of avrdude 6.3 and 7.0) and none of them works.

I tend to believe it is a MuxTO FW issue on the SAM D11.

Interestingly I have a Nano 4808 clone and it works better (still got the RSP_ILLEGAL_MEMORY_TYPE warning message but it works in the end).

PS C:\work\avr\avrdude_test\avrdude_bin> mode COM7 baud=12 dtr=on > nul
PS C:\work\avr\avrdude_test\avrdude_bin> mode COM7 baud=12 dtr=off > nul

PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude.exe -C .\avrdude.conf -patmega4809 -cjtag2updi
 -PCOM7 -b115200 -Ueeprom:w:entest_256B.eep:i

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.29s

avrdude.exe: Device signature = 0x1e9651 (probably m4809)
avrdude.exe: reading input file entest_256B.eep for eeprom
avrdude.exe: writing 256 bytes eeprom ...

Writing |                                                   
 | 0% 0.00savrdude.exe: jtagmkII_paged_write(): bad response to write memory command: RSP_ILLEGAL_MEMORY_TYPE
Writing | #############                                      
| 25% 0.01savrdude.exe: jtagmkII_write_byte(): fatal timeout/error communicating with programmer (status -1)
 ***failed;
avrdude.exe: jtagmkII_write_byte(): fatal timeout/error communicating with programmer (status -1)
 ***failed;
avrdude.exe: jtagmkII_write_byte(): fatal timeout/error communicating with programmer (status -1)
 ***failed;

Debug message with -vvvv.

avrdude.exe: jtagmkII_write_byte(.., eeprom, 0xc, ...)
avrdude.exe: jtagmkII_write_byte(): Sending write memory command:
avrdude.exe: jtagmkII_send(): sending 11 bytes
avrdude.exe: Send: . [1b] . [1d] . [00] . [0b] . [00] . [00] . [00] . [0e] . 
[04] . [c4] . [01] . [00] . [00] . [00] . [0c] . [14] . [00] . [00] o [6f] { [7b] = [3d]
avrdude.exe: jtagmkII_recv():
avrdude.exe: ser_recv(): programmer is not responding
avrdude.exe: jtagmkII_recv(): Timeout receiving packet
@mcuee
Copy link
Author

mcuee commented Aug 17, 2022

Ref: #103

Looks like there is some hurdle to compile the FW even if I want to try the latest git instead of the factory FW.

@mcuee
Copy link
Author

mcuee commented Aug 24, 2022

@mcuee
Copy link
Author

mcuee commented Oct 13, 2022

The following PR from avrdude seems to be able to work around the firmware issue in terminal mode. Normal mode may be fixed using similar method as well.

I will close this one.

@mcuee mcuee closed this as completed Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant