Go Down

Topic: Loopback anomalies. (Read 657 times) previous topic - next topic

turbosnail

Loopback anomalies.
I looked but did not find any report of a problem similar to mine.

I have a new clone UNO R3. I had problems trying to install a bootloader but finally suceeded using the information from this link: http://arduino.cc/en/Tutorial/ArduinoISP  The IDE (1.0.2) signalled sucessful bootloader upload. However I could not upload a sketch into the UNO. I replaced the UNO CPU with a known good one with a blink sketch loaded. UNO blinked as it should. I restored original CPU and began loopback test (using USB to UNO) with following results.

When I activated the serial monitor I was able to echo one message but incompletely, only about 40 characters, see captures 01 ~ 04. Changing the baud rate only changed the number of characters that would loopback before failure. Any attempt to send additional messages failed, yielding no looped back message. If I stopped and restarted the serial monitor I could send another message, but only one per startup of monitor. Shorter second messages disappear quickly but longer ones do not disappear until several seconds have passed.

I checked the schematic of the UNO rev3 and see that the data stream gets through the ATMEGA16U2 and as far as the 328 because there is where the jumper loops back. Because the jumper bypasses the 328 I can not see it as the problem. It works well for a while and that makes me think there is some setup jumper I am missing or maybe something to do with fuses in the 16U2 (which I know nothing about). As it stands it seems that the UNO will only allow loading via the ISP method or by using FTDI and bypassing 16U2.

Any help or information would be appreciated.





Coding Badly


The red wire on the left connects RESET to GND?

Coding Badly

Quote
I have a new clone UNO R3.


If you don't mind my asking, where did you get it?

turbosnail

The reset is jumpered to ground, the TX and RX are jumpered to each other. The angle of the photo misleads. The screen captures are from the IDE console.

The board was purchased here:
http://dx.com/p/arduino-uno-rev3-development-board-120464

Coding Badly


The board is defective.  Very likely the ATMEGA16U2 was not correctly programmed (but there could be other problems).  Were I in your shoes, I would get my money back, including shipping, and buy the board somewhere (anywhere) else.  To get leverage over the vendor I would make it clear they are violating the Arduino trademark and threaten to "turn them in".

If you decide to keep the board, reprogramming the ATMEGA16U2 may bring it to life.

turbosnail

#5
Jan 19, 2013, 12:10 am Last Edit: Jan 19, 2013, 12:23 am by Coding Badly Reason: 1
Regarding:
Quote
If you decide to keep the board, reprogramming the ATMEGA16U2 may bring it to life.


My primary purpose in playing with the Arduino stuff is to learn. Therefore I think I want to apply these links:
http://arduino.cc/forum/index.php/topic,96706.0.html
http://arduino.cc/en/Hacking/DFUProgramming8U2
But I am missing some skills which I will have to pick up. For example
Quote
avrdude -c usbtiny -v -p m328p
sounds great but is it a command line or makefile or what? I am not averse to learning so a pointer to a tutorial would be helpful. As stated I am using Arduino 1.0.2 and have both a Windows and Linux (Ubuntu 12.04) systems. What needs to be installed first, and where, etc. I am still getting acquainted with the Arduino stuff.

Thanks for all comments and help.


Edit: Session ID removed from link.

Coding Badly


avrdude  ? Command line program that comes with GCC.  It's in the Arduino folder under hardware/avr.

-c usbtiny  ? Specifies the programmer (USBtinyISP).  In your case it will be whatever you used to burn the bootloader.

-v  ? Verbose output.

-p m328p  ? Target is an ATmega328P processor.

Go Up