Sysmocom sells pre-modified CP201x. You can use them as they are.
"mostly" LAPDm and Paging messages is normal. You should also see call
setups and SMSs as they are used, much less frequently depending on local
traffic. :-)
If you have your cellphone on the same ARFCN, you should be able to see
your cell making/receiving calls and sending messages.
B.
On Fri, Dec 28, 2012 at 4:12 PM, Erich Dachleger <edachleger(a)yahoo.com>wrote:
> I am also using CP210x from sysmocom and haven't modified it since I
> thought it didn't require modification.
> Is that wrong?
> When I use burst_ind with unmodified CP210x I receive mostly LAPDM and
> System 4 messages in wireshark.
> Regards
> Erich
>
>
Hi all,
I am starting with this project and i have problems downloading the
firmware to a c139, i built the t191 and i'm using a FTDI usb-serial.
I use the command that is described in "Motorola C140" section:
./osmocon -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/layer1.highram.bin
../../target/firmware/board/compal_e86/chainload.compalram.bin
and also i have used it with "-m c140xor" but when i push briefly
power button, shows it in next lines "got 1 byte from modem, data
looks like: ff .", the data are changing in next lines, some times the
bytes received are more than 1, are 2, 5, 6.
I have some questions:
Which is the sequence that have to receive the osmocon to start the
comunication with the phone?
Is posible that the compilation of osmocon has been badly?
Thanks and regards.
Using burst_ind branch, the code switches to a higher speed in function
serial_up_to_eleven like this:
int serial_up_to_eleven(void)
{
int rv;
/* Attempt custom baudrate */
rv = osmo_serial_set_custom_baudrate(dnload.serial_fd.fd, 406250);
if (rv == 0)
return 0;
#ifdef I_HAVE_A_CP210x /* and I know what I'm doing, I swear ! */
/* Try closest standard baudrate (CP210x reprogrammed adapters) */
rv = osmo_serial_set_baudrate(dnload.serial_fd.fd, B460800);
if (rv == 0)
return 0;
#endif
etc....
If the first attempt to switch to 406250 succeeds, the function exits and
never reaches the I_HAVE_A_CP210x code which would switch to a higher speed!
Is this a bug? Or is the lower speed good enough for burst_ind? In which
case why bother with the I_HAVE_A_CP210x option?
Or have I missed something obvious?
B.
Hi all,
I am starting with this project and i have problems downloading the
firmware to a c139, i built the t191 and i'm using a FTDI usb-serial.
I use the command that is described in "Motorola C140" section:
./osmocon -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/layer1.highram.bin
../../target/firmware/board/compal_e86/chainload.compalram.bin
and also i have used it with "-m c140xor" but when i push briefly
power button, shows it in next lines "got 1 byte from modem, data
looks like: ff .", the data are changing in next lines, some times the
bytes received are more than 1, are 2, 5, 6.
I have some questions:
Which is the sequence that have to receive the osmocon to start the
comunication with the phone?
Is posible that the compilation of osmocon has been badly?
Thanks and regards.
Hi group,
what is the most succesful: guessing uplink frames or downlink.
i see some very simple uplink frames that make a good candidate.
or is it all the same...
kind regards
Hello, I am working with a project Osmocom-bb. I did compile the project.
But when the firmware command :
./osmocon -p /dev/ttyUSB0-m c123xor
../../target/firmware/board/compal_e88/hello_world.compalram.bin
screen is just hangs (the power button I also click) , or most likely
expects to input a sequence of bytes, i.e., no information no longer
appears.
The phone is switched on. I used this instructions for checking the
operation of the
http://lists.osmocom.org/pipermail/baseband-devel/2011-August/002230.html .
1) I use the FTDI cable, it is OK. Port is OK.
2) Note : I don't see FMTTOOL ERROR (!!!) when i press the power button. I
tried the next model C113,C115,C118.
Why this may happen?
Thank you!
Hi Group,
i'm using the testing/sylvain burst branch.
sometimes i get double frames in the bursts files taken with ccch_scan.
what does this mean?
bad reception?
kind regards
Hello,
I am in the process of setting up OsmocomBB but I was wondering where/which
files in the firmware responsible for receiving/processing the RAND/SRES
values from the network/SIM.
Does anyone know this or can point me in the right direction?
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/How-can-I-see-the-RAND-SRES-tp40…
Sent from the baseband-devel mailing list archive at Nabble.com.
hello first off al these phone's and tools RULE .
i already tested a couple branches . burst_ind work'd and captured packet's
, sylvain/testing also worked a week or 2 ago and i could make a call en
see it in wireshark :) .
but now i saw that there were some updates in the sylvain testing branch
i updated like the sim reader page on the wiki told me .
could it be that the last commits broke the sylvain/testing branch ?
i get error while loading libosmocore.so.4
i followed the tutorial on the wiki for sim reader . 2 weeks ago it worked
fine .
checked the code in the last updates and it seems that lib osmocore is now
changed ?
or am i doing wrong ??
thx in advance
grts vic
Hello.
I'm struggling with a5/3 test - I've got osmocom usim
(http://shop.sysmocom.de/products/sysmousim-gr1)
which I've programmed with pySim-prog.py
Unfortunately when I plug it into samsung galaxy s2 it indicates (via classmark) that
it only supports a5/1
What am I doing wrong?
I've tried operator's sim with the same phone - a5/3 support is indicated just fine.
--
best regards,
Max, http://fairwaves.ru
