ICE200 difficulties and questions

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

Hello,
I seem to be having a lot of difficulty using the ICE200 AVR emulator.
I have Windows 98 running on a older 350MHz AMD K6-III machine with two serial ports. With this set-up, I'm using AVR Studio 3.56 because the 4.x install demands IE5.x and this machine has some older version of Internet Explorer.
Why do I need an updated internet browser to run a microcontroller in-circuit emulator?

About half the time that I run the ICE200 the red LED stays on. I know that the serial ports are both good on the PC. The Device Manager shows them both there and I can send and receive data with terminal programs. Yet the ICE200 won't acknowledge them even when I use the Studio ComPort Force command on a valid port.
Might anyone have any suggestions why this could be?

I see several stange messages in the bottom box of Studio. There is "No Monitor" and another message that has its text truncated. What could these mean?
The ICE200 manual with its endless photographs of the connector boards seems to be more of an extended marketing brochure than an engineering-level technical document. Is there a detailed supplement that might have the answers that everyone must have had over the years on the operation of the ICE200?
I have very limited resources for microcontroller development tools. Would a debugWIRE or JTag emulation system be a worthwhile investment?
Any comments and suggestions would be welcome.

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

Do you have your ICE hooked up to a target board with power AND clock(Xtal)?
It should work reasonably well with your set up. I have had lots of trouble with instability under win 98 but it does work. I have just updated to win XP pro so I hope that it settles, expecially with Studio 4.xx.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Well, the "no monitor" message seemed to come from not having grounded the capacitors that are connected to the 4MHz crystal that is used for the system clock. The target system is a plug-in wire breadboard, not a PCB or wire-wrapped board.

It may be possible that the red LED was continously on because the target system was not correct due to the caps on the crystal not being grounded. But, the documentation for the ICE200 says that the red LED means that the host PC is not interfaced correctly.

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

The red led goes off once communications with studio starts. i.e you begin a debugging session and all is well. Just the green led stays on.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly