Cell modules - Revision history

Ted: QFirehose expects many files

2025-10-07T21:27:06Z

QFirehose expects many files

Ted: Add section "Eseye ETM states

2024-05-01T16:26:22Z

Add section "Eseye ETM states

Ted: Add note and code excerpt regarding qapi_TIMER_unit_type

2022-10-19T17:39:19Z

Add note and code excerpt regarding qapi_TIMER_unit_type

Ted: /* ^ Choosing a test-able GPIO for GPIO demo app */

2022-10-19T17:26:12Z

^ Choosing a test-able GPIO for GPIO demo app

Ted: /* ^ Choosing a test-able GPIO for GPIO demo app */

2022-10-19T17:22:48Z

^ Choosing a test-able GPIO for GPIO demo app

Ted: /* ^ References */ - add name of Hardware reference manual for BG95.

2022-10-13T22:53:12Z

^ References: - add name of Hardware reference manual for BG95.

Ted: /* ^ Choosing a test-able GPIO for GPIO demo app */ - minor formatting.

2022-10-13T17:52:57Z

^ Choosing a test-able GPIO for GPIO demo app: - minor formatting.

Ted: New section - Choosing a test-able GPIO for GPIO demo app.

2022-10-13T05:38:32Z

New section - Choosing a test-able GPIO for GPIO demo app.

Ted: /* ^ References */ - add link to Quectel_UMTS-LTE_EVB_User_Guide_V2.1-1.pdf.

2022-10-12T22:39:22Z

^ References: - add link to Quectel_UMTS-LTE_EVB_User_Guide_V2.1-1.pdf.

Ted: /* ^ AT command reponses */ - minor correction.

2022-10-12T22:28:38Z

^ AT command reponses: - minor correction.

← Older revision		Revision as of 21:27, 7 October 2025
Line 34:		Line 34:

	* https://forums.quectel.com/t/bg95-</ul></ul>m3-fw-update/6843/4		* https://forums.quectel.com/t/bg95-</ul></ul>m3-fw-update/6843/4
		+
		+	2025-10-07
		+
		+	QFirehose expects some fifteen or more files for a typical Quectel firmware update:
		+
		+	* https://forums.quectel.com/t/ec25-flash-new-firmware-error/5214/3
		+
		+	Excerpt from above post:
		+
		+	<pre>
		+	[alex@debiank QFirehose]$ sudo ./QFirehose -f /home/alex/Downloads/quectel/EC25EFAR06A08M4G
		+	[000.000]: QFirehose Version: Quectel_LTE&5G_QFirehose_Linux&Android_V1.2.3
		+	[000.000]: Builded: Apr 27 2020 12:56:28
		+	[000.000]: Find md5 check file </home/alex/Downloads/quectel/EC25EFAR06A08M4G/md5.txt>
		+	[000.000]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/contents.xml pass
		+	[000.002]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/appsboot.mbn pass
		+	[000.003]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/ENPRG9x07.mbn pass
		+	[000.003]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/firehose/partition_complete_p4K_b256K.mbn pass
		+	[000.003]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/firehose/patch_p4K_b256K.xml pass
		+	[000.004]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/firehose/prog_nand_firehose_9x07.mbn pass
		+	[000.004]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/firehose/rawprogram_nand_p4K_b256K_update.xml pass
		+	[000.036]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/mdm9607-perf-boot.img pass
		+	[000.296]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/mdm9607-perf-sysfs.ubi pass
		+	[000.353]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/mdm-perf-recovery-image-mdm9607-perf.ubi pass
		+	[000.581]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/NON-HLOS.ubi pass
		+	[000.582]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/NPRG9x07.mbn pass
		+	[000.582]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/partition.mbn pass
		+	[000.582]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/partition_nand.xml pass
		+	[000.583]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/rpm.mbn pass
		+	[000.584]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/sbl1.mbn pass
		+	[000.587]: md5 checking: /home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/tz.mbn pass
		+	[000.587]: Totals checking 17 files md5 value, 0 file fail!
		+	[000.587]: [1] /sys/bus/usb/devices/1-2 2c7c/125/0
		+	[000.732]: P: /dev/bus/usb/001/025 idVendor=2c7c idProduct=0125
		+	[000.732]: C: /dev/bus/usb/001/025 bNumInterfaces: 1
		+	[000.732]: I: If#= 0 Alt= 0 #EPs= 2 Cls=ff Sub=ff Prot=ff
		+	[000.732]: E: Ad=81 Atr=02 MxPS= 512 Ivl=0ms
		+	[000.732]: E: Ad=01 Atr=02 MxPS= 512 Ivl=0ms
		+	[000.732]: qusb_noblock_open port_name = /dev/ttyUSB0
		+	[000.733]: dir=/home/alex/Downloads/quectel/EC25EFAR06A08M4G/update/firehose/..
		+	[000.736]: d_name=NPRG9x07.mbn
		+	[000.736]: prog_nand_firehose_filename = NPRG9x07.mbn
		+	[000.736]: STATE ← SAHARA_WAIT_HELLO
		+	[000.736]: RECEIVED ← SAHARA_HELLO_ID
		+	[000.736]: RECEIVED ← SAHARA_MODE_MEMORY_DEBUG
		+	[000.736]: ERROR NOT SAHARA_MODE_IMAGE_TX_PENDING
		+	[000.736]: SENDING → SAHARA_HELLO_RESPONSE
		+	[000.736]: STATE ← SAHARA_WAIT_COMMAND
		+	[000.736]: RECEIVED ← SAHARA_HELLO_ID
		+	</pre>

	<!-- comentario -->		<!-- comentario -->

