Nevertheless, over several days and with the help of the google beaglebone forum I was able to get things working.
BEAGLEBONE BLACK INSTALLING ARDUINO SIMULATOR PC
I suspect I had a lot of trouble because I was usuing a completely clean ubuntu installation on the PC and as a result some things which other people were fortuneate to avoid, I stepped directly in to. I also ran afoul of the -hf problem, and also changing the compiler, etc., solved that issue, it cause grief when doing the debugging. There are floating-point options in gcc that you have to set when using hardware floating point numbers - you should add ” -mfloat-abi=hard” to your compiler options. – I’m using “Linux omap 3.2.18-psp14 armv71″ in this video that I built myself which has defaulted to soft floating point numbers. This seems to have worked for him on the ubuntu 12.04 armhf build. – Graemefisheratwork let me know that he has found that when using the ubuntu armhf distros, applications should be cross-compiled using arm-linux-gnueabihf- and not arm-linux-gnueabi. If it *does* then one likely problem is if that you are using an ARM Linux platform that uses “hard floats” and that you have compiled using my setup which uses “soft floats”.
If it does *not* then there is a problem with your compiler setup and you need to watch the steps again. In Eclipse your executable should display in your source directory as “HelloWorld – ” in the project explorer window. This could happen if for example you are running a 64-bit executable on 32-bit machine, or an x86 executable on an ARM target. The hypothetical script should start off with #!/path/to/interpreter and bash cannot find the (non-existent) interpreter so it returns “file not found”. If bash reports “file not found” when executing an executable file that exists, the reason is that it doesn’t recognise it as a binary file, and attempts to treat it as a script. One common problem that arises with this setup: Video 1 – C and C++ programming on the Beaglebone platform
0 kommentar(er)
