Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Hi for every AVR designer
In all IDE for AVR Mc the Imagecraft is the best.search in FM1 for iccavr you can find ver6.22 with cr@ck it is woderfull use it and don't wory.
bye
Image*cr@ft I*C*C*A*V*R it is really a great tool for productivity in simple to medium complexity projects. The generated code is acceptable in size and speed, but I*A*R code is better. I discussed with an Atmel representative and he told me that some of their firmware never worked with I*C*C*A*V*R but worked fine with I*A*R*E*W*B. It is up to you to decide what you'll use.
Both compilers can be found in FM (6.22B) or in other places. Search on this forum for details.
If you intend to use ATmega128, be careful to search for the latest version tools and a good flash programming utility like "PonyProg" (i.e. one that "knows" the changes/additions that Atmel introduced in this chip after ATmega103). BTW, "PonyProg" is free and allows you to program all members of AVR family on STK200/300 boards (including ATmega128).
My current setup:
- STK300 ev. board;
- ATmega128 in place of ATmega103 (I made the adapter myself);
- PonyProg for ISP;
- Image*cr@ft I*C*C*A*V*R as everyday IDE;
- AVR Studio (for debugging);
I intend to buy a cheap JTag debugger for ATmega128, but I'm still looking for a good deal.
I have done some work with the E.S. of the ATmega128. One can say here that there is no difficulty or something strange. The micro interface is quite straight forward, basically like the 103. The JTAGICE seems to be working nicely although its not so fast.
Have a look at application notes and so on from A*T*M*E*L and others, you will find quite a lot on the net.
My setup (see the previous message) works fine and is cheap. You can find one (i.e. STK300) for about $70 (https://www.kanda.com). Replace your ATmega103 with ATmega128 and you'll obtain a simple development system. For the J-Tag debugger it might not work. I recommnend the newer STK500 that supports ATmega128 (including J-Tag support).
In my case, I've used ATmega128 as a faster replacement of ATmega103, but I intend to benefit from all its new features soon.
On 2002-03-02 10:19, oldman wrote:
My setup (see the previous message) works fine and is cheap. You can find one (i.e. STK300) for about $70 (https://www.kanda.com). Replace your ATmega103 with ATmega128 and you'll obtain a simple development system. For the J-Tag debugger it might not work. I recommnend the newer STK500 that supports ATmega128 (including J-Tag support).
In my case, I've used ATmega128 as a faster replacement of ATmega103, but I intend to benefit from all its new features soon.
Sorry, but the STK500 doesn't support the MEGA128 alone. You have to add it on a daughter card (STK501) plugged on the extansion port of the STK500 and you can't debug with it. But right, The STK501 has a JTAG connector. It works fine but slower than others emulators and the number of break point is limited at 4. This is otherwhere the cheapest solution to developp on MEGA128, MEGA16 and MEGA32 or 323 and the future MEGA64.
You're right. When I mentioned STK500 for ATmega128 I considered "everything included" (i.e. all the accessories like STK501, cables, etc). Sorry for the omission.
I want to use stk500/501, JTAG ICE and atmega128.
When I set CVAR compiler atmega128 cpu, the program not running in atmega128/JTAG.
When I set CVAR compiler atmega103, the program running in atmega128/JTAG.
(The program identical).
Anyone help me?
Here is my assumption (please note that I didn't use CAVR, but ICCAVR as a programming environment). I remember that I had some difficulties to set up everything until the moment I realized that ATmega128 comes in ATmega103 compatibility mode (see http://www.atmel.com/atmel/acrobat/doc2501.pdf). In this case, your environment might not be able to detect ATmega128 properly and it will assume an ATmega103. You'll have to configure your ATmega128 chip by programming the lock bits and fuses for a fully featured ATmega128 and maybe your environment will be able to recognize it.
I hope this will help. If not, I'm interested to find out how you solved the problem.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
