Posts made by Ed Sutter

@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

@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.

@Alex-Gardner Looks like the voxl-camera-server makes a lot of calls into libraries that [I assume] are not available for browsing, true? Is this proprietary Qualcomm stuff?

Running the latest version (VOXL1 4.0.0), we noticed that frame-rate entries in the voxl-camera-server.conf don't have any affect for both stereo and tracking cameras (works as expected with hires).
Digging into this I just wanna make sure I'm not barking up the wrong tree... Am I correct to assume that voxl-camera-server is the code that initializes the cameras? Does any other service read from voxl-camera-server.conf?

@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.

@Alex-Gardner Huh? There's nothing in the README.md "Build Instructions" that says to do that; but yes, I see if I do that, things build clean!
Ed

@Alex-Gardner This is the output I get from build.sh apq8096:

voxl-emulator:~$ ./build.sh apq8096
-- The C compiler identification is GNU 4.9.3
-- The CXX compiler identification is GNU 4.9.3
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
BUILDSIZE does not match 64
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
MODAL_JOURNAL
    linked by target "voxl-streamer" in directory /home/root
MODAL_JSON
    linked by target "voxl-configure-streamer" in directory /home/root
    linked by target "voxl-streamer" in directory /home/root
MODAL_PIPE
    linked by target "voxl-streamer" in directory /home/root

-- Configuring incomplete, errors occurred!
See also "/home/root/build32/CMakeFiles/CMakeOutput.log".
make: *** No targets specified and no makefile found.  Stop.

As best I can tell this is because it can't find the libmodal_json/journal and pipe libraries, so I fixed that by modifying the CMakeLists.txt file and copying those libraries to a directory that would exist under /home/root when docker starts up.
After a few hacks like that I was able to build it, but clearly I'm doing something wrong. Any idea what I might be doing wrong?
I'm using voxl-emulator:V1.7
Ed

@Alex-Gardner Just reviewing the open issues in this thread, looks like 2 things:

1. Do I need to switch out of AE_ISP mode to be able to control the hires camera's gain and exposure settings? As far as I can tell, the answer is yes. If that's not the case, please let me know (I'm guessing that it is more efficient to run in AE_ISP mode).

2. As far as I can tell, the build procedure for voxl-streamer is missing something (if not, I need to understand why I have to move a lot of files around to get the build to complete). Please let me know what the status of this is.
   Thanks,
   Ed

@Alex-Gardner Not sure if this is what you want, but I posted an issue to voxl-camera-server and voxl-streamer and added a comment that points to the branches in my forks that have the changes I made.
If there is a more convenient way to do this, let me know.

@Alex-Gardner Ok, regarding USB camera...
I run voxl-uvc-server -v VID -p PID -o mycam
Then in another window I run voxl-streamer -i mycam.
That works!

(so I think the only open issue is the build procedure for voxl-streamer)

Ed

@Alex-Gardner Great! Can you tell me if the exp/gain adjust has been tested when using AE_ISP with hires? I wasn't able to get that to work; hence, my need to change the ae_mode. If manual exposure/gain adjust does work in AE_ISP mode I assume that is the better way to go (true?); meanwhile, yes, I did a fork and branch with the changes needed for the server to support the ability to change ae_mode in the .conf.
I also made a minor addition to voxl-streamer so the port could be pulled from the .conf file if interested.

How do I get that to you? Could I have just cloned your code and then pushed a branch back to you? If that's the proper way to do it I'll do that next...
I'll look into the USB stuff next and get back to you.

One last question...
When I tried to build voxl-streamer I had to do a lot of hacking to allow the docker environment to "see" the libraries and header files from the required modules (libmodal_json/journal/pipe). Is something missing from the instructions for this or am I just confused? I'm using emulator:V1.7.
Thanks