Re: connecting Huawei E173 to Beaglebone and using minicom

[Ali Muhammad Ali]

Hey,

       I also want to do the same in near future on my project. Can you access internet. Sorry, rather than giving solution I am asking a question.

Regards,

Ali

On Friday, 14 September 2012 01:00:21 UTC+5, wisam wrote:

Hi,
i am new with BeagleBone, I have GSM modem Huawei E173 which is work fine with my PC(Ubuntu). I am using this modem only to send SMS. but it does not work with my beaglebone(Angstrom). every time I  open Minicom I have the following:

root@beaglebone:~# minicom
minicom: cannot open /dev/ttyS5: No such file or directory

its keep have ttyS5!! even when I change it to any other such as ttyS0, ttyS1 .......

When I use minicom -s and change the ttyS to ex. ttyS2 and save, exit I have the following:

Welcome to minicom 2.6.1

OPTIONS: I18n                                                               
Compiled on Apr 25 2012, 11:51:01.                                          
Port /dev/ttyS2                                                             
                                                                            
Press CTRL-A Z for help on special keys


I can not write any AT command or any text!!!
Please any help?

[wisam]

if you mean connected your beaglebone to the internet via Ethernet cable, if so , yes, just connect the cable and on your pc write the following:
majid@ubuntu:~$ ssh 192.168.xx.xxx -l root
ro...@192.168.xx.xxx's password:   "here you write the password which is root"
whrer xx.xxx is the ip edress for you beaglebone.
then you will be in connect with your beaglebone from your pc via internet.

[Ali Muhammad Ali]

Hi,

I am connected to internet using ethernet but I am asking you about the modem you are using. It also has broadcom internet facility.

By the way thanks for replying

Regards,

Ali

--
 
 

[wisam]

oh, ok , actually i did not try to use the modem for internet connection, i just need to use it as GSM/GPRS to send the SMS/MMS only.

[praveen prasad]

hai ,

          if you only want to send sms then its simple if you go with a gsm module  example : sim300. using AT commands you can send sms to mobile

--
 
 

[wisam]

I want to send SMS by E173 modem, but i cannot make it work with Beaglebone.

[praveen prasad]

E172, is it a huwai modem, an are u able to get a minicom window using beaglebone

--
 
 

[wisam]

E173 is Huawei modem, the problem is when I inter the minicom window the modem is keeping offline and I can not write any AT command.

[praveen prasad]

have u changed the default device name of  your minicom ,by using dmesg command u can know your device name

--
 
 

[wisam]

