Can't start a project using ATSAME53N20

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

I've been writing code in studio 7 for several years with AVR's and now I'm moving to some ARM devices. 

I have made my own board using the ATSAME53N20, but I can't see the device when starting an ASF project. 

I have used the Device Pack Manager to make sure the device is installed, but no luck. 

I even uninstalled and reinstalled studio 7 to see if there was a problem there. 

Thanks in advance for your advice, I've spent hours on this so far...

 

Rick

 

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

The newer SAM chips that Atmel is creating uses a newer version of ASF known as "ASF 4", aka "Atmel Start".. So using the ASF dialog for newer uCs will get you nowhere. So if you want to use "ASF" for the newer SAM chips you need to create a new Atmel Start Project.

 

File > New > Atmel Start Project

 

Hope that helps.

 

//Also, here is a link to a thread I started around basically this same problem

https://community.atmel.com/foru...

 

murph

Debugging - Being a detective in a crime movie where you are also the murderer.

Last Edited: Wed. Jun 20, 2018 - 03:52 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Got it. Thanks very much. 

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

At first it seemed like Atmel Start might be handy, but now I see that it has it's share of problems. 

 

As you mention, each time I want to add an API, I have to completely rebuild the project, and potentially overwrite code that I have written. 

I tried to add the driver and middleware to operate the SPI bus for the SAME53, and the process blew up, saying that there wasn't code for a particular SPI a/d Converter which I am not interested in. Now what?

 

I'd really prefer to use the old ASF system, and manually add in independent API's as needed without rebuilding everything. 

I also don't want to be married to Atmel Start...

Do you know of any way to do that, even though they aren't tailored for my device? I'll edit the source code to make things work. 

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

Unfortunately the answer is a solid NO. My follow up email to the FAE asked if they ever planned to release "ASF 4" in a standalone matter like the previous versions, and he said as of now there are zero plans to do so.. 

 

My work around so far was very careful planning of the HW before hand, so I hopefully only have to go through Start ONCE.. Also, I have reworked my working directory quite a bit from the default structure that AS7 creates.. In doing so I actually moved driver init code and so on to a "board" file, so I think if I have to come back to Start and generate more interfaces, they will just create a new file instead of modifying my existing.

 

I have also thought very hard about grabbing my MCU and adding every single driver and middlewear to the project and generating it.. Copying out the "ASF" files and creating my own standalone repo lol.

murph

Debugging - Being a detective in a crime movie where you are also the murderer.

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

I think I'll try creating a dummy project using a controller that has the same peripheral set as the one I'm using. 

Then I can manually copy the driver libraries to a separate file and cut and paste into my project. 

 

 

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

What's the reason for using a different controller with same peripheral? Why not create a dummy project of the same controller?

murph

Debugging - Being a detective in a crime movie where you are also the murderer.