![]() (They used to use the FTDI chip, now they use the 16U2 for USB communication) I put a brand new, from Digi-Key, 16U2 on Arduino 1. I'm not talking about the ATMEGA328 programs that I would write and upload, I'm talking about the programs in the 16U2 that serves as the USB interface. I know there's nothing magical about it, but I need to get it. (I know the code is gone - that's why I'm in this mess) I try to use the read flash and read eeprom functions, and I do get two files, but these files won't write - I keep getting verification errors. (I did read that one can perform the "erase chip" function on a read protected chip - but the code will then be gone. ![]() I'm not sure if I can read another "good" arduino with my USBtiny. I'd like to think I can re-program the 16U2, but this is proving difficult. Now, I'd like to undo the damage I've done. I shouldn't have tried to fix the damaged one when I didn't know what I was doing. Yes, I do indeed wish I had done nothing, but I accidentally erased the 26U2 on a working unit. a "good" ardunio loads the driver and appears as as an arduino connected via com port. Now, when I connect it to my computer, my computer doesn't even know that a USB device has been connected. I had the 16U2 ICSP connected to the USB tiny, and accidently used the "erase chip" function of AVRDUDE. Again, I'm not terribly upset at being out two Arduinos, but because one of them has no hardware problems at all, (was working before I got careless and erased its 16U2) I'd like to undo my mistake for general principles. ![]() I am horrible at using search engines, so forgive me if they are readily available. Can anyone help me out of this mess? Are the files available somewhere? I've looked and looked and can't find it. I attempted to find these files on the internet, but all I can find is a "combined" file that is used with atmel "Flip." "Flip" seems great for firmware upgrades, but since my 16U2 is bricked, it does me no good. I believe that means the good unit is read-protected. ![]() I suspect that I'm not really reading the "good" arduino because the lock bits are set at 0x0F (unmolested, working unit), while the blank 16U2 is showing 0x3F for the lock bits. (They matched the third arduino, Which I've manged to not destroy, so far.) However, when I attempt to write the flash and EEprom to the bricked arduino, I get a verification error. I created two files, one for the flash, and one for the EEprom, and the "Verify" function said the files were good. I took a third Arduino, and tried again to read the flash and EEprom from the 16U2. So now I have a known good (hardware) Arduino, with a blank 16U2. Stupid, careless, many other applicable adjectives - yes, I know. If only I didn't have the "good" Arduino connected at the time. (I know about the 6 pin ICSP header for the 16U2) I barely know how to use AVRDUDE and the USBtiny, but I have learned a costly lesson. ![]() I'll buy another 16U2 and have a go at fixing it." I got the new chip installed, and was trying to reprogram it using my USBtiny and AVRDUDE. I should have just used it as is, or thrown it away, but I thought "eh, why not. I purcased a used Arduino, with a bad 16U2 (USB interface) microcontroller. I'll try to make a long story as short as possible. I've attempted to use Google to search for a solution, but I can't seem to find anything that helps. I don't know much about microcontrollers in general, and I don't know much about Atmel microcontrollers or the Arduino platform/IDE. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |