Studio 7 Fresh Install Atmel Start Issue

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi,

I have a fresh install of Atmel Studio 7 (Just the ARM part).
I start the IDE then go File->New->Atmel Start Project.
The a TAB Atmel|Start appears with CREATE NEW PROJECT.

The left pane has filters and the right pane has all the various Atmel CPUs (Including all the non ARM variants)

I can scroll the list, but cannot select and of the MCUs and thus the Create New Project button is always non functional.

Does anyone know how I can fix this?

I've tried repairing, uninstalling reinstalling. (I also have Visual Studio Community 2017 installed)

Thanks.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Go to start.atmel.com and do it from there.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Thanks Morton.

A couple of questions.

 

1- Why is the File->New->Start Atmel Project even there if it is non functional?

 

2- Is the GUI configuration integrated into the IDE, or only available as a web based tool that auto generates a code blob that must be imported every time a change is made?

 

For example, with the Atmel PSOC system, everything is tightly integrated with the IDE. Any peripheral changes will regenerate the underlying autogenerated code, even trying to perform a merge if local mods were required.

Thanks.

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It works, but apparently not on your machine.

Start is a web based tool, and is not coupled to the IDE. Opening start inside studio basically opens a web browser (with some internal studio hooks in place to make things flow a bit better)

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So if you want to change peripheral configuration after you have established your project, can you still do that via web application and have VS merge changes, or are you stuck with having to directly edit the auto generated code modules?

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Atmel START: Sensors: http://www.youtube.com/playlist?list=PLtQdQmNK_0DS3K9jIyPPMc9m6Tjobtj3d

This playlist shows how you can use Start

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK, thanks to meolsen for pointing me in the right direction.

Just a summary for anyone else wanting to know about Atmels Studio 7 Workflow.

 

In the old days, we had to read data sheets and understand how peripherals worked at the register level and write our own driver code: then along came some gui tools to help configure peripherals, clocks, interrupts etc etc. and now even middle-ware for things like an rtos. These are great productivity enhancers.

 

Atmel have chosen to use a stripped down version of Visual Studio as their dev platform. Nothing wrong with this. VS is a great product.
The gui part of the microcontroller configuration though, instead of being part of the IDE is a separate web application hosted by microchip/atmel.
So the work flow is -> start.atmel.com, configure you micro, download a .zip blob from the web site, import it into your project.

The first import requires you to create a project, subsequent imports require to you to perform a project reconfiguration. The tool is a bit dumb here. It seems you can ask it to leave a source file alone or have it overwritten, I couldn't see a merge option; but at least it knows which are your code modules and which belong to the tool.

This workflow is a bit cludgey compared to Cypreses dev environment.

PSOC has complete integration within the IDE. Every peripheral module is completely versioned and documented with a PDF showing how it works, and with a lot of detail on the API generated and even how much code/ram is used. With Atmel, you need look through the function prototypes to try and find the functions you need. Also, because this is a web based tool, you have no control over the version of code being auto produced. This is potentially a big problem if you have strict auditing/testing requirements or need to come back to a project after some time has elapsed.

Atmel though, seems to be a lot stronger in seeing what is happening during execution with things like their Data Execution Gateway visualization tools.

 

Last Edited: Tue. Sep 12, 2017 - 12:40 AM