Getting started with LUFA and atmel studio

One good friend Chuck99 have posted an excellent article in avrfreaks.net on how to use the LUFA library in studio. Here is the link. http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=118597

My Project Space: Atmel Studio extension for managing projects

Note: For Atmel Studio Version 6.0, Works fine with Atmel Studio 6.0 projects
 
To understand MPS in Short try following exercise;
From a desire project directory that contains your projects
1)      Open a device specific project
2)      Open a ASF version specific project
3)      Open a connected target specific project (or disconnected )
4)      For QTouch Project, Open the project with some no. of Slider, Button or Wheel.
Now try with specific device, ASF module, target, ASF version..etc …etc  L……..
MPS can do all these for you.

Here is what MPS can do for you
1)      Filters Atmel Studio project from project directory.
2)      Added different project directories.
3)      Filters each Project directory based on Project type supported by Atmel Studio.
4)      Based on project type list all Atmel projects with following details  - Solution Name, Project Name, Device used , ASF Version
5)      View project details without opening a project
6)      Displays common project details like Solution Name, Device series , Toolchain used, Output type, Output file extension, Language used, ASF modules used
7)      Displays project Specific details
8)      Open selected project in existing instance or in new instance of Atmel Studio.
9)      MPS can call conversion for Studio 4 specific projects.
10)   Filter projects based on connected Tools
11)   Open Project directory folder or project folder.

Download MPS here.
Just double click on the downloaded VSIX and you should be good to go.

Comments and Suggestion are Welcome!!!

Finding the integrity of an installer download

To an extent it happens that the installer you downloaded is not corrupted or you wonder if at all the download is successful. That too for installers with significant size it’s always a good idea to do so. There are two ways of doing this.

1. Verify the size of the downloaded file against the one published in the website.

2. Verify if the installer name is same as what it is in the website

3. Verify the checksum of the installer. The checksum is the most reliable way. It should match with the checksum of the installer.  Do verify the MD5 of a downloaded file there are a number of tools available . One such is https://md5file.com/calculator. Open this in a browser and follow the instructions. Now verify the MD5 given against the one given below.

(I will post it, when I find time) . If someone has it already, please post them too.

• as5installer-stable-6.0.1843-full.exe (application/x-msdownload) – 778745152 bytes
  • MD5: 3bac4320f22d187714f2d9f2f9155484

• as5installer-stable-6.0.1843-small.exe (application/x-msdownload) – 553412104 bytes
  • MD5: 3cbf22658f65ce86b7bcae19cca4884e