Activation Codes and Methods, Hardware Details, Sniffing
Post Reply
Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

How to use Huawei ET302s in raspberrypi

Post by Yihan » Sat Feb 01, 2020 4:33 pm

Hi, I tried to use ET302s as message dealer but I could not find any ttyUSB*, here is my rules, can anyone know how to solve it?

Code: Select all

# Huawei ET302
DefaultVendor= 0x12d1
DefaultProduct= 0x1d50
Configuration=1

LOM
Posts: 1286
Joined: Wed Jul 11, 2012 3:14 pm
Location: Koh Samui, TH

Re: How to use Huawei ET302s in raspberrypi

Post by LOM » Sat Feb 01, 2020 5:25 pm

Scrap your own rule and use the one which is included in the usb_modeswitch config files datapackage.
ET302 is a cdc_acm device so the serial interfaces will be named ttyACM0 ttyACM1 and so on.

Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

Re: How to use Huawei ET302s in raspberrypi

Post by Yihan » Sat Feb 01, 2020 5:45 pm

Thanks, I removed my own rules and reboot raspberrypi, but there were ttyAMA0 and ttyS0, no ttyACM0 . I set the port for gammu as /dev/ttyS0 or /dev/ttyAMA0, they all failed. How to find ttyACM0 and ttyACM1?

LOM
Posts: 1286
Joined: Wed Jul 11, 2012 3:14 pm
Location: Koh Samui, TH

Re: How to use Huawei ET302s in raspberrypi

Post by LOM » Sun Feb 02, 2020 2:56 am

ttyACM devices are created by the cdc_acm driver, make sure you have it in your system and if it is included as a module then make sure the module is loaded (modprobe cdc_acm , lsmod).
Your system log (dmesg) will show the cdc_acm driver binding to the ET302

Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

Re: How to use Huawei ET302s in raspberrypi

Post by Yihan » Sun Feb 02, 2020 9:31 am

Hey bro, thanks a lot, but I still failed, I successfully loaded cdc_acm with the command you provided, but there was still no any tty ttyACM*, here is the log

Code: Select all

[   98.708460] usbcore: registered new interface driver cdc_acm
[   98.708472] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
It seems cdc_acm driver did not bind ET302s, what should I do now, waiting for your reply

Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

Re: How to use Huawei ET302s in raspberrypi

Post by Yihan » Sun Feb 02, 2020 9:35 am

PS, I plug ET302s out and in again, there is the log , but there is still no ACM*

Code: Select all

[  457.351278] usb 1-1.3: USB disconnect, device number 3
[  463.178345] usb 1-1.3: new high-speed USB device number 4 using xhci_hcd
[  463.318667] usb 1-1.3: New USB device found, idVendor=12d1, idProduct=1d50, bcdDevice= 1.00
[  463.318683] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  463.318696] usb 1-1.3: Product: HUAWEI Mobile System Solution
[  463.318708] usb 1-1.3: Manufacturer: HUAWEI Mobile
[  463.318719] usb 1-1.3: SerialNumber: 000000-00-0000000
[  464.188720] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[  464.189196] scsi host0: usb-storage 1-1.3:1.0
[  465.270601] scsi 0:0:0:0: CD-ROM            HUAWEI   Mobile CMCC CD   1.00 PQ: 0 ANSI: 0
[  465.281500] sr 0:0:0:0: [sr0] scsi-1 drive
[  465.282757] sr 0:0:0:0: Attached scsi CD-ROM sr0
[  465.283395] sr 0:0:0:0: Attached scsi generic sg0 type 5
[  465.359899] scsi 0:0:0:1: Direct-Access     HUAWEI   Mobile CMCC SD   2.11 PQ: 0 ANSI: 0
[  465.360614] sd 0:0:0:1: Attached scsi generic sg1 type 0
[  465.388139] sd 0:0:0:1: [sda] Attached SCSI removable disk

LOM
Posts: 1286
Joined: Wed Jul 11, 2012 3:14 pm
Location: Koh Samui, TH

Re: How to use Huawei ET302s in raspberrypi

Post by LOM » Sun Feb 02, 2020 9:59 am

