Studio breaks into disassembly view

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

When ever I try to break a program ( ICE200, Codevision COFF and 4.10.356) studio breaks into the disassembly view. Very occasionally I can break the program and the C window will hold up, but most times not. The weird thing is that if I set break points its breaks okay. Just seems to be rellated to a manual ctrl F5 break. If I continue the program from the disassembly window it still runs okay. Maybe studio gets lost if I break on a function that includes assembler of which I have a few. Anyone else seen this happen? Its drving me crazy.

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

This has been a long time headache for me too, but it seems there is no answer (i.e. I have learned to live with it :( ) Are you using Win98 and Studio 3.56? The problem seem to arise with Studio 4.xx also but I don't know about some other O/S like Win2000 or XP. If you try and use Studio 4.xx you may get a lock-up at times when you try to run your program. The cursor will go to the first instruction pointed to by the reset vector instead of the rest vector itself and the program will not run. It is clearly visible under assembler but a lot harder to see (but happens just the same) with C. Apart from the above I love my ICE200 :)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I use Studio 4.08 under Win98. Usually I find that when this happens something has slipped and pinched the FPC cables on the ICE200. Since the ICE was checked in luggage on an airline I have had problems with the FPC connectors. Sometimes reseating them clears up this problem.

The other issue, which may have been a contributing factor was that I was running the STK500 and the ICE off of 12V. The floppy motor pulls a lot of current, So there is quite a bit of heat dissipation from the power regulator.

After reading the ATMEL Appnote, I switched to 9V 1Amp wall warts, which helped a bit then started having random assembly breakpoint jumps after a few hours. Downgraded the ICE200's wall wart to a 400mA.
Stuck a PC Fan on the power regulator on the STK500 powered off the Vtarget. (Covers the reset switch, though) Since then the random jumps went away. A can of Circuit freeze confirmed I have a thermal problem in the power regulator. Possibly from the months of being powered at 12V.

I purchased a second ICE200 as a backup, which is probably why the original started working again.

-julieP

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

Quote:
I switched to 9V 1Amp wall warts, which helped a bit then started having random assembly breakpoint jumps after a few hours.

I have been using my ICE with 9V supply, even went to the trouble of having an adjustable supply to go down to 8 V, no difference. The problem occurs by simply running the ICE for a few minutes in my case. Also just switching from Studio to another application (whilst Studio is running) and back again will bring the disassembly window. There is definetely something screwey with Studio, but the ICE200 is now pretty much obsolete so I'm not hoping for a fix anymore, just put up with it. By the way Julie have you ever experienced the problem I'm describing above 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

Quote:
By the way Julie have you ever experienced the problem I'm describing above with Studio 4.xx?

See the first sentence of my prior reply where I write:

Quote:
I use Studio 4.08 under Win98.

-julieP

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

Quote:
I use Studio 4.08 under Win98.

Hmmm so I AM the only person in the world that has problems with the ICE200 and Studio 4.xx :( . I really cannot use Studio 4.08 or 4.09 because of the problem described above. It will work for a while at times and then it will refuse to work, and I go NUTS. This problem does not occur with studio 3.56, only with studio 4.xx and it happened also whilst the Atmel support engineer was present and with a different ICE (she brought another one along) AND with a different computer (1GHz machine also using Win98). I'm stumped!

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Ah no I also am going nuts with my ice200 and studio when it comes to trying to break a program in the c source window, so thats at least two of us. I cant remember having this problem with the older versions of studio at all. Just seems to have appeared since I updated studio. My codevision is about two bug fixes/minor updates behind the current release but I dont thinki that is the problem as there is nothing on the codevision revision history about this (Pavel your annual update fee is too expensive for what you get. I dont mind paying for new features, but not bug fixes)

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

I doubt it's you compiler. Just write a small assembler code (with Studio) like a flashing led program and try to debug it. You will soon come up with the same problems.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly