2013-02-07 by Jim Wagner
I believe that the ONLY way to mask interrupts while single-stepping is to clear the IE flag bit in the Status Register. Jim Wagner On Feb 6, 2013, at 6:54 PM, Dave McLaughlin wrote: > Thanks John and all, > > It's not just the timer interrupt, I also have CAN bus interrupts runn
Thread view
Attachments: 0
2013-02-07 by Dave McLaughlin
Thanks John and all, It's not just the timer interrupt, I also have CAN bus interrupts running. The timers halted option is set anyway. I don't recall ever having to disable interrupts before. Doing a search I come across a few references to an option to mask interrupts during si
Thread view
Attachments: 0
2013-02-06 by Jim Wagner
Go to the view of the peripheral registers and clear the interrupt enable bits of the timers or other devices that are making things hard. Or, go to the Status Register and clear the global interrupt enable bit. Jim Wagner Oregon Research Electronics ----- Original Message -----
Thread view
Attachments: 0
2013-02-06 by John Samperi
At 12:49 AM 7/02/2013, you wrote: >Since doing so, I can't find the option to set interrupt mask during single >stepping so every time I single step my code, I end up in one of the 2 >interrupt handlers! Make debugging a nightmare. You can stop the stop timers from running on bre
Thread view
Attachments: 0
2013-02-06 by Don Kinzer
--- In AVR-Chat@yahoogroups.com, "Dave McLaughlin" wrote: > I can't find the option to set interrupt mask during single > stepping [...] Choose a view that shows the registers including SREG. Click on the I bit in the SREG display and it will toggle. Then, you can single step wit
Thread view
Attachments: 0
2013-02-06 by Dave McLaughlin
Hi all, I have had to switch back to Studio 4 until Atmel sort out the bug with JTAG ICE2 and Studio 6 Since doing so, I can't find the option to set interrupt mask during single stepping so every time I single step my code, I end up in one of the 2 interrupt handlers! Make debug
Thread view
Attachments: 0
2013-02-04 by John Samperi
At 11:52 PM 4/02/2013, you wrote: >do you have an older version on AVR Studio 4 instead of 4.18? I >don't find one... http://www.atmel.com/tools/STUDIOARCHIVE.aspx Remember to download the service packs for it too SP1, SP2 and SP3. Also, if you don't have it, download winAvr20100
Thread view
Attachments: 0
2013-02-04 by Mauro Zanin
By the way it's MEGA32.... Mauro ----- Original Message ----- From: John Samperi To: AVR-Chat@yahoogroups.com Sent: Monday, February 04, 2013 9:34 AM Subject: Re: [AVR-Chat] Strange issue... on AVR Studio 4 At 07:23 PM 4/02/2013, you wrote: >Avr Studio 4.19. It defaults to the At
Thread view
Attachments: 0
2013-02-04 by Mauro Zanin
Ciao John do you have an older version on AVR Studio 4 instead of 4.18? I don't find one... Version 3 is too ancien... Ciao Mauro ----- Original Message ----- From: John Samperi To: AVR-Chat@yahoogroups.com Sent: Monday, February 04, 2013 9:34 AM Subject: Re: [AVR-Chat] Strange i
Thread view
Attachments: 0
2013-02-04 by John Samperi
At 07:23 PM 4/02/2013, you wrote: >Avr Studio 4.19. It defaults to the Atmel Toolchain rather than winAvr like previous versions. V4.18 is still ok if the chip you want to use is supported. Regards John Samperi ******************************************************** Ampertronics
Thread view
Attachments: 0
2013-02-04 by Mauro Zanin
Hi everybody I'm facing this kind of issue. On 2011 i compiled an application under Avr Studio 4(dunno version #). Some day ago I assembled the package on different PC, with a newly installed Avr Studio 4.19. The issue is: the assembled HEX code is completelly different from the
Thread view
Attachments: 0
2013-02-03 by Cagri Tanriover
Well, I did specifically search for that feature in AVR Studio but could not find it. I use Notepad++ and switch between AS and Notepad++ during my debugging sessions. This is rather annoying but it's not the end of the world. [Non-text portions of this message have been removed]
Thread view
Attachments: 0
2013-02-03 by englsprogeny1
John, I don't know how I did a double post. I saw earlier that I did a double post and thought that maybe I sent different versions as I was writing it (by accident)... but no, it's the same exact post. Hopefully, this will post one time. :) As for you (John) writing primarily in
Thread view
Attachments: 0
2013-02-03 by John Samperi
At 02:28 AM 4/02/2013, you wrote: >Does the editor have 'jump to line' function? > >Like CTL-G ? I haven't ever looked for that feature, maybe because I have never needed it since AS4 came out all those years ago. :-) >Also, double clicking errors in the build window has no funct
Thread view
Attachments: 0
2013-02-03 by englsprogeny1
I converted to AVR Studio (so that I could debug using JTAG) about a year ago. I've always wondered and have searched the User Guide / Google for this. Maybe my 'search words' are not right. Does the editor have 'jump to line' function? Like CTL-G ? Also, double clicking errors i
Thread view
Attachments: 0
2013-02-03 by englsprogeny1
I converted to AVR Studio (so that I could debug using JTAG) about a year ago. I've always wondered and have searched the User Guide / Google for this. Maybe my 'search words' are not right. Does the editor have 'jump to line' function? Like CTL-G ? Also, double clicking errors i
Thread view
Attachments: 0
2013-02-03 by Martin McKee
I do it all the time! Martin Jay McKee On Sat, Feb 2, 2013 at 2:47 PM, englsprogeny1 wrote: > ** > > > > Thanks guys! I was thinking in the c++ world again... > > > --- In AVR-Chat@yahoogroups.com, Martin McKee wrote: > > > > Pass-by-reference is only available in C++. In C you h
Thread view
Attachments: 0
2013-02-02 by Martin McKee
Pass-by-reference is only available in C++. In C you have to pass in a pointer, and, for that, you use * as has been mentioned. void CalculateOffTime( uint8_t duration, offTimeStruct* eventOff ) then, eventOff->endMinute = ... Martin Jay McKee On Sat, Feb 2, 2013 at 2:22 PM, Char
Thread view
Attachments: 0
2013-02-02 by Charlie H
I agree with Clark on the pointer issue. The & should be * in the function declaration. Charlie On 2/2/2013 4:17 PM, englsprogeny1 wrote: > > I've updated the struct, thanks. > > I want to be able to update the values within the struct (depending on what 'instance' is passed into
Thread view
Attachments: 0
2013-02-02 by englsprogeny1
Thanks guys! I was thinking in the c++ world again... --- In AVR-Chat@yahoogroups.com, Martin McKee wrote: > > Pass-by-reference is only available in C++. In C you have to pass in a > pointer, and, for that, you use * as has been mentioned. > > void CalculateOffTime( uint8_t dura
Thread view
Attachments: 0
2013-02-02 by Clark Martin
On Feb 2, 2013, at 11:51 AM, englsprogeny1 wrote: > Simple C question.. I guess that I am blowing! Maybe I didn't get enough sleep last night.... > > Using AVR Studio 4.0 with GCC > > 1. I create a type that is a struct > 2. I create multiple 'instances' of this type. > > I get t
Thread view
Attachments: 0
2013-02-02 by Charlie H
It looks like you are expecting the address of the struct passed to your function but not using the address in the function. Try it this way: void CalculateOffTime(uint8_t duration, offTimeStruct eventOff) { ... } Also, I think the typedef is wrong. Try it this way: typedef struc
Thread view
Attachments: 0
2013-02-02 by englsprogeny1
I've updated the struct, thanks. I want to be able to update the values within the struct (depending on what 'instance' is passed into the function). This is why I am doing 'pass by reference' (by the address) I get the following error: menu.c:1732: error: expected ';', ',' or ')
Thread view
Attachments: 0
2013-02-02 by englsprogeny1
Simple C question.. I guess that I am blowing! Maybe I didn't get enough sleep last night.... Using AVR Studio 4.0 with GCC 1. I create a type that is a struct 2. I create multiple 'instances' of this type. I get the following errors when I Build All: menu.c:1729: error: expected
Thread view
Attachments: 0
2013-01-30 by kjoehass
--- In AVR-Chat@yahoogroups.com, Phillip Vogel wrote: > Just to satisfy my curiosity, what chip has a watchdog timer with > an "early strobe" exception? It's known as a "windowed watchdog timer" (WWDT) and it's not uncommon. The NXP LPC800 series, with an ARM Cortex-M0+ processor
Thread view
Attachments: 0
2013-01-30 by englsprogeny1
In my work experience we service the WDM within the schedule. The OS that we wrote is for flight control so deterministic. This allows us to service WDM reliably. The WDM that we use is within a PLD that we design. Not that you ever need a WDM. : ) --- In AVR-Chat@yahoogroups.com
Thread view
Attachments: 0
2013-01-29 by Tim Mitchell
Found the answer... Right click on the tab, there is an option there "tabs at top". I thought I was going mad for a bit... ----Original Message---- From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf Of dr_cagri_tanriover Sent: 24 January 2013 18:11 To: AVR
Thread view
Attachments: 0
2013-01-29 by Philippe Habib
I can't answer about the early strobe, never having seen that either, but on some medical stuff that I've worked on the FDA did not allow the WDT to be part of the micro. They demanded an external WDT wired to the reset line. Of course, mine never triggered either. ----- Original
Thread view
Attachments: 0
2013-01-29 by Phillip Vogel
Just to satisfy my curiosity, what chip has a watchdog timer with an "early strobe" exception? I've never encountered that in my (possibly flawed) recollection of my past 35 years of doing this stuff. It would be pretty annoying to have to keep track of the more-or-less time sinc
Thread view
Attachments: 0
2013-01-26 by Chuck Hackett
> From: bayramdavies > > .... > On a different subject, I don't suppose you could use a bunch of > ATmega1284P-AU (TQFP-44)? I have 25 I bought for a project which then > disappeared and I would let them go for $100 the lot. > > Graham. Hi Graham, That's the part I use but timing
Thread view
Attachments: 0
2013-01-25 by Philippe Habib
You can also set the BOD to different voltages. Are you able to run the part at a high enough voltage to allow enough time to run some cleanup stuff in the interrupt before the voltage goes all the way down? Maybe just increasing the size of some of your capacitors would give you
Thread view
Attachments: 0
2013-01-25 by bayramdavies
--- In AVR-Chat@yahoogroups.com, "Chuck Hackett" wrote: > How does one detect that VCC is dropping > so that one can do cleanup activities ... Ideally, you would detect loss of power *before* VCC starts to fall, for example the failure of the AC input at the main power supply. An
Thread view
Attachments: 0
2013-01-24 by John Samperi
At 10:30 AM 25/01/2013, you wrote: >I know I could detect the VCC drop with some extra external hardware to >generate an interrupt That's about the only way you can do it, once the power is low enough to trigger the BOD it's too late to do anything. You may be able to use the Ana
Thread view
Attachments: 0
2013-01-24 by Chuck Hackett
How does one detect that VCC is dropping so that one can do cleanup activities (reset external controllers that would leave devices in an unknown state, etc.) before a BOD reset occurs? From my reading of the ATMega1284 datasheet I don't see any detection other than the BOD reset
Thread view
Attachments: 0
2013-01-24 by dr_cagri_tanriover
Did you try to drag and drop the tabs to where you want them to appear? This works with the other windows such as debug, memory view etc. It may also work with the files tab. Give it a shot. Regards... Cagri --- In AVR-Chat@yahoogroups.com, Tim Mitchell wrote: > > Due to a change
Thread view
Attachments: 0
2013-01-24 by Tim Mitchell
Due to a change of domain name my desktop PC has created a brand new user account for me... When I run AVR Studio 4, the file tabs which were at the top of the editor window are now at the bottom. I cannot find any setting to change this - anyone know? -- Tim Mitchell
Thread view
Attachments: 0
2013-01-22 by Mauro Zanin
Click Here!http://play4exp.com/curtainbedbrianmitchell/?agoogleid=a8hu8 [Non-text portions of this message have been removed]
Thread view
Attachments: 0
2013-01-12 by Jim Wagner
Nothing about "non-periodic". Here is how it works: 1. WDT timer is reset 2. WDT timer counts If the WDt timer is reset before the count overflows, go back to 2. If the timer overflows, it resets. So the ONLY criterion is that the timer is reset before it overflows from the previ
Thread view
Attachments: 0
2013-01-12 by Jim Wagner
You can reset the WDT at ANY interval less than the timeout time. You could have it set for 60ms and reset it once every 1ms. No difference. Jim Wagner On Jan 12, 2013, at 9:12 AM, englsprogeny1 wrote: > To test this I go into an infinite loop (by way of a UART command). > > My W
Thread view
Attachments: 0
2013-01-12 by Jim Wagner
This is exactly the same. The code has to periodically reset the WDT when it is running. If your code DOES NOT reset it, the WDT will eventually time out. You do not have to reset it to start it. You can enable/disable the WDT and you can set the time in large increments. Enable/
Thread view
Attachments: 0
2013-01-12 by Jim Wagner
It can be argued, quite strongly, actually, that an endless loop is the ONLY error that the WDT handles. Nothing else "triggers" the WDT. Jim Wagner Oregon Research Electronics On Jan 12, 2013, at 7:35 AM, englsprogeny1 wrote: > Using an AtMega16, I am going to make use of the wa
Thread view
Attachments: 0
2013-01-12 by Jim Wagner
The only "crash" of any significance is the endless loop. You look for an I2C peripheral thats not there? That is just an error and the code flows on. Same with virtually everything else. So why not a simple endless loop? You COULD call a function and purposefully corrupt the sta
Thread view
Attachments: 0
2013-01-12 by englsprogeny1
OK That makes sense. So really, there is an 'early strobe' exception by way of the WDT expecting a periodic reset. The WDT must then measure the time between resets. So the WDT causes a reset for two conditions: 1. Not being reset before his timeout 2. Having a non-periodic time
Thread view
Attachments: 0
2013-01-12 by englsprogeny1
To test this I go into an infinite loop (by way of a UART command). My WDT is set for 60ms. I am resetting the WDT at 35ms. This means that I am resetting the WTD early (really early). It works correctly. So, there appears to be no issue with early resets. (as in really early)...
Thread view
Attachments: 0
2013-01-12 by englsprogeny1
Thanks Jim. Using an endless loop is sufficient for verifying my WDT implementation. A follow on question. I just read the ATMega16 datasheet to see that the WDT has to be serviced before it times out. OK, of course... On other WD Timers that I've worked with, there was also an '
Thread view
Attachments: 0
2013-01-12 by englsprogeny1
Using an AtMega16, I am going to make use of the watchdog Timer. I want to cause a crash to verify that the WDT brings us back to life. Instead of going into an infinite loop "crash" I'd like to cause something more catastrophic. I tried a divide by zero scenario but we don't cra
Thread view
Attachments: 0
2013-01-11 by Dave C
>> New to AVR but experienced (long ago) in Mot' 68K assembler, and all >> things electronic. > > If you are/were familiar with the 68HC711 Never heard of it. lol > then a typical AVR would have the same memories except that the EEPROM is serially accessible rather than parallel
Thread view
Attachments: 0
2013-01-10 by John Samperi
At 05:13 PM 10/01/2013, you wrote: >New to AVR but experienced (long ago) in Mot' 68K assembler, and all >things electronic. If you are/were familiar with the 68HC711 then a typical AVR would have the same memories except that the EEPROM is serially accessible rather than paralle
Thread view
Attachments: 0
2013-01-10 by Dave C
On 10 January 2013, at 10:26 AM, Dave C wrote: > I thought EEPROM data cannot be modified unless erased (via UV light or such) and re "burned". Doesn't that mean that during runtime modification is not possible? Oops... ELECTRICALLY-eraseable PROM. I see. Thanks, Dave [Non-text p
Thread view
Attachments: 0
2013-01-10 by Dave C
On 10 January 2013, at 6:07 AM, bayramdavies wrote: > EEPROM can be used to store data that may be modified at run time but must survive a reset or power cycle. I thought EEPROM data cannot be modified unless erased (via UV light or such) and re "burned". Doesn't that mean that d
Thread view
Attachments: 0