Attiny1614 compiler support

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

I have the AVR gcc toolchain from here for my mac: https://www.microchip.com/en-us/...

 

I am using macOS for development and linux for production builds. On Linux I am installing the gcc-avr package using the package manager. Currently using Debian buster but I also tried Debian bullseye in case it was more up to date (it was not).

 

It does not appear to support the '1614. I used this for development for an Attiny841 without any problem but now I am trying to use a '1614. I googled quite a lot for pre-built avr-gcc binaries that are up to date but generally keep ending up back at that microchip site. I am using Mac or Linux, not windows. So maybe the windows version support '1614? I just feel I must be missing something obvious.

 

I am using "-mmcuattiny1614" to specify the device. I was using "-mmcuatttiny841" for the '841 and that worked. My installed toolchain seems to be missing header files (iotn1614.h) and crt and libraries for the '1614.

 

To summarize: where can I find a prebuilt binary AVR GCC toolchain for Mac and/or Linux? Do I need to build it myself?

 

Thanks for reading.

 

Mac version

❯ avr-gcc --version
avr-gcc (AVR_8_bit_GNU_Toolchain_3.6.2_514) 5.4.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Linux version

avr-gcc (GCC) 5.4.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

 

This topic has a solution.
Last Edited: Wed. Mar 17, 2021 - 01:42 PM
This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Device support is injected using packs these days.
.
See for instance https://www.avrfreaks.net/forum/solved-compiling-attiny1607-or-other-0-series1-series-avr-gcc how to give the correct compile switches...

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

barefoot_joe wrote:
On Linux I am installing the gcc-avr package using the package manager.
I think you will get more mileage from using:

 

https://www.microchip.com/en-us/...

 

But as Morten says you also have to understand "packs" and what -B does.

 

Just out of interest, given that a large part of the move from AS7/MCS7 to MPLABX is because the latter is multi-platform why aren't you installing and using MPLABX for Linux? All the packs/-B stuff is "hidden behind the scenes". You just say "build for 1614" and it happens.

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

>To summarize: where can I find a prebuilt binary AVR GCC toolchain for Mac and/or Linux?

 

An easy place to find one- Arduino. An easy web page to find. Download the setup.zip for the ide, extract the hardware/tools/avr/avr folder somewhere, you now have a toolchain which includes the headers and the few other mcu specific files. No need to then download a 'pack' and specify extra folders in the command line as the needed things are already in default locations. This method works for any os, so if you find yourself on another os, same procedure.

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

Thank you!! Perfect.

 

Edit to add: This reply was directed at meolsen. I didn't realize the forum does not do threaded replies.

 

Thanks to everyone else who also made a reply.

Last Edited: Wed. Mar 17, 2021 - 01:45 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:

But as Morten says you also have to understand "packs" and what -B does.

 

Just out of interest, given that a large part of the move from AS7/MCS7 to MPLABX is because the latter is multi-platform why aren't you installing and using MPLABX for Linux? All the packs/-B stuff is "hidden behind the scenes". You just say "build for 1614" and it happens.

 

If I start a new Atmel project I will take a look at MPLABX. Thank you for the suggestion and pointing out it is multi-platform. At the moment, the knowledge I was missing was the use of "packs" for device support using gcc toolchain. I am fairly new to Atmel ecosystem so I am not familiar specifically with MPLABX. In my past experience with other vendors, for a simple 8-bit MCU these kind of big IDE tools are bloated and overcomplicated and try to help a little too much. Also, builds need to be completely scriptable and all configuration/project files in a format that is friendly to version control. Perhaps MPLABX does not have any of these problems and I will consider it in the future.

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

curtvm wrote:

>To summarize: where can I find a prebuilt binary AVR GCC toolchain for Mac and/or Linux?

 

An easy place to find one- Arduino. An easy web page to find. Download the setup.zip for the ide, extract the hardware/tools/avr/avr folder somewhere, you now have a toolchain which includes the headers and the few other mcu specific files. No need to then download a 'pack' and specify extra folders in the command line as the needed things are already in default locations. This method works for any os, so if you find yourself on another os, same procedure.

 

Thank you that is a great idea. I am not using Arduino framework for my project so I didn't even think of downloading it just for the toolchain. However, I prefer to use official tools from the vendor when possible so I think the microchip-provided GCC toolchain plus device pack is the best solution for me now.

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

barefoot_joe wrote:
I am fairly new to Atmel (sic) ecosystem

maybe try not to get into the habit of calling it "Atmel" ... ?

 

cheeky

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:

barefoot_joe wrote:
I am fairly new to Atmel (sic) ecosystem

maybe try not to get into the habit of calling it "Atmel" ... ?

 

cheeky

 

Haha is that Andy Neil? I know you from a past life (Stellaris sound familiar?) I think I shall continue to call it Atmel because of my age and I am stubborn.

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

barefoot_joe wrote:
I know you from a past life (Stellaris sound familiar?) 

Rumbled!

 

blush

 

EDIT

 

Since you mention it: 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...
Last Edited: Wed. Mar 17, 2021 - 06:52 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

See also:  Installing Atmel Packs for how to copy the pack files into your toolchain, so that you don't have to add those extra -B switches...

 

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

westfw wrote:

See also:  Installing Atmel Packs for how to copy the pack files into your toolchain, so that you don't have to add those extra -B switches...

 

 

Thank you!

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

I wrote a little shell script to automate the download/build of the toolchain, here:

 

https://github.com/MarkR42/robot...

 

Mark