Cannot see wlan0 on Sierra Wireless WP7702 MangOH Yellow device

it already in “16” for uart2 which is the debug port.
did you see anything there?

I have connected both USB port and CON port of the mangOH yellow to my laptop. I can ssh root@192.168.2.2 from the USB port (which seems like the ecm0 interface), and I can run AT commands via Putty which is connected to Serial connection with speed 115200 (the one connected to CON port, which I assume must be the UART2). Please correct me if my understanding is wrong. For now, I flashed the image with Octave WP77XX on the device and I can ssh and also run AT commands, but those blinking led lights don’t come (only one solid yellow LED light). Also, can’t see wlan0 listed in interfaces. Is there a method to just factory reset everything and go back to initial state when device out of the box? Thanks a lot!!

see if this helps:

This is to erase the partition? To factory reset you mean? I ran the command to check partition:

root@swi-mdm9x28-wp:~# cat /proc/mtd|grep userapp -i
mtd16: 08300000 00040000 “userapp”
root@swi-mdm9x28-wp:~#

yes, but not sure if it works for you

Or you can downgrade to FW before R12 and use swiflash to erase the partition:
https://source.sierrawireless.com/resources/airprime/software/swiflash/#sthash.vDzj03u5.dpbs

I did this:

The command ran
and I had to setup the ssh keys again

But still the same issue. ifconfig -a does not show wlan0 in the list of interfaces:

root@swi-mdm9x28-wp:~# ifconfig -a
bridge0 Link encap:Ethernet HWaddr 0A:0E:F1:AA:A1:0C
inet addr:192.168.225.1 Bcast:192.168.225.255 Mask:255.255.255.0
inet6 addr: fe80::80e:f1ff:fea7:9e09/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:76 (76.0 B)

ecm0 Link encap:Ethernet HWaddr 0A:29:0C:06:18:F8
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::829:cff:fe06:18f8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:614 errors:0 dropped:0 overruns:0 frame:0
TX packets:345 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:64021 (62.5 KiB) TX bytes:46722 (45.6 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:76 (76.0 B) TX bytes:76 (76.0 B)

rmnet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING MTU:2000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

rmnet_data0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

rmnet_data1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

rmnet_data2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

rmnet_data3 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

So I am back at the original problem. Can’t start wlan0 on my device. Can you please help how to resolve that? Thanks a lot!!

did you capture the UART debug message to understand version 6 spk has boot up problem?

another way is to compile the mangoh yellow layer v0.6:

I didn’t understand still how to capture the UART debug message, and when? When I do ifconfig -a (I don’t expect any error to come there, it just doesn’t show the wlan0 interface), or when I try to start wifi client start where ti gives error:

ERROR: le_wifiClient_Start returns ERROR.

in which I have already put a logread to read the logs which say this:

root@swi-mdm9x28-wp:~# logread -f | grep wifi
Jul 13 13:36:52 swi-mdm9x28-wp user.info Legato: INFO | wifiService[2087] | wlan0 interface was not created by Cypress drivers
Jul 13 13:36:55 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | /etc/init.d/cywifi:
Jul 13 13:36:55 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | line 109:
Jul 13 13:36:55 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | can’t create /sys/devices/platform/expander.0/wl_reg_on: nonexistent directory
Jul 13 13:36:55 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] |
Jul 13 13:36:59 swi-mdm9x28-wp user.info Legato: INFO | wifiService[2087] | Cypress chip MMC recognition may have been overwritten
Jul 13 13:36:59 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | insmod: can’t insert ‘/lib/modules/3.18.140/backports/compat.ko’: File exists
Jul 13 13:36:59 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | insmod: can’t insert ‘/lib/modules/3.18.140/backports/cfg80211.ko’: File exists
Jul 13 13:36:59 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | insmod: can’t insert ‘/lib/modules/3.18.140/backports/brcmutil.ko’: File exists
Jul 13 13:36:59 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | insmod: can’t insert ‘/lib/modules/3.18.140/backports/brcmfmac.ko’: File exists
Jul 13 13:37:04 swi-mdm9x28-wp user.info Legato: INFO | wifiService[2087] | wlan0 interface was not created by Cypress drivers
Jul 13 13:37:07 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | /etc/init.d/cywifi:
Jul 13 13:37:07 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | line 109:
Jul 13 13:37:07 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | can’t create /sys/devices/platform/expander.0/wl_reg_on: nonexistent directory
Jul 13 13:37:07 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] |
Jul 13 13:37:11 swi-mdm9x28-wp user.info Legato: INFO | wifiService[2087] | Cypress chip MMC recognition may have been overwritten
Jul 13 13:37:11 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | insmod: can’t insert ‘/lib/modules/3.18.140/backports/compat.ko’: File exists
Jul 13 13:37:11 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | insmod: can’t insert ‘/lib/modules/3.18.140/backports/cfg80211.ko’: File exists
Jul 13 13:37:11 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | insmod: can’t insert ‘/lib/modules/3.18.140/backports/brcmutil.ko’: File exists
Jul 13 13:37:11 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[2087] | insmod: can’t insert ‘/lib/modules/3.18.140/backports/brcmfmac.ko’: File exists
Jul 13 13:37:16 swi-mdm9x28-wp user.info Legato: INFO | wifiService[2087] | wlan0 interface was not created by Cypress drivers
Jul 13 13:37:16 swi-mdm9x28-wp user.warn Legato: -WRN- | wifiService[2087]/daemon T=main | pa_wifi_client.c pa_wifiClient_Start() 532 | Failed to start WiFi client command “WIFI_START” systemResult (32512)
Jul 13 13:37:16 swi-mdm9x28-wp user.warn Legato: -WRN- | wifiService[2087]/daemon T=main | le_wifiClient.c le_wifiClient_Start() 821 | Unable to start WIFI client; return code: -6
Jul 13 13:37:16 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[2087]/framework T=main | le_wifiClient_server.c CleanupClientData() 163 | Client 0x7f56c330 is closed !!!
Jul 13 13:37:16 swi-mdm9x28-wp user.info Legato: INFO | supervisor[1113]/supervisor T=main | proc.c proc_SigChildHandler() 2079 | Process ‘wifi@0’ (PID: 20783) has exited with exit code 1.
Jul 13 13:37:16 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[2087]/framework T=main | le_wifiClient_server.c CleanupClientData() 185 | Found session ref 0x7f56c3c0; does not match
Jul 13 13:37:16 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[2087]/framework T=main | le_wifiAp_server.c CleanupClientData() 163 | Client 0x7f56c2a0 is closed !!!
Jul 13 13:37:16 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[1113]/supervisor T=main | app.c app_SigChildHandler() 4066 | Process ‘wifi@0’ in app ‘wifi’ faulted: Ignored.
Jul 13 13:37:16 swi-mdm9x28-wp user.info Legato: INFO | supervisor[1113]/supervisor T=main | app.c app_StopComplete() 4753 | app ‘wifi’ has stopped.
Jul 13 13:37:16 swi-mdm9x28-wp user.info Legato: INFO | supervisor[1113]/supervisor T=main | apps.c DeactivateAppContainer() 374 | Application ‘wifi’ has stopped.

