Trying to compile WINC1500 Driver source code

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

Hi guys

 

For the last two days, I have been trying to compile the Atmel WINC 1500 Wi-Fi driver source code in my Atmel studio project. I have been struggling to get it working, as the Atmel studio compiler has been throwing all these errors saying that such and such headers aren't there but are, despite triple-checking I have imported the files into the project. I have also added the driver folders in the AVR32/GNU C Compiler directories. 

 

Here's the Winc1500 driver source code 

https://github.com/ARMmbed/sal-driver-atmel-winc1500

 

I even tried importing the WINC1500 driver files on a completely empty project and I'm still getting issues. Eventually, I have to get the WINC1500 module working with an AT32UC1256C Microcontroller that is on a custom board. 

Attachment(s): 

This topic has a solution.
Last Edited: Sun. Dec 1, 2019 - 08:20 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"Error List" in AS7 (and VS2015 on which it is based) is almost entirely pointless. try just looking at the "Ouput" tab where the raw errors were reported. Concentrate only on fixing whatever error is reported first (because often the solution for the first error is the solution for the next 2,741 errors too)

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

It's mainly the bus wrapper and bsp file from the WINC1500 driver source code that's causing it to not compile. Has anyone done a port of the WINC1500 Wi-Fi driver source code for the AT32UC3C1256C MCU, in order to get it communicating with each over via the SPI?

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

sahil885 wrote:
Here's the (sic) Winc1500 driver source code

Well, that's the mbed driver.

 

Don't Atmel provide their own driver ?

 

IIRC, the WINC is SAM-based - so you might find better answers in the SAM forums ... ?

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 wrote:
Don't Atmel provide their own driver ?

 

Indeed they do:

 

On the WINC1500 Product Page, Microchip wrote:

A MCU host driver can be found in the Advanced Software Framework (ASF).

 

https://www.microchip.com/wwwproducts/en/ATwinc1500

 

Also check out the 'Documents' tab there ...

 

 

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

All the examples of the Winc1500 driver are for the SAM boards but I need the wi fi driver code to work with the AT32UC1256C MCU via the SPI

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

sahil885 wrote:
I need the wi fi driver code to work with the AT32UC1256C MCU

An AVR32?

 

Well, that's going to be a fundamental problem!

 

See: https://www.avrfreaks.net/commen...

 

If you want ready-to-go, out-of-the-box solutions, then you need to choose your components accordingly - you need to go for the mainstream parts which have the wide support!

 

I think neither AVR32 nor WINC are "mainstream" ?

 

All the examples of the Winc1500 driver are for the SAM boards

The only thing that's actually specific to the SAM (or any other microcontroller) should be the low-level hardware details.

 

So, once you've got them going on the AVR32, the rest of the code should be (largely) platform-agnostic.

 

Some of the SAM peripherals are quite similar to AVR32 ...

 

 

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 didn't get a say on the parts unfortunately so I'm out of luck. I really don't know where to began with getting the winc1500 working with the AT32UC1256C MCU.

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

sahil885 wrote:
I didn't get a say on the parts unfortunately so I'm out of luck.

Oh well - such is life.

 

But you need to feed back to whoever was responsible for the decision.

If they are assuming that your task will be simply (sic) a matter of grabbing ready-to-go drivers, then they will need to revise their plans!

 

I really don't know where to began with getting the winc1500 working with the AT32UC1256C MCU.

That's really a separate topic - I think we've finished the topic here of "Trying to compile WINC1500 Driver source code".

 

So time to mark this as resolved - see Tip #5 - and maybe start a new topic.

 

If you really don't know where to start, then you need to go back to whoever assigned you the task.

 

But, again, the general principles & process of how to do peripheral interfacing are not specific to a particular target.

 

http://www.8052mcu.com/forum/read/160143

 

 

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

awneil wrote:
I think we've finished the topic here of "Trying to compile WINC1500 Driver source code".

 

So time to  mark this as resolved - see Tip #5 - and maybe start a new topic.

So you've marked this a resolved, but then started a new thread which is still about the topic "Trying to compile WINC1500 Driver source code"

 

https://www.avrfreaks.net/forum/...

 

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

awneil wrote:
The only thing that's actually specific to the SAM (or any other microcontroller) should be the low-level hardware details

There are many threads on the WINC forums about using them with other hosts:

 

https://www.avrfreaks.net/commen...

 

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...