Home › Forums › TinyG › TinyG Support › Compiling firmware for TinyG?
- This topic has 6 replies, 2 voices, and was last updated 7 years, 10 months ago by cmcgrath5035.
-
AuthorPosts
-
January 9, 2017 at 7:51 pm #10158ehrichweissMember
I’m attempting to see if I can fix my problems with the G38.2/M6 commands by recompiling the firmware. The problem seems to be that there are no updated instructions on how to compile.
I initially tried to compile on Linux but none of the Makefiles worked. Eventually I tried AVRStudio 4(because everything I read said it was the best to work with) on XP and it still shows problems compiling. I can compile xboot but if I’m understanding correctly that’s just the bootloader and won’t actually help me with the firmware itself. When I try to compile the firmware it complains with
“system.c:50 error: ‘HW_VERSION_TINYGV8’ undeclared (first use in this function)”
Any help appreciated.
Eric
January 9, 2017 at 8:03 pm #10159cmcgrath5035ModeratorJanuary 10, 2017 at 2:34 am #10161ehrichweissMemberI have a V8 though, how do I use the V9 instructions? Merely change any “V9” references in commands to “V8”?
- This reply was modified 7 years, 10 months ago by ehrichweiss.
January 10, 2017 at 2:43 am #10163ehrichweissMemberNever mind. I think I get it. I’ve been working with G1 code and if I’m understanding correctly V8 hardware is now included in G2.
January 10, 2017 at 5:59 am #10164cmcgrath5035ModeratorI’ve been working with G1 code and if I’m understanding correctly V8 hardware is now included in G2.
Perhaps this G2 wiki item will help clarify
If you have tinyG V8, you need to work with the tinyG code base.
The DUE class microcontroller which is the target for G2 code base has capabilities beyond those available in tinyG’s Atmel ATxmega192 device.
The G2 code does not run on the tinyG, but many of the internals are derived from common logic ported to the two different architectures.tinyG V9 is a prototype product that was not offered for sale. It featured the higher capability microcontroller used on the DUE. V9 will not be productized, but you will see it in the G2 code base build environment.
Hope that helps
January 13, 2017 at 3:11 pm #10172ehrichweissMemberOk, I’m a bit further along. I still can’t seem to get it to compile on Linux but I got AVR Studio 6.2 working in Windows(thank goodness for VirtualBox) and it’s successfully compiled the code as-is.
Now for my next big question, if I’m attempting to debug the code, is the Atmel-ICE(or MKII) device 100% necessary?
January 15, 2017 at 6:14 am #10176cmcgrath5035ModeratorAssuming you are compiling the tinyG (not G2) project, you might want to post an Issue here:
We don’t see much forum traffic on compile issues.
You can also review open and closed issues for helpful hints -
AuthorPosts
- You must be logged in to reply to this topic.