- This topic has 6 replies, 2 voices, and was last updated 7 years, 5 months ago by
.
-
Posts
-
Hello !
I’m trying to cross-compile some projects for a CortexA53 aarch64 target ( namely, a Samsung S5P6818 octo-core board, the NanoPi Fire3, running a lightweight ubuntu ditrib ).
So I downloaded ARM’s official GNU toolchain, version 7.2.1 20170904, hoping to user the -Aarch64 option for armv8 cores.Here is the *gdb executable : (attachment 1)
But when I specify its arm-none-eabi-gdb.exe location, the wizard brings me back to a no-toolchain-selected situation : (attachment 2)
Even weirder, the toolchain appears in VisualGDB’s installed packages list : (attachment 3)
What am I doing wrong here ?
Hi,
The normal ARM cross-toolchain only works for barebone devices (i.e. without Linux). If you would like to target Linux, you would need a special toolchain that is built to match your Linux distro and configuration. Please check your device vendor’s site whether they provide such a toolchain. If not, we could build one for you as a part of our custom toolchain building service. Please contact our sales if you would like to get a quote.
I just hate FriendlyARM… disappointed in 2008, disappointed in 2018 again… 10 years and still not an ounce of professionalism.
It’s a if they get SOCs from a tipped-over truck and slap them onto PCBs.Hi,
Sorry, getting a toolchain right is often tricky, that’s why we provide it as a paid service. The good news is that 64-bit ARM boards are becoming more mainstream (Raspberry Pi 3 is actually 64-bit, although the Raspbian distro is 32-bit), so we may eventually add a free 64-bit cross-toolchain if one of the boards becomes really popular.
Yes, the aarch64 is spreading ! =)
And both BCM2837 and S5P6818 share Cortex A53 cores, so it shouldn’t be long before I get a quick fix to my predicament.Right now, I’ve opted to remote-compile my code directly on the target. Its eight cores might be able to do the job quickly. =P
- You must be logged in to reply to this topic.