Firmware debug: handover to the community

[Das Signal]

Hi SF,

I do use my own SIM (without PIN). This way I can do a complete
authentication procedure, as if I were a real network. QtMoko shows
the PIN entry in any case, then it disappears.

So I've followed your advice and used this combination of sp/AT commands:
sp MM TRACECLASS FFFFFFFF  (mobility management)
sp RR TRACECLASS FFFFFFFF  (radio resource)
sp L1 TRACECLASS FFFFFFFF  (layer1 control of dsp)
AT+CREG=2  (to be notified of network registration state)
AT+CFUN=1  (to enable the radio)
<wait for OK>
AT+COPS=0  (to enable automatic network registration)
<wait for registration complete>
AT+CMGF=1  (send SMS in text mode)
AT+CMGS="+..."
ATsomemessage

Now it appears this unit does not exhibit the deep sleep issue: it goes
to deep sleep frequently and when using leo2moko-debug, does not lose
network registration; I have been able to reproduce this bug with gsm-fw,
and also was able to test the ctracedec as well when using the log option
(-l) of rvinterf.

I'm still busy analyzing the traces, but one thing was apparent: I'm
getting 138 "Trc Abort" messages in gsm-fw, whereas leo2moko only got 2.
One reason a trace can be aborted is a problem with memory allocation,
so I'm tempted to examine deeper the memory allocation mechanism.

One further idea would be the development of a small gdb stub that would
be able to trace the execution of the firmware, using the rvt protocol.
I'm not completely sure this is doable, because the code to be traced,
unless in RAM, would be read-only.

--DS