I tried all the eight debugging steps, but the error persists.

My arduino board works perfectly with the latest FTDI drive, but with DIY FTDI cable I have this error:



So I will try to use an Usbasp AVR programmer to replace the bootloader with AVRDude.
It will require a "path-board" between programer and ArduIMU, because the pins order is different. But the worse part is the pin "D10"... what is it funcion?

On AVR programer I have this pins:

MOSI
VCC
RST
SCK
MISO
GND

On the ArduIMU+ there is:

GND
VCC
SCK
MISO
MOSI
D10     <---- ( what is this??? Is it mandatory for the connection with ArduIMU+?)
RST

Last question: Is the bootloader exactly the same that Arduino 328?

My spine is freezing... but I don't see another way to go.

------------------------------------------------------------------------------
Added:

SOLVED

It was solved by doing this steps over an AVR programmer.
(Is VERY important that you do the first step and check the result)

1 - Erasing the chip (make sure that "lock fuses" are changed to FF);
2 - Setting the other fuses by this way:

low_fuses = 0xFF (bits 11111111)
high_fuses = 0xDA (bits 11011010)
extended_fuses = 0x05 (bits xxxxx101, because only the three last bits are changeable) ;

3 - Recording the "ATmegaBOOT_168_atmega328.hex".


Views: 2527

Reply to This

Replies to This Discussion

Ken, Mark and Morli. Thanks for reply!

I think the angle and shiny really don't helped. But, anyway, I soldered again for make sure. Nothing happen. The same error here. :(
Really better, but... :(

Check on top, near solder jumper by IC2 741xxx, make sure it only contact two pads, it may have a splash to pin 4 on IC2, shorting RX-in to +5v....
I checked. There is no splash. I'm thinking about to make a bridge bypassing the IC2, for testing the direct connection with pin 30 on ATMEGA 328. Do you know if I will burn out the chip with it? I think that it will be "innocuous", but maybe I need to open the VCC's jump.

OK!!! It's working now!!!

I tested the mix chip through a code that I sent to ARDUIMU+ with the AVR Programmer:
The code received and sent data over FTDI cable. It commuted the serial data flux on MIX chip by D2 output with a pre-programmed delay time. OK! Nothing is wrong with the board.

So... I cheked all again in avrdude ans saw some inconsistent data. I did run all the setup again: erasing all the chip, setting the fuses and recording the bootloader. OK!!! It's finally working.

I noticed that at the fist atempt the "lock fuses" wasn't changed. The value wasn't "FF" but "CF". Other thing that happens: the first program that I used (eXtreme burner) recorded weird bits on the extended fuses by the input value "0xDF" instead "0x05". Man... I'm so very... very... happy now!!! :D

Thanks for all the friends that helped me here! I'm very grateful.

Congrats! Now you really know that boot loader is working .. Cool beans
Correcting:

[...Other thing that happens: the first program that I used (eXtreme burner) recorded weird bits on the extended fuses by the input value "0xFD" instead "0x05"...]
Thank you, Mark! ;)
At the start I was very bored... but now I can see that the challenge gave me some benefits.
I learned a lot of things because of it. Now I'm a little bit more prepared for the next one and I met some nice people. Very cool! :D

So what did you use instead?

Hi Greg, on early days I used to use those GUI tools.
With some time and experience I can see now that the prompt way is easy and safe.
Just install the WinAVR. It will include the AVRDude path to the ENV variables of your Windows install. So it will be available on command prompt.

After that, just start the Windows "cmd" prompt and execute each line like here:

avrdude
 -c usbasp -p m328p -U lfuse:w:0xFF:m
avrdude -c usbasp -p m328p -U hfuse:w:0xDA:m
avrdude -c usbasp -p m328p -U efuse:w:0x05:m
avrdude -c usbasp -p m328p -U flash:w:ATmegaBOOT_168_atmega328.hex

NOTES:
The programmer above can be replaced by other one if necessary (usbtiny and others).
The easiest way to flash the firmware is by copying the hex file from the Arduino install to the root (c:\) and execute the last command from there. That's it...
Good luck! 

Extra infos:

For understanding the WinAVR install as well as the commands that I sent you, check this great tutorial from LadyAda: http://www.ladyada.net/learn/avr/

Reply to Discussion

RSS

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service