← Older revision		Revision as of 16:26, 1 May 2024
Line 364:		Line 364:
	</pre>		</pre>

		+	<!-- comentario -->

		+	== [[#top\|^]] Eseye ==
		+
		+	* https://docs.eseye.com/Content/SoftwareProducts/AnyNetSMARTconnectATcommands/ETMSTATE.htm ETM states

	<!-- comentario -->		<!-- comentario -->

@@ Line 344: / Line 344: @@
          uint32_t gpio_func;^M
 }GPIO_MAP_TBL;^M
 </pre>

← Older revision		Revision as of 17:26, 19 October 2022
Line 337:		Line 337:
	./quectel/utils/include/quectel_gpio.h:71:}GPIO_MAP_TBL; <-- this is the data structure we need understand		./quectel/utils/include/quectel_gpio.h:71:}GPIO_MAP_TBL; <-- this is the data structure we need understand

−		+	<pre>
		+	typedef struct{^M
		+	uint32_t pin_num;^M
		+	char *pin_name;^M
		+	uint32_t gpio_id;^M
		+	uint32_t gpio_func;^M
		+	}GPIO_MAP_TBL;^M
		+	</pre>

← Older revision		Revision as of 17:22, 19 October 2022
Line 330:		Line 330:

	From document Quectel_BG95BG77BG600L_Series_QuecOpen_Application_Note_V1.4.pdf, page 23, it appears that BG95 pin 18 has signal/port name GPIO5, which in turn can be configured to be GPIO_3 or I2C1_SCL. This matters because the eval board breaks out a limited number of test pins on J803, J805, J806 and J804. On J804 there is a pin designated as I2C_SCL. In document Quectel_BG95BG77BG600L_Series_QuecOpen_Application_Note_V1.4.pdf there are references only to I2C1, not any other numbered I2C peripheral.		From document Quectel_BG95BG77BG600L_Series_QuecOpen_Application_Note_V1.4.pdf, page 23, it appears that BG95 pin 18 has signal/port name GPIO5, which in turn can be configured to be GPIO_3 or I2C1_SCL. This matters because the eval board breaks out a limited number of test pins on J803, J805, J806 and J804. On J804 there is a pin designated as I2C_SCL. In document Quectel_BG95BG77BG600L_Series_QuecOpen_Application_Note_V1.4.pdf there are references only to I2C1, not any other numbered I2C peripheral.
		+
		+	To iterate over valid GPIOs in QuecOpen gpio sample app, a review of _____ data structure assists in needed modification to source file example_gpio.c:
		+
		+	ted@localhost1:/usr/local/include/quectel$ grep -nr GPIO_MAP_TBL ./*
		+	./include/qapi/qapi_pwm.h:144:}PWM_GPIO_MAP_TBL;
		+	./quectel/utils/include/quectel_gpio.h:71:}GPIO_MAP_TBL; <-- this is the data structure we need understand
		+
		+
		+
		+

	<!-- comentario -->		<!-- comentario -->

@@ Line 341: / Line 341: @@
 User manual for UMTS&LTE EVAL KIT:
 *  [https://www.quectel.com/download_file/1402 Quectel_UMTS-LTE_EVB_User_Guide_V2.1-1.pdf]
 <!-- comentario -->

@@ Line 282: / Line 282: @@
 == [[#top|^]] Choosing a test-able GPIO for GPIO demo app ==
 Following GPIO pin table from QuecOpen gpio demo app:
@@ Line 290: / Line 316: @@
   #if defined(_QUECTEL_PROJECT_BG95)
 GPIO_MAP_TBL gpio_map_tbl[PIN_E_GPIO_MAX] = {
-/* PIN NUM,     PIN NAME,    GPIO ID  GPIO FUNC */
+/* PIN NUM,   PIN NAME,  GPIO ID  GPIO FUNC */
-        {  4,           "GPIO_01",      24,      0},
+    {  4,     "GPIO_01",    24,       0},
-        {  5,           "GPIO_02",      21,      0},
+    {  5,     "GPIO_02",    21,       0},
-        {  6,           "GPIO_03",      22,      0},
+    {  6,     "GPIO_03",    22,       0},
-        {  7,           "GPIO_04",      23,      0},
+    {  7,     "GPIO_04",    23,       0},
-        { 18,           "GPIO_05",      3,           0},
+    { 18,     "GPIO_05",     3,       0},
-        { 19,           "GPIO_06",      2,           0},
+    { 19,     "GPIO_06",     2,       0},
-        { 22,           "GPIO_07",      1,           0},
+    { 22,     "GPIO_07",     1,       0},
 </pre>