Yihan wrote:
Sun Feb 02, 2020 9:35 am
PS, I plug ET302s out and in again, there is the log , but there is still no ACM*

Code: Select all

[  464.188720] usb-storage 1-1.3:1.0: USB Mass Storage device detected
Your dongle is still in configuration#1 where there is only a storage interface, did you forget to remove your faulty config file?
You can change config from a cmdline:
sudo usb_modeswitch -v 12d1 -p 1d50 -u 2

Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

Re: How to use Huawei ET302s in raspberrypi

Post by Yihan » Sun Feb 02, 2020 10:08 am

Thanks ,I have removed, but it was just default #1, I used your cmdline, Here is the status,

Code: Select all

Look for default devices ...
 Found devices in default mode (1)
Access device 004 on bus 001
Get the current device configuration ...
Current configuration number is 2
Use interface number 0
 with class 2
Target configuration 2 already active. Nothing to do. Bye!
But when you turn to the system log, it seems there is an error when it turned into configuration#2, and thus cdc failed to load it,

Code: Select all

[ 2178.170195] usb-storage 1-1.3:2.5: USB Mass Storage device detected
[ 2178.170403] scsi host0: usb-storage 1-1.3:2.5
[ 2178.193788] cdc_wdm: probe of 1-1.3:2.3 failed with error -22
[ 2178.193817] cdc_wdm: probe of 1-1.3:2.4 failed with error -22
[ 2178.193852] usbcore: registered new interface driver cdc_wdm
[ 2178.202348] usb 1-1.3: bad CDC descriptors
[ 2178.202404] usbcore: registered new interface driver cdc_ether
[ 2179.231564] scsi 0:0:0:0: CD-ROM            HUAWEI   Mobile CMCC CD   2.00 PQ: 0 ANSI: 0
[ 2179.245312] sr 0:0:0:0: [sr0] scsi-1 drive
[ 2179.246361] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 2179.246743] sr 0:0:0:0: Attached scsi generic sg0 type 5
[ 2179.308855] scsi 0:0:0:1: Direct-Access     HUAWEI   Mobile CMCC SD   2.11 PQ: 0 ANSI: 0
[ 2179.309696] sd 0:0:0:1: Attached scsi generic sg1 type 0
[ 2179.324986] sd 0:0:0:1: [sda] Attached SCSI removable disk

Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

Re: How to use Huawei ET302s in raspberrypi

Post by Yihan » Sun Feb 02, 2020 10:09 am

PS , your cmdline successfully turned ET302s into configuration #2, the cmdline result is the second time result

LOM
Posts: 1286
Joined: Wed Jul 11, 2012 3:14 pm
Location: Koh Samui, TH

Re: How to use Huawei ET302s in raspberrypi

Post by LOM » Sun Feb 02, 2020 11:12 am

I've read your PM but sorry I don't do privaste support, only here in the forum so other user can see it and maybe learn something from it.

The errors in your system log for interface#3 and #4 is because they have attributes saying that they are cdc_acm interfaces but they are not, they are probably single serial interfaces which would have created ttyUSB devices if there had been a linux driver for them.
Interface #5 is a storage interface probably for a built in TF/SD card reader in the dongle and it looks to be ok.

Interface #1 and #2 on the other hand are a cdc_acm pair and should have created the modem device ttyACM0, you cut the log short so I can't see what happened with them. Check the log again and check if there is a /dev/ttyACM0.

Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

Re: How to use Huawei ET302s in raspberrypi

Post by Yihan » Sun Feb 02, 2020 11:32 am

Thanks, it's nice to post the process in the forum. In fact, it's the old post attract me here. As for the short log, I'm sure I have removed all rules and then reboot the raspberry pi and only ET302s is plugged in, I
reproduced all the processes and here is the total log.

At first, I loaded cdc_acm mod, then is this command:

sudo usb_modeswitch -v 12d1 -p 1d50 -u 2

here is the switch result:

Code: Select all

Look for default devices ...
 Found devices in default mode (1)
Access device 003 on bus 001
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 8
Bogus Class/InterfaceClass: 0x02/0x08
Change configuration to 2 ...
Looking for active drivers ...
 OK, driver detached
 OK, configuration set
