MM6108 EKH01 firmware development

[Skt]

Hello OpenWrt community,

I am working with the Morse Micro MM6108-EKH01 (HaLow evaluation kit)which is based on openWrt. I am trying to understand the correct workflow for building a flashable .img firmware for the device.My end goal is to reconfigure RAW parameters a little bit for my research purpose(currently pursuing my PhD).

Here is where I am confused:

• Morse Micro also provides an open-source Linux driver repository (morse driver).
• My assumption initially was that the driver source could somehow be “converted” into a firmware image, but I now suspect that this understanding has been wrong.

What I have tried:

• Building the full OpenWrt tree (from morse micro OpenWrt repository) to produce .img files, but haven't been successful.
• On the running EKH01 device, I do not see /lib/modules/$(uname -r)/build or Module.symvers, which makes out-of-tree module builds confusing.
• I am unsure whether kernel modules for the Morse driver are expected to be:
  • Built inside the OpenWrt SDK, or
  • Built externally and inserted into an already-flashed firmware.

My core questions is:

1. What is the correct and intended workflow for EKH01 development?
   *The minimum set of steps to reliably generate a flashable .img for EKH01?

I would really appreciate clarification from anyone.

Thanks in advance for your guidance.

[frollic]

Kmods need to be merged into the Openwrt SDK.

[Skt]

Thanks @frollic, just to explicitly confirm:
By kmods, you are referring to the kernel modules built from the morse_driver repository, which need to be packaged as OpenWrt kmod-* packages and built inside the matching OpenWrt SDK for EKH01 — correct?
If not please explain.

[frollic]

Any kmod, not only yours.

[andrewjlamarche]

This is really a question for Morse Micro since this platform is not supported in upstream OpenWrt.