Thank you very much! Finally unbricked my Yun! Your link was very helpful, after reading a little bit, what I ended up doing was accessing the file /usr/bin/run-avrdude thorugh vi. For anyone that don't understand what I just said, vi is a text editor, you type vi /usr/bin/run-avrdude and you can edit the file, there press "i" so you can edit the file, in the file I changed te part that sais "efuse" from FB to CB, then pressed "esc", typed :wq! + enter and saved the file that way. After that I was done, just opened the Arduino IDE, compiled and uploaded a simple blank program, and the board was unbricked!
Thanks everyone for the help! I hope this post might help someone with similar problems, apparently it is a Yun bug that I'm not even sure how I triggered.
Glad you are running again, this seems to crop up every so often, I don't know exactly what circumstances trigger the 0xcb != 0xfb bug. Since I never had it my setup always had 0xFB.
Vi is hard to adjust to but you can edit with a minimum of keystrokes when you get good at it.
BTW:
:wq! is:
: - command mode
w - write the file (save)
q - quit
! - I know I made changes, quit anyway
:x is exit saving changes, saves 2 whole keystrokes, 2 1/2 if you count the shift for the ! as a half.
davidrumsjb:
Thank you very much! Finally unbricked my Yun! Your link was very helpful, after reading a little bit, what I ended up doing was accessing the file /usr/bin/run-avrdude thorugh vi. For anyone that don't understand what I just said, vi is a text editor, you type vi /usr/bin/run-avrdude and you can edit the file, there press "i" so you can edit the file, in the file I changed te part that sais "efuse" from FB to CB, then pressed "esc", typed :wq! + enter and saved the file that way. After that I was done, just opened the Arduino IDE, compiled and uploaded a simple blank program, and the board was unbricked!
Thanks everyone for the help! I hope this post might help someone with similar problems, apparently it is a Yun bug that I'm not even sure how I triggered.
David.
noblepepper:
Glad you are running again, this seems to crop up every so often, I don't know exactly what circumstances trigger the 0xcb != 0xfb bug. Since I never had it my setup always had 0xFB.
Vi is hard to adjust to but you can edit with a minimum of keystrokes when you get good at it.
BTW:
:wq! is:
: - command mode
w - write the file (save)
q - quit
! - I know I made changes, quit anyway
:x is exit saving changes, saves 2 whole keystrokes, 2 1/2 if you count the shift for the ! as a half.
noblepepper and davidrumsjb, thak you, thank you, thank you!! i used your instructions to unbrick my 32u4 of yun. fantastic!!