AVR Freaks

I tried, both methods with no luck

That's why I posted this

Jim

very simple PWM. I am using timer0 for something else, but with the timer1 being 16bit i can create very slow pulses. I am loading the high byte first, just like the data sheet says. I then setup the timers parameters(fast pwm #14/divide by 1024, etc.) As soon as I set eiter WGMn2 or WGMn3 the high byte goes to zero.

Jim

I am not using interrupts. As I said before I could not get this simple code to operate. I found out tonight that the dragon merely emulates to the target system what the simulator does in the pc. Meaning, that since the simulator does not support the 16bit operations correctly the dragon won't either. I ran the final codebelow in the simulator only, and it did not work on the high bytes correctly. I then connected the dragon and ran the same code with the simulator on the target, and got the same results. I then simply programmed the target with the code and it ran just fine.

Here is the final code

;16bit timer1 operating in fast pwm mode #14.
;

;only use include when needed
.include "m162def.inc"

.equ pulseh =0xff
.equ pulsel =0xa0
.equ periodh =0x15
.equ periodl =0xff

;only use this section when needed!!
.org 0x00
Reset:
ldi r16,high(ramend)
out sph,r16
ldi r16,low(ramend)
out spl,r16
rjmp begin
;this is the actual code
begin:
ldi r16,0x80
sts clkpr,r16 ;enable the cpu clock to be divided
ldi r16,0x01
sts clkpr,r16 ;cpu clock divided by 2
ldi r16,0xff
out ddrd,r16
cli

ldi r16,(1<<com1a1|0<<com1a0|1<<wgm11|0<<wgm00)
out tccr1a,r16
ldi r17,periodh ;tempa and try set the time between pulses - 1.5 seconds
ldi r16,periodl
out icr1h,r17
out icr1l,r16
ldi r17,pulseh ;tempa and try set pulse width - 150msec
ldi r16,pulsel
out OCR1aH,r17
out OCR1aL,r16
ldi r16,0x1d
out tccr1b,r16

done: rjmp done ;this could also be a "ret" statement

Mind you this section is a part of a larger code. the rjmp line will be a ret statement

the include at the top of the code is omitted, as is the ramend section

Again, thanks to all who helped. I am taking this as a big learning experience

Jim

Koshchi:
I connected the dragon via the JTAG, selected my platform as avrdragon and the device. When I run the code the registers did not display correctly, not did the part operate properly.

I have a call in to my local FAE locally to see what he says. Looking back I see that my original code posting was rather sloppy. The final 'masterpiece' is much better and as I said before with regard to the reset/rjmp stuff is that I was not getting anywhere and was willing to try anything. One thing we seem to be forgetting is that sometimes you have to do something that makes no sense in order to get the results we want.

Oh well,

Jim

To All:
I spoke to one of th Atmel FAE's, Jamie Hunter, great guy. He agreed with me that the simulator cannot support the 'older' mcu's with the temp register due to how things are dealt with internal to the chip. It has to do with the in and out statements. Newer devices no longet use the temp register and are now strictly accessed as memory locations with sts and lds.

As far as the dragon issue i came accross, he said I should retry it again. The dragon first loads the code into the chip and then simply acts as a translator between the micro and the pc.

I could have goofed, not the first time, will not be the last

Hope this is worthwhile info to anyone.

Jim