GSM modem access

[vvb5]

Maybe ignorant question, but is there any way to send AT commands to modem from within telnet shell/ qconsole? What chardev is responsible for that? I hope that the phone stuff is not hidden bihind some built-in closed protocol...

[numbski]

Huh, very interesting question, and I can't say that I know the answer to it.

I don't have my phone handy, but ls /dev/cu*, what comes up?

[mserougi]

i'm not sure but this was used before to switch the phone to usblan:
echo 'AT+MODE=99' > /dev/ttyACM0
which means you could run something similar from telnet, with /dev/cu instead? however i'm not sure how i would record the output from any AT command if i'm not running telnet... i don't think another > redirect would work... i'm particularly interested in the output from 'AT+CREG?'...
will try it when i get the e680i back... the a1200 has some complications...

[vvb5]

Huh, very interesting question, and I can't say that I know the answer to it.

I don't have my phone handy, but ls /dev/cu*, what comes up?

# ls /dev
CEBus_chardev  keypad0    mux0   ram10        tty      usbdl   vcsa11
animation      keypad1    mux1   ram11        tty0     usbi6c  vcsa12
apl0           keypad2    mux10  ram12        tty1     usbi6d  vcsa13
aplog0         kmem       mux11  ram13        tty10    usbi8   vcsa14
apm_bios       led        mux12  ram14        tty11    vcs0    vcsa15
apnetmon       loop0      mux13  ram15        tty12    vcs1    vcsa16
audio          loop1      mux14  ram16        tty13    vcs10   vcsa17
button         loop2      mux15  ram2         tty14    vcs11   vcsa18
camerai2c      loop3      mux2   ram3         tty15    vcs12   vcsa19
console        loop4      mux3   ram4         tty16    vcs13   vcsa2
dc_char        loop5      mux4   ram5         tty17    vcs14   vcsa3
dsp            loop6      mux5   ram6         tty18    vcs15   vcsa4
dsp16          loop7      mux6   ram7         tty19    vcs16   vcsa5
dsplog         mem        mux7   ram8         tty2     vcs17   vcsa6
emu            midi       mux8   ram9         tty3     vcs18   vcsa7
ezx_ts         midicomm   mux9   random       tty4     vcs19   vcsa8
ezxlog_p       mixer      null   roflash      tty5     vcs2    vcsa9
fb0            mmca       phone  roflash1     tty6     vcs3    vibrator
fb1            mmca1      plog   roflash2     tty7     vcs4    video0
fb2            mmcsysif   port   rtc          tty8     vcs5    video1
fmradio        mtd2       ppp    shm          tty9     vcs6    zero
full           mtd3       ptf0   tffsa        ttyS0    vcs7
h3600_ts       mtdblock2  ptmx   tffsa1       ttyS1    vcs8
h3600_tsraw    mtdblock3  pts    tffsb        ttyS2    vcs9
initctl        mtdblock4  ram    tffsb1       ttyS3    vcsa0
ircomm0        mtdblock5  ram0   tffsb2       ttyUSB0  vcsa1
keylight       mtdblock6  ram1   touchscreen  urandom  vcsa10
# ls /dev/cu*
ls: /dev/cu*: No such file or directory

I suspected either ttyS or ttyUSB, but they are silent.

The way I got tested is ordinary for UARTs: on one telnet, cat /dev/ttyS0, on the other, echo "ATZ" >/dev/ttyS0

As I see from googling stuff, phone functions itsef are accessible via /dev/mux, but is is not clear how exactly. I am thinking about alternative phone APP framework, since Mot likely will not revial sources ever.

[ageraldnaveen]

Is there any update on this further? I am also looking for the modem device from the phone itself. Can you update this with what u've discovered on this?

thanx

[vvb5]

Is there any update on this further? I am also looking for the modem device from the phone itself. Can you update this with what u've discovered on this?

thanx

I afraid, this ability has to be implemented.
The mux devices provide such interface, and to discover the details, I guess one need to patch kernel, making debug uotputs in what's read/write to those devices in the driver, replace kernel and collect some information. Motorola has made the kernel source available to public, so with enough time, you'll figure it out.