The problem is there is no ttyUSB0 .....ttyUSB3 as in ubuntu,
this is the result of dmesg (sorry for long details),
root@beaglebone:~# dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.1.0+ (koen@dominion) (gcc version 4.5.4 20111126 (prerelease) (GCC) ) #1 Fri Jan 6 11:31:55 CET 2012
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c53c7f
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: am335xevm
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c047bbe8, node_mem_map c04c2000
[    0.000000]   Normal zone: 512 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 65024 pages, LIFO batch:15
[    0.000000] AM335X ES1.0 (neon )
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyO0,115200n8 run_hardware_tests quiet root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait ip=none
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] allocated 1048576 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 253964k/253964k available, 8180k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xffa00000 - 0xffe00000   (   4 MB)
[    0.000000]     vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf800000 - 0xc0000000   (   8 MB)
[    0.000000]       .text : 0xc0008000 - 0xc03fc6e4   (4050 kB)
[    0.000000]       .init : 0xc03fd000 - 0xc0431000   ( 208 kB)
[    0.000000]       .data : 0xc0432000 - 0xc047c6c0   ( 298 kB)
[    0.000000]        .bss : 0xc047c6e4 - 0xc04c12e0   ( 275 kB)
[    0.000000] NR_IRQS:410 nr_irqs:410 410
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] Total of 128 interrupts on 1 active controller
[    0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz
[    0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] Console: colour dummy device 80x30
[    0.000171] Calibrating delay loop... 718.02 BogoMIPS (lpj=3590144)
[    0.059036] pid_max: default: 32768 minimum: 301
[    0.059157] Security Framework initialized
[    0.059214] Mount-cache hash table entries: 512
[    0.059543] Initializing cgroup subsys cpuacct
[    0.059572] Initializing cgroup subsys memory
[    0.059604] Initializing cgroup subsys devices
[    0.059615] Initializing cgroup subsys freezer
[    0.059625] Initializing cgroup subsys blkio
[    0.059646] Initializing cgroup subsys perf_event
[    0.059721] CPU: Testing write buffer coherency: ok
[    0.060628] devtmpfs: initialized
[    0.063956] print_constraints: dummy:
[    0.064155] NET: Registered protocol family 16
[    0.064301] GPMC revision 6.0
[    0.065115] OMAP GPIO hardware version 0.1
[    0.065824] omap_l3_smx omap_l3_smx.0: couldn't find resource
[    0.065901] omap_mux_init: Add partition: #1: core, flags: 0
[    0.067798]  omap_i2c.1: alias fck already exists
[    0.067982] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.068331]  omap2_mcspi.1: alias fck already exists
[    0.068420]  omap2_mcspi.2: alias fck already exists
[    0.074990] bio: create slab <bio-0> at 0
[    0.075921] SCSI subsystem initialized
[    0.076578] usbcore: registered new interface driver usbfs
[    0.076676] usbcore: registered new interface driver hub
[    0.076817] usbcore: registered new device driver usb
[    0.077449] omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
[    0.078159] Advanced Linux Sound Architecture Driver Version 1.0.24.
[    0.078596] Switching to clocksource gp timer
[    0.079106] Switched to NOHz mode on CPU #0
[    0.087464] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    0.087608] musb-hdrc musb-hdrc.0: dma type: pio
[    0.087769] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    0.087789] musb-hdrc: MHDRC RTL version 2.0
[    0.087799] musb-hdrc: setup fifo_mode 4
[    0.087820] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    0.088080] musb-hdrc musb-hdrc.0: USB OTG mode controller at d080a000 using PIO, IRQ 18
[    0.088315] musb-hdrc musb-hdrc.1: dma type: pio
[    0.088441] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    0.088458] musb-hdrc: MHDRC RTL version 2.0
[    0.088467] musb-hdrc: setup fifo_mode 4
[    0.088486] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    0.088780] musb-hdrc musb-hdrc.1: USB OTG mode controller at d080c800 using PIO, IRQ 19
[    0.089075] NET: Registered protocol family 2
[    0.089245] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.089594] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.089750] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.089844] TCP: Hash tables configured (established 8192 bind 8192)
[    0.089856] TCP reno registered
[    0.089868] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.089891] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.090126] NET: Registered protocol family 1
[    0.090424] RPC: Registered named UNIX socket transport module.
[    0.090437] RPC: Registered udp transport module.
[    0.090446] RPC: Registered tcp transport module.
[    0.090455] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.090688] omap_init_opp_table: no hwmod or odev for iva, [8] cannot add OPPs.
[    0.101369] VFS: Disk quotas dquot_6.5.2
[    0.101430] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.102479] msgmni has been set to 496
[    0.103342] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.103427] io scheduler noop registered
[    0.103437] io scheduler deadline registered
[    0.103490] io scheduler cfq registered (default)
[    0.104305] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.105315] omap_uart.0: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
[    0.111508] console [ttyO0] enabled
[    0.111827] omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
[    0.112070] omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
[    0.112292] omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
[    0.112501] omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
[    0.112714] omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
[    0.113822] brd: module loaded
[    0.116733] loop: module loaded
[    0.116801] at24 1-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.188632] No daughter card found
[    0.188679] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.196609] Board name: A335BONE
[    0.196619] Board version: 00A6
[    0.196627] The board is a AM335x Beaglebone.
[    0.197333] da8xx_lcdc da8xx_lcdc.0: GLCD: Found 1024x768@60 panel
[    0.212651] Console: switching to colour frame buffer device 128x48
[    0.222973]  omap_i2c.3: alias fck already exists
[    0.223231] omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz
[    0.223778]  omap_hsmmc.0: alias fck already exists
[    0.224040] _omap_mux_get_by_name: Could not find signal leds-gpio
[    0.230980] at24 3-0054: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.231016] at24 3-0055: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.231047] at24 3-0056: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.231078] at24 3-0057: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.231642] SCSI Media Changer driver v0.25
[    0.278658] davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
[    0.278673] davinci_mdio davinci_mdio.0: detected phy mask fffffffe
[    0.279545] davinci_mdio.0: probed
[    0.279563] davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver SMSC LAN8710/LAN8720
[    0.279948] usbcore: registered new interface driver catc
[    0.279959] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
[    0.280010] usbcore: registered new interface driver kaweth
[    0.280023] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
[    0.280075] usbcore: registered new interface driver pegasus
[    0.280086] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver
[    0.280135] usbcore: registered new interface driver rtl8150
[    0.280186] usbcore: registered new interface driver asix
[    0.280236] usbcore: registered new interface driver cdc_ether
[    0.280288] usbcore: registered new interface driver dm9601
[    0.280339] usbcore: registered new interface driver cdc_subset
[    0.280390] usbcore: registered new interface driver zaurus
[    0.280435] cdc_ncm: 04-Aug-2011
[    0.280485] usbcore: registered new interface driver cdc_ncm
[    0.280578] usbcore: registered new interface driver cdc_acm
[    0.280589] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    0.280671] usbcore: registered new interface driver usblp
[    0.280726] usbcore: registered new interface driver cdc_wdm
[    0.280779] usbcore: registered new interface driver uas
[    0.280789] Initializing USB Mass Storage driver...
[    0.280856] usbcore: registered new interface driver usb-storage
[    0.280866] USB Mass Storage support registered.
[    0.280935] usbcore: registered new interface driver libusual
[    0.281004] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[    0.281082] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
[    0.281195] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.281210] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.281224] usb usb1: Product: MUSB HDRC host driver
[    0.281234] usb usb1: Manufacturer: Linux 3.1.0+ musb-hcd
[    0.281245] usb usb1: SerialNumber: musb-hdrc.1
[    0.281884] hub 1-0:1.0: USB hub found
[    0.281910] hub 1-0:1.0: 1 port detected
[    0.282594] mousedev: PS/2 mouse device common for all mice
[    0.283074] dev addr = c044ea20
[    0.283084] pdev addr = c044ea18
[    0.283639] omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
[    0.283671] omap_rtc: already running
[    0.283784] i2c /dev entries driver
[    0.284160] Linux media interface: v0.10
[    0.284298] lirc_dev: IR Remote Control driver registered, major 249
[    0.284312] IR NEC protocol handler initialized
[    0.284321] IR RC5(x) protocol handler initialized
[    0.284330] IR RC6 protocol handler initialized
[    0.284338] IR JVC protocol handler initialized
[    0.284347] IR Sony protocol handler initialized
[    0.284356] IR RC5 (streamzap) protocol handler initialized
[    0.284365] IR MCE Keyboard/mouse protocol handler initialized
[    0.284375] IR LIRC bridge handler initialized
[    0.284383] Linux video capture interface: v2.00
[    0.284520] usbcore: registered new interface driver uvcvideo
[    0.284530] USB Video Class driver (1.1.1)
[    0.284594] Driver for 1-wire Dallas network protocol.
[    0.285373] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    0.286244] Registered led device: beaglebone::usr0
[    0.286345] Registered led device: beaglebone::usr1
[    0.286427] Registered led device: beaglebone::usr2
[    0.286503] Registered led device: beaglebone::usr3
[    0.286577] Registered led device: dvi::usr0
[    0.286650] Registered led device: dvi::usr1
[    0.286971] usbcore: registered new interface driver usbhid
[    0.286982] usbhid: USB HID core driver
[    0.287467] usbcore: registered new interface driver snd-usb-audio
[    0.287885] ALSA device list:
[    0.287894]   No soundcards found.
[    0.288269] TCP cubic registered
[    0.288279] Initializing XFRM netlink socket
[    0.288300] NET: Registered protocol family 17
[    0.288359] NET: Registered protocol family 15
[    0.288399] Registering the dns_resolver key type
[    0.288451] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.288473] ThumbEE CPU extension supported.
[    0.289342] omap2_set_init_voltage: unable to get clk dpll1_ck
[    0.295440] omap2_set_init_voltage: unable to set vdd_mpu_iva
[    0.301470] omap2_set_init_voltage: unable to get clk l3_ick
[    0.307373] omap2_set_init_voltage: unable to set vdd_core
[    0.317209] registered taskstats version 1
[    0.317480] Detected MACID=0:18:31:8d:88:a6
[    0.318198] omap_rtc omap_rtc: setting system clock to 2000-01-01 03:12:53 UTC (946696373)
[    0.318755] Waiting for root device /dev/mmcblk0p2...
[    0.369658] mmc0: host does not support reading read-only switch. assuming write-enable.
[    0.371592] mmc0: new high speed SDHC card at address 1234
[    0.372072] mmcblk0: mmc0:1234 SA04G 3.63 GiB
[    0.373698]  mmcblk0: p1 p2
[    0.442096] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    0.442115] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[  161.574530] EXT4-fs (mmcblk0p2): recovery complete
[  161.812607] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[  161.812673] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[  161.815021] devtmpfs: mounted
[  161.815369] Freeing init memory: 208K
[  162.057648] systemd[1]: systemd 37 running in system mode. (+PAM +LIBWRAP -AUDIT -SELINUX +SYSVINIT -LIBCRYPTSETUP; angstrom)
[  162.162729] NET: Registered protocol family 10
[  162.167470] systemd[1]: Set hostname to <beaglebone>.
[  162.745285] udevd[57]: starting version 175
[  163.063613] systemd-fsck[53]: Angstrom-Cloud9-: clean, 29976/874496 files, 788653/3494137 blocks
[  163.093411] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[  164.754750]
[  164.754758] CPSW phy found : id is : 0x7c0f1
[  164.761576] PHY 0:01 not found
[  164.781121] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  167.132199]  gadget: Mass Storage Function, version: 2009/09/11
[  167.132222]  gadget: Number of LUNs=1
[  167.132244]  lun0: LUN: removable file: /dev/mmcblk0p1
[  167.132283]  gadget: Mass Storage Gadget, version: 2009/09/11
[  167.132301]  gadget: userspace failed to provide iSerialNumber
[  167.132328]  gadget: g_mass_storage ready
[  167.132358] musb-hdrc musb-hdrc.0: MUSB HDRC host driver
[  167.132407] musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 2
[  167.132530] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[  167.132545] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  167.132560] usb usb2: Product: MUSB HDRC host driver
[  167.132570] usb usb2: Manufacturer: Linux 3.1.0+ musb-hcd
[  167.132581] usb usb2: SerialNumber: musb-hdrc.0
[  167.133267] hub 2-0:1.0: USB hub found
[  167.133294] hub 2-0:1.0: 1 port detected
[  167.749379] PHY: 0:00 - Link is Up - 100/Full
[  167.749566] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  178.308637] eth0: no IPv6 routers present
[ 1198.318654] usb 1-1: new high speed USB device number 2 using musb-hdrc
[ 1198.751366] usb 1-1: New USB device found, idVendor=12d1, idProduct=1c0b
[ 1198.751385] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 1198.751399] usb 1-1: Product: HUAWEI Mobile
[ 1198.751409] usb 1-1: Manufacturer: HUAWEI
[ 1198.754569] scsi0 : usb-storage 1-1:1.0
[ 1198.756119] scsi1 : usb-storage 1-1:1.1
[ 1199.750452] scsi 0:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
[ 1199.760299] sr0: scsi-1 drive
[ 1199.760321] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 1199.760958] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 1199.761532] scsi 1:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
[ 1199.761911] sr 0:0:0:0: Attached scsi generic sg0 type 5
[ 1199.764489] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 1199.769690] sd 1:0:0:0: [sda] Attached SCSI removable disk

