[[Main_Page | Back to Main Page]]

===== Permission denied =====
If you try to connect to a mote and receive a permission error, you may need to add yourself to the dialout group. The error may look something like the following:

/home/user/contiki/tools/sky/serialdump-linux -b115200 /dev/ttyUSB0
connecting to /dev/ttyUSB0 (115200)
/dev/ttyUSB0: Permission denied
make: *** [login] Error 255

Use the following command (replace <username> with your account):

sudo adduser <username> dialout

-OR-

sudo usermod -a -G dialout <username>

These two commands are equivalent. They both will add username to the dialout group. '''You will then have to re-login to or reboot your computer for the changes to take effect.''' You should now have read/write permissions to your USB serial devices. It is not necessary to remove any packages.



===== Issue with make login =====
If you are trying to execute the serial-dump application (contiki/tools/sky/serialdump-linux) and see the message: "No such file or directory" or "Command not found", it means that you are running in a 64-bit operating system that does not have proper 32-bit libraries installed. Since serialdump-linux is a pre-compiled 32-bit tool you need to execute the following command to install the necessary libraries:

<code><nowiki>sudo apt-get install ia32-libs</nowiki></code>

On newer versions of Ubuntu, try:

<code><nowiki>sudo apt-get install libc6-i386</nowiki></code>

If the above does not work

Then, try few commands like:

ldd serialdump-linux

The output look similar to the following:

ldd serialdump-linux
linux-gate.so.1 => (0xf772d000)
libc.so.6 => /lib32/libc.so.6 (0xf75b4000)
/lib/ld-linux.so.2 (0xf772e000)

Then it means that you have to install 32-bit packages.
Remember to add i386 architecture or you won't be able to install 32-bit packages:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs

===== Input/output error =====
If you try to connect to a mote and receive an Input/output error as shown below,

/contiki/examples/hello-world$ sudo -s make login
using saved target 'sky'
../../tools/sky/serialdump-linux -b115200
connecting to /dev/ttyS0 (115200) [OK]
could not get options: Input/output error
make: *** [login] Error 255

Then it means that VirtualBox cannot detect the mote connected to the USB interface.

This issue can be fixed by making a minor change in the VM settings.

In the VirtualBox Manager, select the 'Contiki' VM.

Settings-> USB-> Add new USB Filter with all fields set to the values of the selected USB device

and select the mote to be added. You will have to restart the VM for the changes to take effect.

===== Problem running Cooja =====
If you have a problem regarding using the correct version of Java, please check that your default Java compiler is set correctly. You can use the following command:

sudo update-alternatives --config java

===== Problem with compiling in Cooja =====
If you get an error in the linking there may be 2 possible places u need to check to correct them.

LD example-netflood.sky
/usr/lib/gcc/msp430/4.6.3/../../../../msp430/lib/mmpy-16/libc.a(rand.o):(.debug_info+0xd3):
relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
collect2: ld returned 1 exit status
make: *** [example-netflood.sky] Error 1

First, check the line near 132 in file : contiki/cpu/msp430/Makefile.msp430

which looks like the following

CFLAGSNO = -Wall -mmcu=$(CC_MCU) -g $(CFLAGSWERROR)

and delete the option “-g”.

The line should look like :

CFLAGSNO = -Wall -mmcu=$(CC_MCU) $(CFLAGSWERROR)

Use the second one if the first doesnot work.

Second one is go to the Makefile of the currently compiling program and remove the line which looks similar to the following.

CFLAGS += -g
==== Attribute Error while interfacing with Python ====
After installing sky-shell on the tmote sky, if you encounter the following error while running 'python serial.py':