Get the current device configuration ...
The configuration was set successfully
-> Run lsusb to note any changes. Bye!
and here is the total system log,

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.75-v7l+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG 
crosstool-ng-1.22.0-88-g8460611)) #1270 SMP Tue Sep 24 18:51:41 BST 2019
[    0.000000] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 256 MiB at 0x000000001ec00000
[    0.000000] On node 0 totalpages: 1012736
[    0.000000]   DMA zone: 1728 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 196608 pages, LIFO batch:63
[    0.000000]   HighMem zone: 816128 pages, LIFO batch:63
[    0.000000] random: get_random_bytes called from start_kernel+0xc0/0x4e8 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu s39488 r8192 d21952 u69632
[    0.000000] pcpu-alloc: s39488 r8192 d21952 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1011008
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-
A-1:1920x1080M@60,margin_left=0,margin_right=0,margin_top=0,margin_bottom=0 smsc95xx.macaddr=DC:A6:32:17:7A:D7
 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=tty1 console=ttyS0,115200 root=PARTUUID=d9b3f436-02
  rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 3735592K/4050944K available (8192K kernel code, 661K rwdata, 2352K rodata, 2048K init, 850K bss,
 53208K reserved, 262144K cma-reserved, 3264512K highmem)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
                   lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0x(ptrval) - 0x(ptrval)   (10208 kB)
                     .init : 0x(ptrval) - 0x(ptrval)   (2048 kB)
                     .data : 0x(ptrval) - 0x(ptrval)   ( 662 kB)
                      .bss : 0x(ptrval) - 0x(ptrval)   ( 851 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 28124 entries in 83 pages
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns
[    0.000005] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
[    0.000018] Switching to timer-based delay loop, resolution 18ns
[    0.000237] Console: colour dummy device 80x30
[    0.000261] console [tty1] enabled
[    0.000305] Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=540000)
[    0.000327] pid_max: default: 32768 minimum: 301
[    0.000584] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000601] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001330] CPU: Testing write buffer coherency: ok
[    0.001732] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002364] Setting up static identity map for 0x200000 - 0x20003c
[    0.002519] rcu: Hierarchical SRCU implementation.
[    0.003365] smp: Bringing up secondary CPUs ...
[    0.004233] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.005231] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.006189] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.006321] smp: Brought up 1 node, 4 CPUs
[    0.006334] SMP: Total of 4 processors activated (432.00 BogoMIPS).
[    0.006344] CPU: All CPU(s) started in HYP mode.
[    0.006352] CPU: Virtualization extensions available.
[    0.007121] devtmpfs: initialized
[    0.017437] VFP support v0.3: implementor 41 architecture 3 part 40 variant 8 rev 0
[    0.017636] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.017656] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.025149] pinctrl core: initialized pinctrl subsystem
[    0.025980] NET: Registered protocol family 16
[    0.028740] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.030208] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.030218] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.030410] Serial: AMBA PL011 UART driver
[    0.033444] bcm2835-mbox fe00b880.mailbox: mailbox enabled
[    0.069298] bcm2835-dma fe007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
[    0.071699] vgaarb: loaded
[    0.072072] SCSI subsystem initialized
[    0.072260] usbcore: registered new interface driver usbfs
[    0.072318] usbcore: registered new interface driver hub
[    0.072413] usbcore: registered new device driver usb
[    0.090393] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-09-24 17:34, variant start
[    0.100119] raspberrypi-firmware soc:firmware: Firmware hash is cd3add54955f8fa065b414d8fc07c525e7ddffc8
[    0.111642] clocksource: Switched to clocksource arch_sys_counter
[    0.188775] VFS: Disk quotas dquot_6.6.0
[    0.188850] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.188996] FS-Cache: Loaded
[    0.189170] CacheFiles: Loaded
[    0.189714] simple-framebuffer 3e7fe000.framebuffer: framebuffer at 0x3e7fe000, 0x3fc000 bytes, mapped to 0x(ptrval)
[    0.189729] simple-framebuffer 3e7fe000.framebuffer: format=r5g6b5, mode=1920x1080x16, linelength=3840
[    0.197075] Console: switching to colour frame buffer device 240x67
[    0.203758] simple-framebuffer 3e7fe000.framebuffer: fb0: simplefb registered!
[    0.212730] NET: Registered protocol family 2
[    0.213367] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.213391] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.213462] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.213532] TCP: Hash tables configured (established 8192 bind 8192)
[    0.213642] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.213669] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.213954] NET: Registered protocol family 1
[    0.214483] RPC: Registered named UNIX socket transport module.
[    0.214493] RPC: Registered udp transport module.
[    0.214502] RPC: Registered tcp transport module.
[    0.214511] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.214526] PCI: CLS 0 bytes, default 64
[    0.217548] Initialise system trusted keyrings
[    0.217722] workingset: timestamp_bits=14 max_order=20 bucket_order=6
[    0.226585] FS-Cache: Netfs 'nfs' registered for caching
[    0.227068] NFS: Registering the id_resolver key type
[    0.227115] Key type id_resolver registered
[    0.227124] Key type id_legacy registered
[    0.227143] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.229338] Key type asymmetric registered
[    0.229349] Asymmetric key parser 'x509' registered
[    0.229457] bounce: pool size: 64 pages
[    0.229495] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.229650] io scheduler noop registered
[    0.229661] io scheduler deadline registered (default)
[    0.229808] io scheduler cfq registered
[    0.229819] io scheduler mq-deadline registered (default)
[    0.229828] io scheduler kyber registered
[    0.253624] brcm-pcie fd500000.pcie: dmabounce: initialised - 32768 kB, threshold 0x00000000c0000000
[    0.253643] brcm-pcie fd500000.pcie: could not get clock
[    0.253702] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[    0.253738] brcm-pcie fd500000.pcie:   MEM 0x600000000..0x603ffffff -> 0xf8000000
[    0.311678] brcm-pcie fd500000.pcie: link up, 5.0 Gbps x1 (!SSC)
[    0.311928] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
[    0.311944] pci_bus 0000:00: root bus resource [bus 00-01]
[    0.311972] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])
[    0.312015] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
[    0.312153] pci 0000:00:00.0: PME# supported from D0 D3hot
[    0.314882] PCI: bus0: Fast back to back transfers disabled
[    0.314899] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.315061] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
[    0.315120] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.315284] pci 0000:01:00.0: PME# supported from D0 D3cold
[    0.317939] PCI: bus1: Fast back to back transfers disabled
[    0.317955] pci_bus 0000:01: busn_res: [bus 01] end is updated to 01
[    0.318001] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
[    0.318020] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
[    0.318049] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.318067] pci 0000:00:00.0:   bridge window [mem 0x600000000-0x6000fffff]
[    0.318278] pcieport 0000:00:00.0: enabling device (0140 -> 0142)
[    0.318444] pcieport 0000:00:00.0: Signaling PME with IRQ 56
[    0.318597] pcieport 0000:00:00.0: AER enabled with IRQ 56
[    0.318733] pci 0000:01:00.0: enabling device (0140 -> 0142)
[    0.320486] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    0.322471] iproc-rng200 fe104000.rng: hwrng registered
[    0.322692] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.323180] vc-sm: Videocore shared memory driver
[    0.323566] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
[    0.333295] brd: module loaded
[    0.342724] loop: module loaded
[    0.343470] Loading iSCSI transport class v2.0-870.
[    0.345113] libphy: Fixed MDIO Bus: probed
[    0.345523] bcmgenet fd580000.genet: failed to get enet clock
[    0.345539] bcmgenet fd580000.genet: GENET 5.0 EPHY: 0x0000
[    0.345556] bcmgenet fd580000.genet: failed to get enet-wol clock
[    0.345571] bcmgenet fd580000.genet: failed to get enet-eee clock
[    0.345594] bcmgenet: Skipping UMAC reset
[    0.345816] unimac-mdio unimac-mdio.-19: DMA mask not set
[    0.361672] libphy: bcmgenet MII bus: probed
[    0.402157] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus at 0x(ptrval)
[    0.403028] usbcore: registered new interface driver r8152
[    0.403087] usbcore: registered new interface driver lan78xx
[    0.403145] usbcore: registered new interface driver smsc95xx
[    0.403344] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    0.403373] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[    0.405449] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000001000000890
[    0.405613] genirq: irq_chip Brcm_MSI did not update eff. affinity mask of irq 57
[    0.406224] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.406238] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.406250] usb usb1: Product: xHCI Host Controller
[    0.406260] usb usb1: Manufacturer: Linux 4.19.75-v7l+ xhci-hcd
[    0.406271] usb usb1: SerialNumber: 0000:01:00.0
[    0.406773] hub 1-0:1.0: USB hub found
[    0.406824] hub 1-0:1.0: 1 port detected
[    0.407229] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    0.407251] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    0.407269] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    0.407603] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    0.407615] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.407626] usb usb2: Product: xHCI Host Controller
[    0.407637] usb usb2: Manufacturer: Linux 4.19.75-v7l+ xhci-hcd
[    0.407647] usb usb2: SerialNumber: 0000:01:00.0
[    0.408128] hub 2-0:1.0: USB hub found
[    0.408186] hub 2-0:1.0: 4 ports detected
[    0.409267] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.434825] dwc_otg fe980000.usb: base=(ptrval)
[    0.635164] Core Release: 2.80a
[    0.635177] Setting default values for core params
[    0.635203] Finished setting default values for core params
[    0.835523] Using Buffer DMA mode
[    0.835533] Periodic Transfer Interrupt Enhancement - disabled
[    0.835542] Multiprocessor Interrupt Enhancement - disabled
[    0.835553] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.835609] Dedicated Tx FIFOs mode
[    0.836153] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = ded34000 dma = 0x00000000ded34000 len=9024
[    0.836175] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.836187] dwc_otg: Microframe scheduler enabled
[    0.836249] WARN::hcd_init_fiq:457: FIQ on core 1
[    0.836266] WARN::hcd_init_fiq:458: FIQ ASM at c07b6224 length 36
[    0.836283] WARN::hcd_init_fiq:497: MPHI regs_base at f0810200
[    0.836317] dwc_otg fe980000.usb: DWC OTG Controller
[    0.836345] dwc_otg fe980000.usb: new USB bus registered, assigned bus number 3
[    0.836377] dwc_otg fe980000.usb: irq 38, io mem 0x00000000
[    0.836426] Init: Port Power? op_state=1
[    0.836435] Init: Power Port (0)
[    0.836690] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.836703] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.836715] usb usb3: Product: DWC OTG Controller
[    0.836725] usb usb3: Manufacturer: Linux 4.19.75-v7l+ dwc_otg_hcd
[    0.836736] usb usb3: SerialNumber: fe980000.usb
[    0.837239] hub 3-0:1.0: USB hub found
[    0.837287] hub 3-0:1.0: 1 port detected
[    0.837869] dwc_otg: FIQ enabled
[    0.837878] dwc_otg: NAK holdoff enabled
[    0.837887] dwc_otg: FIQ split-transaction FSM enabled
[    0.837900] Module dwc_common_port init
[    0.838101] usbcore: registered new interface driver uas
[    0.838210] usbcore: registered new interface driver usb-storage
[    0.838366] mousedev: PS/2 mouse device common for all mice
[    0.839525] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    0.839710] bcm2835-cpufreq: min=600000 max=1500000
[    0.840253] sdhci: Secure Digital Host Controller Interface driver
[    0.840262] sdhci: Copyright(c) Pierre Ossman
[    0.840647] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe
[    0.841038] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.844056] ledtrig-cpu: registered to indicate activity on CPUs
[    0.844194] hidraw: raw HID events driver (C) Jiri Kosina
[    0.844315] usbcore: registered new interface driver usbhid
[    0.844324] usbhid: USB HID core driver
[    0.845019] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[    0.846314] [vc_sm_connected_init]: start
[    0.852632] [vc_sm_connected_init]: end - returning 0
[    0.853695] Initializing XFRM netlink socket
[    0.853722] NET: Registered protocol family 17
[    0.853808] Key type dns_resolver registered
[    0.854189] Registering SWP/SWPB emulation handler
[    0.854761] registered taskstats version 1
[    0.854776] Loading compiled-in X.509 certificates
[    0.862463] uart-pl011 fe201000.serial: cts_event_workaround enabled
[    0.862525] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 34, base_baud = 0) is a PL011 rev2
[    0.865742] console [ttyS0] disabled
[    0.865774] fe215040.serial: ttyS0 at MMIO 0x0 (irq = 36, base_baud = 62500000) is a 16550
[    0.865829] console [ttyS0] enabled
[    0.866249] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    0.866751] brcmstb_thermal fd5d2200.thermal: registered AVS TMON of-sensor driver
[    0.867354] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    0.867366] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
[    0.892217] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1
[    0.910411] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.912112] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.913701] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.916597] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.918183] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.926909] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA
[    0.929331] of_cfs_init
[    0.929410] of_cfs_init: OK
[    0.930163] Waiting for root device PARTUUID=d9b3f436-02...
[    0.974563] random: fast init done
[    0.981750] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    0.986212] mmc1: new high speed SDIO card at address 0001
[    1.033056] mmc0: new ultra high speed DDR50 SDXC card at address aaaa
[    1.034105] mmcblk0: mmc0:aaaa SC128 119 GiB
[    1.036295]  mmcblk0: p1 p2
[    1.056520] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.056562] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.057225] devtmpfs: mounted
[    1.063483] Freeing unused kernel memory: 2048K
[    1.091896] Run /sbin/init as init process
[    1.173234] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.20
[    1.173249] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.173261] usb 1-1: Product: USB2.0 Hub
[    1.174826] hub 1-1:1.0: USB hub found
[    1.175065] hub 1-1:1.0: 4 ports detected
[    1.453699] systemd[1]: System time before build time, advancing clock.
[    1.542116] NET: Registered protocol family 10
[    1.543300] Segment Routing with IPv6
[    1.574805] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    1.575457] systemd[1]: Detected architecture arm.
[    1.583213] systemd[1]: Set hostname to <Pi>.
[    1.588508] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
[    1.888644] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any),
 but the local system does not support BPF/cgroup based firewalling.