Please tell me if this is what you were asking or something else? I don’t understand the UART debug message and how to do it, please point me to the correct resource to generate if this is not the one you asked. Thanks a lot!!

in my mangoh red board, if i connect UART2 during power on, it will have the debug message like this:



Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.2-00096
S - IMAGE_VARIANT_STRING=LAATANAZA
S - OEM_IMAGE_VERSION_STRING=SWI9X07Y_03.01.07.00 41ad93 jenkins 2023/03/16 10:58:16
S - Boot Config, 0x000002e1
B -      1216 - PBL, Start
B -      3720 - bootable_media_detect_entry, Start
B -      4994 - bootable_media_detect_success, Start
B -      4998 - elf_loader_entry, Start
B -      8452 - auth_hash_seg_entry, Start
B -     32162 - auth_hash_seg_exit, Start
B -     83544 - elf_segs_hash_verify_entry, Start
B -    130609 - PBL, End
B -    117516 - SBL1, Start
B -    169946 - pm_device_init, Start
B -    187270 - PM_SET_VAL:Skip
D -     16165 - pm_device_init, Delta
B -    188581 - boot_config_data_table_init, Start
D -         0 - boot_config_data_table_init, Delta - (0 Bytes)
B -    197335 - CDT version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:129
B -    204228 - sbl1_ddr_set_params, Start
B -    208040 - Pre_DDR_clock_init, Start
D -       213 - Pre_DDR_clock_init, Delta
D -         0 - sbl1_ddr_set_params, Delta
B -    220759 - pm_driver_init, Start
D -      4453 - pm_driver_init, Delta
B -    227011 - cpr_init, Start
D -       122 - cpr_init, Delta
B -    231678 - cpr_cx_mx_apc_vol_update, Start
D -        91 - cpr_cx_mx_apc_vol_update, Delta
B -    246867 - clock_init, Start
D -       152 - clock_init, Delta
B -    247111 - boot_flash_init, Start
D -     39924 - boot_flash_init, Delta
B -    290085 - boot_flash_swi_ddr_init, Start
D -     30713 - boot_flash_swi_ddr_init, Delta
B -    472567 - hw_family:5, hw_type:16, hw_rev:16
B -    475861 - cannot detect SSMEM base
B -    475922 - SSMEM bad, reinit
B -    478514 - SSMEM init OK
B -    484584 - DEBUG OU: 0000000000000002
B -    484645 - DEBUG OU - setting: 2
B -    487329 - is_memory_dump_allowed (0) in this secure module
B -    493185 - ssmem_get: region 18 not exists
B -    497363 - cannot get SSMEM fwupdate region
B -    517554 - USB non-zero endpoint requirements: 9 in, 5 out
B -    519781 - opening partition 0:SWIFOTA
B -    521336 - error for readpage:0
B -    526643 - DWL-get: ecnt=0 code=0
B -    534177 - API change: date not generated by cwe_header_init
B -    541070 - Failed to read size: /swinv/item_files/CUST_IM_SWITCH_HIDE
B -    547292 - Failed to read size: /swinv/item_files/FOTA_PARTITION
B -    548512 - Failed to read size: /swinv/item_files/CUST_IM_CONFIG
B -    560437 - flags: u=1 e=1 obmsk=c,0
B -    561749 - ssmem_get: region 21 not exists
B -    570868 - error for readpage:0
B -    571356 - error for readpage:64
B -    571997 - error for readpage:128
B -    575138 - error for readpage:192
B -    578158 - ssmem_release: region 20 not exists
B -    582824 - ssmem_get: region 20 not exists
B -    588406 - Image Load, Start
D -    145149 - QSEE Image Loaded, Delta - (930032 Bytes)
D -       213 - boot_pm_post_tz_device_init, Delta
B -    737978 - sbl1_efs_handle_cookies, Start
D -         0 - sbl1_efs_handle_cookies, Delta
B -    745938 - Image Load, Start
D -     38735 - DEVCFG Image Loaded, Delta - (31520 Bytes)
B -    784734 - Image Load, Start
D -        30 - SEC Image Loaded, Delta - (0 Bytes)
B -    791353 - Image Load, Start
D -     55571 - RPM Image Loaded, Delta - (154680 Bytes)
B -    847625 - Image Load, Start
B -    849974 - Auth disabled for image 9
B -    896212 - error for readpage:0
B -    896700 - error for readpage:64
B -    897340 - error for readpage:128
B -    900451 - error for readpage:192
B -    903501 - ssmem_release: region 20 not exists
B -    908137 - ssmem_get: region 20 not exists
D -     64782 - APPSBL Image Loaded, Delta - (440068 Bytes)
B -    917775 - QSEE Execution, Start
D -       976 - QSEE Execution, Delta
B -    924394 - SBL1, End
D -    809257 - SBL1, Delta
S - Throughput, 9000 KB/s  (1743540 Bytes,  191988 us)
S - DDR Frequency, 240 MHz
Android Bootloader - UART_DM Initialized!!!
[10] QUP: I2C status flags :0x1363c8
[10] QUP: I2C status flags :0x11163c8
[40] Board: MangOH Red
[40] ERROR: No devinfo partition found
[40] Neither 'config' nor 'frp' partition found
[50] ERROR: No misc partition found

