@tom That sounds good.
On a separate note, is there anywhere to see what you are working on and what you are planning?
It would be really cool to follow along and have an idea about upcoming features.

@Vinny Any update on the difference of the debug and perf build would be appreciated.

Best
Kasper

I'm just going to bump this a last time in the hopes that someone from @Moderator team replies as i see this as an important feature.

I have looked at bit more in to this myself, and have concluded that you have patched out the OTA capability from Qualcomm in patch 14.1a-META-QTI-UBUNTU-MODIFY-CORE-PKGS.patch.
Is there any plans to enable and support OTA updates in the future?

Best
Kasper

@Moderator
I am stil really interested to know lore about these questions as it is essential to have a complete produkt.

Best
Kasper

Hi ModalAI team,

I have a Voxel 2 board and are building the kernel image as shown in your documentation.

I need to be able to update the board trough some OTA method as the board will not be easily accessible.
I have looked in to Qualcomm's recommended way, but some files of the files are not build in order to utilize their proposed way of doing OTA.

How do you suggest updating the board via some OTA method, and is it currently possible using your framework?

Best
Kasper

@ksl
This problem was linked to: https://forum.modalai.com/topic/3329/voxl2-kernel-rebuild-gpio-sysfs-does-not-work/5

So it seems that if the kernel is build in debug mode the Voxl kerne modules are not rebuild and the

disagrees about version of symbol module_layout

will happen.
I would be good that this is either documented in the kenel build guide or even better, that this is corrected so that the kernel can be build and run in debug mode.

@ksl Possebly related to this, when i build my own kernel, i get:

[   23.886763] 8188eu: disagrees about version of symbol module_layout
[   23.917344] 8821cu: disagrees about version of symbol module_layout
[   23.940321] 88XXau: disagrees about version of symbol module_layout
[   23.950527] q6_pdr_dlkm: disagrees about version of symbol module_layout
[   24.037974] q6_pdr_dlkm: disagrees about version of symbol module_layout
[   24.159403] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.166971] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.232182] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.331171] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.453120] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.460695] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.469246] pinctrl_wcd_dlkm: disagrees about version of symbol module_layout
[   24.477432] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.588591] swr_dlkm: disagrees about version of symbol module_layout
[   24.595719] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.604323] hdmi_dlkm: disagrees about version of symbol module_layout
[   24.611722] stub_dlkm: disagrees about version of symbol module_layout
[   24.620298] wcd_core_dlkm: disagrees about version of symbol module_layout
[   24.627745] wcd_core_dlkm: disagrees about version of symbol module_layout
[   24.635146] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.642687] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.650231] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.657966] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.780032] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.868200] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.978382] swr_dlkm: disagrees about version of symbol module_layout
[   24.986022] snd_event_dlkm: disagrees about version of symbol module_layout
[   24.994470] voxl_fsync_mod: disagrees about version of symbol module_layout
[   25.016775] voxl_gpio_mod: disagrees about version of symbol module_layout
[   25.025231] voxl_platform_mod: disagrees about version of symbol module_layout

@Vinny I will give that a try, otherwise I heard from my college that he might have had one that stopped working at some point.
That said, this was mainly to validate that our own kernel build worked as the one shipped in the SDK, Any idea about what could stop the extra devices from being detected?

Best
Kasper

@Moderator,
I did a little more digging and came a bit further, but I have two different problems now.

Firstly I can see the Ethernet adapter using lsusb. That said, it never registers as connected and no communication runs over it.
I have isolated the eth. adapter on the board by having a USB Ethernet adapter on the USB port. This works and get and ip etc.
This is using your release image for the VOXEL 2 board.

The second problem (and what started this) is that I am building my own image, when doing this i only get the root hubs

The build is your base image, from the documentation, to validate this was not changes on my end. The physical setup is as above. In this scenario nothing is showing up on though.

Best
Kasper

Hi,

I have a VOXEL 2 and the M0062-2 shield on top of it.
The documentation is a little sparse on this module, hence why i ask here.

Is there anything i have to do in order to enable the Ethernet port?

lsusb shows two hubs, but nothing else.
It is not showing up at all when it is connected.

Best
Kasper