[    1.888665] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[    2.050493] systemd[1]: /etc/systemd/system/teamviewerd.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/teamviewerd.pid → /run/teamviewerd.pid; please update the unit file accordingly.
[    2.245041] random: systemd: uninitialized urandom read (16 bytes read)
[    2.253923] random: systemd: uninitialized urandom read (16 bytes read)
[    2.253994] systemd[1]: Reached target Swap.
[    2.254335] random: systemd: uninitialized urandom read (16 bytes read)
[    2.254616] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.259792] systemd[1]: Created slice system-getty.slice.
[    2.360794] i2c /dev entries driver
[    2.975531] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.075402] systemd-journald[115]: Received request to flush runtime journal from PID 1
[    3.692872] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x0000ffff
[    3.695611] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00000fff
[    3.696501] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x0000ffff
[    3.702461] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x0000ffff
[    3.896211] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    3.919011] bcm2835_audio soc:audio: card created with 8 channels
[    3.926097] media: Linux media interface: v0.10
[    3.926583] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    3.928483] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    3.928498] [vc_sm_connected_init]: start
[    3.935619] [vc_sm_connected_init]: installed successfully
[    3.967873] videodev: Linux video capture interface: v2.00
[    4.016006] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    4.021111] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    4.021935] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    4.024902] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
[    4.051306] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    4.116363] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    4.116397] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[    4.123244] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    4.123275] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[    4.133117] vc4-drm soc:gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
[    4.133135] checking generic (3e7fe000 3fc000) vs hw (0 ffffffffffffffff)
[    4.133145] fb: switching to vc4drmfb from simple
[    4.133356] Console: switching to colour dummy device 80x30
[    4.134281] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1
[    4.134292] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    4.134302] [drm] No driver support for vblank timestamp query.
[    4.134311] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL
[    4.136645] vc4-drm soc:gpu: HDMI-A-1: EDID is invalid:
[    4.136661] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    4.136671] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    4.136680] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    4.136689] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    4.136698] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    4.136707] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    4.136716] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    4.136725] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    4.147051] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[    4.147097] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[    4.290935] Console: switching to colour frame buffer device 240x67
[    4.312464] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    4.326509] vc4-drm soc:gpu: fb0: DRM emulated frame buffer device
[    4.433539] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    4.507848] brcmfmac: F1 signature read @0x18000000=0x15264345
[    4.521922] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    4.522637] usbcore: registered new interface driver brcmfmac
[    4.738320] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    4.753645] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32
 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[    5.541730] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd
