**** BEGIN LOGGING AT Sat Oct 24 02:59:56 2009 Oct 24 15:24:29 denkenz: Do you follow the command order we use inside ConnMan? Oct 24 15:24:46 holtmann: More or less Oct 24 15:24:49 It seems that ENAP and E2NAP have to be executed in the right order. Oct 24 15:25:02 holtmann: I don't execute E2NAP Oct 24 15:25:07 its only used as unsolicited Oct 24 15:25:22 You might have to. Try to enable it. Oct 24 15:25:40 E2NAP enables the notifications. Oct 24 15:26:55 E2NAP is never executed then Oct 24 15:28:05 You just need to send it to enable the notifications. Oct 24 15:28:39 I doubt that this is causing it to crash though Oct 24 15:28:43 But lemme try Oct 24 15:29:49 Yeah. Also on the 35xx hardware it needs to be send after the ENAP for some stupid reason. At least there is commit inside ModemManager that indicates that. Oct 24 15:30:42 Unpossible Oct 24 15:30:47 it crashes on the ENAP Oct 24 15:31:14 E.g. ENAP=1,1 -> OK, crash Oct 24 15:32:10 But using ConnMan this works for you? Oct 24 15:33:10 haven't tried connman actually Oct 24 15:33:31 Can you do that first. If that also crashes then it is the card. Oct 24 15:33:52 Not really a solution Oct 24 15:33:53 I can't really try it here without causing roaming charges like crazy. I don't have a Japanese SIM card. Oct 24 15:34:14 Connman can easily control the command order, ofono can't Oct 24 15:34:30 I know, but then we at least know it can work and is not the firmware. Oct 24 15:36:08 Also maybe waiting for +PACSP1 is required before calling ENAP. Oct 24 15:36:16 There are some weird corner cases. Oct 24 15:37:44 wtf is this pacsp1? Oct 24 15:37:57 can you share the command set btw? Oct 24 15:38:15 I only have what is public available and inside ModemManager. Oct 24 15:39:01 well considering they don't do jack with those commands Oct 24 15:39:12 And also considering they've no idea wtf they're doing... Oct 24 15:39:32 The order is important for some of them. That is a problem. Oct 24 15:41:17 Nah, they just have no idea wtf they're doing Oct 24 15:41:38 I am serious. You have to wait for certain events before you can send the next command. Oct 24 15:41:55 Not on the mbm Oct 24 15:42:00 Works manually btw Oct 24 15:42:31 That is because you are too slow manually. Seriously some stuff is just weird and black magic. Oct 24 15:42:32 The MBM hardware does not register to GPRS until you attach Oct 24 15:43:29 Actually no, it takes ages for me to get signal where I am Oct 24 15:43:37 The modem has plenty of time either way :) Oct 24 15:47:45 Still dies in oFono even with E2NAP=1 Oct 24 15:48:03 I get an OK for ENAP, immediate E2NAP=2 and boom Oct 24 15:50:56 We don't store the context data yet? Oct 24 15:52:32 no Oct 24 15:55:48 still goes kaboom after I took out all atoms except sim / netreg / gprs Oct 24 15:59:06 How do I activate a context? Oct 24 15:59:15 CreateContext Oct 24 15:59:25 Got that part. Set the APN etc. Oct 24 15:59:28 on context: SetProperty("AccessPointName", "foo") Oct 24 15:59:33 Just to Active=true? Oct 24 15:59:34 SetProperty("Active", True) Oct 24 15:59:47 Oh and SetProperty("Powered", True) on DCM Oct 24 16:04:37 So mine doesn't crash. Oct 24 16:04:56 Yah, sounds like a broken device Oct 24 16:05:07 It also never connects either. Oct 24 16:05:14 Heh Oct 24 16:05:36 This is why I'm harping on andrew, the logic for registering is fucked Oct 24 16:05:56 I've already had a few infinite CGATT=0 / CGATT=1 loops happen Oct 24 16:06:37 Do we get a signal when we are attached? Oct 24 16:08:04 The way my MBM device works is that it doesn't send CGREG until we attach Oct 24 16:08:14 However, I'm working with shitty signal right now Oct 24 16:08:15 Also we might wanna disable the scanning when connecting to GPRS. Most modems can't handle it. Oct 24 16:08:28 yeah I know ;) Oct 24 16:08:31 I don't see the CGREG at all. Oct 24 16:09:17 SetProperty("Powered", True) on DataConnectionManager Oct 24 16:09:27 Yes. Did that. Oct 24 16:12:25 roamingallowed = true? Oct 24 16:13:00 Crap. That might be it. Oct 24 16:16:51 And you have to read ENAP on startup to see if we are already have been connected. Oct 24 16:17:25 Also Powered succeeds and Active succeeds even if RoamingAllowed=false. Oct 24 16:17:31 It just doesn't work. Oct 24 16:18:29 powered should Oct 24 16:19:09 active should just check attached and fail if not Oct 24 16:20:52 I think your problem is that CDGCONT and ENAP are send to quickly after each other. Oct 24 16:21:05 But ConnMan indeed does the same. Oct 24 16:21:21 ofonod[6442]: > AT+CGDCONT=1,"IP","internet.com"\r Oct 24 16:21:21 ofonod[6442]: < \r\nOK\r\n Oct 24 16:21:21 ofonod[6442]: > AT*ENAP=1,1\r Oct 24 16:21:21 ofonod[6442]: < \r\nOK\r\n Oct 24 16:21:30 It see this, but usb0 never gets LOWER_UP. Oct 24 16:22:03 send e2nap=1 at init and see? Oct 24 16:26:34 Crap. I forgot that you have to manually do ifup usb0. Oct 24 16:26:51 Try to ifup usb0 first and see if that makes a difference. Oct 24 16:28:56 it works when i do all of this manually Oct 24 16:29:08 no ifup required Oct 24 16:31:06 Please try it with ConnMan. I am curious if it works ther. Oct 24 16:41:13 Ok, I give up on this for now Oct 24 16:41:20 My card shoots itself randomly now Oct 24 17:17:17 So taking out CGATT=1 and ifconfig usb0 up it seems to work now **** ENDING LOGGING AT Sun Oct 25 02:59:56 2009