Differences

This shows you the differences between two versions of the page.

--- zephyr [2016/06/22 19:35] – admin
+++ zephyr [2016/10/13 10:33] (current) – admin
@@ Line 1: / Line 1: @@
+https://www.zephyrproject.org/sites/local-zephyr/files/zephyr_project_technical_overview.pdf
+https://wiki.zephyrproject.org/view/Development_Model
+https://wiki.zephyrproject.org/view/Collaboration_Guidelines
+====== Boards ======
+https://wiki.zephyrproject.org/view/Arduino_101
 ====== CoAP ======
@@ Line 679: / Line 689: @@
         application developer could himself maintain if they want to keep using
         the old API names once we stop supporting them ?
+====== ARC ======
+Note that for ARC the gcc mainline is not fully working as not all required patches are in yet. Current recommendation for gcc is to use the one from Synopsys github.
+Binutils from mainline are ok to use.
+You can check the latest gcc for ARC mainline developments, provided as is, here:
+https://github.com/foss-for-synopsys-dwc-arc-processors/gcc/tree/dev
+The stable port and officially supported version currently is 4.8.5, which can be found here:
+https://github.com/foss-for-synopsys-dwc-arc-processors/gcc/tree/arc-4.8-dev
+How to build and other info:
+https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain
+If you have issues, let me know, or even better: open an issue using the github issues mechanism.
+Regards,
+Ruud.
+-----Original Message-----
+From: Lukasz Janyst [mailto:xyz@jany.st]
+Sent: Wednesday, May 25, 2016 1:27 PM
+To: devel@lists.zephyrproject.org
+Subject: [devel] building zephyr with mainline toolchain for Arduino 101
+Hi there,
+I have recently started playing with Zephyr and decided to see whether I can build it for Arduino 101 with the mainline toolchain. I compiled the following for both i586-none-elfiamcu and arc-none-elf targets:
+* binutils master branch, 2.26.51 has messed up commandline parsing for arc (fixed in master)
+* gcc 6.1
+* newlib 2.4.0
+* gdb 7.11 (mainline for Intel, foss-for-synopsys-dwc-arc-processors for
+arc)
+Things work well for Intel except for one minor glitch in newlib's 'strtold()'. However, for arc, I have encountered some issues with zephyr itself:
+) In various assembler files you use the 'j_s.nd [blink]' instruction.
+I could not find anywhere what it is supposed to do and mainline gas does not know what to do about it. When you look at the actual opcodes emitted by poky gas, it seems that what you meant is 'j_s [blink]':
+https://jany.st/tools/zerobin/?0720d0b22d454d12#0isJEY6pqj4aMNiHL5tUOn627K/c746sR24Smx9qKL8=
+Things work if I change that. I can send out a patch if there is an interest.
+) gcc 6.1 for arc seems to emit code containing traps calling
+'abort()':
+https://jany.st/tools/zerobin/?4b679a767b37a3a5#JBh80TwI4M3jahfRBLvWQvjVhRIDFnnB4AVEewXUTNY=
+Zephyr does not provide the symbol, so the compilation fails. It seems that Linux provides 'abort()' for certain architectures:
+http://lxr.free-electrons.com/source/arch/arm/kernel/traps.c#L756
+I don't know enough about arc to provide a sensible implementation so suggestions would be appreciated. A dummy symbol makes the compilation pass.