Hi,
I changed the keypad bit mask so to match for the Pirelli DP-L10 (patch attached).
some remarks:
- the additional volume up/down and camera buttons press are detected by keypad_poll(), but not visible in KBR_LATCH_REG
- the power button press is not detected by keypad_poll() (or ignored by "with_interrupts && !polling")
- the keypad.h file is in target/firmware/include/, but it's board dependent. is there a clean way to handle that?
thanks,
kevin
Hi,
I am studying the GSM voice interception of airprobe,and want to port
to BB,using
the ccch_scan.c .the problem is that,
the airprobe is written by C++,and the BB is C;
I find the useful part of airport is
airprobe/gsm-receiver/src/lib/decoder/openbtsstuff,
and how to modify the makefile of BB to use the source of openbtsstuff?
Thanks!
On Tue, Jul 3, 2012 at 3:27 PM, Alexander Huemer <alexander.huemer(a)xx.vu> wrote:
> On Tue, Jul 03, 2012 at 03:08:02PM +0200, Dario Lombardo wrote:
>> On Tue, Jul 3, 2012 at 1:44 PM, Sylvain Munaut <246tnt(a)gmail.com> wrote:
>> >> In some past post of the ML, I've read that someone was trying to get
>> >> the GSM 10MHz clock reference from the motorola phones.
>> >> This aimed at feeding usrp with a stable reference, if I'm not wrong.
>> >> Anything new this side? This would be extremely useful if GPS signal
>> >> can't be got but GSM cell can.
>> >
>> > 1) It's not 10 MHz but 26 MHz
>>
>> Mmm... but the front panel of usrp is fed by 10 MHz/1pps... isn't it?
>>
> There are different revisions of the USRP. Sylvain is talking about the
> USRP1, you of a later rev.
> The USRP1 has an (unpopulated) direct clock input.
> The other USRP revisions have a reference clock input, which is
> something different.
>
You are definitly right. I was taling about N210, which can be fed by
reference clock input.
>> > 2) Yes it works, but you can't feed the USRP directly, you need to
>> > multiply it by 2 (using a PLL chip) to get 52 MHz for the USRP.
>>
>> Can you provide some link to read something about it?
>>
> See [1,2,3]
>> Don't you think that this way could be much more preferrable than the
>> GPS way, if USRP is under GSM coverage? I mean: the clock from GSM is
>> next to us... why just don't use it? Probably there's something I'm
>> missing, since this approach is much less used than GPS clocking...
>>
>
> There are many ways to provide a stable reference clock. A OCXO (e.g.
> [4]), a cheap rubidium standard, the clock tamer[5], ...
> Every option has up and downsides.
>
Just the "pirelli" way uses clock from existing GSM network.
As said before I think that "reusing" the clock from network could be
very useful, but I don't know if it is more difficult than generate
the signal itself.
Is that possible using motorola phones? Did anyone investigate that possibility?
In some past post of the ML, I've read that someone was trying to get
the GSM 10MHz clock reference from the motorola phones.
This aimed at feeding usrp with a stable reference, if I'm not wrong.
Anything new this side? This would be extremely useful if GPS signal
can't be got but GSM cell can.
Dario.
in layer23 apps
we open local unix socket in layer23 app and one in osmocon another socket
to communicate in between.
now in layer23 we just send (write) or receive (read) msg.
but we handle actual communication with phone is handled in osmocon.
now flow of functions is
main
->register_tool_server->tool_accept->un_tool_read->hdlc_send_to_phone->sercomm_sendmsg
then sercomm handles all transmission in details
then layer1 accept all data via
so i wanted to ask that how does rssi firmware is sending data directly to
l1 -l2 and i would also like to ask what is actual protocol used in
communication between l1 and l2
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
Hello all,
I am using osmocomm (branch sylvain) on a motorola C140.
I have uncommented the line "#define DEBUG" on
src/target/firmware/calypso/sim.c and recompiled.
I have connected an interface between my PC and phone sim slot ( a pl2303
usb module, with a diode between TXD and RXD and a 22K resistor between +5V
and RXD).
Now I have opened the serial port on my PC with these settings:
baud rate = 9600
databits = 8
parity = even
stopbits = 2
and I am sending the byte "3B" to the phone, but I see in osmocon console:
"SIM-ISR: Waiting for read (9B)..." (id est the phone seems like to
receive "9B" instead of "3B"),
where I am wrong?