Electronic – How to connect a large exisiting code (some simulator) to the AVR Studio Simulator

avravr-gccbrushless-dc-motorsimulation

Context

I am working on a brushless DC motor controller project.
And I would like to verify that the interrupt timings make sense in simulation before downloading my code to the board.

Challenge

For that, I have already some C code simulating a brushless DC motor and I would like to run that motor simulation code in parallel with my AVR code.

I wish not to run the motor code in the simulator as well because it makes uses of floating point arithmetic: I want this motor code to run on my PC.

[edit]
I found a way to stimulate the editor. Unfortunately, one must create the input sequence before hand in a file.
This is not convenient because my motor simulator must react depending on the AVR code.
It seems that a good approach could leverage Python debug scripting interface.
However, the documentation seems to be lacking information.
Have you got an idea on how to approach this?

Thanks

Best Answer

You cannot simulate thinks like motor,LED,LCD screen or any type of external components in the AVR simulator.You can run the code and see how the code works internally inside the chip.You also cant get response from the simulator like which you like to get response from a device.You can use Multisim simulator to run your code in PC with external components connected but still you may or maynot get response from a output device.In Multisim,simulation with ATmel's 89C51 is possible.I dont have idea on other Mega series of MCU. You can try Proteus ISIS software to get mere expected simulation.It contains lot of microcontrollers and external components.So probably,Proteus will help to solve your problem.

THe screenshot is attached to configure ATmel studio as simulator

Here is how it's looks like,when you run by 'debug with break'.To move next step,click on Stepin(F11 shortcut).To move to a specific line,drag the cursor to the specific line and then stepinto(F11 shortcut).You can see the changes happening in General Purpose registers,I/O pin registers,RAM etc due to your code.

Related Solutions

Electronic – arduino – Debug an Arduino project on AVR Studio 5 Simulator

Here is an Arduino Simulator. There's a "Pro" version, which costs $5 now but will later cost $50, as well as a free version with a time-delayed startup but otherwise full functionality.

This isn't a way to debug on the AVR Studio 5 Simulator, but it offers similar functionality within its own IDE:

screenshot from http://www.arduino.com.au/Images/SFA%20Screenshot.jpg

According to the linked website, it includes the following features:

Steps through the program line by line. If a new line is selected, the program will continue from that point.
Performs digitalWrite, digitalRead and PinMode for pins 0-21
analogRead for pins 0-5 and analogWrite for digital pins 0-13
Serial output data and input emulation for Serial, Serial1 and SoftSerial
Emulates LCD output
If,while,for loop functionality
Subroutines (multi-level) with arguments
View variables in real-time
Step Into, Step Over, Step Out of or AutoStep run mode
Ability to edit sketch or open in Arduino IDE
#include code
Undock output emulation Serial and LCD windows
Context-sensitive help

See the software datasheet for more information.

Electronic – How to create a static library for the AVR Atmega328p

The AVR-Libc user manual has an entire chapter on how to build a library. I would suggest starting there. If you use an IDE like eclipse, there will be project settings that are applicable if you want to build as a library instead of an executable.

Edit

Here's what eclipse does when I set it up for your example:

So that it couldn't be trivially compiled away, I changed your test_function to:

#include "test.h"

void test_function()
{
    volatile int i = 0;
    i++;
}

Building the library:

avr-gcc -Wall -g2 -gstabs -Os -fpack-struct -fshort-enums -std=gnu99 -funsigned-char -funsigned-bitfields -mmcu=atmega328p -DF_CPU=16000000UL -MMD -MP -MF"test.d" -MT"test.d" -c -o"test.o" "../test.c"

avr-ar -r "libtest.a"  ./test.o 

avr-objdump -h -S libtest.a  >"libtest.lss"

avr-size --format=avr --mcu=atmega328p libtest.a

Building the main program

avr-gcc -I"C:\path\to\my\workspace\test" -Wall -g2 -gstabs -Os -fpack-struct -fshort-enums -std=gnu99 -funsigned-char -funsigned-bitfields -mmcu=atmega328p -DF_CPU=16000000UL -MMD -MP -MF"program.d" -MT"program.d" -c -o"program.o" "../program.c"

avr-gcc -Wl,-Map,MainProgram.map -L"C:\path\to\my\workspace\test\Release" -mmcu=atmega328p -o"MainProgram.elf"  ./program.o   -ltest

avr-objdump -h -S MainProgram.elf  >"MainProgram.lss"

avr-size --format=avr --mcu=atmega328p MainProgram.elf

... and it builds without error. My guess is you need include paths specified in the command lines. Following proper naming conventions is pretty important too, try and follow the pattern above. Obviously the avr-objdump and avr-size commands are just for more information and not required if you're just building.

I'm pretty certain that if you'll need to recompile your library for specific target architectures and clock speeds as well.