Lefora Free Forum
256 views

Problems getting G24 to respond

Page 1
posts 1–4 of 4
rookie - member
4 posts

Hi There Everyone

I have a problem....

I've built a circuit that brings out the following lines from the G24 (Java) :

above

rts, rxd, cts, dtr, txd
reset
rxd2, txd2, rts2, cts2
txen, ant_det
ign, on


below

usb_vbus, xusb_dp, xusb_dn
wkupi, wkupo

and all the sim lines.

I can switch the unit on using either ign or on and that works fine.
The sim connections are ok as I can see "RING" when I call the unit.

Plugging UART2 unit into a PC through a MAX232 ic (and using resistor dividers to bring the 5v down to below 3) shows me all the bootup and shutdown messages so I know TXD_N is ok. Cannot seem to send anything through terminal into usart2. Nothing is echoed back when typing into the terminal.

UART1 responds with "G24 KJAVA READY" some seconds after power on. It also sends "RING" and "NO CARRIER" when I call the unit. All characters typed into the terminal is echoed back, so I presume but RX and TX is working fine (local echo is off in term app).

*** but here is my main problem: **

typing "AT<cr>" does not respond with "OK". No AT commands work, I can see what I type, but the G24 seems "command deaf".

I finally gave up and connected the USB, loaded the modem driver from Motorola. The PC detects that it is talking to a G24 and tries toad the modem driver, but after a while it says that the modem might not work! (Win 2000). I'll follow up on this later (might be my OS, will test on another machine sometime) The thing is : I'm trying to connect the G24 to a PIC microprocessor and will have to get the UART to work.

I know that it is probably a hardware / circuit error on my part - but was wondering if anyone had seen a G24 behave in this manner.

thanks for listening

azurensces from South Africa


rookie - member
4 posts

this is the bootup serial data that is sent on UART2 :

=== service API trace: AmTimeNotifyTimeChangedEvent()

  initData -jam  address     0x126b77cc : 0x126b77f0

              126b77b4 : 126b77cc

              126b77f0 : 126bef5c




*** Initializing SMS MO/MT API build for JSR120 version 1.1
*** Initialization succeed
STATES of F6615 DL_DB_FEATURE_IDs NVM:SIM:TTP: 1:0:1
SM_GetNumRootCerts: Total number of KJAVA certs on SIM and NVM (Type-15): 0, 1
STATES of F6615 DL_DB_FEATURE_IDs NVM:SIM:TTP: 1:0:1
[VMproxyStart] proxyId: 0xffffffff
VB: VMproxyDisableIM()
[VMproxyGainFocus]: proxyId = 0xffffffff
VB: Default backlight is ON.
VB: Duration will be not limited.
VB: Vibration is enabled.
VB: BKLT_Restore() Restores Java Settings backlight state.
VB: VMproxyBkltTurnOn()
jbVmVmStartMIDP(vmId=1,heapSize=2036008,heapAddr=0x123f373c)

