START ASF4 multiple definitions for FLEXCOM Handler ATSAMG55

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

Hi all,

 

I am running into a problem that I hope is easily duplicated because I used the tools directly to configure a project and it won't compile properly.  I am using AS7 along with START/ASF4 to attempt to generate a project for the ATSAMG55 XPlained board.  I began by using the START tool (web version at start.atmel.com) to generate the example EDBG UART project.  This worked fine by itself but then I reconfigured the project to add in a SPI port.  The EDBG UART uses FLEXCOM7 and the SPI on the EXT3 port uses FLEXCOM5.  When I add in the SPI port, the project will not compile due to getting a multiple definition of 'FLEXCOM7_Handler'.

 

I can see in the file hpl_spi.c that there is a definition of this function that conflicts with a definition in hpl_usart.c. But I didn't define the FLEXCOM7 for SPI since I didn't declare any SPI interrupt and if I did it should be FLEXCOM5.

 

I also attempted this by making another instance of the project from scratch by starting with the start.atmel.com > browse examples. Set the board to SAM G55 Xplained Pro and EDBG UART then Open Selected Example.

 

This brings up the component view showing EDBG_COM using FLEXCOM7.  I then add the software driver for a SPI port and configure it to use FLEXCOM5.  Then I generate and download the project and import into AS7 (build 7.0.1417).  I then get the error about multiple definitions when I attempt to build the solution.  I have not added any code other than what it generated.

 

I can see in the multiple definitions of FLEXCOM7_Handler in both the hpl_spi.c and hpl_usart.c.  It will compile if I comment out the handler define in hpl_spi.c.

 

As a trial, I did attempt to declare an interrupt for FLEXCOM5 using the START configuration (I set the SPI for async mode) and then I get two multiple definition, one for FLEXCOM5_Handler and one for FLEXCOM7_Handler.

 

This seems like a bug to me but I'm new to using AS7 and ASF.  Does anyone know if this is the normal expected behavior and the user is expected to find and modify these problems.

 

Comments or help is appreciated.  Thanks in advance.

 

 

 

 

This topic has a solution.
Last Edited: Thu. Aug 24, 2017 - 12:26 PM
This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This issue was presented to Microchip support as a support ticket.  They have agreed it is a bug in the tool.  My workaround is to delete the unwanted interrupt handlers.