← Older revision		Revision as of 05:38, 13 October 2022
Line 278:		Line 278:

	* Quectel_BG95&BG77_FILE_Application_Note_V1.0.pdf		* Quectel_BG95&BG77_FILE_Application_Note_V1.0.pdf
		+
		+	<!-- comentario -->
		+
		+	== [[#top\|^]] Choosing a test-able GPIO for GPIO demo app ==
		+
		+	Following GPIO pin table from QuecOpen gpio demo app:
		+
		+	<pre>
		+	52 /* !!! This Pin Enumeration Only Applicable BG95-OPEN Project !!!
		+	53 */
		+	54 #if defined(_QUECTEL_PROJECT_BG95)
		+	55 GPIO_MAP_TBL gpio_map_tbl[PIN_E_GPIO_MAX] = {
		+	56 /* PIN NUM, PIN NAME, GPIO ID GPIO FUNC */
		+	57 { 4, "GPIO_01", 24, 0},
		+	58 { 5, "GPIO_02", 21, 0},
		+	59 { 6, "GPIO_03", 22, 0},
		+	60 { 7, "GPIO_04", 23, 0},
		+	61 { 18, "GPIO_05", 3, 0},
		+	62 { 19, "GPIO_06", 2, 0},
		+	63 { 22, "GPIO_07", 1, 0},
		+	</pre>
		+
		+	From document Quectel_BG95BG77BG600L_Series_QuecOpen_Application_Note_V1.4.pdf, page 23, it appears that BG95 pin 18 has signal/port name GPIO5, which in turn can be configured to be GPIO_3 or I2C1_SCL. This matters because the eval board breaks out a limited number of test pins on J803, J805, J806 and J804. On J804 there is a pin designated as I2C_SCL. In document Quectel_BG95BG77BG600L_Series_QuecOpen_Application_Note_V1.4.pdf there are references only to I2C1, not any other numbered I2C peripheral.

	<!-- comentario -->		<!-- comentario -->

← Older revision		Revision as of 22:28, 12 October 2022
Line 54:		Line 54:


−	== [[#top\|^]] AT command ~~reponses~~ ==	+	== [[#top\|^]] AT command responses ==

	A number of the following commands noted from Quectel forum post https://forums.quectel.com/t/bg95-m3-doesnt-call-callback-function/15647 . . .		A number of the following commands noted from Quectel forum post https://forums.quectel.com/t/bg95-m3-doesnt-call-callback-function/15647 . . .