Quote:
Originally Posted by Turing'sEgo
The most common method of compiling / deploying is do cross-compiling. This is the safest way to ensure you don't accidentally break your stable (yet fragile) jetson configuration.
Look into gcc-arm-linux-gnueabi
|
So, you'd recommend rolling my own cross-compilation scripts (using existing toolchains, of course)? Would something like Eclipse be willing to do remote debugging on a binary cross-compiled for ARM?
Quote:
Originally Posted by Turing'sEgo
Are you writing your own routines in cuda-c? (If so, that is pretty metal)
|
Yep, I've been using OpenCV data structures and most of their functions, but occasionally writing my own CUDA C code (which I learned through trial and error) when I'm unhappy with what OpenCV has to offer. Unfortunately, I don't think I've done memory management right -- I keep getting unfortunately low frame rates when using my own code. And definitely no Java here! Although, we do program our main robot program in Java.