Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Wednesday, December 6th 2017, 10:04am
Please read the forum rules before posting: Forum Rules
Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/
Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/
Friday, February 9th 2018, 9:03am
Oh wow 
... Looks like they not using GCC front end, Segger has it's own. (Is this unfortunate, or ?)
U dunno, I would be feeling better if it would be possible to use GCC front end, but .. I''ll see what they reply.
Edit:
So I gave it a quick try building external and note:
1) Tool Chain Directory was the only thing I had to change. Note, I tried GNU ARM v 6, and v7 latest . On sample project Hello only.
2) Unlike the internal (pre-installed) toolchain path - $(StudioDir)/gcc/$(GCCTarget)/bin - your external can point to the GCC bin folder, and the external build configuration
comes with pre-configured "External Build", which is all specified in GCC/G++ commands, so
Alleluah Jeses thank ya,
.
I'm starting to feel warmer
... Looks like they not using GCC front end, Segger has it's own. (Is this unfortunate, or ?)markuskrug, that's the backend ..
Quoted
In SES the compiler is called by cc1
U dunno, I would be feeling better if it would be possible to use GCC front end, but .. I''ll see what they reply.
Edit:
So I gave it a quick try building external and note:
1) Tool Chain Directory was the only thing I had to change. Note, I tried GNU ARM v 6, and v7 latest . On sample project Hello only.
2) Unlike the internal (pre-installed) toolchain path - $(StudioDir)/gcc/$(GCCTarget)/bin - your external can point to the GCC bin folder, and the external build configuration
comes with pre-configured "External Build", which is all specified in GCC/G++ commands, so
Alleluah Jeses thank ya,
.I'm starting to feel warmer
This post has been edited 1 times, last edit by "v01d" (Feb 9th 2018, 9:48am)
Tuesday, February 13th 2018, 11:05am
Please read the forum rules before posting: Forum Rules
Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/
Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/
Similar threads
-
J-Link/Flasher related »-
[ABANDONED] J-Trace SDK says ETM unit is not present on K21F
(Mar 23rd 2017, 5:52pm)
-
- emWin related »
-
GUIBuilder - using non-standard fonts
(May 7th 2015, 9:44pm)
-
- J-Link/Flasher related »
-
Using two J-Links via JLINKGDBSERVER
(Apr 18th 2008, 4:21am)
-
- embOS related »
-
big-endian and embOS ARM/GNU
(Feb 7th 2008, 2:28pm)