[praveen prasad]

are u working know on the board , give me your number

 

--
 
 

[wisam]

if you mean the BeagleBone serial number, then this is:
3312BB000136
Rev.A6

[praveen prasad]

remove the device and reinsert it, then do dmesg and chech what re the things changing in the message, its not necessary that always the name will start from ttyUSB0 etc

[wisam]

ok, I remved the device for som seconds and plug in it again, run dmesg, this is the result:

[ 2648.504957] usb 1-1: USB disconnect, device number 2
[ 2675.978655] usb 1-1: new high speed USB device number 3 using musb-hdrc
[ 2676.411123] usb 1-1: New USB device found, idVendor=12d1, idProduct=1c0b
[ 2676.411142] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 2676.411156] usb 1-1: Product: HUAWEI Mobile
[ 2676.411166] usb 1-1: Manufacturer: HUAWEI
[ 2676.414348] scsi2 : usb-storage 1-1:1.0
[ 2676.415906] scsi3 : usb-storage 1-1:1.1
[ 2677.409909] scsi 2:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
[ 2677.420331] sr0: scsi-1 drive
[ 2677.420820] scsi 3:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
[ 2677.421354] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 2677.422605] sr 2:0:0:0: Attached scsi generic sg0 type 5
[ 2677.424562] sd 3:0:0:0: Attached scsi generic sg1 type 0
[ 2677.429769] sd 3:0:0:0: [sda] Attached SCSI removable disk
root@beaglebone:~#

