AMcTools Forum 
1  General discussion boards / VMLAB / Re: attyny 2313
 on: 08/28/14 at 17:22:21 
Started by culibin_100 | Post by culibin_100
I have a complete description of tiny2313 .  wants to work with the file? ?
I will send to

2  General discussion boards / VMLAB / Re: attyny 2313
 on: 08/28/14 at 05:55:10 
Started by culibin_100 | Post by culibin_100
hi, everybody. there is here someone live? there are changes of support of tiny2313? while I try to change itself the description file, the program an error doesn't give out and shows porta god.я I think that else people have problems with vmlab & tiny2313

3  General discussion boards / VMLAB / AtmelStudio 6 + VMLAB configuration
 on: 02/03/13 at 17:15:41 
Started by Peo | Post by Peo
Here are suggested settings if you want to create your code in the latest Atmel Studio and run it in VMLAB.

In AtmelStudio 6:
Create a new GCC project.

Go to the project properties:
Project-> (Solution name) Properties (Alt+f7)

Configuration: Debug

Under Build Events:
Post-build event command line:
avr-objcopy --debugging --change-section-address .data-0x800000 --change-section-address .bss-0x800000 --change-section-address .noinit-0x800000 --change-section-address .eeprom-0x810000  -O coff-ext-avr $(OutputFileName)$(OutputFileExtension) ..\$(OutputFileName).cof
copy $(OutputFileName).hex ..\
avr-size $(OutputFileName)$(OutputFileExtension)

(The settings above shall be three "lines". The "avr-size" line is not needed, it will give you info in the Output window.)

Under Toolchain:
AVR/GNU Common -> OutputFiles
Tick ".hex"

AVR/GNU C Compiler -> Miscellaneous
Other flags:
-std=gnu99 -gstabs

AVR/GNU Assembler -> General
Assembler Flags:

With these settings AtmelStudio will include debug info in the created .cof file and copy the .hex file to the source directory.

In VMLab:

Create a project in the source directory and make sure you have at least these settings in the project file (.PROGRAM shall not be used):
.MICRO     "<target AVR>"
.TARGET    "<file name>.hex"
.COFF      "<file name>.cof"

Tick "Automatic VMLAB editors reloaded."


4  General discussion boards / VMLAB / Ignore "RESET vector must contain..."?
 on: 02/03/13 at 01:47:34 
Started by Peo | Post by Peo

Is it possible to let VMLAB ignore "RESET vector must contain a RJMP instruction"? I've tried the Option menu, but not able to fix it.
The code is built outside VMLAB and .TOOLCHAIN "GENERIC" is used. During the "Checking code..." phase I get this warning/error and it seems like this causes the result "Building process not completed!".
I can see this should be a warning, but I can't see it should be a stopping error. I'm working with FemtoOS and in its compact mode it starts with an instruction at address 0000 and puts code in non-used irq vectors to save flash memory. FemtoOS standard mode works fine!


5  General discussion boards / Embedded Systems and Microcontrollers / using c
 on: 07/05/12 at 19:11:30 
Started by naveen | Post by naveen
Can some one explain me the method of setting up VMLAB to use c codes.


6  General discussion boards / Contributors /  User-defined Components Repository / Re: RGB color panel/LED
 on: 05/29/12 at 07:50:56 
Started by justinlove | Post by Unknow
I have a living solution, ipod dock and when its on it has a blue LED light. I like the light it gives off, and i want to know how long before the LED light dies. I keep the dock on every night for like 9 hours. Can someone please help me??
[url=]LED Fluorescent[/url]
[url=]LED Par Light[/url]
[url=]LED Flood Lamp[/url]

7  General discussion boards / VMLAB / Re: ATmega168b and PWM
 on: 04/23/12 at 19:35:15 
Started by mixjoe | Post by ThVortex
Yes, that's correct but only in the phase correct and phase/frequency correct waveform generation modes. Are you sure the right one is selected in the WGM bits?

8  General discussion boards / VMLAB / ATmega168b and PWM
 on: 04/22/12 at 21:02:50 
Started by mixjoe | Post by mixjoe
According pag. 131 of ATmega168 d/s, by setting

[b]COM1A1=1 COM1A0=0[/b]

Clear OC1A/OC1B on Compare Match when upcounting.
Set OC1A/OC1B on Compare Match when

and by setting:

[b]COM1A1=1 COM1A0=1[/b]

Set OC1A/OC1B on Compare Match when upcounting.
Clear OC1A/OC1B on Compare Match
when downcounting)

On VMlab waveforms seems are inverted between them: when I set the first option should be result in a inverted wave ([color=#ff0000]but I see not-inverted in VMlab Scope[/color]), while the second option should be result in a "non inverted" wave ([color=#ff0000]but I see inverted wave in VMlab scope[/color])

Am I mistaking?

Thanks in advance

9  General discussion boards / Bug Reports / Re: VMLab crash, while creating new micro files (3.15)
 on: 03/30/12 at 07:03:29 
Started by Eddy-B | Post by Eddy-B
Portion of INI-file [code]
DLL_model = TinyUSI        ; DLL-based model defined in "TinyUSI.dll"
Register_map = "USICR=$2D, USISR=$2E, USIDR=$2F"
Port_map = "MISO=PB6, MOSI=PB5, SCK=PB7"
Interrupt_map = "USI_Start=USIS, USI_Overflow=USIOVF"

Portion of CPP-source for TinyUSI.dll [code]
  DISPLAY(USIDR, GADGET2, *, *, *, *, *, *, *, *)

If you forget to declare the [b]USICR[/b] in the CPP, like in the above code snippit, VMLab will crash. Omitting any of the other registers will result in a nice warning message about the REGISTER_VIEW info missing. But not if it is the first register that you've declared in the INI file.

(using Windows XP).

10  General discussion boards / Bug Reports / Re: VMLab crash, while creating new micro files (3.15)
 on: 03/29/12 at 18:39:08 
Started by Eddy-B | Post by moderator
Can you be a bit more specific?

Crash example: