https://forum.dlang.org/post/bwqfbfsdkvmdztmccfhx@forum.dlang.org

On Thursday, 22 October 2020 at 08:04:48 UTC, Denis Feklushkin wrote:
> Hi!
>
> Looks like druntime fork dedicated "to support almost any system" (https://github.com/denizzzka/druntime) works well with ARM Cortex-M3 backend! Almost all unittests is passed on QEMU emulated hardware (except threads and fiberes, see more: https://github.com/denizzzka/d_c_arm_test/issues/5)
>
> So, it will be cool if some real project will have its firmware implemented on D!
> ARM Cortex or MCU based on RISC-V is preferred, but another architectures is also appropriate.
>
> Any ideas?

I will experiment with this soon (about 3-4 months). Anything I should be aware of before trying it out? Will probably be using a stm32, but not 100% sure yet.

On Saturday, 8 May 2021 at 12:08:06 UTC, Imperatorn wrote:
> https://forum.dlang.org/post/bwqfbfsdkvmdztmccfhx@forum.dlang.org
>
> On Thursday, 22 October 2020 at 08:04:48 UTC, Denis Feklushkin wrote:
>> Hi!
>>
>> Looks like druntime fork dedicated "to support almost any system" (https://github.com/denizzzka/druntime) works well with ARM Cortex-M3 backend! Almost all unittests is passed on QEMU emulated hardware (except threads and fiberes, see more: https://github.com/denizzzka/d_c_arm_test/issues/5)
>>
>> So, it will be cool if some real project will have its firmware implemented on D!
>> ARM Cortex or MCU based on RISC-V is preferred, but another architectures is also appropriate.
>>
>> Any ideas?
>
> I will experiment with this soon (about 3-4 months). Anything I should be aware of before trying it out? Will probably be using a stm32, but not 100% sure yet.

* Needs a lot of flash (I recommend minimum 512kB)
* Not provides safety rule for embedded systems about disabling of dynamic memory allocations.
* Phobos support isn't ready for now

All latest info placed in issues section https://github.com/denizzzka/d_c_arm_test/issues

On Saturday, 8 May 2021 at 12:08:06 UTC, Imperatorn wrote:

>> So, it will be cool if some real project will have its firmware implemented on D!
>> ARM Cortex or MCU based on RISC-V is preferred, but another architectures is also appropriate.
>>
>> Any ideas?
>
> I will experiment with this soon (about 3-4 months). Anything I should be aware of before trying it out? Will probably be using a stm32, but not 100% sure yet.

Also, try not to just clone and change this project, but use it as a dependency for your own Meson-based project. You may need to make some changes for this, but the result would be excellent!