Loading existing project to Atmel Start and reconfiguring Sercom ports

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

Hello everybody,

I have Atsamd21 Xplained Pro kit, I am using USB MSC example project and configured it to work with SD Cards. I want to add USART drivers to my project and change SPI port of SD Card from Sercom port 1 to Sercom port 2 using Atmel START. 
How can i load this project to Atmel START and reconfigure existing SPI sercom port to Sercom port 2 or 3 and add USART drivers apply on Sercom port 1.?

Thank you

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

Go to http://start.atmel.com and click on the "Load Project From File" button.  Browse to your project, select it, and if you are lucky, update your project as needed.

 

Unfortunately it's more likely that START will throw an error trying to load your previous project and you are screwed.  This happens because Atmel has not thought through the process of reloading projects into START.  Atmel rightfully so will update the server code that START is running on.  They likewise update the code generating portions underneath it.  Newly created projects should work fine with each update.  But they often break the ability to reload older projects with each update.  And to make it worse there is no selection available to use an older version of START to match it to the one you used with your project.

 

What to do?  Painfully recreate your project from scratch if you want to add a module to an existing project.  Then back merge the source code changes by hand into your project.  And pray Atmel gives us the ability to select the version of START on their server or better yet releases an offline version of START so you can be assured of its version.

 

Atmel - if you are reading this - you need versioning capabilities on the START server.  What good is the START code generator if two weeks later I can't reload my project and add a module simply because the START server that you control was updated?!?

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

Hello,
thank you very much for replying,

 

 recreate your project from scratch if you want to add a module to an existing project.

 

Now that's a painful work.. 

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

ScottMN wrote:
Atmel - if you are reading this ...

I copied your post into this thread - https://www.avrfreaks.net/comment... - Where Jacob of Microchip said he's listening ...

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I asked the START team about their plans for adding versioning... and they are aware of the problem, but do not have a short term solution for this. Sorry.

Jacob

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

SO how did they envisage that customers would use this??

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'd like to know that one too.  

 

Small projects usually from hobbyists, makers, experimenters, students, and so on usually will not see the problem.  The hobbyist tends to work on a small board, load in the few modules from START that they need the first time around, and go.  I'd guess the project length is measured in days to weeks at best.  It's rare to need to go back into START, or if they do go back the Atmel server code hasn't changed.

 

A commercial project though where the team starts bringing up their board module by module, will run into the lack of START versioning often.  Right now I'm on a two-man project eight months deep.  We're looking to add Ethernet support as all the other dozen or so modules are finally working along with the upper layer application.  But the project will not reload into START to add Ethernet and TCP/IP.  Why won't it load?  Because Atmel upgraded the START server and broke backwards compatibility.  And Atmel does not expose access to the prior version of their START server code that was running when I created the project eight months ago.

 

You would think the needs of the commercial market where chips are bought in huge quantities would matter.  But no, the message from Atmel so far has been very disappointing.  If you need to reload your project into START, good luck, no gaurantees it works, and no plans to fix it.  So yeah, the commercial market and the dollars you spend do not matter to Atmel.

 

In my case we've decided to go with a third party TCP/IP stack simply because the pain of recreating the project in START to load the TCP/IP support was just too great.  And on the next project we will be reevaluating our decision to go with Atmel ARM processors because of the immaturity of the Atmel development tools.  Yes Atmel you are driving away your commercial customers.