Need help making minimal bare metal ARM Cortex-M D program
I am very new to D, but I finally got my toolchain compiled and
working. I'm using LDC. I failed with GDC and eventually gave
up.
I am trying to get an _extremely_ minimal bare metal ARM Cortex-M
HelloWorld-type program compiled and executed on my STM32F4-based
hardware. I know the toochain is buggy for arm right now, but
I'm hoping I can do something about that if I can just get
started.
Here's the basic C code and linker script for my hardware. It
doesn't actually print "hello world". I intend to add that after
I get the following basic code compiled and downloaded to my
hardware.
/***
* start.c
/
// defined in linker script
extern unsigned long _stack_end;
void handler_reset(void)
{
//Print hello world using SWI
}
__attribute__ ((section(".interrupt_vector")))
void (* const table_interrupt_vector[])(void) =
{
(void *) &_stack_end,
handler_reset
};
/***
* linkerscript.ld
/
MEMORY
{
CCRAM(rxw) : ORIGIN = 0x1000, LENGTH = 64k
SRAM (rxw) : ORIGIN = 0x2000, LENGTH = 128k
FLASH(rx) : ORIGIN = 0x0800, LENGTH = 1024k
}
SECTIONS
{
.ccm (NOLOAD) :
{
. = ALIGN(4);
*(.ccm)
. = ALIGN(4);
} >CCRAM
stackTop = ORIGIN(CCRAM) + LENGTH(CCRAM);
Need help making minimal bare metal ARM Cortex-M D program
I am very new to D, but I finally got my toolchain compiled and
working. I'm using LDC. I failed with GDC and eventually gave
up.
I am trying to get an _extremely_ minimal bare metal ARM Cortex-M
HelloWorld-type program (no phobos, no runtime, nothing but what
I type myself) compiled and executed on my STM32F4-based
hardware. I know the toolchain is buggy for arm right now, but
I'm hoping I can do something about that if I can just get
started.
Here's the basic C code and linker script for my hardware. It
doesn't actually print "hello world". I intend to add that after
I get the following code compiled and downloaded to my hardware.
/***
* start.c
/
// defined in linker script
extern unsigned long _stack_end;
void handler_reset(void)
{
//Print hello world using SWI
}
__attribute__ ((section(".interrupt_vector")))
void (* const table_interrupt_vector[])(void) =
{
(void *) &_stack_end,
handler_reset
};
/***
* linkerscript.ld
/
MEMORY
{
CCRAM(rxw) : ORIGIN = 0x1000, LENGTH = 64k
SRAM (rxw) : ORIGIN = 0x2000, LENGTH = 128k
FLASH(rx) : ORIGIN = 0x0800, LENGTH = 1024k
}
_stack_end = ORIGIN(CCRAM) + LENGTH(CCRAM);
SECTIONS
{
.isr_vector :
{
. = ALIGN(4);
KEEP(*(.isr_vector))
. = ALIGN(4);
} >FLASH
.text :
{
. = ALIGN(4);
KEEP(*(.interrupt_vector))
*(.text)
*(.text*)
*(.rodata)
*(.rodata*)
. = ALIGN(4);
} > flash
}
Can anyone out them tell me if/how this can be accomplished in D?
Is there some syntax equivalent to __attribute__
((section(".interrupt_vector")))?
Would the following give me a minimal reset_handler?
// compile with: ldc2 -c -nodefaultlib -noruntime
module reset_handler;
extern(C) __gshared void * _Dmodule_ref;
extern(C) void reset_handler()
{ }
I've seen some examples out on the web, but they all either use
C, or are written specifically for an x86/x86_64 platform. So
any help you could provide would be great to help me get started.
Re: Need help making minimal bare metal ARM Cortex-M D program
Please delete this thread. I hit a tab and a space while typing my code, resulting in a premature submit. I will make a separate complete post. Sorry, Mike
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 12:43:01 UTC, Mike wrote: I am very new to D, but I finally got my toolchain compiled and working. I'm using LDC. I failed with GDC and eventually gave up. I know Johannes has some patches yet to trickle down into gdc. And druntime is does not support ARM fully in 2.063, but it would be helpful if you could take some time to let people know what went wrong when you tried things, rather than just giving up. Otherwise, nothing will get fixed.
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 12:45:19 UTC, Mike wrote: Please delete this thread. I hit a tab and a space while typing my code, resulting in a premature submit. I will make a separate complete post. Sorry, Mike This is a mailing list, not a forum. We can't delete things here. :o)
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 12:53:42 UTC, Iain Buclaw wrote: On Sunday, 24 November 2013 at 12:43:01 UTC, Mike wrote: I am very new to D, but I finally got my toolchain compiled and working. I'm using LDC. I failed with GDC and eventually gave up. I know Johannes has some patches yet to trickle down into gdc. And druntime is does not support ARM fully in 2.063, but it would be helpful if you could take some time to let people know what went wrong when you tried things, rather than just giving up. Otherwise, nothing will get fixed. I don't think the problems I encountered with GDC were the fault of GDC. They were my fault. I have more to learn about the Linux platform. It seems the GCC toolchain is highly dependent on the host platform and if things aren't set up just right, you get errors that have nothing to do with the actual problem. Also, when I tried to follow the crosstools instructions here (http://wiki.dlang.org/GDC/Cross_Compiler) I found that the latest crosstools was missing some of the options that are needed. I have been quite successful using the GNU Tools for ARM Embedded Processors here (https://launchpad.net/gcc-arm-embedded), and I hope to merge this with the GDC code and give it another try. I tried it this weekend, but I wasn't even able to get the shell scripts to run without errors. And, I didn't JUST give up. I worked on it all weekend, every weekend, for the past 3 weeks. I'm tired of the platform dependencies, and I'm anxious to just get started. Once I get more familiar with D and have some working code, I'll give GDC another try.
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 13:00:39 UTC, Mike wrote:
Is there some syntax equivalent to __attribute__
((section(".interrupt_vector")))?
There isn't right now, but it would be entirely feasible to
implement this in an LDC-specific extension. Could you open an
issue on our GitHub tracker?
David
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 13:30:10 UTC, David Nadlinger
wrote:
On Sunday, 24 November 2013 at 13:00:39 UTC, Mike wrote:
Is there some syntax equivalent to __attribute__
((section(".interrupt_vector")))?
There isn't right now, but it would be entirely feasible to
implement this in an LDC-specific extension. Could you open an
issue on our GitHub tracker?
David
https://github.com/ldc-developers/ldc/issues/547
Re: Need help making minimal bare metal ARM Cortex-M D program
Am Sun, 24 Nov 2013 14:19:43 +0100 schrieb "Mike" : > On Sunday, 24 November 2013 at 12:53:42 UTC, Iain Buclaw wrote: > > On Sunday, 24 November 2013 at 12:43:01 UTC, Mike wrote: > >> I am very new to D, but I finally got my toolchain compiled > >> and working. I'm using LDC. I failed with GDC and eventually > >> gave up. > >> > > > > I know Johannes has some patches yet to trickle down into gdc. > > And druntime is does not support ARM fully in 2.063, but it > > would be helpful if you could take some time to let people know > > what went wrong when you tried things, rather than just giving > > up. Otherwise, nothing will get fixed. Cortex-M is the 'bare metal' branch of ARM where you usually don't run linux so druntime won't work anyway. There are some compiler fixes in my branch that could be interesting though: https://github.com/jpf91/GDC/commits/arm BTW: I'll start merging back the fixes to gdc master this week. Some fixes have to be merged into phobos upstream though so it might take some time. > > I don't think the problems I encountered with GDC were the fault > of GDC. They were my fault. I have more to learn about the > Linux platform. It seems the GCC toolchain is highly dependent > on the host platform and if things aren't set up just right, you > get errors that have nothing to do with the actual problem. > > Also, when I tried to follow the crosstools instructions here > (http://wiki.dlang.org/GDC/Cross_Compiler) I found that the > latest crosstools was missing some of the options that are needed. You mean options for bare metal builds or options described in the wiki? I'm not sure if crosstool-NG works well with bare metal builds. > > I have been quite successful using the GNU Tools for ARM Embedded > Processors here (https://launchpad.net/gcc-arm-embedded), and I > hope to merge this with the GDC code and give it another try. I > tried it this weekend, but I wasn't even able to get the shell > scripts to run without errors. > > And, I didn't JUST give up. I worked on it all weekend, every > weekend, for the past 3 weeks. I'm tired of the platform > dependencies, and I'm anxious to just get started. Once I get > more familiar with D and have some working code, I'll give GDC > another try. > GCC build scripts can be annoying, especially when cross-compiling. Your best bet is still crosstool-NG though, what exactly are the missing options?
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 14:21:57 UTC, Johannes Pfau wrote: Cortex-M is the 'bare metal' branch of ARM where you usually don't run linux so druntime won't work anyway. There are some compiler fixes in my branch that could be interesting though: https://github.com/jpf91/GDC/commits/arm I'm aware of the druntime will not work, which is why I'm trying to find a way to write and compile code _without_ the druntime or phobos. See my re-post. Also, when I tried to follow the crosstools instructions here (http://wiki.dlang.org/GDC/Cross_Compiler) I found that the latest crosstools was missing some of the options that are needed. You mean options for bare metal builds or options described in the wiki? I'm not sure if crosstool-NG works well with bare metal builds. GCC build scripts can be annoying, especially when cross-compiling. Your best bet is still crosstool-NG though, what exactly are the missing options? A couple of the options don't seem to exist in crosstools. Specifically "Go to C compiler, select Other languages and enter d". Pretty hard to tell the compiler to support D without this option. The GNU Tools for ARM scripts are specifically written for cross-compiling, and even Canadian cross compiling. When I run the build scripts, I get: cat ~/mylongdir/src/gcc/gcc/BASE-VER: No such file or directory. I looked through the shell script, but code like this GCC_VER=`cat $SRCDIR/$GCC/gcc/BASE-VER` GCC_VER_NAME=`echo $GCC_VER | cut -d'.' -f1,2 | sed -e 's/\./_/g'` is a little hard for me to figure out. Again, the problem here is not with GDC; it's that I don't know enough about the Linux tools to know what its trying to do here and what I can do about it. LLVM, clang, and LDC built on the first try after 3 weekends struggling with GCC.
Re: Need help making minimal bare metal ARM Cortex-M D program
A couple of the options don't seem to exist in crosstools. Specifically "Go to C compiler, select Other languages and enter d". Pretty hard to tell the compiler to support D without this option. Have you set 'Try features marked as EXPERIMENTAL'? Are you using a recent version of crosstool-NG? And in case this isn't clear, there isn't a 'D' option to choose from, you need to type 'D' into the field.
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 15:32:04 UTC, jerro wrote: A couple of the options don't seem to exist in crosstools. Specifically "Go to C compiler, select Other languages and enter d". Pretty hard to tell the compiler to support D without this option. Have you set 'Try features marked as EXPERIMENTAL'? Are you using a recent version of crosstool-NG? And in case this isn't clear, there isn't a 'D' option to choose from, you need to type 'D' into the field. Yes, I tried experimental features, obsolete features, and number of other things. I know there isn't a D option to check. I was fully expecting a text field to type the letter 'D' into, but the "Other languages" option does not exist. It appears to have been replaced with a "C++" check option. Give it a try yourself, and you'll see what I mean.
Re: Need help making minimal bare metal ARM Cortex-M D program
It seems languages other than C are disabled for bare metal builds. You could try searching for cc.ini in your crosstool-ng installation and commenting out the line if ! BARE_METAL and endif # ! BARE_METAL
Re: Need help making minimal bare metal ARM Cortex-M D program
On 11/24/2013 06:21 AM, Johannes Pfau wrote: Am Sun, 24 Nov 2013 14:19:43 +0100 schrieb "Mike" : On Sunday, 24 November 2013 at 12:53:42 UTC, Iain Buclaw wrote: On Sunday, 24 November 2013 at 12:43:01 UTC, Mike wrote: I am very new to D, but I finally got my toolchain compiled and working. I'm using LDC. I failed with GDC and eventually gave up. I know Johannes has some patches yet to trickle down into gdc. And druntime is does not support ARM fully in 2.063, but it would be helpful if you could take some time to let people know what went wrong when you tried things, rather than just giving up. Otherwise, nothing will get fixed. Cortex-M is the 'bare metal' branch of ARM where you usually don't run linux so druntime won't work anyway. There are some compiler fixes in my branch that could be interesting though: https://github.com/jpf91/GDC/commits/arm BTW: I'll start merging back the fixes to gdc master this week. Some fixes have to be merged into phobos upstream though so it might take some time. I actually tried to get a gdc build a week or two ago for a cortex-a8 using ng-crosstools-linaro. I managed to get up to compiling druntime, which then was pointing to a commit prior to https://github.com/D-Programming-Language/druntime/commit/541e7ba00d5e75426bb677d7f7548a47a904551f so it failed. Then I figured I'd wait for your fixes.
Re: Need help making minimal bare metal ARM Cortex-M D program
Am Sun, 24 Nov 2013 18:18:22 +0100 schrieb "jerro" : > It seems languages other than C are disabled for bare metal > builds. You could try searching for cc.ini in your crosstool-ng > installation and commenting out the line > > if ! BARE_METAL > > and > > endif # ! BARE_METAL > Good to know. I'll prepare a patch ( I'm currently implementing cross-native builds for crosstool-NG anyway)
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 14:10:54 UTC, Mike wrote:
On Sunday, 24 November 2013 at 13:30:10 UTC, David Nadlinger
wrote:
On Sunday, 24 November 2013 at 13:00:39 UTC, Mike wrote:
Is there some syntax equivalent to __attribute__
((section(".interrupt_vector")))?
There isn't right now, but it would be entirely feasible to
implement this in an LDC-specific extension. Could you open an
issue on our GitHub tracker?
David
https://github.com/ldc-developers/ldc/issues/547
A full working example for gdc and cortex-m4 (stm32f4) is in my
repo at
https://bitbucket.org/timosi/minlibd
I have used startup file from st and have no need to put
interrupt vectors in d code.
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 20:00:56 UTC, Timo Sintonen wrote:
A full working example for gdc and cortex-m4 (stm32f4) is in my
repo at
https://bitbucket.org/timosi/minlibd
I have used startup file from st and have no need to put
interrupt vectors in d code.
Thanks Timo, your minlibd is awesome, and will be my next object
of study.
I already know how do do what you did with assembly and C, but my
goal is not just to get something working, but to learn what can
and can't be done with D.
minlibd uses an assembly startup file and calls into C functions
to set up the clock, flash, etc... That works, and may be the
only (best?) way to go. But I'd like to explore and learn what
limitations exist in the D language and the D tools.
If the LDC folks add a section-attribute-like feature, then I
believe it should be possible to do away with the assembly
startup file, and put the vectors, data section relocation, and
bss initialization all in D, and that appeals to me.
I'm wondering, though, if the vector table's simple name could be
added to the text section. Then the attribute syntax would be
unnecessary. Something like this:
void (* const table_interrupt_vector[])(void) =
{
(void *) &_stack_end,
handler_reset
};
.text :
{
. = ALIGN(4);
*(.text.table_interrupt_vector)
*(.text)
*(.text*)
*(.rodata)
*(.rodata*)
. = ALIGN(4);
} > flash
...but maybe the symbol will be added twice. Unfortunately I
won't be home for a few more days to try it out.
According to LDs docs, execution should default to the start of
text, and if I could just figure out how to make sure
table_interrrupt_vector is there, that would basically be it.
Re: Need help making minimal bare metal ARM Cortex-M D program
I finally succeeded in doing what I set out to do: Write a
simple hello world program for an ARM Cortex-M processor using
ONLY D.
/*
* The D Program (start.d)
*/
module start;
import ldc.llvmasm;
extern(C) __gshared void * _Dmodule_ref;
//Must be stored as second 32-bit word in .text section
immutable void function() ResetHandler = &OnReset;
void SendCommand(int command, void* message)
{
__asm
(
"mov r0, $0;
mov r1, $1;
bkpt #0xAB",
"r,r,~{r0},~{r1}",
command, message
);
}
void OnReset()
{
while(true)
{
// Create semihosting message message
uint[3] message =
[
2,//stderr
cast(uint)"hello\r\n".ptr,//ptr to string
7 //size of string
];
//Send semihosting command
SendCommand(0x05, &message);
}
}
/*
* The Linker Script (link.ld)
*/
MEMORY
{
CCRAM(rxw) : ORIGIN = 0x1000, LENGTH = 64k
SRAM (rxw) : ORIGIN = 0x2000, LENGTH = 128k
FLASH(rx) : ORIGIN = 0x0800, LENGTH = 1024k
}
_stackStart = ORIGIN(CCRAM) + LENGTH(CCRAM);
SECTIONS
{
.text :
{
LONG(_stackStart); /* Initial stack pointer */
KEEP(start.o(.data.rel.ro)) /* Internet vector table */
/* the code */
*(.text)
*(.text*)
/* for "hello\r\n" string constant */
. = ALIGN(4);
*(.rodata)
*(.rodata*)
}>FLASH
/* Need .data, .bss, .ctors and probably more as program becomes
More complex */
}
Tools used:
Operating System: Arch Linux 64-bit
Compiler: LDC (2063b4)
Linker & Binary Utilities & Debugger: GNU Tools for ARM Embedded
Processors (https://launchpad.net/gcc-arm-embedded)
JTAG Emulator: JTAG-lock-pick Tiny 2 w/ OpenOCD 0.7.0
To compile:
ldc2 -march=thumb -mcpu=cortex-m4 -noruntime -nodefaultlib -c
start.d
To link:
arm-none-eabi-ld -T link.ld --gc-sections start.o -o start.elf
To execute:
openocd -f interface/jtag-lock-pick_tiny_2.cfg -f
target/stm32f4x.cfg
arm-none-eabi-gdb start.elf
.. in GDB:
target remote localhost:
monitor arm semihosting enable
monitor reset halt
load
monitor reset init
continue
Output:
hello
hello
...
Code Size: 148 bytes (not bad)
Why I think this is significant:
1. It shows D can write the most low level of programs and does
not require an operating system
2. It shows that the D runtime and D standard library are not
mandatory and do not need to be fully ported to one's platform to
begin programming ARM Cortex-M bare metal hardware in D (although
this is not the first to do so:
https://bitbucket.org/timosi/minlibd)
3. It shows linking to C code and assembly files are optional
4. It shows the tools are capable (although they have not been
well exercised in this example) and more specifically MY
toolchain is working.
5. It's a great start to writing very embedded systems in D, or
more importantly, not C/C++ (good riddance!)
What's next for me:
1. Get a GDC toolchain working, although I'll probably switch to
LDC when LDC matures.
2. Learn more about D.
3. Study minlibd and the d runtime and program the bare
essentials to make D a productive language for the ARM Cortex-M.
4. Help the D community help me, by testing the toolchains for
the ARM Cortex-M platform and file bug reports.
Thanks to those who commented on my previous posts. I'm quite
excited about this language.
Re: Need help making minimal bare metal ARM Cortex-M D program
On Nov 30, 2013 11:40 AM, "Mike" wrote:
>
> I finally succeeded in doing what I set out to do: Write a simple hello
world program for an ARM Cortex-M processor using ONLY D.
>
> /*
> * The D Program (start.d)
> */
> module start;
>
> import ldc.llvmasm;
>
>
> extern(C) __gshared void * _Dmodule_ref;
>
> //Must be stored as second 32-bit word in .text section
> immutable void function() ResetHandler = &OnReset;
>
> void SendCommand(int command, void* message)
> {
> __asm
> (
> "mov r0, $0;
> mov r1, $1;
> bkpt #0xAB",
> "r,r,~{r0},~{r1}",
> command, message
>);
> }
>
> void OnReset()
> {
> while(true)
> {
> // Create semihosting message message
> uint[3] message =
> [
> 2,//stderr
> cast(uint)"hello\r\n".ptr,//ptr to string
> 7 //size of string
> ];
>
> //Send semihosting command
> SendCommand(0x05, &message);
> }
> }
>
> /*
> * The Linker Script (link.ld)
> */
>
> MEMORY
> {
> CCRAM(rxw) : ORIGIN = 0x1000, LENGTH = 64k
> SRAM (rxw) : ORIGIN = 0x2000, LENGTH = 128k
> FLASH(rx) : ORIGIN = 0x0800, LENGTH = 1024k
> }
>
> _stackStart = ORIGIN(CCRAM) + LENGTH(CCRAM);
>
> SECTIONS
> {
> .text :
> {
> LONG(_stackStart); /* Initial stack pointer */
> KEEP(start.o(.data.rel.ro)) /* Internet vector table */
>
> /* the code */
> *(.text)
> *(.text*)
>
> /* for "hello\r\n" string constant */
> . = ALIGN(4);
> *(.rodata)
> *(.rodata*)
> }>FLASH
>
> /* Need .data, .bss, .ctors and probably more as program becomes
> More complex */
> }
>
> Tools used:
> Operating System: Arch Linux 64-bit
> Compiler: LDC (2063b4)
> Linker & Binary Utilities & Debugger: GNU Tools for ARM Embedded
Processors (https://launchpad.net/gcc-arm-embedded)
> JTAG Emulator: JTAG-lock-pick Tiny 2 w/ OpenOCD 0.7.0
>
> To compile:
> ldc2 -march=thumb -mcpu=cortex-m4 -noruntime -nodefaultlib -c start.d
>
> To link:
> arm-none-eabi-ld -T link.ld --gc-sections start.o -o start.elf
>
> To execute:
> openocd -f interface/jtag-lock-pick_tiny_2.cfg -f target/stm32f4x.cfg
> arm-none-eabi-gdb start.elf
>
> .. in GDB:
> target remote localhost:
> monitor arm semihosting enable
> monitor reset halt
> load
> monitor reset init
> continue
>
> Output:
> hello
> hello
> ...
>
> Code Size: 148 bytes (not bad)
>
> Why I think this is significant:
> 1. It shows D can write the most low level of programs and does not
require an operating system
> 2. It shows that the D runtime and D standard library are not mandatory
and do not need to be fully ported to one's platform to begin programming
ARM Cortex-M bare metal hardware in D (although this is not the first to do
so: https://bitbucket.org/timosi/minlibd)
> 3. It shows linking to C code and assembly files are optional
> 4. It shows the tools are capable (although they have not been well
exercised in this example) and more specifically MY toolchain is working.
> 5. It's a great start to writing very embedded systems in D, or more
importantly, not C/C++ (good riddance!)
>
> What's next for me:
> 1. Get a GDC toolchain working, although I'll probably switch to LDC when
LDC matures.
> 2. Learn more about D.
> 3. Study minlibd and the d runtime and program the bare essentials to
make D a productive language for the ARM Cortex-M.
> 4. Help the D community help me, by testing the toolchains for the ARM
Cortex-M platform and file bug reports.
>
> Thanks to those who commented on my previous posts. I'm quite excited
about this language.
In before the "that's not D! That's some D, a bit of some extended inline
assembly, and a custom linker script."
Congrats though. :)
Regards
--
Iain Buclaw
*(p < e ? p++ : p) = (c & 0x0f) + '0';
Re: Need help making minimal bare metal ARM Cortex-M D program
On Saturday, 30 November 2013 at 11:37:25 UTC, Mike wrote: What's next for me: 1. Get a GDC toolchain working, although I'll probably switch to LDC when LDC matures. 2. Learn more about D. 3. Study minlibd and the d runtime and program the bare essentials to make D a productive language for the ARM Cortex-M. 4. Help the D community help me, by testing the toolchains for the ARM Cortex-M platform and file bug reports. Thanks to those who commented on my previous posts. I'm quite excited about this language. Congratulations from me too. I just put my old gdc cross compiler instructions in the wiki: https://bitbucket.org/timosi/minlibd/wiki/gdc_cross_compiler If you are not going to have your own repository, feel free to send pull requests to me.
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 24 November 2013 at 18:38:19 UTC, Johannes Pfau wrote: Am Sun, 24 Nov 2013 18:18:22 +0100 schrieb "jerro" : It seems languages other than C are disabled for bare metal builds. You could try searching for cc.ini in your crosstool-ng installation and commenting out the line if ! BARE_METAL and endif # ! BARE_METAL Good to know. I'll prepare a patch ( I'm currently implementing cross-native builds for crosstool-NG anyway) Just tried again with crosstools-ng 1.19.0. I commented out the appropriate lines in my cc.ini file, but the build failed with... " The following requested languages could not be built: d " ... in the build.log file. Also, the instructions here (http://gdcproject.org/wiki/Cross%20Compiler/crosstool-NG) say: "If druntime & phobos do not yet compile for your target you can disable them: Start ct-ng menuconfig, go to "C compiler" and add "--disable-libphobos" to "Core gcc extra config" and "gcc extra config". " While the "Core gcc extra config" option exists, "gcc extra config" does not. The quest continues...
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 1 December 2013 at 05:23:19 UTC, Mike wrote: On Sunday, 24 November 2013 at 18:38:19 UTC, Johannes Pfau wrote: Am Sun, 24 Nov 2013 18:18:22 +0100 schrieb "jerro" : It seems languages other than C are disabled for bare metal builds. You could try searching for cc.ini in your crosstool-ng installation and commenting out the line if ! BARE_METAL and endif # ! BARE_METAL Good to know. I'll prepare a patch ( I'm currently implementing cross-native builds for crosstool-NG anyway) Just tried again with crosstools-ng 1.19.0. I commented out the appropriate lines in my cc.ini file, but the build failed with... " The following requested languages could not be built: d " ... in the build.log file. Also, the instructions here (http://gdcproject.org/wiki/Cross%20Compiler/crosstool-NG) say: "If druntime & phobos do not yet compile for your target you can disable them: Start ct-ng menuconfig, go to "C compiler" and add "--disable-libphobos" to "Core gcc extra config" and "gcc extra config". " While the "Core gcc extra config" option exists, "gcc extra config" does not. The quest continues... Thinking about this a little more, I figured the only way GCC would not no about D is if the GCC sources were not patched...and sure enough, I had crosstools pointing to the wrong folder. My mistake.
Re: Need help making minimal bare metal ARM Cortex-M D program
On Sunday, 1 December 2013 at 06:00:08 UTC, Mike wrote: On Sunday, 1 December 2013 at 05:23:19 UTC, Mike wrote: On Sunday, 24 November 2013 at 18:38:19 UTC, Johannes Pfau wrote: Am Sun, 24 Nov 2013 18:18:22 +0100 schrieb "jerro" : It seems languages other than C are disabled for bare metal builds. You could try searching for cc.ini in your crosstool-ng installation and commenting out the line if ! BARE_METAL and endif # ! BARE_METAL Good to know. I'll prepare a patch ( I'm currently implementing cross-native builds for crosstool-NG anyway) Just tried again with crosstools-ng 1.19.0. I commented out the appropriate lines in my cc.ini file, but the build failed with... " The following requested languages could not be built: d " ... in the build.log file. Also, the instructions here (http://gdcproject.org/wiki/Cross%20Compiler/crosstool-NG) say: "If druntime & phobos do not yet compile for your target you can disable them: Start ct-ng menuconfig, go to "C compiler" and add "--disable-libphobos" to "Core gcc extra config" and "gcc extra config". " While the "Core gcc extra config" option exists, "gcc extra config" does not. The quest continues... Thinking about this a little more, I figured the only way GCC would not no about D is if the GCC sources were not patched...and sure enough, I had crosstools pointing to the wrong folder. My mistake. I was finally able to build a GDC cross compiler using GCC 4.8.2, the GDC 4.8 branch, and crosstools-ng 1.19.0. However, I found the following errors in the instructions located here (http://gdcproject.org/wiki/Cross%20Compiler/crosstool-NG) 1. The "Other Languages" option does not appear for a bare metal build. You must modify the cc.ini file to make it available per jerro's insructions above. Thanks jerro 2. The "Core gcc extra config" option exists, but the "gcc extra config" does not. It doesn't appear to be necessary, but I have yet to test this toolchain. 3. The "Paths and misc options, Local tarballs directory" option does not seem to be correct. For me, I had to go to "C Compiler" -> "gcc version" and choose "Custom gcc" and point crosstools-ng to the folder containing the merged GCC/GDC source code. I hope this information is useful to someone.
Re: Need help making minimal bare metal ARM Cortex-M D program
Am Sun, 01 Dec 2013 09:58:01 +0100 schrieb "Mike" : > I was finally able to build a GDC cross compiler using GCC 4.8.2, > the GDC 4.8 branch, and crosstools-ng 1.19.0. However, I found > the following errors in the instructions located here > (http://gdcproject.org/wiki/Cross%20Compiler/crosstool-NG) BTW: The new location is http://wiki.dlang.org/GDC/Cross_Compiler/crosstool-NG > > 1. The "Other Languages" option does not appear for a bare metal > build. You must modify the cc.ini file to make it available per > jerro's insructions above. Thanks jerro That's a bug in crosstool-NG, I'll try to get it fixed. > 2. The "Core gcc extra config" option exists, but the "gcc extra > config" does not. It doesn't appear to be necessary, but I have > yet to test this toolchain. It's indeed not necessary for bare-metal builds. That's probably because the instructions weren't tested on bare metal builds. > 3. The "Paths and misc options, Local tarballs directory" option > does not seem to be correct. For me, I had to go to "C Compiler" > -> "gcc version" and choose "Custom gcc" and point crosstools-ng > to the folder containing the merged GCC/GDC source code. Back when I wrote those instructions the "Custom gcc" option didn't exist. Custom gcc will work just fine, but there's a subtle difference: crosstool-NG may automatically apply some patches for certain GCC versions. It won't apply those patches when using the "Custom gcc" option. However, the method described in the wiki only works if the patched sources are packaged into a new tarball with exactly the same name as the original tarball (gcc-4.7.1.tar.bz2/gcc-4.8.2.tar.bz2/...). Then crosstool-NG may have cached the extracted sources and those have to be deleted. And nowadays crosstool-NG might actually prefer .tar.xz files, so if you have an unpatched tar.xz file in the source directory it file has to be deleted. I'll probably add some text about these issues to the documentation. > I hope this information is useful to someone. It definitely is. Thanks for the feedback!
Re: Need help making minimal bare metal ARM Cortex-M D program
Am Sun, 24 Nov 2013 09:35:57 -0800 schrieb Ellery Newcomer : > On 11/24/2013 06:21 AM, Johannes Pfau wrote: > > Am Sun, 24 Nov 2013 14:19:43 +0100 > > schrieb "Mike" : > > > >> On Sunday, 24 November 2013 at 12:53:42 UTC, Iain Buclaw wrote: > >>> On Sunday, 24 November 2013 at 12:43:01 UTC, Mike wrote: > I am very new to D, but I finally got my toolchain compiled > and working. I'm using LDC. I failed with GDC and eventually > gave up. > > >>> > >>> I know Johannes has some patches yet to trickle down into gdc. > >>> And druntime is does not support ARM fully in 2.063, but it > >>> would be helpful if you could take some time to let people know > >>> what went wrong when you tried things, rather than just giving > >>> up. Otherwise, nothing will get fixed. > > > > Cortex-M is the 'bare metal' branch of ARM where you usually don't > > run linux so druntime won't work anyway. There are some compiler > > fixes in my branch that could be interesting though: > > https://github.com/jpf91/GDC/commits/arm > > > > BTW: I'll start merging back the fixes to gdc master this week. Some > > fixes have to be merged into phobos upstream though so it might take > > some time. > > > > I actually tried to get a gdc build a week or two ago for a cortex-a8 > using ng-crosstools-linaro. I managed to get up to compiling > druntime, which then was pointing to a commit prior to > > https://github.com/D-Programming-Language/druntime/commit/541e7ba00d5e75426bb677d7f7548a47a904551f > > so it failed. Then I figured I'd wait for your fixes. > > Hi, as Iain started merging 2.064 the ARM branch merge will probably be delayed until the 2.064 merge is complete. I updated my branch to be on the last 2.063 revision which still compiles with gcc-4.8: https://github.com/jpf91/GDC/commits/arm It'd be awesome if you could help with some alpha-testing. Unfortunately cross-compilers are completely untested and I'll first have to make the test suite run for cross-compilers. But if you could build a native compiler, run the test suite and unit tests and report the results, that'd be awesome. See http://wiki.dlang.org/GDC/Test_Suite and http://wiki.dlang.org/GDC/Test_Suite#Running_unit_tests for more information.
Re: Need help making minimal bare metal ARM Cortex-M D program
On Saturday, 30 November 2013 at 11:37:25 UTC, Mike wrote: I finally succeeded in doing what I set out to do: Write a simple hello world program for an ARM Cortex-M processor using ONLY D. That's some nice progress indeed! Would you mind transferring your excellent description of the process to the D wiki and link it from http://wiki.dlang.org/LDC? This way, it would be easier to find in a few months than an old forum post. David
Re: Need help making minimal bare metal ARM Cortex-M D program
Would you mind transferring your excellent description of the process to the D wiki and link it from http://wiki.dlang.org/LDC? This way, it would be easier to find in a few months than an old forum post. David http://wiki.dlang.org/Extremely_minimal_semihosted_%22Hello_World%22
Re: Need help making minimal bare metal ARM Cortex-M D program
On Monday, 2 December 2013 at 11:09:15 UTC, Mike wrote: http://wiki.dlang.org/Extremely_minimal_semihosted_%22Hello_World%22 Thanks a lot, Mike! I linked the page from the LDC platform overview. David
