This forum as an engine...

Go To Last Post
6 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all AVRers.

The growing of this forum signs me AVRs are very interesting and living MCUs, and any techical choice I made two years ago when I left PICs was the right one.
I believe this forum can became an engine of ideas (commercial ideas, yet) to Atmel in developing new MCUs or MCU's new features.
AT this time I only red about troubles or tips requests, now I would bigin to say new things.
An example: me and many other people, I see, use little MCUs, 8 pins. What could be the interest to have a 10 or 12 PIN MCU, so saving space again, and giving the most full support to PORTB I/Os...
Could it be?
Support this forum with new ideas!

Fabrizio

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Dear Fabrizio,

Atmel will absolutely watch this site for new ideas and improvements to the AVR product family. This site seems to have potential to be a high quality knowledge base for new and existing users of our products. I hope this site also will provide application solutions with AVR parts soon. By sharing designs we believe that all our customers can learn new ways to use our parts and to improve their products.

Keep up the good work !

Alf-Egil Bogen
Director, AVR Products
Atmel Corporation

admin's test signature
 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Dear Alf,

First of all let me state that I think the AVR is a very good design. Having all the things you normally need on the same chip is very cost effective to the user. It also frees up a lot of pins for I/O which is important to my application.

I do however have some things on my wish list. The most important of these is the ability for the cpu to reprogram itself, which the 163 is supposed to have. I have been told that the 104 will also be capable of this. I am anxiously awaiting the data sheet. It would be helpfull if some of the smaller ones such as the 4414/8515 could do this also.

I do have a few other things on my wish list if you are interested.

admin's test signature
 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Laurence,

I'm using Atmel AVR's since 1997 and I also missed the "self reprogramming" option. But later on I used a better solution (but a little bit more expensive)....use a cheap AVR with an UART as network processor and let that one (re)program the "application" processor. Both processor's can communicate with eachother by SPI or I2C. A great advantage of this solution is that the mainprocessor can do his job without concerning network traffic and CRC failures. The AVR network processor will do this....oke when you have made a mistake in your network software you have to reprogram the network AVR by an external programmer.... but mostly you want to change your application software.

Greetings,
Robert
www.roesink.com

And Fabrizio, I good idea.... As Alf-Egil said "Keep up the good work!" :-)

admin's test signature
 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Robert,

I currently have another AVR cpu in the circuit, just to reprogram the first. However, since the design requirement has both using the same network, it would be much more convient to have the first able to reprogram itself.

admin's test signature
 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Laurence,

I agree with you that in some situations it's very convient that a microcontroller can reprogram itself. I use for example the Dallas DS80C390 that support single flash reprogramming (external flash). But I must say, I love the AVR instruction set....it's so effective compared with the 8052 set.

Greetings,
Robert

admin's test signature