Firmware Binaries
Software Development Kits > Guide to Linux Porting
Before the module can be inserted, in a running platform, two binary files need to be installed into /lib/firmware/morse of the rootfs. Not all board configuration les are required to be installed onto the device, just the file associated with the module model number.
unzip firmware_binaries_1_11_3.zip
cd firmware_binaries_1_11_3
install -D $STAGING_DIR/lib/firmware/morse
install -c -m 644 mm6108.bin $STAGING_DIR/lib/firmware/morse
install -c -m 644 bcf_*.bin $STAGING_DIR/lib/firmware/morse
On insertion of the morse.ko kernel module, there are three paths the driver might take for selecting which BCF to use.
- Use the file specified in the bcf module parameter- e.g. bcf=bcf_mf08651.bin
- For modules with the board type ID programmed into OTP, use the file with name bcf_boardtype_.bin
- Use bcf_default.bin
MM6108-MF08651-US modules are shipped with the board type ID programmed into OTP. To support this module it is recommended the developer adds the following symbolic link to their rootfs/target platform.
ln -s /lib/firmware/morse/bcf_mf08651.bin
$STAGING_DIR/lib/firmware/morse/bcf_boardtype_0801.bin
For other modules the developer should run the following command:
ln -s /lib/firmware/morse/$BCF.bin
$STAGING_DIR/lib/firmware/morse/bcf_default.bin
where $BCF matches the appropriate BCF for the target platform.