Initial Feedback

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

Hi all - I grabbed a copy of Studio 4 from here on AVRFreaks, and have run into two issues that I would like to pass on:

1. I am simulating a MEGA103, with a very simple piece of code that does almost no hardware specific stuff, it can run on any AVR, all it needs is a stack and LPM support. When I "Start Debugging" I get these messages:

Loaded partfile: c:\program files\atmel\avr tools\PartDescriptionFiles\ATmega103
Loaded plugin STK500
AVR Simulator Please wait while configuring simulator...
AVR Simulator Error finding IO bitmask in xml file ; PORTF/PORTF
AVR Simulator Error finding IOAddress in xml file ; TCCR1C
AVR Simulator Error finding IOAddress in xml file ; OCR1CH
AVR Simulator Error finding IOAddress in xml file ; OCR1CL
AVR Simulator Error finding IOAddress in xml file ; ETIMSK
AVR Simulator Error finding IOAddress in xml file ; ETIFR
AVR Simulator Error finding IOAddress in xml file ; SFIOR
AVR Simulator Error finding IO bitmask in xml file ; ETIFR/OCF1B
AVR Simulator Error finding IO bitmask in xml file ; ETIFR/OCF1C
AVR Simulator ATmega103 Configured OK
Loaded objectfile: C:\My Documents\avr_code4\TT800\tt800.obj
I'm not terribly worried about this because I am not using any of these devices.

2. I can't replicate it now, but for a while I had one section of code where a DEC R16 was not setting the Zero flag when it decremented from 1 to 0. It did it consistently until I exited Studio4 and then restarted it, at which point it was behaving properly. Here's the bit of code:
RESET1: lpm ; Get byte
st Y+, lpmdest ; Store byte in SRAM, inc Y
adiw ZL, 1 ; Increment Z pointer
dec temp ; Decrement loop counter
brne RESET1 ; and continue
...it never came out of the loop. I watched it go through this section many times where Z wasn't being set on the transition from 1->0.

---------

I will wait patiently for support for the smaller devices, the 1200 and 8535 being the ones I use most often.

Let me just say that I really appreciate Atmel putting a lot of time and effort into a free tool.

Russell Keegstra

admin's test signature
 

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

Ditto on the error messages in Russell's problem #1.

Otherwise, I like the look and feel, but haven't really done enough with it to offer any more useful comments.

Regards,
Clark

admin's test signature
 

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

Just a detail for the buglist.

The dialogues in the Help file and the program does not match.

Start AVRStudio4. You'll get a Wizard for creating a new project e.t.c.
Click Help. The dialogue is not the same.
Click the Create new project button. Click Help on the Assembler Project dialog that turns up. Again not showing the same dialog.

There may be more. Haven't tried more than those.

/Jesper
www.yampp.com

/Jesper
http://www.yampp.com
The quick black AVR jumped over the lazy PIC.
What boots up, must come down.

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

I replicated issue 2 above (DEC R16 not setting Z flag on transition from 1 -> 0), but not consistently. I switched devices while in debug mode from a MEGA103 to a MEGA16 and it occurred, consistently. However, when I set the device back to MEGA103 it was fine. When I reset the device again to MEGA16 it was still fine.

Maybe it's just me.

Russ

admin's test signature
 

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

Yes indeed, the Z flag not getting set thing seems to be related to switching the device in debug mode. It doesn't always happen, but it does occasionally. Also the disassembly window sometimes comes up when I switch devices.

I made a project that consisted only of this code:

ldi r16, 5

TEST: dec r16
brne TEST

TEST1: rjmp TEST1

and then switched devices back and forth in debug mode.

Hope this helps,
Russ

admin's test signature
 

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

when I made the CAVR compiler look to avrstudio4.exe for
debug, and then run it, AVRstudio 4 opened up the .COF file and that
was it. Is there something different to be done to make studio 4 work
the same as 3.53?
thx!
bob

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

Also, did they remove "binary" display mode from the I/O watch
window?
bob

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

Hi all

and thanks for your initial feedback. We would appreciate if you use the avrbeta@atmel.com email for bug reports. Feedback will get lost if we have to look for reports hidden in all the threads on this forum. The reports sent to avrbeta@atmel.com are entered into our error tracking system and will be handled by one of the developers of AVR Studio 4. You mighe even get a direct answer!

:-)

Dag

admin's test signature
 

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

I see that binary IS there in I/O watch. It was in the black and white
squares instead of 1's and 0's
boB

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

I submitted the following to avrbeta@atmel.com:

I downloaded Studio 4 on the weekend, and quickly discovered that on
attempting to read the signature of my Mega128, it returned 0xFF 0xFF 0xFF,
instead of the 0x1E 0x97 0x02 returned by the programmer on Studio 3.53.

I received the following reply:

William,

Thanks for your bug repport. It will be fixed till next release.

Jo Inge

So for those of you also wishing to try this, we'll have to wait.

Bill

admin's test signature