How can i add a architecture which is available in new version of gcc to a old version of gcc?Unable to compile TinyOs applications with avr-gcc 4.2.1 but able to compile with avr-gcc 3.3Can I upgrade Xcode to support a newer version of GCC to learn C++0x?Installing an old version of gcc on linux-redhatIs it possible to cross-compile adb for old c89 compiler arm-linux-gcc --version 2.95.2?GCC compiler porting to new architecture : Call external library functiongcc atomic builtins and availability versionHow to change the gcc version on the MacHow to determine architecture to build GCC cross compiler?How can I determine what architectures gcc supports?How to get GCC version supports specific feature?Unable to compile TinyOs applications with avr-gcc 4.2.1 but able to compile with avr-gcc 3.3
Is it possible to Ready a spell to be cast just before the start of your next turn by having the trigger be an ally's attack?
Past Perfect Tense
How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?
Build a trail cart
How does a Swashbuckler rogue "fight with two weapons while safely darting away"?
When to use 1/Ka vs Kb
Transfer over $10k
Feels like I am getting dragged in office politics
What word means to make something obsolete?
What's the metal clinking sound at the end of credits in Avengers: Endgame?
Are Boeing 737-800’s grounded?
Weird result in complex limit
Is thermodynamics only applicable to systems in equilibrium?
What is the strongest case that can be made in favour of the UK regaining some control over fishing policy after Brexit?
Single Colour Mastermind Problem
How to creep the reader out with what seems like a normal person?
What's the polite way to say "I need to urinate"?
Sci-fi novel series with instant travel between planets through gates. A river runs through the gates
How to back up a running remote server?
Packing rectangles: Does rotation ever help?
Find the coordinate of two line segments that are perpendicular
"ne paelici suspectaretur" (Tacitus)
Are some sounds more pleasing to the ear, like ㄴ and ㅁ?
Why is current rating for multicore cable lower than single core with the same cross section?
How can i add a architecture which is available in new version of gcc to a old version of gcc?
Unable to compile TinyOs applications with avr-gcc 4.2.1 but able to compile with avr-gcc 3.3Can I upgrade Xcode to support a newer version of GCC to learn C++0x?Installing an old version of gcc on linux-redhatIs it possible to cross-compile adb for old c89 compiler arm-linux-gcc --version 2.95.2?GCC compiler porting to new architecture : Call external library functiongcc atomic builtins and availability versionHow to change the gcc version on the MacHow to determine architecture to build GCC cross compiler?How can I determine what architectures gcc supports?How to get GCC version supports specific feature?Unable to compile TinyOs applications with avr-gcc 4.2.1 but able to compile with avr-gcc 3.3
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I want to add Atmega1281 architecture to my current version of gcc that i am using i.e. v3.3.
The Atmega1281 is not supported in the v3.3 and its support got added in v4.2.1 .
I cannot upgrade the gcc to 4.2.1, so i need to add the support to my existing compiler.
Is there any way to do this ?
gcc cross-compiling avr atmega avr-gcc
|
show 1 more comment
I want to add Atmega1281 architecture to my current version of gcc that i am using i.e. v3.3.
The Atmega1281 is not supported in the v3.3 and its support got added in v4.2.1 .
I cannot upgrade the gcc to 4.2.1, so i need to add the support to my existing compiler.
Is there any way to do this ?
gcc cross-compiling avr atmega avr-gcc
2
If you want to backport the Atmega1281 support into v3.3, then go for it. Here's the code.
– Raymond Chen
Mar 19 at 6:11
its just link to raw gcc. doesn't make sense.
– Biswajeet Sahoo
Mar 19 at 10:24
Generally, whole the AVR family is the same, so, all you need is it locate all .h files (which are indirectly included inside <avr/io.h> in the new tool chain and include them directly to your project.
– AterLux
Mar 19 at 13:53
The compiler should know to generate the executable for the new architecture, including doesn't make sense .
– Biswajeet Sahoo
Mar 20 at 5:55
The code is the same for the whole AVR mega familiy, let's say there is no difference in code between ATmega328 and ATmega1281, only the difference is size of flash/ram/eeprom, and where and which IO registers are located.
– AterLux
Mar 20 at 11:12
|
show 1 more comment
I want to add Atmega1281 architecture to my current version of gcc that i am using i.e. v3.3.
The Atmega1281 is not supported in the v3.3 and its support got added in v4.2.1 .
I cannot upgrade the gcc to 4.2.1, so i need to add the support to my existing compiler.
Is there any way to do this ?
gcc cross-compiling avr atmega avr-gcc
I want to add Atmega1281 architecture to my current version of gcc that i am using i.e. v3.3.
The Atmega1281 is not supported in the v3.3 and its support got added in v4.2.1 .
I cannot upgrade the gcc to 4.2.1, so i need to add the support to my existing compiler.
Is there any way to do this ?
gcc cross-compiling avr atmega avr-gcc
gcc cross-compiling avr atmega avr-gcc
asked Mar 19 at 5:49
Biswajeet SahooBiswajeet Sahoo
64
64
2
If you want to backport the Atmega1281 support into v3.3, then go for it. Here's the code.
– Raymond Chen
Mar 19 at 6:11
its just link to raw gcc. doesn't make sense.
– Biswajeet Sahoo
Mar 19 at 10:24
Generally, whole the AVR family is the same, so, all you need is it locate all .h files (which are indirectly included inside <avr/io.h> in the new tool chain and include them directly to your project.
– AterLux
Mar 19 at 13:53
The compiler should know to generate the executable for the new architecture, including doesn't make sense .
– Biswajeet Sahoo
Mar 20 at 5:55
The code is the same for the whole AVR mega familiy, let's say there is no difference in code between ATmega328 and ATmega1281, only the difference is size of flash/ram/eeprom, and where and which IO registers are located.
– AterLux
Mar 20 at 11:12
|
show 1 more comment
2
If you want to backport the Atmega1281 support into v3.3, then go for it. Here's the code.
– Raymond Chen
Mar 19 at 6:11
its just link to raw gcc. doesn't make sense.
– Biswajeet Sahoo
Mar 19 at 10:24
Generally, whole the AVR family is the same, so, all you need is it locate all .h files (which are indirectly included inside <avr/io.h> in the new tool chain and include them directly to your project.
– AterLux
Mar 19 at 13:53
The compiler should know to generate the executable for the new architecture, including doesn't make sense .
– Biswajeet Sahoo
Mar 20 at 5:55
The code is the same for the whole AVR mega familiy, let's say there is no difference in code between ATmega328 and ATmega1281, only the difference is size of flash/ram/eeprom, and where and which IO registers are located.
– AterLux
Mar 20 at 11:12
2
2
If you want to backport the Atmega1281 support into v3.3, then go for it. Here's the code.
– Raymond Chen
Mar 19 at 6:11
If you want to backport the Atmega1281 support into v3.3, then go for it. Here's the code.
– Raymond Chen
Mar 19 at 6:11
its just link to raw gcc. doesn't make sense.
– Biswajeet Sahoo
Mar 19 at 10:24
its just link to raw gcc. doesn't make sense.
– Biswajeet Sahoo
Mar 19 at 10:24
Generally, whole the AVR family is the same, so, all you need is it locate all .h files (which are indirectly included inside <avr/io.h> in the new tool chain and include them directly to your project.
– AterLux
Mar 19 at 13:53
Generally, whole the AVR family is the same, so, all you need is it locate all .h files (which are indirectly included inside <avr/io.h> in the new tool chain and include them directly to your project.
– AterLux
Mar 19 at 13:53
The compiler should know to generate the executable for the new architecture, including doesn't make sense .
– Biswajeet Sahoo
Mar 20 at 5:55
The compiler should know to generate the executable for the new architecture, including doesn't make sense .
– Biswajeet Sahoo
Mar 20 at 5:55
The code is the same for the whole AVR mega familiy, let's say there is no difference in code between ATmega328 and ATmega1281, only the difference is size of flash/ram/eeprom, and where and which IO registers are located.
– AterLux
Mar 20 at 11:12
The code is the same for the whole AVR mega familiy, let's say there is no difference in code between ATmega328 and ATmega1281, only the difference is size of flash/ram/eeprom, and where and which IO registers are located.
– AterLux
Mar 20 at 11:12
|
show 1 more comment
2 Answers
2
active
oldest
votes
You don't need to update GCC (I presume you are actually using AVR-GCC to generate AVR specific machine code...). All AVR chips use the same AVR core and instruction set. The only thing that changes from one chip to another are memory sizes, register addresses, and the availability of peripherals.
You might need to update AVRlibc if you use those core libraries, and you'll need to add device configurations for a programming utility like avrdude.
You must update the core headers that define register locations, unless you define your own pointers to the raw memory addresses (like a boss). This can be found in the Atmel Packs, specifically the support for Atmega devices.
When you include io.h in your project, that pulls in the device-specific definitions with nice defined pointers to memory to access peripherals configuration and data registers. This only works if you pass the device in use as a special definition in your compilation command. If you are using the standard Makefile template, the device is one of the things you edit, and it handles those commands. Similarly, an IDE like Atmel Studio will ask what device you are using and generate the Makefile for you.
But don't take it from me, here is the relevant information from the AVR-GCC wiki in the section titled Supporting "unsupported" Devices.
When you feed code into the compiler and compile for a specific
device, the compiler will only care for the respective core; it won't
care for the exact device. It does not matter to the compiler how many
I/O pins the device has, at what voltage it operates, how much RAM is
present, how many timers or UARTs are on the silicon or in what
package it is shipped. The only thing the compiler does with
-mmcu=device is to build-in define a specific macro and to call the linker in a specific way, i.e. the compiler driver behaves a bit
differently, but the sub-tools like compiler proper and assembler will
generate exactly the same code.
Thus, you can support your device by setting these options by hand.
So, if you cannot update AVR-GCC for whatever reason, you can still compile for your device by manually telling the linker where to look for stuff and specifying the correct includes from the io.h tree.
The wiki also gives more instructions on how to do this.
if i use my current avr-gcc 3.3 to build for atmega1281, i get error as its a unknown mcu. Also if i do , "avr-gcc --target-help", that architecture is not available. So i need to add the support for Atmega1281 to the current avr-gcc3.3.
– Biswajeet Sahoo
Mar 26 at 8:38
See the updated section of my answer. You are misunderstanding what those messages mean. You can still compile for your "unsupported" device because the compiler doesn't care about the device, it's only helping you to include the correct definitions and linked libs.
– Kurt E. Clothier
Mar 26 at 20:15
Thanks a lot. Now things got clear to me.
– Biswajeet Sahoo
Mar 27 at 9:06
add a comment |
In order to add the architecture,
three things need to be updated,
gcc -
gccconfigavravr.c,
gccconfigavravr.h,
gccconfigavrt-avr,Binutils -
gastc-avr.cavr-libc -
avrio.h,
configure,
configure.in,
And Header file changes.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55234417%2fhow-can-i-add-a-architecture-which-is-available-in-new-version-of-gcc-to-a-old-v%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You don't need to update GCC (I presume you are actually using AVR-GCC to generate AVR specific machine code...). All AVR chips use the same AVR core and instruction set. The only thing that changes from one chip to another are memory sizes, register addresses, and the availability of peripherals.
You might need to update AVRlibc if you use those core libraries, and you'll need to add device configurations for a programming utility like avrdude.
You must update the core headers that define register locations, unless you define your own pointers to the raw memory addresses (like a boss). This can be found in the Atmel Packs, specifically the support for Atmega devices.
When you include io.h in your project, that pulls in the device-specific definitions with nice defined pointers to memory to access peripherals configuration and data registers. This only works if you pass the device in use as a special definition in your compilation command. If you are using the standard Makefile template, the device is one of the things you edit, and it handles those commands. Similarly, an IDE like Atmel Studio will ask what device you are using and generate the Makefile for you.
But don't take it from me, here is the relevant information from the AVR-GCC wiki in the section titled Supporting "unsupported" Devices.
When you feed code into the compiler and compile for a specific
device, the compiler will only care for the respective core; it won't
care for the exact device. It does not matter to the compiler how many
I/O pins the device has, at what voltage it operates, how much RAM is
present, how many timers or UARTs are on the silicon or in what
package it is shipped. The only thing the compiler does with
-mmcu=device is to build-in define a specific macro and to call the linker in a specific way, i.e. the compiler driver behaves a bit
differently, but the sub-tools like compiler proper and assembler will
generate exactly the same code.
Thus, you can support your device by setting these options by hand.
So, if you cannot update AVR-GCC for whatever reason, you can still compile for your device by manually telling the linker where to look for stuff and specifying the correct includes from the io.h tree.
The wiki also gives more instructions on how to do this.
if i use my current avr-gcc 3.3 to build for atmega1281, i get error as its a unknown mcu. Also if i do , "avr-gcc --target-help", that architecture is not available. So i need to add the support for Atmega1281 to the current avr-gcc3.3.
– Biswajeet Sahoo
Mar 26 at 8:38
See the updated section of my answer. You are misunderstanding what those messages mean. You can still compile for your "unsupported" device because the compiler doesn't care about the device, it's only helping you to include the correct definitions and linked libs.
– Kurt E. Clothier
Mar 26 at 20:15
Thanks a lot. Now things got clear to me.
– Biswajeet Sahoo
Mar 27 at 9:06
add a comment |
You don't need to update GCC (I presume you are actually using AVR-GCC to generate AVR specific machine code...). All AVR chips use the same AVR core and instruction set. The only thing that changes from one chip to another are memory sizes, register addresses, and the availability of peripherals.
You might need to update AVRlibc if you use those core libraries, and you'll need to add device configurations for a programming utility like avrdude.
You must update the core headers that define register locations, unless you define your own pointers to the raw memory addresses (like a boss). This can be found in the Atmel Packs, specifically the support for Atmega devices.
When you include io.h in your project, that pulls in the device-specific definitions with nice defined pointers to memory to access peripherals configuration and data registers. This only works if you pass the device in use as a special definition in your compilation command. If you are using the standard Makefile template, the device is one of the things you edit, and it handles those commands. Similarly, an IDE like Atmel Studio will ask what device you are using and generate the Makefile for you.
But don't take it from me, here is the relevant information from the AVR-GCC wiki in the section titled Supporting "unsupported" Devices.
When you feed code into the compiler and compile for a specific
device, the compiler will only care for the respective core; it won't
care for the exact device. It does not matter to the compiler how many
I/O pins the device has, at what voltage it operates, how much RAM is
present, how many timers or UARTs are on the silicon or in what
package it is shipped. The only thing the compiler does with
-mmcu=device is to build-in define a specific macro and to call the linker in a specific way, i.e. the compiler driver behaves a bit
differently, but the sub-tools like compiler proper and assembler will
generate exactly the same code.
Thus, you can support your device by setting these options by hand.
So, if you cannot update AVR-GCC for whatever reason, you can still compile for your device by manually telling the linker where to look for stuff and specifying the correct includes from the io.h tree.
The wiki also gives more instructions on how to do this.
if i use my current avr-gcc 3.3 to build for atmega1281, i get error as its a unknown mcu. Also if i do , "avr-gcc --target-help", that architecture is not available. So i need to add the support for Atmega1281 to the current avr-gcc3.3.
– Biswajeet Sahoo
Mar 26 at 8:38
See the updated section of my answer. You are misunderstanding what those messages mean. You can still compile for your "unsupported" device because the compiler doesn't care about the device, it's only helping you to include the correct definitions and linked libs.
– Kurt E. Clothier
Mar 26 at 20:15
Thanks a lot. Now things got clear to me.
– Biswajeet Sahoo
Mar 27 at 9:06
add a comment |
You don't need to update GCC (I presume you are actually using AVR-GCC to generate AVR specific machine code...). All AVR chips use the same AVR core and instruction set. The only thing that changes from one chip to another are memory sizes, register addresses, and the availability of peripherals.
You might need to update AVRlibc if you use those core libraries, and you'll need to add device configurations for a programming utility like avrdude.
You must update the core headers that define register locations, unless you define your own pointers to the raw memory addresses (like a boss). This can be found in the Atmel Packs, specifically the support for Atmega devices.
When you include io.h in your project, that pulls in the device-specific definitions with nice defined pointers to memory to access peripherals configuration and data registers. This only works if you pass the device in use as a special definition in your compilation command. If you are using the standard Makefile template, the device is one of the things you edit, and it handles those commands. Similarly, an IDE like Atmel Studio will ask what device you are using and generate the Makefile for you.
But don't take it from me, here is the relevant information from the AVR-GCC wiki in the section titled Supporting "unsupported" Devices.
When you feed code into the compiler and compile for a specific
device, the compiler will only care for the respective core; it won't
care for the exact device. It does not matter to the compiler how many
I/O pins the device has, at what voltage it operates, how much RAM is
present, how many timers or UARTs are on the silicon or in what
package it is shipped. The only thing the compiler does with
-mmcu=device is to build-in define a specific macro and to call the linker in a specific way, i.e. the compiler driver behaves a bit
differently, but the sub-tools like compiler proper and assembler will
generate exactly the same code.
Thus, you can support your device by setting these options by hand.
So, if you cannot update AVR-GCC for whatever reason, you can still compile for your device by manually telling the linker where to look for stuff and specifying the correct includes from the io.h tree.
The wiki also gives more instructions on how to do this.
You don't need to update GCC (I presume you are actually using AVR-GCC to generate AVR specific machine code...). All AVR chips use the same AVR core and instruction set. The only thing that changes from one chip to another are memory sizes, register addresses, and the availability of peripherals.
You might need to update AVRlibc if you use those core libraries, and you'll need to add device configurations for a programming utility like avrdude.
You must update the core headers that define register locations, unless you define your own pointers to the raw memory addresses (like a boss). This can be found in the Atmel Packs, specifically the support for Atmega devices.
When you include io.h in your project, that pulls in the device-specific definitions with nice defined pointers to memory to access peripherals configuration and data registers. This only works if you pass the device in use as a special definition in your compilation command. If you are using the standard Makefile template, the device is one of the things you edit, and it handles those commands. Similarly, an IDE like Atmel Studio will ask what device you are using and generate the Makefile for you.
But don't take it from me, here is the relevant information from the AVR-GCC wiki in the section titled Supporting "unsupported" Devices.
When you feed code into the compiler and compile for a specific
device, the compiler will only care for the respective core; it won't
care for the exact device. It does not matter to the compiler how many
I/O pins the device has, at what voltage it operates, how much RAM is
present, how many timers or UARTs are on the silicon or in what
package it is shipped. The only thing the compiler does with
-mmcu=device is to build-in define a specific macro and to call the linker in a specific way, i.e. the compiler driver behaves a bit
differently, but the sub-tools like compiler proper and assembler will
generate exactly the same code.
Thus, you can support your device by setting these options by hand.
So, if you cannot update AVR-GCC for whatever reason, you can still compile for your device by manually telling the linker where to look for stuff and specifying the correct includes from the io.h tree.
The wiki also gives more instructions on how to do this.
edited Mar 26 at 20:14
answered Mar 22 at 19:14
Kurt E. ClothierKurt E. Clothier
1208
1208
if i use my current avr-gcc 3.3 to build for atmega1281, i get error as its a unknown mcu. Also if i do , "avr-gcc --target-help", that architecture is not available. So i need to add the support for Atmega1281 to the current avr-gcc3.3.
– Biswajeet Sahoo
Mar 26 at 8:38
See the updated section of my answer. You are misunderstanding what those messages mean. You can still compile for your "unsupported" device because the compiler doesn't care about the device, it's only helping you to include the correct definitions and linked libs.
– Kurt E. Clothier
Mar 26 at 20:15
Thanks a lot. Now things got clear to me.
– Biswajeet Sahoo
Mar 27 at 9:06
add a comment |
if i use my current avr-gcc 3.3 to build for atmega1281, i get error as its a unknown mcu. Also if i do , "avr-gcc --target-help", that architecture is not available. So i need to add the support for Atmega1281 to the current avr-gcc3.3.
– Biswajeet Sahoo
Mar 26 at 8:38
See the updated section of my answer. You are misunderstanding what those messages mean. You can still compile for your "unsupported" device because the compiler doesn't care about the device, it's only helping you to include the correct definitions and linked libs.
– Kurt E. Clothier
Mar 26 at 20:15
Thanks a lot. Now things got clear to me.
– Biswajeet Sahoo
Mar 27 at 9:06
if i use my current avr-gcc 3.3 to build for atmega1281, i get error as its a unknown mcu. Also if i do , "avr-gcc --target-help", that architecture is not available. So i need to add the support for Atmega1281 to the current avr-gcc3.3.
– Biswajeet Sahoo
Mar 26 at 8:38
if i use my current avr-gcc 3.3 to build for atmega1281, i get error as its a unknown mcu. Also if i do , "avr-gcc --target-help", that architecture is not available. So i need to add the support for Atmega1281 to the current avr-gcc3.3.
– Biswajeet Sahoo
Mar 26 at 8:38
See the updated section of my answer. You are misunderstanding what those messages mean. You can still compile for your "unsupported" device because the compiler doesn't care about the device, it's only helping you to include the correct definitions and linked libs.
– Kurt E. Clothier
Mar 26 at 20:15
See the updated section of my answer. You are misunderstanding what those messages mean. You can still compile for your "unsupported" device because the compiler doesn't care about the device, it's only helping you to include the correct definitions and linked libs.
– Kurt E. Clothier
Mar 26 at 20:15
Thanks a lot. Now things got clear to me.
– Biswajeet Sahoo
Mar 27 at 9:06
Thanks a lot. Now things got clear to me.
– Biswajeet Sahoo
Mar 27 at 9:06
add a comment |
In order to add the architecture,
three things need to be updated,
gcc -
gccconfigavravr.c,
gccconfigavravr.h,
gccconfigavrt-avr,Binutils -
gastc-avr.cavr-libc -
avrio.h,
configure,
configure.in,
And Header file changes.
add a comment |
In order to add the architecture,
three things need to be updated,
gcc -
gccconfigavravr.c,
gccconfigavravr.h,
gccconfigavrt-avr,Binutils -
gastc-avr.cavr-libc -
avrio.h,
configure,
configure.in,
And Header file changes.
add a comment |
In order to add the architecture,
three things need to be updated,
gcc -
gccconfigavravr.c,
gccconfigavravr.h,
gccconfigavrt-avr,Binutils -
gastc-avr.cavr-libc -
avrio.h,
configure,
configure.in,
And Header file changes.
In order to add the architecture,
three things need to be updated,
gcc -
gccconfigavravr.c,
gccconfigavravr.h,
gccconfigavrt-avr,Binutils -
gastc-avr.cavr-libc -
avrio.h,
configure,
configure.in,
And Header file changes.
answered Apr 8 at 12:40
Biswajeet SahooBiswajeet Sahoo
64
64
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55234417%2fhow-can-i-add-a-architecture-which-is-available-in-new-version-of-gcc-to-a-old-v%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
If you want to backport the Atmega1281 support into v3.3, then go for it. Here's the code.
– Raymond Chen
Mar 19 at 6:11
its just link to raw gcc. doesn't make sense.
– Biswajeet Sahoo
Mar 19 at 10:24
Generally, whole the AVR family is the same, so, all you need is it locate all .h files (which are indirectly included inside <avr/io.h> in the new tool chain and include them directly to your project.
– AterLux
Mar 19 at 13:53
The compiler should know to generate the executable for the new architecture, including doesn't make sense .
– Biswajeet Sahoo
Mar 20 at 5:55
The code is the same for the whole AVR mega familiy, let's say there is no difference in code between ATmega328 and ATmega1281, only the difference is size of flash/ram/eeprom, and where and which IO registers are located.
– AterLux
Mar 20 at 11:12