[    5.682621] usb 1-1.3: New USB device found, idVendor=12d1, idProduct=1d50, bcdDevice= 1.00
[    5.682640] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    5.682663] usb 1-1.3: Product: HUAWEI Mobile System Solution
[    5.682680] usb 1-1.3: Manufacturer: HUAWEI Mobile
[    5.682691] usb 1-1.3: SerialNumber: 000000-00-0000000
[    6.457346] uart-pl011 fe201000.serial: no DMA platform data
[    6.575515] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[    6.612435] random: crng init done
[    6.612452] random: 7 urandom warning(s) missed due to ratelimiting
[    6.622476] scsi host0: usb-storage 1-1.3:1.0
[    6.799956] 8021q: 802.1Q VLAN Support v1.8
[    7.040146] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[    7.094173] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    7.094183] brcmfmac: power management disabled
[    7.405487] bcmgenet: Skipping UMAC reset
[    7.501928] bcmgenet fd580000.genet: configuring instance for external RGMII (no delay)
[    7.502076] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    7.673855] scsi 0:0:0:0: CD-ROM            HUAWEI   Mobile CMCC CD   1.00 PQ: 0 ANSI: 0
[    7.680379] scsi 0:0:0:1: Direct-Access     HUAWEI   Mobile CMCC SD   2.11 PQ: 0 ANSI: 0
[    7.689317] sd 0:0:0:1: [sda] Attached SCSI removable disk
[    7.725310] scsi 0:0:0:0: Attached scsi generic sg0 type 5
[    7.725425] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    7.753153] sr 0:0:0:0: [sr0] scsi-1 drive
[    7.753160] cdrom: Uniform CD-ROM driver Revision: 3.20
[    7.755166] sr 0:0:0:0: Attached scsi CD-ROM sr0
[    8.551860] bcmgenet fd580000.genet eth0: Link is Down
[   11.632616] fuse init (API version 7.27)
[   11.671813] bcmgenet fd580000.genet eth0: Link is Up - 1Gbps/Full - flow control off
[   11.671836] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   13.127540] Bluetooth: Core ver 2.22
[   13.127582] NET: Registered protocol family 31
[   13.127587] Bluetooth: HCI device and connection manager initialized
[   13.127598] Bluetooth: HCI socket layer initialized
[   13.127605] Bluetooth: L2CAP socket layer initialized
[   13.127623] Bluetooth: SCO socket layer initialized
[   13.148609] Bluetooth: HCI UART driver ver 2.3
[   13.148618] Bluetooth: HCI UART protocol H4 registered
[   13.149086] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   13.149197] Bluetooth: HCI UART protocol Broadcom registered
[   13.442283] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.442291] Bluetooth: BNEP filters: protocol multicast
[   13.442304] Bluetooth: BNEP socket layer initialized
[   13.503327] Bluetooth: RFCOMM TTY layer initialized
[   13.503343] Bluetooth: RFCOMM socket layer initialized
[   13.503359] Bluetooth: RFCOMM ver 1.11
[  186.468498] usbcore: registered new interface driver cdc_acm
[  186.468509] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[  201.766413] usb-storage 1-1.3:2.5: USB Mass Storage device detected
[  201.774791] scsi host0: usb-storage 1-1.3:2.5
[  201.828405] cdc_wdm: probe of 1-1.3:2.3 failed with error -22
[  201.828466] cdc_wdm: probe of 1-1.3:2.4 failed with error -22
[  201.828542] usbcore: registered new interface driver cdc_wdm
[  201.835166] usb 1-1.3: bad CDC descriptors
[  201.835296] usbcore: registered new interface driver cdc_ether
[  202.796499] scsi 0:0:0:0: CD-ROM            HUAWEI   Mobile CMCC CD   2.00 PQ: 0 ANSI: 0
[  202.809527] sr 0:0:0:0: [sr0] scsi-1 drive
[  202.810692] sr 0:0:0:0: Attached scsi CD-ROM sr0
[  202.811145] sr 0:0:0:0: Attached scsi generic sg0 type 5
[  202.855803] scsi 0:0:0:1: Direct-Access     HUAWEI   Mobile CMCC SD   2.11 PQ: 0 ANSI: 0
[  202.856497] sd 0:0:0:1: Attached scsi generic sg1 type 0
[  202.877419] sd 0:0:0:1: [sda] Attached SCSI removable disk
There is still no ACM* , only ttyAMA0, ttyprintk and ttyS0.

