Jump to content
  • 0

AVR Programming using Analog Discovery original version- Supported or not?


DavidM

Question

I needed to program an AVR microcontroller, so I located an Analog Discovery original version and the latest Waveforms software.  I set it in the AVR protocol mode and connected up, set the data lines etc.  I can read the chip ID and fuses etc.  However, it does not work if I try to read the flash from the chip (it is not write protected).  I have tried all speed  and configuration settings etc.  I can see that the MISO line out of the AVR chip does not seem to be going to the proper levels, and instead seems to have a low-level digital signal visible on the scope.  Before I keep at this, is AVR programming supported for the original version Analog Discovery unit, and should this work?  If so, what might I be missing? Thanks.

 

Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0

Hi @DavidM

Have you tried at lower rate ?

I just tested with ATmega64 and found a flash read issue with configurations having less Pattern Generator device buffer. It will be corrected in the next software version.
To overcome this, select a configuration with more buffer under Settings/ Device Manager, 4th for Analog Discovery 1

image.png

Link to comment
Share on other sites

  • 0

Hello Attila,

Thanks for the Beta update, sorry about the delay in responding, I didn't get much time for this test project.  I am now able to read back the flash from an ATmega328P (Arduino UNO chip).  It works up to 2 MHz most of the time, I typically use the 100kHz setting, seems solid.  It also seems to work at both 3.3 Volts and 5.0 Volts VCC on the test board.  

I also ran this test on an ATmega2560 (Arduino MEGA chip).  Unfortunately, it did not work.  I have the Mode set to 4.  Many times it would not even read the signature or fuses, even at slow speeds.  But it would work often enough to confirm that it is communicating with the chip.  This board only has 5 Volt VCC operation, I'm not sure if that would be an issue, what do you think?

I will try some programming tests next, I just wanted to confirm I could read things back before I started erasing the chips.  If the problem is related to buffer size, perhaps programming will not encounter this issue and will still work.

Thanks

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...