@modaltb Using USB 2.
Got my hands on an OTG adapter, seems to be doing the trick.
Best posts made by Nirge
-
RE: VOXL as usb2 host not working via j8posted in VOXL
Latest posts made by Nirge
-
RE: VOXL CPU Performance with ROSposted in VOXL
@Chad-Sweet Hi, the utility shows the same CPU usage if I add usr & sys.
-
VOXL CPU Performance with ROSposted in VOXL
Hi,
I'm migrating an app to VOXL, and noticed the performance is better, but the hidden "sys" values are negating any advantage (28% when 21% is for system).Mem: 2737440K used, 1123880K free, 41796K shrd, 140144K buff, 1824000K cached CPU: 6.9% usr 20.9% sys 0.0% nic 67.4% idle 0.0% io 2.3% irq 2.3% sirq Load average: 3.84 3.14 1.65 4/750 13545Using dmesg it seems it's overflowing with errors:
[ 586.199252] type=1123 audit(1641721335.544:9489): pid=15875 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0-s15:c0.c1023 msg='cwd="/root/.ros" cmd=69776C69737420776C616E30207363616E terminal=? res=failed' [ 586.229739] type=1123 audit(1641721335.574:9490): pid=15876 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0-s15:c0.c1023 msg='cwd="/root/.ros" cmd=69776C69737420776C616E30207363616E terminal=? res=failed' [ 586.269861] type=1123 audit(1641721335.614:9491): pid=15877 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0-s15:c0.c1023 msg='cwd="/root/.ros" cmd=69776C69737420776C616E30207363616E terminal=? res=failed' [ 586.304811] type=1123 audit(1641721335.644:9492): pid=15878 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0-s15:c0.c1023 msg='cwd="/root/.ros" cmd=69776C69737420776C616E30207363616E terminal=? res=failed' [ 586.505185] audit: audit_lost=900 audit_rate_limit=20 audit_backlog_limit=64 [ 586.505199] audit: rate limit exceededAny suggestions on how to diagnose this issue?
-
RE: Unbricking fails due to "protocol error"posted in VOXL
Missed that part, thank you, it seems to do the trick.
-
Unbricking fails due to "protocol error"posted in VOXL
Hi,
I have bricked a voxl in dev, trying to restore using the debug expansion, but the process fails:~/Downloads/modalai-3-1-0$ sudo ./install.sh [INFO] adb installed [INFO] fastboot installed This process will completely wipe your VOXL Would you like to preserve the /data/ partition which contains things like calibration, wifi config, and docker images To preserve files in /data/ answer Y To wipe /data/ for a full factory flash answer N Enter Y or N: n [INFO] Rebooting into fastboot... error: no devices/emulators found [INFO] Waiting for fastboot... [INFO] Waiting for fastboot... [INFO] Waiting for fastboot... [INFO] Waiting for fastboot... target reported max download size of 536870912 bytes sending 'aboot' (494 KB)... OKAY [ 0.047s] writing 'aboot'... OKAY [ 0.444s] finished. total time: 0.492s target reported max download size of 536870912 bytes sending 'boot' (56066 KB)... OKAY [ 2.140s] writing 'boot'... OKAY [ 0.745s] finished. total time: 2.885s target reported max download size of 536870912 bytes erasing 'system'... OKAY [ 0.004s] sending sparse 'system' 1/3 (523027 KB)... FAILED (data write failure (Protocol error)) finished. total time: 9.678sWould appreciate any insights and help I can get.
-
RE: Setting up network interfacesposted in Ask your questions right here!
@tom Originaly configured it station, did not change it when tried to configure it to static.
-
RE: Setting up network interfacesposted in Ask your questions right here!
Hi @tom
I tried this for wlan0 and it doesn't work for me, am I missing a configuration for out-of-the-box VOXL before I can add /etc/network/interfaces? or is it overriden by voxl-wifi? -
RE: VOXL as usb2 host not working via j8posted in VOXL
@modaltb Using USB 2.
Got my hands on an OTG adapter, seems to be doing the trick. -
VOXL as usb2 host not working via j8posted in VOXL
Hi,
Connecting my laptop to voxl via adb works on j8 connecter.
However, an STM based device is not recognized when connecting a client device to voxl using micro-usb to micro-usb cable.
The same device is recognized when connecting via the usb expander (https://docs.modalai.com/usb-expander-and-debug-datasheet/)Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0483:5740 STMicroelectronics STM32F407 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubhttps://docs.modalai.com/voxl-as-usb-host/ does not specify any special requirements.
Am I missing something? is the micro-usb cable needs to be an OTG cable with ID pin?
Best regards,
Nir -
Unbrickingposted in VOXL
Hi,
Just starting up a migration to Voxl as a companion.
Was reading up and wondering how often does it brick if shut-down without shutdown -f?
Is this a common occurence or a 1 in a 1000?
@see https://docs.modalai.com/unbrick-voxl/
Best regards,
Nirge