Thanks for sharing this @jyijyi

So I already have the CON port connected and can access it to enter the AT commands via Putty:

image

So I have to debug using this port only? what command to run here? or shall I reboot the device while this is connected (I think the connection will drop if I reboot)

I suspect this is actually uart1, not uart2.

You can try

At!mapuart=17,2
At!mapuart=16,1
At!reset

Done this:

image

Reset caused the connection to drop. Reconnecting

Reconnected and checked again. Here is the output:

image

Now how to get debug message?

No idea why it is still in AT command mode …

I have checked the schematic, uart2 should be connected to this debug port, but no idea why your module kept uart2 as AT command port

I suspect you have opened the wrong port COM11

Oh ok. Thanks a lot for the help @jyijyi
Looks like I will have to give up on this. I tried but not able to find solution :frowning:
You have been super helpful in guiding and helping. Thank you!!

have you really checked if COM11 is the UART port?
Or it is the modem port from USB?

It was the modem port, listed in device manager as Modem WWAN when I connected the USB wire to CON port of the device. Isn’t that the UART2 ?

modem port is coming out from USB… not from the CN800

but it doesn’t show up in device manager until I connect the CON port on device (CN800) to the second USB slot on my laptop. Earlier it didn’t show up when I had just connected USB port of device to first USB slot on laptop.

you need to change back

AT!MAPUART=17,1
AT!MAPUART=16,2
AT!RESET