Besides, according to other post I searched these days, I tried to install Huawei Linux driver but failed, I tried the solution https://askubuntu.com/questions/323031/ ... nd-devices but it did not work, it's all the message I know, do you need any other message? If so, please tell me

LOM
Posts: 1286
Joined: Wed Jul 11, 2012 3:14 pm
Location: Koh Samui, TH

Re: How to use Huawei ET302s in raspberrypi

Post by LOM » Sun Feb 02, 2020 2:05 pm

This is a very weird device and also very old and low-speed.
The specification says TD-SCDMA which is something China Mobile invented and built 12-13 years ago but are you sure that there is still a Chinese Mobile Provider using that standard today?

If there is then we should try to force one of linux other serial driver to bind to it instead of cdc_acm.

Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

Re: How to use Huawei ET302s in raspberrypi

Post by Yihan » Sun Feb 02, 2020 2:31 pm

Thanks for your continuous help.

Yeap, I'm sure. I tried this device in Windows and Mac(Mojave), Now my mac is Catalina, which does not support 32-bit app,
but in windows10 it still works(I tried yesterday and received several messages from China Mobile saying I'm to be out of money for this sim-card).

My aim for this device is to receive and send messages, because my iphone does not support a second sim-card, so the speed is not question.

So, what should we do to force one of linux other serial driver to bind to it instead of cdc_acm?

Besides, if we succeed to make it work in linux, I'll must write a blog and a post about these for other people's reference.
And it's also a good opportunity for me to learn hardware

LOM
Posts: 1286
Joined: Wed Jul 11, 2012 3:14 pm
Location: Koh Samui, TH

Re: How to use Huawei ET302s in raspberrypi

Post by LOM » Sun Feb 02, 2020 3:23 pm

ok, so after you have selected config#2 then:

sudo modprobe usb_wwan
sudo modprobe usbserial
sudo modprobe option

sudo echo "12d1 1d50" >/sys/bus/usb-serial/drivers/option1/new_id

and then check your system log for creation of one or maybe two ttyUSB devices.
ttyUSB0 is likely the dial-up modem device.

Yihan
Posts: 9
Joined: Sat Feb 01, 2020 3:43 pm

Re: How to use Huawei ET302s in raspberrypi

Post by Yihan » Sun Feb 02, 2020 3:46 pm

Wow! That's great, I found ttyUSB, but unfortunately there is only ttyUSB2, here is the system log:

Code: Select all

[  202.877419] sd 0:0:0:1: [sda] Attached SCSI removable disk(This is the last of the log I pasted before )
[15591.800122] usbcore: registered new interface driver usbserial_generic
[15591.800186] usbserial: USB Serial support registered for generic
[15601.120530] usbcore: registered new interface driver option
[15601.120606] usbserial: USB Serial support registered for GSM modem (1-port)
[15608.289817] option 1-1.3:2.0: GSM modem (1-port) converter detected
[15608.290320] option 1-1.3:2.1: GSM modem (1-port) converter detected
[15608.290754] option 1-1.3:2.2: GSM modem (1-port) converter detected
[15608.291078] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB2
[15608.291446] option 1-1.3:2.3: GSM modem (1-port) converter detected
[15608.292211] option 1-1.3:2.4: GSM modem (1-port) converter detected
I tried to set USB2 as the prot, wait....

Wow!!!!!!!!!!!! Great!!!!!!! Thanks !!!!!!!!!!! ,I succeed to send a message !!!!!!!!

I'm really grateful, thank you! I have failed for nearly a whole week! Thank you, really,
after I successfully set this device for receive message, I'll summerize and write a blog and a post for following people's reference.

Post Reply