Matrix user forums

Having had the interrupt problem fixed for the ATTiny13, I now find I have the same type of problem this time with the ATTiny26 !!
No Interrupt vector is created and various errors appear ... see attached.

Benj,

Thanks for the reply but I don't see or understand how this info allows an informed assessment of stack overflow ???

Iain

So after discovering that an older program I had in V4 would not run in an ATTiny13 in FC8 due to the stack overflowing, I am wondering what measures FC8 could take to flag this up as an error or a warning, this should be I would have though be a fairly important check given that the programmer may ...

Thanks Benj.

Did you get my PM ??

Iain

Hi Steve,

Thanks ... what I did was uninstall and reinstall the AVR compiler and now its fine. Mind you it looks like I'm still running the 30 day free trial as
it says at the bottom of the screen that I have 18 days left and all the modules are available ???

Iain

Having evaluated the 30 day free version, I decided to take advantage of the black friday offer. I have bought a Pro licence + AVR chip pack + Basic I/O Went through the licencing procedure but now I cannot compile with an error saying the AVR toolchain is not installed. After a bit of faffing aroun...

Ok ... all confirmed, using an ATTiny25 solves the problem. So stack overflow was the reason and the fact that ATTINY13 is ok in V4 and not in V8 is because V4 uses much less stack especially when calling an interrupt. Which raises the question ..... Should we not be receiving an error and warning m...

Martin, I totally agree with you. Looking at the .lst outputs from V4 and V8 it is clear the V8 output used much more stack than the V4. A stack problem would definitely explain every scenario experienced. I have ordered up a ATTiny25 which is basically exactly the same as the 13 but has twice as mu...

Hi Martin, I understand about the small ram area ... however its the same chip we are using when trying this with V4 and remember it works fine. Anyway I think I have made a bit of progress ...... if I change the Divisor from an INT to a BYTE although this screws a time setting, the program now work...

Hi Martin, I will have a look at your suggestions to see if any help, however please note that these would not explain why removing a call and placing its code in-line would suddenly make things work. Also note everything else is fine .... PWM/Interrupt/delays all work perfectly, its just if I put t...

Hi Benj, Thanks for replying. Yes I did check the ADC values and they do appear to be exactly the same in V8 as in V4. Also I can confirm that the interrupt time is as per the comments ..... this has been checked using a scope on the target hardware. As requested I have attached the V4 edition of th...

Hi Benj, I fully understand that the jump from V4 to V8 is massive and appreciate that there is no doubt this would cause problems. As we have new projects coming up where I was going to use Flowcode it became apparent to me that we should upgrade to V8 and as part of the learning curve for V8 I obv...

ARRRG !!! So I updated to 8.1 (still evaluating for purchase) so this means I can no longer import my previous V4 programs !!! I realize there may be a bit of incompatibility that may need attention when doing this but a least you could move the bulk of a program over to V8 very easily. I also noted...

Hi Martin, Thanks for taking an interest in this. I have attached the offending program. You will see that in the MAIN section there is a group of icons that are "disabled" and just at the very start of that group is a macro called RAMPUP. That group of disabled icons are the exact program that is c...

I have been having a nightmare getting a program in V4 to run in V8. Programs simulate ok but when transferred to chip I have the problem After an update on the ATTiny13 from MM that was causing an interrupt problem, I have finally tracked down the source of another problem which seems to me to be s...

Woops sorry ....
Screenshot is here

See attached screenshot for the config fuses for a ATTiny13 as selected ..... This looks very strange !! If I load up V4 and look at the config fuses it reads 0x0,0xdf. Also after getting an update file from MM for the ATTiny13 which got the interrupt working, I find that the ADC inputs no longer wo...

Bingo !!!!

All working great now, thanks for the fast update, can hopefully get on with my evaluation of Flowcode8 now

Cheers

Iain

Benj,

You can still view the assembler code by opening the .asm file in your project folder with a text editor.

There is no .asm file produced !! ... only a .lst file

Iain

Taking this problem forward. I have attached a program for ATTiny13 with simply an enabled Timer0 interrupt and the interrupt routine toggling an output line. This simulates ok BUT will not run on hardware. When you look at the .lst file it produces you will see there is no timer overflow vector cre...

After a great deal of faffing around with code from V4 imported into V8 and not working I seem to have found the problem but how to fix it ?? I have attached the code. If you compile this and look at the .lst file you will see that no TIMER0 Overflow vector is generated and indeed no interrupt code ...

Ok updating the driver worked for V8 but doesn't work on my V4 !!! What I mean is the programmer now works on V8 but not on V4 ... I have to revert back to the old driver to work on V4 It works fine downloading to chip in V4 but not downloading from V8 What I mean is the program runs good if progra...

Hi Benj, The problem I seem to have is with TIMR0 overflow interrupt (on a ATTiny13) It works fine downloading to chip in V4 but not downloading from V8 It seems the interrupt screws things .... could it be too long in V8 ??? not sure. I note there is no "View ASM" in V8 ????? this would help me fin...

Hi Benj, Ok updating the driver worked for V8 but doesn't work on my V4 !!! This is causing me problems as to upgrade to V8 I need my V4 programs to work under V8 and they don't and I'm not entirely sure why. I *think* it might have something to do with the PORT i/o writing or TMR0 interrupt ... has...

Hi Benj,

Did that but now it doesn't seem to find the programmer on the USB !!!
Programmer is plugged in and does enumerate ..... also still works fine in the V4 Flowcode.

Any more ideas ???

Snapshot of error attached

Iain