<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 20, 2015, at 12:22 AM, Dmitri Gribenko via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Regarding the microcontroller that you referenced, I think it would be an overly ambitious goal to try to make everything work with 256 Kb of flash and 32 Kb of RAM. I would recommend to start with a more powerful bare-metal target</div></div></blockquote><br class=""></div><div>It would be great to get Swift up and running on a beefier ARM system like a BeagleBoard or Raspberry Pi 2, or the upcoming C.H.I.P. (The other RPi models could be problematic because their CPUs are only ARM6.)</div><div><br class=""></div><div>Writing for the bare metal probably isn’t the most effective way to go unless your primary goal is to learn — before you can get Swift running you’d need to implement a memory allocator, enough concurrency/threading to be able to handle I/O interrupts, and drivers for whatever I/O devices you need like USB or WiFi. If I were doing a project like this I’d start with a microkernel like FreeRTOS or the guts of MINIX3, which provide the above and a bit more.</div><div><br class=""></div><div>—Jens</div></body></html>