Topics created by Ed Sutter

I am not sure about that adsp.service error.. Hmm. Would need to actually look into what it's doing. but it seems like if you just (re)move the firmware, the GPIO works.

Thanks Chad...
I'll dig into this; meanwhile, someone here suggested that perhaps we can fork the kernel, then just build the module and install that with modprobe (without actually updating the on-board kernel).
Has that kind of thing ever been done with VOXL1?
Ed

@Alex-Gardner So I guess I can't really do much to debug this (without knowing more about the proprietary implementation), true?
Point being... if there is documentation you can share, I'll gladly dig into this.

@Chad-Sweet I'm not familiar with a "ci script", I've just been referring to the README.md file at the top of each of the project repositories. Most of the projects do include a install_build_deps.sh step, but that wasn't in voxl-streamer's README.md, so I didn't realize I had to run it. No worries; although, it's probably a good idea that the README.md be updated to include that.

Hi @Ed-Sutter,

A platform release just includes the latest sdk along with the system image build. As for voxl-configure-opkg, this was replaced by voxl-configure-pkg-manager with the same functionality.

Ok great.
Thanks Alex

@Chad-Sweet Yet another update... after rebooting, and re-installing the EM7565, wwan0 did come up this time. 🙂 But I still have the problem that I can't communicate with /dev/ttyUSB2. 😞

@Eric-Katzfey I tried grep OMX.qcom from header files, could not find any.

But, string libOmxCore.so only displayed video and audio codec. There is no image codec.

voxl:/usr/include$ strings /usr/lib/libOmxCore.so |grep OMX.qcom
OMX.qcom.video.decoder.avc
OMX.qcom.video.decoder.avc.dsmode
OMX.qcom.video.decoder.mpeg4
OMX.qcom.video.decoder.vc1
OMX.qcom.video.decoder.wmv
OMX.qcom.file.muxer
OMX.qcom.video.decoder.divx4
OMX.qcom.video.decoder.divx
OMX.qcom.video.decoder.divx311
OMX.qcom.video.decoder.h263
OMX.qcom.video.decoder.hevc
OMX.qcom.video.decoder.vp8
OMX.qcom.video.decoder.vp9
OMX.qcom.video.encoder.mpeg4
OMX.qcom.video.encoder.h263
OMX.qcom.video.encoder.avc
OMX.qcom.video.encoder.vp8
OMX.qcom.video.encoder.hevc
OMX.qcom.audio.decoder.Qcelp13
OMX.qcom.audio.decoder.evrc
OMX.qcom.audio.decoder.wma
OMX.qcom.audio.decoder.wma10Pro
OMX.qcom.audio.decoder.alac
OMX.qcom.audio.decoder.ape
OMX.qcom.audio.encoder.aac
OMX.qcom.audio.encoder.qcelp13
OMX.qcom.audio.encoder.evrc
OMX.qcom.audio.encoder.amrnb
OMX.qcom.audio.encoder.g711mlaw
OMX.qcom.audio.encoder.g711alaw
OMX.qcom.audio.encoder.amrwb
OMX.qcom.audio.decoder.g711mlaw
OMX.qcom.audio.decoder.g711alaw
OMX.qcom.audio.decoder.amrwb
OMX.qcom.audio.decoder.amrnb
OMX.qcom.audio.decoder.aac
OMX.qcom.audio.decoder.multiaac
1

Build time

@Alex-Gardner Great, thanks.

@Alex-Gardner Will we be notified when the new version is available?

@Ed-Sutter That is correct, modemmanager is not used.

As you can see in the patch here: https://gitlab.com/voxl-public/system-image-build/meta-voxl/-/blob/master/recipes-kernel/linux-quic/files/qmi_wwan2.patch

The path to the qmi_wwan.c file that is being modified / used is drivers/net/usb/qmi_wwan.c

@Vinny Just re-reading my last reply to you. The wording of the first sentence may be confusing, so rewritten...

... I'm not claiming that the "ModalAI USB-expansion add-on board" is doing anything wrong....

Ok... whatever you did seems to have fixed it.
Thanks

@Steve-Turner voxl-build allows you to build the kernel only which you can then flash on top of an existing system. Qualcomm licenses are required in order to build a full system image.

@Ed-Sutter Ok, I see in the actual busybox code for udhcpc it uses /usr/share/udhcpc/default.script, and I just verified that this script does execute on VOXL. Still I don't understand why /etc/resolv.conf gets overwritten. I don't know a lot about this, does anyone know if it is supposed to overwrite?

@Eric-Katzfey @tom Digging a bit deeper into this, I see that the voxl-build procedure does patch the qmi_wwan.c file, and after the patch, the VID/PID for EM7565 is in there. On one hand this is good news because it implies that the kernel does have support for the modem I'm trying to use; however, its not-so-good news for me because running with that modem has not reliable on VOXL. 😞
Aside from verifying that I am actually running the same version on my VOXL-Flight-Deck as is being built in voxl-build (see below), I'm at a loss regarding other things to do to debug this. Any thoughts on this?
Following is the output of voxl-version on my board:

/ # voxl-version cat: /etc/modalai/voxl-software-bundle-version.txt: No such file or directory -------------------------------------------------------------------------------- system-image: ModalAI 3.3.0 BUILDER: ekatzfey BUILD_TIME: 2021-06-06_19:28 kernel: #1 SMP PREEMPT Sun Jun 6 19:41:01 UTC 2021 3.18.71-perf factory-bundle: 1.0.1 (Yocto installation) -------------------------------------------------------------------------------- architecture: aarch64 processor: apq8096 os: GNU/Linux -------------------------------------------------------------------------------- voxl-suite: Package: voxl-suite Version: 0.5.0 Depends: libjpeg_turbo (>= 9.0.4), libmodal_exposure (>= 0.0.2), libmodal_json (>= 0.3.6), libmodal_pipe (>= 2.1.1), lib rc_math (>= 1.1.5), libvoxl_cutils (>= 0.0.2), libvoxl_io (>= 0.5.4), mavlink-camera-manager (>= 0.0.2), mongoose (>= 7. 3.0), opencv (>= 4.5.2-2), openmp (>= 10.0.2), voxl-camera-calibration (>= 0.1.1), voxl-camera-server (>= 0.8.1), voxl-c pu-monitor (>= 0.2.0), voxl-dfs-server (>= 0.2.2), voxl-docker-support (>= 1.1.3), voxl-gphoto2 (>= 0.0.5), voxl-imu-ser ver (>= 0.9.1), voxl-mavlink (>= 0.0.2), voxl-modem (>= 0.12.0), voxl-mpa-tools (>= 0.3.6), voxl-nodes (>= 0.2.0), voxl- portal (>= 0.1.2), voxl-qvio-server (>= 0.3.4), voxl-streamer (>= 0.2.6), voxl-tag-detector (>= 0.0.2), voxl-tflite (>= 2.2.3), voxl-tflite-server (>= 0.1.5), voxl-utils (>= 0.8.4), voxl-vision-px4 (>= 0.9.5), voxl-vpn (>= 0.0.3) Status: install user installed Section: base Architecture: all Maintainer: james@modalai.com MD5Sum: 172dd2541a4b01ec415651b5ded3afab Size: 1956 Filename: voxl-suite_0.5.0_202111041852.ipk Description: meta-package for voxl-suite software collection Installed-Time: 144 --------------------------------------------------------------------------------

@Ed-Sutter Good catch, does look like that print statement is never reached, I'll move it to the correct location to avoid future confusion.