/contiki/examples/sky-shell$ python serial.py
Traceback (most recent call last):
File "serial.py", line 2, in <module>
import serial
File "/home/user/contiki/examples/sky-shell/serial.py" , line 3 , in <module>
ser = serial.Serial(
AttributeError: 'module' object has no attribute 'Serial'

Cooja Simulator

2016-07-21T23:56:17Z

Gugri:

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial aims at introducing the Cooja Simulator and guiding the reader in a simple debugging exercise. We are going to work with Hello World example for the debugging process. You can also study the [[Hello_World]] tutorial to get familiar with its source code.

== You Will Learn ==

* How to run Cooja Simulator.
* How to debug an application using Cooja Simulator.

== Relevant Directories ==

* /contiki/tools/cooja/ - This folder has Cooja Simulator source code. You can run Cooja inside this directory.
* /contiki/examples/hello-world/ - This has the source code of Hello World example.

== Running Cooja Simulator ==

Cooja Simulator is a network simulator specifically designed for Wireless Sensor Networks. A summary of how Cooja executes binaries of different platforms (different types of nodes) and a few details about its structure can be found here:[https://github.com/contiki-os/contiki/wiki/An-Introduction-to-Cooja#Create_a_Hello_World_simulation].

The simple way of running Cooja is executing it inside its own directory (we will see later how to execute Cooja from any working directory):

cd contiki/tools/cooja
ant run

We you execute Cooja the following window pops up.

[[File:cooja-1.png|center|450px]]

=== Creating a new simulation ===

In the File menu you can start a new simulation or open an existing one. At this moment we will start a new one. You should select: File > New simulation... The following window should show up.

[[File:cooja-2.png|center|350px]]

In the ''Simulation name'' box you should enter an identifier for the new simulation, and in ''Advanced settings'' you can choose parameters of the simulation such as Radio medium, node startup delay and random seed generation. We are going to create a simulation called "First Cooja Sim", as shown above.

After creating a new simulation, Cooja's window is filled with the main simulating tools, as shown in the next image.

[[File:cooja-3.png|center|650px]]

Here we briefly describe the functionalities of each tool:
* '''Network''' - Shows the location of each node in the network. Can be used to visualize the status of each node, including LEDs, mote IDs, addresses, lof outputs, etc. Initially this window is empty and we need to populate it with our sensors.
* '''Simulation Control''' - This panel is used to Start, Pause, Reload or execute Steps of the simulation. It shows the time of execution and the speed of simulation. It means that we can run the events several times faster than it would take in real-time execution.
* '''Notes''' - This is a simple notepad for taking notes about the simulation.
* '''Mote output''' - Shows all output of serial interface of the nodes. It is possible to enable one window of Mote output for each node in the simulation.
* '''Timeline''' - Simulation timeline where messages and events such as channel change, LEDs change, log outputs, etc are shown.

In addition to the default tools, it is possible to exhibit other tools such as '''Breakpoints''', '''Radio messages''', '''Script editor''', '''Buffer view''' and '''Mote duty cycle''', which can be enable in the ''Tools'' menu.

=== Creating a new mote type ===

You need to create a new mote type before starting any simulation. You can do this in the menu '''Motes''' > '''Add motes''' > '''Create new motes type'''. Let's select '''Sky mote''' in order to create a mote of the same type as the used Tmote Sky.

The window that shows up (see below) asks for the '''Description''' of the new mote type and the '''Contiki process / Firmware'''. You can name your mote type as ''First mote type'' and you can select the firmware that will be used during the simulation using the ''Browse'' button. After selecting the desired firmware you can test the compilation click the ''Compile'' button. In this example we will use the Hello World fimware, typically located at ''/contiki/examples/hello-world/hello-world.c''. If the compiling process is successed, you will see a final message: ''LD hello-world.sky'' in the Compilation output tab.

[[File:cooja-4.png|center|500px]]

=== Adding motes and running the simulation ===

After successfully compiling the firmware in the last step you should click on ''Create'' button (see figure above). A new mote type will be created and you will be able to add a few nodes of that same type in your simulation. You will see the window shown below, where you will be able to set the number of nodes that will be created and specify their positioning. In this example we are going to create 3 new nodes and they will have random positioning.

[[File:cooja-5.png|center|350px]]

=== Saving simulation file ===

The simulation configuration and parameters such as number of nodes, type of nodes, firmware used, location of nodes, etc. can be stored in a file for future simulations. You can save your simulation configuration in ''File'' > ''Save simulation as...''. The generated file has extension ".csc". In the case of Hello World firmware there already exist a .csc file inside ''contiki/examples/hello-world'', called hello-world-example.csc, which contains 2 nodes. We are going to use this pre-existing Cooja file to show how to debug an application.

== Debugging with Cooja Simulator ==

The easiest way to debug an application is to initially create a proper .csc simulation file, as described above. Then, inside the folder with the simulation file and all firmware source code (.c and .h files), you need to execute the following command.

make TARGET=cooja <simulation_file>.csc

The command above will initialize Cooja Simulator loaded with the desired simulation file and will make Cooja recognized the source code of the application we intend to debug. In our case we are going to simulate and debug the Hello Worls application, so we need to go into /contiki/examples/hello-world folder and execute the command ''make TARGET=cooja hello-world-example.csc''. The window shown below should be displayed.

[[File:cooja-6.png|center|400px]]

If we click on ''Start'' button the simulation begins and we can see both nodes printing out log messages on the '''Mote output''' window.

All debugging tools can be accessed by right-clicking on a node and selecting ''Mote tools for Sky'' in the pop-up menu. The two main debugging tools that we are going to use are: ''Msp Code Watcher'' and ''Msp Stack Watcher''. The first one can be used for analysing the source code of the application in a step-by-step fashion, with the possibility of setting breakpoints. The second tool is used to read and write the variables used throughout the execution.

The ''Msp Code Watcher'' tool can be seen below.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by: Pedro

Cooja Simulator

2016-07-21T23:55:39Z

Gugri:

Contiki tutorials

2016-07-21T23:54:50Z

Gugri:

[[Main_Page | Back to Main Page]]

== List of Tutorials ==

'''<pre style="color: red">Disclaimer: Please note that the following tutorials are a work in progress. Use at your own risk.</pre>'''

Completed
# [[Installation]]
# [[Hello World]]
# [[Broadcast Example]]
# [[Collect View]]
# [[Contiki build system]]
# [[Interfacing with Python]]
# [[Sensor acquisition]] (light, temperature, humidity)

Need review
# [[Timers]] Tim, Leo
# [[CFS-Coffee]] Kevin
# [[Cooja Simulator]] (Getting started, debugging) Pedro

Starting
# [[Tutornet]] Pedro, Kwame
# [[Network Stack]] Yash
# [[CSMA]] Tim, Leo
# [[RSS measurement]] Nitin
# [[RPL objective function & simulation using DGRM model in cooja ]] Ashwini Telang
# [[RPL UDP]] Jiahao Liang
# [[MAC protocols in ContikiOS]] Pedro
# [[RPL Border Router]] Chhavi
# [[REST example running on Cooja and Sky motes]] Mrunal Muni
# [[Trickle library]] Subhashini Sundaresan
# [[Packetbuffer Basics]] Pradipta
# [[Antelope(Database Management System) - Contiki]] Gopi Krishna
# [[Mobility of Nodes in Cooja]] Pratyush Deshpande
# [[Contiki Shell]] Abhilash Nagaraj Hegde
# [[Contiki Coffee File System]] Zhikun Liu
# [[Contiki Programming Guide]] Haimo Bai
# [[Analyse of a real 6LoWPAN network using a Contiki-based sniffer module]] Yash Goyal
# [[Build your own application in Contiki]] Nitin





<pre style="color: red">Be sure to include references in your tutorials, especially if you quote material from other sites!</pre>

Cooja Simulator

2016-07-21T23:48:17Z

Gugri:

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This tutorial aims at introducing the Cooja Simulator and guiding the reader in a simple debugging exercise. We are going to work with Hello World example for the debugging process. You can also study the [[Hello_World]] tutorial to get familiar with its source code.

[[Collect_View#Using_Cooja_Simulator]]

== You Will Learn ==

* How to run Cooja Simulator.
* How to debug an application using Cooja Simulator.

== Relevant Directories ==

* /contiki/tools/cooja/ - This folder has Cooja Simulator source code. You can run Cooja inside this directory.
* /contiki/examples/hello-world/ - This has the source code of Hello World example.

== Running Cooja Simulator ==

Cooja Simulator is a network simulator specifically designed for Wireless Sensor Networks. A summary of how Cooja executes binaries of different platforms (different types of nodes) and a few details about its structure can be found here:[https://github.com/contiki-os/contiki/wiki/An-Introduction-to-Cooja#Create_a_Hello_World_simulation].

The simple way of running Cooja is executing it inside its own directory (we will see later how to execute Cooja from any working directory):

cd contiki/tools/cooja
ant run

We you execute Cooja the following window pops up.

[[File:cooja-1.png|center|450px]]

=== Creating a new simulation ===

In the File menu you can start a new simulation or open an existing one. At this moment we will start a new one. You should select: File > New simulation... The following window should show up.

[[File:cooja-2.png|center|350px]]

In the ''Simulation name'' box you should enter an identifier for the new simulation, and in ''Advanced settings'' you can choose parameters of the simulation such as Radio medium, node startup delay and random seed generation. We are going to create a simulation called "First Cooja Sim", as shown above.

After creating a new simulation, Cooja's window is filled with the main simulating tools, as shown in the next image.

[[File:cooja-3.png|center|650px]]

Here we briefly describe the functionalities of each tool:
* '''Network''' - Shows the location of each node in the network. Can be used to visualize the status of each node, including LEDs, mote IDs, addresses, lof outputs, etc. Initially this window is empty and we need to populate it with our sensors.
* '''Simulation Control''' - This panel is used to Start, Pause, Reload or execute Steps of the simulation. It shows the time of execution and the speed of simulation. It means that we can run the events several times faster than it would take in real-time execution.
* '''Notes''' - This is a simple notepad for taking notes about the simulation.
* '''Mote output''' - Shows all output of serial interface of the nodes. It is possible to enable one window of Mote output for each node in the simulation.
* '''Timeline''' - Simulation timeline where messages and events such as channel change, LEDs change, log outputs, etc are shown.

In addition to the default tools, it is possible to exhibit other tools such as '''Breakpoints''', '''Radio messages''', '''Script editor''', '''Buffer view''' and '''Mote duty cycle''', which can be enable in the ''Tools'' menu.

=== Creating a new mote type ===

You need to create a new mote type before starting any simulation. You can do this in the menu '''Motes''' > '''Add motes''' > '''Create new motes type'''. Let's select '''Sky mote''' in order to create a mote of the same type as the used Tmote Sky.

The window that shows up (see below) asks for the '''Description''' of the new mote type and the '''Contiki process / Firmware'''. You can name your mote type as ''First mote type'' and you can select the firmware that will be used during the simulation using the ''Browse'' button. After selecting the desired firmware you can test the compilation click the ''Compile'' button. In this example we will use the Hello World fimware, typically located at ''/contiki/examples/hello-world/hello-world.c''. If the compiling process is successed, you will see a final message: ''LD hello-world.sky'' in the Compilation output tab.

[[File:cooja-4.png|center|500px]]

=== Adding motes and running the simulation ===

After successfully compiling the firmware in the last step you should click on ''Create'' button (see figure above). A new mote type will be created and you will be able to add a few nodes of that same type in your simulation. You will see the window shown below, where you will be able to set the number of nodes that will be created and specify their positioning. In this example we are going to create 3 new nodes and they will have random positioning.

[[File:cooja-5.png|center|350px]]

=== Saving simulation file ===

The simulation configuration and parameters such as number of nodes, type of nodes, firmware used, location of nodes, etc. can be stored in a file for future simulations. You can save your simulation configuration in ''File'' > ''Save simulation as...''. The generated file has extension ".csc". In the case of Hello World firmware there already exist a .csc file inside ''contiki/examples/hello-world'', called hello-world-example.csc, which contains 2 nodes. We are going to use this pre-existing Cooja file to show how to debug an application.

== Debugging with Cooja Simulator ==

The easiest way to debug an application is to initially create a proper .csc simulation file, as described above. Then, inside the folder with the simulation file and all firmware source code (.c and .h files), you need to execute the following command.

make TARGET=cooja <simulation_file>.csc

The command above will initialize Cooja Simulator loaded with the desired simulation file and will make Cooja recognized the source code of the application we intend to debug. In our case we are going to simulate and debug the Hello Worls application, so we need to go into /contiki/examples/hello-world folder and execute the command ''make TARGET=cooja hello-world-example.csc''. The window shown below should be displayed.

[[File:cooja-6.png|center|400px]]

If we click on ''Start'' button the simulation begins and we can see both nodes printing out log messages on the '''Mote output''' window.

All debugging tools can be accessed by right-clicking on a node and selecting ''Mote tools for Sky'' in the pop-up menu. The two main debugging tools that we are going to use are: ''Msp Code Watcher'' and ''Msp Stack Watcher''. The first one can be used for analysing the source code of the application in a step-by-step fashion, with the possibility of setting breakpoints. The second tool is used to read and write the variables used throughout the execution.

The ''Msp Code Watcher'' tool can be seen below.

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by: Pedro

Collect View

2016-07-08T01:14:59Z

Gugri: /* Step 4 */

[[Contiki_tutorials | Back to Contiki Tutorials]]

__TOC__

== Introduction ==

This exercise is to familiarize the user with the collect view app provided in the Contiki OS source code. It basically involves a sink mote and one or more than one source motes. The source motes send their sensor, network, power and node properties to the sink. A java app presents all this compiled data in a graphical manner.

== You Will Learn ==

* How to upload an introductory code for UDP source and sink.
* How to program nodes and collect data through the collect-view GUI.
* Things to see on the collect-view GUI.

== Relevant Directories ==

* /contiki/examples/collect/ - This has the shell code for collect view and the various targets.
* /contiki/examples/ipv6/rpl-collect/ - This has the codes which are to be uploaded to the source and sink motes for UDP communication.
* /contiki/tools/collect-view/ - This contains the java file for the collect view GUI.
* /contiki/apps/collect-view/ - This contains the codes corresponding to the targets mentioned in the examples folder.

== Connect the Tmote Sky ==

Before continuing with the tutorial, plug 2 Tmote Sky into the computer's USB port, one for the source and the other for the sink.

In order to transfer the ownership of the contiki directories use the following command.

<code><nowiki> sudo chown :user /dev/ttyUSB0 </nowiki></code>

<code><nowiki> sudo chown :user /dev/ttyUSB1 </nowiki></code>

== Using the Source Code ==

=== Step 1 ===

Go to /examples/collect/ directory.

=== Step 2 ===

Now we need to program one mote as the sink and the other as source. We will use a predefined target called sky to upload the code in the motes.

For sink:

<code><nowiki> make TARGET=sky MOTES=/dev/ttyUSB0 collect-view-shell.upload </nowiki></code>

For source:

<code><nowiki> make TARGET=sky MOTES=/dev/ttyUSB1 collect-view-shell.upload </nowiki></code>

=== Step 3 ===

Now we would like to see the transfer and depiction of data on the collect-view GUI. For that to happen, go to /tools/collect-view directory and run "ant" to build the collect viewer.

<code><nowiki> ant run </nowiki></code>

'''Note''' - In order to edit GUI java files go to the /src directory.

=== Step 4 ===

To view the data collected at the sink, go to the generated /tools/collect-view/dist and run -

<code><nowiki> java -jar collect-view.jar /dev/ttyUSB0 </nowiki></code>

=== Step 5 ===

In the collect window from the Tools menu, select "Run Init script" and in the "Node Control" tab and click on "Start Collect." This will enable the communication between the source and the sender and you will be able to see the received statistics in a graphical manner.

== Using the GUI ==

=== Step 1 ===

Once the motes are connected to the USB ports, go to /tools/collect-view directory and run "ant" to build the collect viewer.

<code><nowiki> ant run </nowiki></code>

=== Step 2 ===

Press the "Program Nodes..." button as seen on the GUI.

=== Step 3 ===

Disconnect all except one node from the USB ports. Press the "Connect to serial" button. The disconnected motes should be connected to independent power sources.

=== Step 3 ===

Now in order to collect various statistics, press "Send Collect" button.

=== Step 4 ===

Set the various "Collect Settings" based on how frequently the data is to be collected and then press "Send command to nodes" button.

=== Step 5 ===

Now go through the other tabs on the GUI to study and analyze the statistics plotted.

== Things to See on the GUI ==

=== Topological graphs ===

* Sensor Map
* Network Graph

=== Sensor Related Plots ===

These are subject to the availability of a particular type of sensor on the motes.

* Temperature Sensor - Average Temperatue and Temperature.
* Humidity Sensor - Relative Humidity.
* Battery Sensor - Battery Indicator and Battery Voltage.
* Light Sensor - Light 1 and Light 2.

=== Network Metrics Related Plots ===

* Neighbours
* Beacon Interval
* Network Hops
** Over Time
** Per Node
* Router Metric (Over Time)
** Instantaneous
** Average
* ETX (Over Time)
* Next Hop (Over Time)
* Latency
* Lost Packets (Over Time)
* Received Packets
** Over Time
** Per Node
** Every 5 min

=== Power Related Plots ===

* Average Power
* Instantaneous Power
* Power History
* Radio Duty Cycle

=== Other Tabs ===

* Node Info - This gives a summary of all the nodes and their statistics.
* Serial Console - The user can interact directly with the mote, sending commands to read and transmit data.

'''Primary contributors:''' Bhavna, Deepanker, Nikhil, Rahul

[[Contiki_tutorials | Back to Contiki Tutorials]]

Edited by: Deepanker

Troubleshooting

2016-07-01T22:34:26Z

Gugri:

[[Main_Page | Back to Main Page]]

===== Permission denied =====
If you try to connect to a mote and receive a permission error, you may need to add yourself to the dialout group. The error may look something like the following:

/home/user/contiki/tools/sky/serialdump-linux -b115200 /dev/ttyUSB0
connecting to /dev/ttyUSB0 (115200)
/dev/ttyUSB0: Permission denied
make: *** [login] Error 255

Use the following command (replace <username> with your account):

sudo adduser <username> dialout

-OR-

sudo usermod -a -G dialout <username>

These two commands are equivalent. They both will add username to the dialout group. '''You will then have to re-login to or reboot your computer for the changes to take effect.''' You should now have read/write permissions to your USB serial devices. It is not necessary to remove any packages.



===== Issue with make login =====
If you are trying to execute the serial-dump application (contiki/tools/sky/serialdump-linux) and see the message: "No such file or directory" or "Command not found", it means that you are running in a 64-bit operating system that does not have proper 32-bit libraries installed. Since serialdump-linux is a pre-compiled 32-bit tool you need to execute the following command to install the necessary libraries:

<code><nowiki>sudo apt-get install ia32-libs</nowiki></code>

On newer versions of Ubuntu, try:

<code><nowiki>sudo apt-get install libc6-i386</nowiki></code>

If the above does not work

Then, try few commands like:

ldd serialdump-linux

The output look similar to the following:

ldd serialdump-linux
linux-gate.so.1 => (0xf772d000)
libc.so.6 => /lib32/libc.so.6 (0xf75b4000)
/lib/ld-linux.so.2 (0xf772e000)

Then it means that you have to install 32-bit packages.
Remember to add i386 architecture or you won't be able to install 32-bit packages:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs

===== Input/output error =====
If you try to connect to a mote and receive an Input/output error as shown below,

/contiki/examples/hello-world$ sudo -s make login
using saved target 'sky'
../../tools/sky/serialdump-linux -b115200
connecting to /dev/ttyS0 (115200) [OK]
could not get options: Input/output error
make: *** [login] Error 255

Then it means that VirtualBox cannot detect the mote connected to the USB interface.

This issue can be fixed by making a minor change in the VM settings.

In the VirtualBox Manager, select the 'Contiki' VM.

Settings-> USB-> Add new USB Filter

and select the mote to be added.

===== Problem running Cooja =====
If you have a problem regarding using the correct version of Java, please check that your default Java compiler is set correctly. You can use the following command:

sudo update-alternatives --config java

===== Problem with compling in Cooja =====
If you get an error in the linking there may be 2 possible places u need to check to correct them.

LD example-netflood.sky
/usr/lib/gcc/msp430/4.6.3/../../../../msp430/lib/mmpy-16/libc.a(rand.o):(.debug_info+0xd3):
relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
collect2: ld returned 1 exit status
make: *** [example-netflood.sky] Error 1

First, check the line near 132 in file : contiki/cpu/msp430/Makefile.msp430

which looks like the following

CFLAGSNO = -Wall -mmcu=$(CC_MCU) -g $(CFLAGSWERROR)

and delete the option “-g”.

The line should look like :

CFLAGSNO = -Wall -mmcu=$(CC_MCU) $(CFLAGSWERROR)

Use the second one if the first doesnot work.

Second one is go to the Makefile of the currently compling program and remove the line which looks similar to the following.

CFLAGS += -g