[praveen prasad]

now what i think is your device name can be either

sr0

scsi2

scsi3

sg1

sg2

 

if you want to know which one is the exact name you can do a trial and error or what u cando is repeat thesame step with your PC and check in which line its showing ttyUSB0 then find out what is it when doing with beaglebone

 

--
 
 

[praveen prasad]

now what i think is your device name can be either
sr0
scsi2
scsi3
sg1
sg2
 
if you want to know which one is the exact name you can do a trial and error or what u cando is repeat thesame step with your PC and check in which line its showing ttyUSB0 then find out what is it when doing with beaglebone

[wisam]

ok, I will try with all the names you just have suggested, and I will return the result.
as bellow:

            ┌─────[configuration]──────┐                                    
            │ Filenames and paths      │                                    
            │ File transfer protocols  │                                    
            │ Serial port setup        │                                    
            │ Modem and dialing        │                                    
            │ Screen and keyboard      │                                 
            │ Save setup as dfl        │                                 
            │ Save setup as..          │                                 
            │ Exit                     │                                 
            └──────────────────────────┘ 

│ A -    Serial Device      : /dev/sr0                                  │
│ B - Lockfile Location     : /var/lock                                 │
│ C -   Callin Program      :                                           │
│ D -  Callout Program      :                                           │
│ E -    Bps/Par/Bits       : 115200 8N1                                │
│ F - Hardware Flow Control : Yes                                       │
│ G - Software Flow Control : No                                        │
│                                                                       │
│    Change which setting?

[praveen prasad]

can you mail me the message when you type

 

$cd /dev

$ls | grep "^s"

[wisam]

root@beaglebone:~# cd /dev
root@beaglebone:/dev# ls | grep "^s"
sda
sg0
sg1
shm
snd
sr0
stderr
stdin
stdout
root@beaglebone:/dev#

[praveen prasad]

go to /var and remove the lock file and check

 

--
 
 

[praveen prasad]

On Mon, Sep 17, 2012 at 12:26 AM, praveen prasad <prave...@gmail.com> wrote:

