I need to know if ROS can work with all kits? or needs specific requirements?
I mean, can I buy any kit and control it by ROS?
If yes, is there any needed chip, ports, or connectors?
Thanks in advance.
You should use http://answers.ros.org/questions/ for questions regarding ROS, but yes, it is in general robot-agnostic.
No, not all robots. Only robots with X86 or ARM hardware that can run Ubuntu Linux.
There are also experimental versions of ROS for OS X, Gentoo Linux, Arch Linux, and Android (NDK)
When choosing your hardware platform, consider ROS support for various sensors and actuators, as well as the library of packages that add other capabilities.
Here's a very long list of robots that use ROS.
Related
I like Linux but I have spare capacity on an enterprise class SPARC Solaris platform. I'm just wondering if anyone has tried running Julia there before as it doesn't seem to be a supported OS.
No Julia does not run SPARC Solaris. Supported platforms are x86 (Linux+windows+mac+FreeBSD), ARM and Power8-LE. A SPARC port would not be too difficult, but would need to be done by someone who cares about that platform, and has access to relevant hardware. Unfortunately, that does not describe most of the current developers and contributors.
Not yet but future interest might also come from wanting to use Julia on FPGAs, in combination with open softcores such as Leon -- a SPARC architecture already supported by LLVM.
I have two GPUs installed on my machine. I am working with library which uses OpenCL acceleration that only support one GPU and it is not configurable. I can not tell it which one I want. It seems that this library for some reason chose one of my GPUs that I do not want.
How can I delete/stop/deactivate this GPU from being supported as an OpenCL device?
I want to do this so I get only one supported GPU and the library will be forced to use it.
Note: Any option that contains change or edit the library is available for me.
P.S. I am on Windows 10 with Intel processor and Intel GPU + NVidia GPU
On Windows the OpenCL ICD system uses Registry entries to find all of the installed OpenCL platforms.
Solution: Using RegEdit you can backup and then remove the entry for the GPU you do not want to use. The Registry location is HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors.
Reference: https://www.khronos.org/registry/cl/extensions/khr/cl_khr_icd.txt
Is it possible to use the MCU on the Intel Edison without having the standard Yocto Linux installed?
At the moment I have downloaded the specific Eclipse MCU SDK and have been using that to program the MCU on the Edison. I have the newest version (from Intel's website) of Yocto on the Edison as well.
If I switch to e.g. Emutex's Ubilinux will I still be able to use the MCU in any way? With or without the standard Eclipse MCU SDK?
The main reason I want to switch to Ubilinux is to have an easier time using ROS (Robot Operating System), but this is not strictly relevant to the question.
The Quark core runs its own Zephyr based OS, but I do expect some sort of support to be required on the Linux side too for intercommunication between CPUs. As dwelch said, the required drivers might be there for Ubilinux too.
If you are specific about ROS someone is working on adding it to Yocto. A quick google search also returned an unfinished project of ROS on Edison.
In the ARM world vendors supply their own BSPs to initialize board peripherals. Intel boards that you buy on the market all seems to come with some version of BIOS. Does BIOS do thing that BSPs cannot do? What if some hobbyist or engineer wants to do development using Intel processors but do not want anything to do with the BIOS? Why restrict programming with a layer of firmware that programmers have no source access to?
Typically the BIOS is no layer of firmware but rather the firmware to boot the system. After booting control is provided by the OS such as Windows or Linux.
This is not really my area, but ....
The initials BSP are heavily overloaded. It appears you mean board support package and not Boot-strap-processor or one of the other computer related terms that use those initials.
It is my understanding that BSP's (board support packages) are primarily used for embedded systems and indeed, when I did a web search on 'Intel bsp', most of the hits were discussing Intel Galileo and Intel Edison boards, which are targeted toward IoT (internet of things) projects and other embedded projects. But I also found BSP's, for sale and for free, in executable and in source form, for a wide variety of Intel boards. If you are working with Linux, you might want to check out https://www.yoctoproject.org/ .
I don't know if there are any vendors packaging a BSP with an Intel board, but it is certainly possible.
The only open source boot firmware for Intel processors that I know of is coreboot. It doesn't support every board. If you are building your own board, then you could customize it to work with your design. A typical modern BIOS has lots of bloat such as ACPI and UEFI that you may or may not want.
I'm in the research phase of my next computer build. I have the idea in my head of running a hypervisor as the base of the system, but i would want to be able to take a shot at programming opencl with one of the OS's installed on the hypervisor...and maybe some gaming. Would i have enough access to the GPU to be able to achieve this effectively, or am i better off installing an OS that i will do development(and gaming) from and then just virtualize any systems on top of that?
what are your recommendations for a hypervisor, vmware, microsoft or other?
sidenote: Recently graduated with a BS in CS, the massive parallel processing seems like a good idea of something to learn, won't be doing any 'real'/major development work. also, i'm aware that CUDA is more mature in it's development, but i'm sticking with opencl for a few reasons, so please don't try to persuade me.
thanks for your input!
dave k.
whats your focus? Virtualisation or OpenCL?
Hak5 did a nice walkthrough of debian based virtualisation environment ProxMox, but I don't know whether it allows virtual hosts hardware access or OpenCL virtualisation.