I have some questions:
- Does mf04151 stand for Morse firmware 04151? What does 04151 stand for? (bcf_mf04151.bin)
- How do i specify which BCF file to include in a Morse Micro OpenWRT build?
- How does the morse_setup.sh include the BCF? (if it does so)
Welcome to the Morse Micro Community!
mf04151 refers to a module reference design, and quite an old one at that. There’s a method to how those numbers are derived, but it not worth delving into. BCF compatibility with specific versions of the firmware and linux driver is determined by an internal version number, and there aren’t any standalone user-facing tools for that. You can see some information about the currently selected BCF within OpenWRT. Look in Network → Wireless, then edit the HaLow interface and look in the Advanced Settings tab.
Our OpenWRT builds include a set of BCFs to allow the images to correctly operate a range of Morse Micro devices. The actual selection mechanism in the driver is as follows:
- If the BCF was set by a modparam when the driver was loaded, use that.
- If the module has a boardtype programmed in OTP, use bcf_boardtype_xxxx.bin.
(All of our eval kits should have boardtype programmed correctly) - Fall back to bcf_default.bin
This is how all of our OpenWRT-based eval kits operate. morse_setup.sh itself takes a -b option that specfies a board so that the right architecture and device trees are included, but does not specify a single BCF.
I’m sure there are some subtleties I’ve missed here, so some of my colleagues may chime in, but that’s the broad view.
Current BCFs for our own reference modules, and (coming soon) our module partners, are available on Github.
2 Likes