@Alex-Kushleyev
Ok, good to know.
Thanks

This seems odd...

/ # systemctl status -l adsp.service
● adsp.service - slpi start service
   Loaded: loaded (/etc/initscripts/adsp.sh; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 1970-01-01 00:22:10 UTC; 53 years 2 months ago
  Process: 2032 ExecStart=/etc/initscripts/adsp.sh start (code=exited, status=1/FAILURE)

Jan 01 00:22:06 apq8096 systemd[1]: Starting slpi start service...
Jan 01 00:22:10 apq8096 systemd[1]: adsp.service: Control process exited, code=exited status=1
Jan 01 00:22:10 apq8096 systemd[1]: Failed to start slpi start service.
Jan 01 00:22:10 apq8096 systemd[1]: adsp.service: Unit entered failed state.
Jan 01 00:22:10 apq8096 systemd[1]: adsp.service: Failed with result 'exit-code'.
Jan 01 00:22:10 apq8096 adsp.sh[2032]: Starting adsp: [INFO] Bringing adsp out of reset
Jan 01 00:22:10 apq8096 adsp.sh[2032]: [ERROR] adsp fail to boot

Seems like it tried to startup (despite being disabled) and failed.

Sure... here is the output...

/ # dmesg | grep adsp
[    0.000000] Reserved memory: allocated memory for 'adsp_region' node: base 0x00000000ff800000, size 4 MiB
[    0.000000] Reserved memory: initialized node adsp_region, compatible id shared-dma-pool
[    0.336712] platform soc:qcom,msm-adsprpc-mem: assigned reserved memory node adsp_region
[    0.337300] platform soc:qcom,msm-mdsprpc-mem: assigned reserved memory node adsp_region
[    0.661470] platform soc:qcom,ion:qcom,ion-heap@22: assigned reserved memory node adsp_region
[    0.662328] ION heap adsp created at 0x00000000ff800000 with size 400000
[    0.688677] gdsc_hlos1_vote_lpass_adsp: no parameters
[    1.740246] subsys-pil-tz 9300000.qcom,lpass: for adsp segments only will be dumped.
[    1.786834] fastrpc soc:qcom,msm-adsprpc-mem: for adsp_rh segments only will be dumped.
[    1.788263] adsprpc: channel link type: 0
[    2.438965] systemd[1]: [/lib/systemd/system/adsprpcd.service:11] Failed to parse service restart specifier, ignoring: yes
[    4.909223] SELinux:  Context u:object_r:adsprpcd_file:s0 is not valid (left unmapped).
[    5.451916] adsp-loader soc:qcom,msm-adsp-loader: adsp_loader_do: scheduling work to load ADSP fw
[    5.455155] subsys-pil-tz 9300000.qcom,lpass: adsp: loading from 0x000000008ea00000 to 0x0000000090400000
[    5.912485] subsys-pil-tz 9300000.qcom,lpass: adsp: Brought out of reset
[    5.937106] subsys-pil-tz 9300000.qcom,lpass: adsp: Power/Clock ready interrupt received
[    5.950516] 'opened /dev/adsprpc-smd c 224 0'
[    6.056923] sysmon-qmi: sysmon_clnt_svc_arrive: Connection established between QMI handle and adsp's SSCTL service
[    8.476656] type=1130 audit(1330.153:70): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0-s15:c0.c1023 msg='unit=ads
p comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Note that this is after disabling it...

@Alex-Kushleyev
By the way, the reason I picked GPIO70 was because it appeared to be used for other modems in the voxl-modem script. As a result, I mistakenly took for granted that this pin was "available" for use in bringing up our custom modem module.

It would probably be wise to update that voxl-modem script.

@Alex-Kushleyev
Just to clarify, I went ahead and did some preliminary tests, and it appears that just doing the systemctrl disable adsp.service does not allow /sys/class/gpio to control GPIO70.
I did the following before disabling adsp:

/ # echo 70 > /sys/class/gpio/export
/ # echo out > /sys/class/gpio/gpio70/direction
/ # echo 1 > /sys/class/gpio/gpio70/value
/ # cat /sys/class/gpio/gpio70/value
0

Note that I set value to 1, but it didn't stick (expected at this point). I followed this with systemctl disable adsp.service and rebooted. Then I repeated the above steps and still got a 0 for gpio70/value.

Thanks Alex! It was a trivial change on our hardware, but good to know.

Nevermind... I just saw this post...
https://forum.modalai.com/topic/741/voxl-j13-b2b-clarifications?_=1679325218510

I guess APQ_GPIO_70 is off limits for now...

Hi,
We are using APQ_GPIO_107 and APQ_GPIO_70 on a custom board, and noticed this morning that 107 works fine but 70 does not respond to typical gpio commands through /sys/class/gpio. For example...

echo 70 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio70/direction
echo 1 > /sys/class/gpio/gpio70/value

Any idea why?

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

One of the modems we may use comes up over USB and presents itself to the host as a network interface. the documentation says that the linux host needs vlan (8021q kernel module).
Has this ever been used on VOXL1?
If not, is there any reason it couldn't be installed?
Thanks,
Ed