go to /var and remove the lock file and check

do the same thing after removing the device and check which are the names not present you will find sg0, sg1, sr0,sda willl go. when you try with these names remember always remove the lock file from /var

[wisam]

the file lock cannot be removed even when I unplog the device and restart the beaglebone.
root@beaglebone:~# cd /var
root@beaglebone:/var# ls
backups  cache    lib  local  lock  log  run  spool  tmp    volatile
root@beaglebone:/var# rm -r lock
rm: cannot remove `lock': Device or resource busy
root@beaglebone:/var# rm -r lock

[praveen prasad]

remove forcefull

 

rm -Rf lock

--
 
 

[wisam]

sorry the file still cannot be removed!!

root@beaglebone:/var# ls
backups  cache    lib  local  lock  log  run  spool  tmp    volatile

root@beaglebone:/var# rm -Rf lock

rm: cannot remove `lock': Device or resource busy

root@beaglebone:/var# rm -rf lock

rm: cannot remove `lock': Device or resource busy
root@beaglebone:/var#

[wisam]

I am also tried with the devices names you gave me "sr0, scsi2, scsi3, sg1, sg2", all of them do not working!!

I thing I must install usb-modeswitch beacause it is not find in Angstrom!!

[praveen prasad]

connect an another USB device and do dmesg whether it is showing ttyUSB0 or something

if not then you have to install

--
 
 

[praveen prasad]

any way i will try finding out some solution and get back to you later now its late

[wisam]

Ok thank you so much praveen prasad.

[praveen prasad]

:)

--
 
 

[Alexander Lehner]

On Sun, 16 Sep 2012, wisam wrote:

> I am also tried with the devices names you gave me "sr0, scsi2, scsi3, sg1,
> sg2", all of them do not working!!
>
> I thing I must install usb-modeswitch beacause it is not find in Angstrom!!

Hi,

I'm not an active BB developer but I know this problem. usb-modeswitch
will probably help.
Usually the UMTS/GSM dongles at first plugin identify themselves as a
CD-ROM and provide driver software (for Windows).

Using modeswitch will change the device into a tty, then.

You will need the vendor and device ID of your stick as arguments to
modeswitch (can be found by some USB tools).

A.

[wisam]

Thanks Alexander,
But where can I find the usb-modeswitch for Beagleone(angstrom) and how to install it?? do have an idea?

[Alexander Lehner]

On Sun, 16 Sep 2012, wisam wrote:

> Thanks Alexander,
> But where can I find the usb-modeswitch for Beagleone(angstrom) and how to
> install it?? do have an idea?

Nope - I have an old version here as source, it's just about a 1000 lines
single .c file.

So you either need a cross-compiler or have gcc installed on your
beagleboard.

Google finds several locations about this tool, for example this one:

http://www.draisberghof.de/usb_modeswitch/

A.

[Christophe Devine]

Hi,

If there is no /dev/ttyUSB{0,1,2} (or /dev/ttyHS{0,1,2}) you are probably lacking the necessary kernel module (called "option" iirc), and/or the usb-modeswitch package as well. You may have to recompile your kernel and install usb-modeswitch.

2012/9/16 wisam <majid_...@hotmail.com>

I want to send SMS by E173 modem, but i cannot make it work with Beaglebone.

On Saturday, September 15, 2012 8:50:48 PM UTC+2, praveen prasad wrote:

hai ,

          if you only want to send sms then its simple if you go with a gsm module  example : sim300. using AT commands you can send sms to mobile

On Fri, Sep 14, 2012 at 11:43 PM, wisam <majid_...@hotmail.com> wrote:

oh, ok , actually i did not try to use the modem for internet connection, i just need to use it as GSM/GPRS to send the SMS/MMS only.

On Friday, September 14, 2012 8:07:26 PM UTC+2, Ali Muhammad Ali wrote:

Hi,

I am connected to internet using ethernet but I am asking you about the modem you are using. It also has broadcom internet facility.

By the way thanks for replying

Regards,

Ali

On Fri, Sep 14, 2012 at 10:42 PM, wisam <majid_...@hotmail.com> wrote:

if you mean connected your beaglebone to the internet via Ethernet cable, if so , yes, just connect the cable and on your pc write the following:
majid@ubuntu:~$ ssh 192.168.xx.xxx -l root
ro...@192.168.xx.xxx's password:   "here you write the password which is root"
whrer xx.xxx is the ip edress for you beaglebone.
then you will be in connect with your beaglebone from your pc via internet.

On Friday, September 14, 2012 7:28:53 PM UTC+2, Ali Muhammad Ali wrote:

Hey,

       I also want to do the same in near future on my project. Can you access internet. Sorry, rather than giving solution I am asking a question.

Regards,

Ali

On Friday, 14 September 2012 01:00:21 UTC+5, wisam wrote:

Hi,
i am new with BeagleBone, I have GSM modem Huawei E173 which is work fine with my PC(Ubuntu). I am using this modem only to send SMS. but it does not work with my beaglebone(Angstrom). every time I  open Minicom I have the following:

root@beaglebone:~# minicom
minicom: cannot open /dev/ttyS5: No such file or directory

its keep have ttyS5!! even when I change it to any other such as ttyS0, ttyS1 .......

When I use minicom -s and change the ttyS to ex. ttyS2 and save, exit I have the following:

Welcome to minicom 2.6.1

OPTIONS: I18n                                                               
Compiled on Apr 25 2012, 11:51:01.                                          
Port /dev/ttyS2                                                             
                                                                            
Press CTRL-A Z for help on special keys


I can not write any AT command or any text!!!
Please any help?

--
 
 

--
 
 

--
 
 

[wisam]

Thanks Alexander for the link,

[wisam]

unfortunately there are no any ttyUSB neither ttyHS in dev directory.

root@beaglebone:/dev# ls -al
total 1
drwxr-xr-x 14 root root        3080 Jan 11  2012 .
drwxr-xr-x 19 root root        1024 Jan 11  2012 ..
crw-------  1 root root     10, 235 Jan 11  2012 autofs
drwxr-xr-x  2 root root         340 Jan 11  2012 block
drwxr-xr-x  2 root root          60 Jan 11  2012 bsg
crw------T  1 root root     10, 234 Jan  1  2000 btrfs-control
drwxr-xr-x  3 root root          60 Jan  1  1970 bus
drwxr-xr-x  2 root root        2380 Jan 11  2012 char
crw-------  1 root root      5,   1 Jan 11  2012 console
lrwxrwxrwx  1 root root          11 Jan  1  2000 core -> /proc/kcore
crw-------  1 root root     10,  63 Jan 11  2012 cpu_dma_latency
drwxr-xr-x  6 root root         120 Jan 11  2012 disk
crw-rw----  1 root video    29,   0 Jan  1  2000 fb0
lrwxrwxrwx  1 root root          13 Jan  1  2000 fd -> /proc/self/fd
crw-rw-rw-  1 root root      1,   7 Jan 11  2012 full
crw-rw-rwT  1 root root     10, 229 Jan  1  2000 fuse
crw-------  1 root root     89,   1 Jan 11  2012 i2c-1
crw-------  1 root root     89,   3 Jan 11  2012 i2c-3
prw-------  1 root root           0 Jan  1  2000 initctl
drwxr-xr-x  2 root root          60 Jan  1  1970 input
crw-r-----  1 root kmem      1,   2 Jan 11  2012 kmem
crw-------  1 root root      1,  11 Jan 11  2012 kmsg
srw-rw-rw-  1 root root           0 Jan  1  2000 log
crw-------  1 root root     10, 237 Jan 11  2012 loop-control
brw-rw----  1 root disk      7,   0 Jan 11  2012 loop0
brw-rw----  1 root disk      7,   1 Jan 11  2012 loop1
brw-rw----  1 root disk      7,   2 Jan 11  2012 loop2
brw-rw----  1 root disk      7,   3 Jan 11  2012 loop3
brw-rw----  1 root disk      7,   4 Jan 11  2012 loop4
brw-rw----  1 root disk      7,   5 Jan 11  2012 loop5
brw-rw----  1 root disk      7,   6 Jan 11  2012 loop6
brw-rw----  1 root disk      7,   7 Jan 11  2012 loop7
drwxr-xr-x  2 root root          60 Jan  1  2000 mapper
crw-r-----  1 root kmem      1,   1 Jan 11  2012 mem
brw-rw----  1 root disk    179,   0 Jan 11  2012 mmcblk0
brw-rw----  1 root disk    179,   1 Jan 11  2012 mmcblk0p1
brw-rw----  1 root disk    179,   2 Jan 11  2012 mmcblk0p2
drwxrwxrwt  2 root root          40 Jan  1  1970 mqueue
drwxr-xr-x  2 root root          60 Jan  1  2000 net
crw-------  1 root root     10,  62 Jan 11  2012 network_latency
crw-------  1 root root     10,  61 Jan 11  2012 network_throughput
crw-rw-rw-  1 root root      1,   3 Jan 11  2012 null
crw------T  1 root root    108,   0 Jan  1  2000 ppp
crw-------  1 root root     10,   1 Jan 11  2012 psaux
crw-rw-rw-  1 root tty       5,   2 Sep 16 21:01 ptmx
drwxr-xr-x  2 root root           0 Jan  1  1970 pts
brw-rw----  1 root disk      1,   0 Jan 11  2012 ram0
brw-rw----  1 root disk      1,   1 Jan 11  2012 ram1
crw-rw-rw-  1 root root      1,   8 Jan 11  2012 random
crw-------  1 root root    254,   0 Jan 11  2012 rtc0
brw-rw----  1 root disk      8,   0 Jan 11  2012 sda
brw-rw----  1 root disk      8,   1 Jan 11  2012 sda1
crw-rw----  1 root disk     21,   0 Jan 11  2012 sg0
drwxrwxrwt  2 root root          40 Jan  1  2000 shm
drwxr-xr-x  2 root root          80 Jan  1  2000 snd
lrwxrwxrwx  1 root root          15 Jan  1  2000 stderr -> /proc/self/fd/2
lrwxrwxrwx  1 root root          15 Jan  1  2000 stdin -> /proc/self/fd/0
lrwxrwxrwx  1 root root          15 Jan  1  2000 stdout -> /proc/self/fd/1
crw-rw-rw-  1 root tty       5,   0 Jan 11  2012 tty
crw--w----  1 root tty       4,   0 Jan 11  2012 tty0
crw-rw----  1 root tty       4,   1 Jan 11  2012 tty1
crw--w----  1 root tty       4,  10 Jan 11  2012 tty10
crw--w----  1 root tty       4,  11 Jan 11  2012 tty11
crw--w----  1 root tty       4,  12 Jan 11  2012 tty12
crw--w----  1 root tty       4,  13 Jan 11  2012 tty13
crw--w----  1 root tty       4,  14 Jan 11  2012 tty14
crw--w----  1 root tty       4,  15 Jan 11  2012 tty15
crw--w----  1 root tty       4,  16 Jan 11  2012 tty16
crw--w----  1 root tty       4,  17 Jan 11  2012 tty17
crw--w----  1 root tty       4,  18 Jan 11  2012 tty18
crw--w----  1 root tty       4,  19 Jan 11  2012 tty19
crw--w----  1 root tty       4,   2 Jan 11  2012 tty2
crw--w----  1 root tty       4,  20 Jan 11  2012 tty20
crw--w----  1 root tty       4,  21 Jan 11  2012 tty21
crw--w----  1 root tty       4,  22 Jan 11  2012 tty22
crw--w----  1 root tty       4,  23 Jan 11  2012 tty23
crw--w----  1 root tty       4,  24 Jan 11  2012 tty24
crw--w----  1 root tty       4,  25 Jan 11  2012 tty25
crw--w----  1 root tty       4,  26 Jan 11  2012 tty26
crw--w----  1 root tty       4,  27 Jan 11  2012 tty27
crw--w----  1 root tty       4,  28 Jan 11  2012 tty28
crw--w----  1 root tty       4,  29 Jan 11  2012 tty29
crw--w----  1 root tty       4,   3 Jan 11  2012 tty3
crw--w----  1 root tty       4,  30 Jan 11  2012 tty30
crw--w----  1 root tty       4,  31 Jan 11  2012 tty31
crw--w----  1 root tty       4,  32 Jan 11  2012 tty32
crw--w----  1 root tty       4,  33 Jan 11  2012 tty33
crw--w----  1 root tty       4,  34 Jan 11  2012 tty34
crw--w----  1 root tty       4,  35 Jan 11  2012 tty35
crw--w----  1 root tty       4,  36 Jan 11  2012 tty36
crw--w----  1 root tty       4,  37 Jan 11  2012 tty37
crw--w----  1 root tty       4,  38 Jan 11  2012 tty38
crw--w----  1 root tty       4,  39 Jan 11  2012 tty39
crw--w----  1 root tty       4,   4 Jan 11  2012 tty4
crw--w----  1 root tty       4,  40 Jan 11  2012 tty40
crw--w----  1 root tty       4,  41 Jan 11  2012 tty41
crw--w----  1 root tty       4,  42 Jan 11  2012 tty42
crw--w----  1 root tty       4,  43 Jan 11  2012 tty43
crw--w----  1 root tty       4,  44 Jan 11  2012 tty44
crw--w----  1 root tty       4,  45 Jan 11  2012 tty45
crw--w----  1 root tty       4,  46 Jan 11  2012 tty46
crw--w----  1 root tty       4,  47 Jan 11  2012 tty47
crw--w----  1 root tty       4,  48 Jan 11  2012 tty48
crw--w----  1 root tty       4,  49 Jan 11  2012 tty49
crw--w----  1 root tty       4,   5 Jan 11  2012 tty5
crw--w----  1 root tty       4,  50 Jan 11  2012 tty50
crw--w----  1 root tty       4,  51 Jan 11  2012 tty51
crw--w----  1 root tty       4,  52 Jan 11  2012 tty52
crw--w----  1 root tty       4,  53 Jan 11  2012 tty53
crw--w----  1 root tty       4,  54 Jan 11  2012 tty54
crw--w----  1 root tty       4,  55 Jan 11  2012 tty55
crw--w----  1 root tty       4,  56 Jan 11  2012 tty56
crw--w----  1 root tty       4,  57 Jan 11  2012 tty57
crw--w----  1 root tty       4,  58 Jan 11  2012 tty58
crw--w----  1 root tty       4,  59 Jan 11  2012 tty59
crw--w----  1 root tty       4,   6 Jan 11  2012 tty6
crw--w----  1 root tty       4,  60 Jan 11  2012 tty60
crw--w----  1 root tty       4,  61 Jan 11  2012 tty61
crw--w----  1 root tty       4,  62 Jan 11  2012 tty62
crw--w----  1 root tty       4,  63 Jan 11  2012 tty63
crw--w----  1 root tty       4,   7 Jan 11  2012 tty7
crw--w----  1 root tty       4,   8 Jan 11  2012 tty8
crw--w----  1 root tty       4,   9 Jan 11  2012 tty9
crw-rw----  1 root tty     251,   0 Jan 11  2012 ttyO0
crw-rw----  1 root dialout 251,   1 Jan 11  2012 ttyO1
crw-rw----  1 root dialout 251,   2 Jan 11  2012 ttyO2
crw-rw----  1 root dialout 251,   3 Jan 11  2012 ttyO3
crw-rw----  1 root dialout 251,   4 Jan 11  2012 ttyO4
crw-rw----  1 root dialout 251,   5 Jan 11  2012 ttyO5
crw-rw----  1 root dialout   4,  64 Jan 11  2012 ttyS0
crw-rw----  1 root dialout   4,  65 Jan 11  2012 ttyS1
crw-rw----  1 root dialout   4,  66 Jan 11  2012 ttyS2
crw-rw----  1 root dialout   4,  67 Jan 11  2012 ttyS3
crw------T  1 root root     10, 223 Jan  1  2000 uinput
crw-rw-rw-  1 root root      1,   9 Jan 11  2012 urandom
crw-------  1 root root    189,   0 Jan 11  2012 usbdev1.1
crw-------  1 root root    189,   2 Jan 11  2012 usbdev1.3
crw-------  1 root root    189, 128 Jan 11  2012 usbdev2.1
crw-rw----  1 root tty       7,   0 Jan 11  2012 vcs
crw-rw----  1 root tty       7,   1 Jan 11  2012 vcs1
crw-rw----  1 root tty       7,   2 Jan 11  2012 vcs2
crw-rw----  1 root tty       7,   3 Jan 11  2012 vcs3
crw-rw----  1 root tty       7,   4 Jan 11  2012 vcs4
crw-rw----  1 root tty       7,   5 Jan 11  2012 vcs5
crw-rw----  1 root tty       7,   6 Jan 11  2012 vcs6
crw-rw----  1 root tty       7, 128 Jan 11  2012 vcsa
crw-rw----  1 root tty       7, 129 Jan 11  2012 vcsa1
crw-rw----  1 root tty       7, 130 Jan 11  2012 vcsa2
crw-rw----  1 root tty       7, 131 Jan 11  2012 vcsa3
crw-rw----  1 root tty       7, 132 Jan 11  2012 vcsa4
crw-rw----  1 root tty       7, 133 Jan 11  2012 vcsa5
crw-rw----  1 root tty       7, 134 Jan 11  2012 vcsa6
crw-------  1 root root     10, 130 Jan 11  2012 watchdog
crw-rw-rw-  1 root root      1,   5 Jan 11  2012 zero

[wisam]

just for the people who have the same problem:
the only solution I could manage is by used linux arm (ubuntu) instade of angstrom, then the USB0---USB2 are appear, and the modem work successfully.

to send sms from the beaglebone I used the follwoing command on the terminal :
udo echo -e -n "AT+CMGF=1 \015" > /dev/ttyUSB0
sudo echo -e -n "AT+CMGS=\"your mobile number\" \015" > /dev/ttyUSB0
sudo echo -e -n "your text message \015" > /dev/ttyUSB0
sudo echo -e -n "\032" > /dev/ttyUSB0
sudo echo "******SMS was sent successfully!******"

you can copy past the above command to a text file after append:
#!/bin/bash
and make the file as an excutable file (chmod 755 yourfilename)

then you can send sms by just run the above txt file.
thanks for every one for help

[praveen prasad]

thanks buddy, can i know any link where i can get this linux arm (ubuntu) for beagle board-XM

--
 
 

[wisam]

 For beagle board-xm, I am really do not know, but for beaglebone, I install linux arm by follow the instructions in the following link, its very helpful. the tutorial originally is to using wifi with beaglebone with linux arm.

http://www.youtube.com/watch?v=HJ9nUqYMjqs&feature=channel&list=UL

regards

[beyond.hack]

--
 
 

Sorry to jump in between, 

but I just thought that this may help you

http://beyondszine.wordpress.com/2012/07/23/access-internet-with-816-bit-controllers/

the commands are pretty much the same, you just have to redirect the command to desired serial terminal.
I did some projects on GSM and GPRS both usage with 8 bit microcontrollers and with Beaglebone/board its too easy and convinient.

Hope it helps..

--
Regards,

saurabh

http://about.me/shandilyasaurabh

www.beyondszine.wordpress.com