Posts made by jcai

@Alex-Kushleyev Yup, editing kona-perf_defconfig looks to have worked, thanks!

@Alex-Kushleyev I think this is just an issue with Windows drivers. I ended up switching over to OSX to use adb and fastboot, no issues there. I'm just using a USB drive to get the .img file from the VM to the Mac. Boot tests look good.

One more thing, I'm looking at the kernel build guide and there's a section that says I can enable in tree drivers by editing:

apps_proc/poky/meta-voxl2-bsp/recipes-kernel/linux-msm/files/m005x.cfg

I don't have this file in my system. the closest I found is ../linux-msm/files/configs/m0054. In this directory, there's kona_defconfig and kona-perf_defconfig. What's the difference between these two files? Are these the correct files to be editing to enable, for example, CONFIG_MACVLAN?

@Alex-Kushleyev I've managed to get the build working, thanks! I think the problems started because my initial docker image was built with sudo. Removing the workspace folder and starting from scratch got everything set up as user.

I'm now attempting to test the build using:

adb reboot bootloader
fastboot boot your_new_kernel.img

Are there specific drivers I need to download? Once I put the voxl into bootloader, VirtualBox can't detect the device anymore. The same is true on my Windows host. As a result, running fastboot boot new_kernel.img gives me a constant <waiting for any device> message. As reference, here's my device manager during normal and bootloader modes. The "Android" device also comes and goes. It usually exists for a couple seconds before disappearing.

On the host:

jcai@jcai-VirtualBox:~/qrb5165-kernel-build-docker/workspace/lu.um.1.2.1/apps_proc$ ls -lah
total 48K
drwxr-xr-x  8 root root 4.0K Oct  9 15:42 .
drwxr-xr-x  3 root root 4.0K Oct  8 13:03 ..
drwxrwxr-x  2 1001 1001  20K Aug 23  2022 deb_premirror_packages
drwxr-xr-x  5 root root 4.0K Oct  8 17:27 disregard
drwxr-xr-x  2 root root 4.0K Oct  9 09:49 downloads
drwxr-xr-x 34 root root 4.0K Oct  9 15:25 poky
drwxr-xr-x  7 root root 4.0K Oct  9 15:23 .repo
lrwxrwxrwx  1 root root   27 Oct  8 17:33 setup-environment -> poky/qti-conf/set_bb_env.sh
drwxr-xr-x 25 root root 4.0K Oct  8 17:31 src

In Docker:

user@8de0065c2813:~/build_mount/lu.um.1.2.1/apps_proc$ ls -lah
total 48K
drwxr-xr-x  8 root root 4.0K Oct  9 19:42 .
drwxr-xr-x  3 root root 4.0K Oct  8 17:03 ..
drwxrwxr-x  2 1001 1001  20K Aug 23  2022 deb_premirror_packages
drwxr-xr-x  5 root root 4.0K Oct  8 21:27 disregard
drwxr-xr-x  2 root root 4.0K Oct  9 13:49 downloads
drwxr-xr-x 34 root root 4.0K Oct  9 19:25 poky
drwxr-xr-x  7 root root 4.0K Oct  9 19:23 .repo
lrwxrwxrwx  1 root root   27 Oct  8 21:33 setup-environment -> poky/qti-conf/set_bb_env.sh
drwxr-xr-x 25 root root 4.0K Oct  8 21:31 src

Yeah, ownership looks like an issue here

@Alex-Kushleyev I was only able to follow the guide exactly until I got into the container. From there , all the scripts inside were run with sudo. Otherwise, I would get permission issues like below.

@Alex-Kushleyev Yeah, no changes

@Alex-Kushleyev I'm having some issues with building the kernel. I'm running the latest Ubuntu in VirtualBox (on Windows) for this. In the container, the sync and patch scripts run without issue but when building as root, I get the following error:

If I run build without sudo, I get access permission issues:

@Zachary-Lowell-0 I'm on Docker 24.0.2

So I was reading through the kernel build guide, and I saw an example that enabled smsc95xx by modifying the m005x.cfg file (CONFIG_USB_NET_SMSC95XX=y).

From what I can tell by reading through the IPVLAN docs, it's much the same steps to enable it (CONFIG_IPVLAN=y or CONFIG_IPVLAN=m). So it looks like it should be safe? Is this still something you would advise against? Also, would there be any issues with running all of the build stuff on MacOS?

Hello,

I'm trying to set up a Docker network with an ipvlan driver. The network starts without issue, but when creating the container, I'm getting the following error:

Error response from daemon: failed to create the ipvlan port: operation not supported

Unfortunately, I haven't been able to find much about this error, so currently the only lead I have has to do with the Linux kernel version. The Docker docs says:

Kernel requirements:
IPvlan Linux kernel v4.2+ (support for earlier kernels exists but is buggy). To check your current kernel version, use uname -r

I see that my current version is 4.19.125. Is there a way to upgrade? I'm fairly new to Linux so reading through the VOXL2 Kernel Build Guide hasn't been very helpful to me.

Thanks!

Update: running

voxl2:/$ ip link add link eth0 name ipvlan-test type ipvlan
RTNETLINK answers: Operation not supported

It looks like I might be missing a module? Not sure there

@Eric-Katzfey There might be something about networking that I'm not understanding here.
voxl-streamer by default streams RTSP to <IP>:8900, so for me I can see the stream by going to rtsp://192.168.1.222:8900/live
Just changing the port to 9976 doesn't equate to udp @ 127.0.0.1:9976, does it?

@Moderator Am I able to specify the IP and port that the stream from voxl-streamer is sent to? Since the third-party software encodes and writes to UDP:127.0.0.1:9976, I'm wondering if it's possible to direct voxl-streamer straight there instead

Hello, I'm somewhat new to video streaming, networking, and Linux development. I'm working on a VOXL2 running voxl-suite 1.3.4~beta3. In addition, I have an M0173 breakout connected with two M0166 tracking and two M0161 Hires cameras. My current project will only use one of the Hires cameras. I've been able to successfully stream the Hires cam over RTSP using voxl-streamer as a sanity check.

However, my project involves third-party (whom I'm able to contact) software onboard that uses ffmpeg to encode and compress video from /dev/video0 and write it to UDP:127.0.0.1:9976. Is it possible for me to direct the Hires camera to video0 for the software to use? From what I've read, the camera can't be accessed directly via video0 (hence the use of voxl-camera-server). Are there any workarounds here?