|Robert Smith bdc4bc974b Update README.md||7 kuukautta sitten|
|1_firmwares||7 kuukautta sitten|
|2_qflash_qfirehose||7 kuukautta sitten|
|3_doc_on_module||7 kuukautta sitten|
|4_doc_common||7 kuukautta sitten|
|5_OpenLinux||7 kuukautta sitten|
|EG25_SDK_and_OpenLinux_FW||7 kuukautta sitten|
|LICENSE||7 kuukautta sitten|
|README.md||7 kuukautta sitten|
Here is our external repository to remotely work on Quectel EG25-G GB related project. Since the unwise public re-distribution may affect our ability to get more such files, don’t do this. You can share them privately with trusted people who will respect this secrecy, and download this repository for backup purposes.
AT+EGMR=1,7,“newIMEI” - is a command for changing the IMEI. It is undocumented, maybe because in some countries there are stupid privacy-hating laws against the IMEI changes (although this can be done with some precautions, such as making sure that the devices with the same IMEI will not be powered at the same time).
The “modem core” of Quectel EG25-G GB - which works with cellular and does the sound processing - is executing the internal code which belongs to Qualcomm. But, this module has a partially open design - “OpenLinux” - which allows to install and execute your own code as a Linux app on its Application Processor.
In any case, such an implementation would contain some closed source binaries by Qualcomm and API libraries by Quectel (although the API libraries aren’t needed if you are using the AT commands or QMI protocol for working with “modem core”). Luckily, the communication of a Linux Host-PC with this module doesn’t need any closed source stuff and can be done on any not-too-ancient Linux out-of-the-box. Can use the AT commands, QMI (open-source: uqmi or qmicli), MBIM, ECM or RNDIS.
EC25 and EG25 modules are built on the same chipset, so the OpenLinux EC25 files are compatible with EG25. The main difference is: EG25 has a larger RF-frontend for a global version, and is a bigger size, but the module pinouts are the same. And AG35 should be similar as well, seeing that many files are for both modules.
OCPU releases and the matching them SDK versions - are less frequent than the firmware releases, and their version numbers are not connected to each other.
EG25GGBR07A08M2G_01.003.01.003.zip is the latest firmware for EG25-G GB module. Can be installed with QFlash on Windows Host-PC, or QFirehose on Linux Host-PC. It’s a standard firmware: its ADB is closed, it doesn’t have API libraries, etc. So it is not planned to add your own software into this firmware. Module with such a firmware - should be controlled by the external Host-PC (how? see above).
EG25GGBR07A07M2G_OCPU_01.001.01.001.zip is OpenLinux firmware. Its ADB is open, and you can add your own software (compiled with SDK) into this firmware. Also, it contains the firmware of the “modem core”.
EG25GGBR07A07M2G_OCPU_01.001.01.001_SDK.tar.bz2 is a SDK. Contains the header files for Quectel API and matching libraries in a binary-only format; and also: the software examples, Linux kernel sources, image of system partition, matching cross-compiler and other scripts which are necessary to do the compilation.
When you compile with SDK, you get only a Linux firmware for the Application Processor inside the module. Firmware of the “modem core” is binary-only. This is why the two files above (OCPU and SDK matching this OCPU) are in a pair.
./upgrade/targetfiles.zip in the OCPU archive - is needed to produce the update package, because in case of OpenLinux this package is created by a customer. But if using a standard firmware, need Quectel’s help to create this update package.
If you have any questions, please open an issue: we will see if we can help you.