jbVmVmInitialize(vmId=1,heapSize=2036008,heapAddr=0x123f373c

section bss  address: 3f99378 size 4052

section data address: 3f99374 size 4

section bss  address: 126b77b4 size 30632

section data address: 126ac730 size 45188

section size data 45192 bss 34684

section save size data 14841 bss 34684

all class blocks      601

instance class blocks 581

array class blocks    20

sizoef class blocks   35660

newHeapAddr=0x123ff90c, newHeapSize=1986392

JBlend[micro] Copyright 2000-2004 Aplix Corporation. All rights reserved.

 build date : 2006-11-02_22:22

VM variable initialization.

  type: 1

  bssAddress: 0x03f99378 bssSize: 0xfd4

  dataAddress: 0x03f99374 dataSize: 0x4

  initDataAddress: 0x10c47278

 -jam  address     0x126b77cc : 0x126b77f0

  type: 2

  bssAddress: 0x126b77b4 bssSize: 0x77a8

  dataAddress: 0x126ac730 dataSize: 0xb084

  initDataAddress: 0x10c32f88

 -jam  address     0x126b77cc : 0x126b77f0

              126b77b4 : 126b77cc

              126b77f0 : 126bef5c

===> jbVmStartMIDP

vmId:1

heapAddr:0x123ff90c

heapSize:1986392

EventHandler:102cf267

vmParamCount:0

vmParams:0x0

vmParamLens:0x0

===> JKT_MIDP_Application

jarAddr:0x0

jarSize:32472

jarRead:0x102cffd1

className:302644465

classNameLen:17

jadAddr:0x0

jadSize:3339

jadRead:0x102cffb5

trusted:1

ExtLib: jarAddress:0x101bcc64 length:611703 jarReader:0x00000000

VM heap 0x123ff920 0x1e4f44

ROMIZE byteCode Size ROM:188672 RAM:49

GCF Extension: Scheme:datagram

GCF Extension: Scheme:socket

GCF Extension: Scheme:ssl

GCF Extension: Scheme:file

GCF Extension: Scheme:comm

GCF Extension: Scheme:wappush

GCF Extension: Scheme:drm

GCF Extension: Scheme:csd

----- JB_VMEVENT_VM_STARTED callback begin.

----- JB_VMEVENT_VM_STARTED callback end.

----- VM JK_VMEVENT_VMPAINTREADY callback begin.

----- VM JK_VMEVENT_VMPAINTREADY callback end.

default_midlet.DM@d590dbc 100
DM: OEM backup MIDlet (Default MIDlet) initializing
DM: Unit is an OEM unit, outputting to standard output only
DM: Info: Retrieving unit information
DM: Info: Default MIDlet version: 2.2.2
DM: Info: Earliest required software version for this DM: G24_G_0C.11.91R
DM: Info: Software version: G24_G_0C.11.95R
DM: Info: Flex version: GCEG24xJ2400E10AB080
DM: Info: Product description: G24 OEM Module
DM: Info: Unit operation mode: java_mode
DM: Info: IMEI: 355832010039078
DM: Info: Date: Sun Feb 11 09:52:52 UTC 2007
DM: Info: Error: Cannot get MSISDN: com.motorola.oem.access.AccessException: Access: Phone Book reading failed
DM: Info: User MIDlet version: No User MIDlet
DM: Info: Last OTA status is success
DM: Info: Run fault data found:
DM: <?xml version="1.0"?>
<RunFault>
<Date>Network clock unavailable</Date>
<Suite>
<Id>130000</Id>
<Name>DefaultMIDlet</Name>
<Vendor><![CDATA[Motorola, Inc.]]></Vendor>
<Version>2.2.2</Version>
</Suite>
<MIDletClassName>default_midlet.DM</MIDletClassName>
<StandardOutput><![CDATA[nput by SMS is enabled
DM: Browser messages listener started
DM: SMS listener started on port 16001
default_midlet.DM@d590dbc 7
DM: Default MIDlet exited

|========== KVM stdout log ended at Network clock unavailable

|========== KVM stdout log started at Network clock unavailable
default_midlet.DM@d590dbc 100
DM: OEM backup MIDlet (Default MIDlet) initializing
DM: Unit is an OEM unit, outputting to standard output only
DM: Info: Retrieving unit information
DM: Info: Default MIDlet version: 2.2.2
DM: Info: Earliest required software version for this DM: G24_G_0C.11.91R
DM: Info: Software version: G24_G_0C.11.95R
DM: Info: Flex version: GCEG24xJ2400E10AB080
DM: Info: Product description: G24 OEM Module
DM: Info: Unit operation mode: java_mode
DM: Info: IMEI: 355832010039078
DM: Info: Date: Sun Feb 11 09:52:52 UTC 2007
DM: Info: Error: Cannot get MSISDN: com.motorola.oem.access.AccessException: Access: Phone Book reading failed
DM: Info: User MIDlet version: No User MIDlet
DM: Info: Last OTA status is success
]]></StandardOutput>
</RunFault>

DM: Info: Fault report address (1): file
DM: Info: Fault report address (2) is empty
DM: Info: Fault report address (3) is empty
DM: Info: Input by SMS is enabled
DM: Browser messages listener started
PUSHREGISTRY: PR_QueryConnectionInfo: sms://:16001
PUSHREGISTRY: PR_QueryConnectionInfo result = -6
DM: SMS listener started on port 16001
DM: Starting fault report
DM: Error: Cannot get MSISDN: com.motorola.oem.access.AccessException: Access: Phone Book reading failed
DM: Writing fault report to file
DM: Fault report was written to file successfully
----- APP JK_VMEVENT_APPSTARTED callback begin.

----- APP JK_VMEVENT_APPSTARTED callback end.

rookie - member
4 posts

and some more info....

tried the usb on another PC, driver installs fine and "Motorola USB Modem" appears under modems.

connecting to the com port that it installs (com3), no echo, no response.

everything else the same

rookie - member
4 posts

Contacted Motorola....

Excellent customer support :) The best I've ever received....

Solved all my problems waiting to see if they need to help me further.

The issue was me not reading the manual (RTFM).

On the G24 Java, The midlet by default controls the UART1, 2  and USB.

Need to toggle GPIO 8 for JTool mode and the select ATCmd mode...

Very impressed with them :)

laters....

Page 1
posts 1–4 of 4

This Topic Is Locked To Guest Posts

It's been a while since this topic was active, if you'd like to get it going again, please post as a registered member

join now