Hello baseband hacking folks,
I have heard several people complain that they are no longer able to
find/obtain a Motorola C1xx phone or any other Calypso device for
playing with OsmocomBB. I assume these complaints probably come from
people in the EU and other 900/1800 MHz regions, as US band C139 phones
are still readily available on ebay (63 listings as of right now, all
dirt cheap), but either way, I have what I believe to be the proper
solution to the shortage and the crippled nature of all pre-existing
Calypso devices: a new Calypso board.
Back in 2012 Harald Welte posted here saying that his company was
going to be making a new Calypso board for the very same purpose of
addressing the shortage and the deficiencies of pre-existing devices,
but as far as I know, no such product has ever been produced - nor do
I know if whoever was behind that project even got as far as creating
the design for it.
Fast-forwarding to the present, we now have a ready-to-build design
for a Calypso development board called FCDEV3B, which stands for
FreeCalypso development board, triband. It is based on a reuse of the
known-working Calypso modem design from Openmoko, reuse at the level
of physical PCB layout, based on the GTA02 design files which Openmoko
founder Mr. Sean Moss-Pultz released in April of 2015 at my urging.
Back in 2012 Harald was saying that he was only going to release PDF
schematics but not the full design files for his board; I feel
differently about such matters, hence the complete design files for
*my* board are free to the world:
ftp://ftp.freecalypso.org/pub/GSM/FreeCalypso/fcdev3b/
Now we need to get these boards physically made, and toward that end I
have started a crowdfunding campaign:
https://www.gofundme.com/fcdev3b-board-production-2umevjw
In the interest of transparency, I have to disclose (most people know
it already, but I have to state it anyway) that I do not use OsmocomBB
and will never contribute to Osmocom software because I am working on
my own personally preferred alternative GSM MS firmware implementation,
but when it comes to the hardware I seek to build and offer to the
community, there is no reason why it won't work with OsmocomBB - it
should work just fine.
Because my board is a derivative of Openmoko's modem design and the
part that is different between Openmoko's board and mine (the flash
chip - I will populate a higher-capacity chip on the same footprint)
is not used by OsmocomBB software, the images currently built in
board/gta0x/*.highram.bin should work as-is on my FCDEV3B without
needing any code changes.
Hasta la Victoria, Siempre,
M~
Yes, my plan was:
- get osmocom-bb (layer1/rssi) firmware working (without graphics probably)
- use that work side-by-side to integrate into fernvale nuttx
- create a layer1 "app" in nuttx
- port "mobile" app to nuttx
With the goal being that you can call/text from the nuttx shell.
I have the following hardware with which to experiment:
- c139 motorola phones
- pirelli phone
- a few other calypso phones
- seeedstudio rephone (mtk6261)
- sim800 of various types
- several watch phones (dz09 gt08 v9, both 6260 and 6261)
- raw 6260 chips which I hope to design a custom pcb for
My end goal which is far too ambitious is to make a rock-like device which has no ports/holes:
- bluetooth serial to nuttx shell
- qi wireless charging
- accelerometer gestures for basic controls
- bone conducting speaker
- speech synth (sam/espeak) and voice recognition (pocketsphinx)
- all source is included on-device, even to the point that I would like to port all this work to a forth-like language of my own invention so you can debug, learn and experiment on the device
I have so far fixed up the existing mtk-firmware target and was debating whether to submit that small patch or wait until I get some 626x work done. On that front I have the basic registers and an initial BSI power on routine written (but not tested).
Thanks to all the giants upon whose shoulders I stand to do this work,
Craig
--------------------------------------------
On Thu, 10/13/16, Harald Welte <laforge(a)gnumonks.org> wrote:
Subject: Re: nuttx-bb layout? inside or outside nuttx?
To: "Craig Comstock" <craig_comstock(a)yahoo.com>
Cc: "Marcin Mielczarczyk" <marcin.mielczarczyk(a)gmail.com>, "baseband-devel" <baseband-devel(a)lists.osmocom.org>
Date: Thursday, October 13, 2016, 2:09 AM
Hi Craig,
this is just a small note that
I just met Marcin Mielczarczyk (who did
the
existing but still incomplete MTK support work a few years
back) at
Embedded Linux Conf Europe, and
informed him about your work.
It is really exciting for both of us to see
somebody picking this up and
trying to bring
things together.
If I'm
not mistaken, you basically have the following agenda:
* Structure OsmocomBB in a way
that it can be built 'side-by-side into Nuttx
* Build /integrate it from the
fernvale nuttx port that is available
* Implement the bulk of the MTK L1 integration,
i.e. the interface to
the DSP.
And afterwards hope that you
have something that supports either the
Fernvale, SIM800H, Linkit One, or other MTK 2G
baseband chips out there.
Please let me know this was an accurate
understanding.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a
desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
osmocombb+c118 gsm-sniffer:
youtube:
https://youtu.be/ZDToZIYHmJM
blog:
http://gsmsuperben.blogspot.my/2016/07/osmocombbc118-gsm-sniffer.html
System :
ubuntu12.04-i386(or kali)
一:update system
update(or vi /etc/apt/sources.list )
settings
Inside find software update source download from modifying their own country
Then save the exit
now open terminal
$ sudo apt-get update
$ sudo apt-get upgrade
二:Then install a series of dependency
$ sudo apt-get install libusb-0.1-4 libpcsclite1 libccid pcscd
$ sudo apt-get install libtool shtool autoconf git-core pkg-config make gcc
build-essential libgmp3-dev libmpfr-dev libx11-6 libx11-dev texinfo flex
bison libncurses5 libncurses5-dbg libncurses5-dev libncursesw5
libncursesw5-dbg libncursesw5-dev zlibc zlib1g-dev libmpfr4 libmpc-dev
libpcsclite-dev
(copy)
三:Create several directories , download ARM compiler
$ mkdir osmocombb
$ cd osmocombb
$ mkdir build install src
$ cd src
$ wget ftp://sources.redhat.com/pub/newlib/newlib-1.19.0.tar.gz
四:install gnu-arm-build.3.sh
$ cd ..
$ chmod +x gnu-arm-build.3.sh
$ ./gnu-arm-build.3.sh
See here you can directly enter
五:After you install the add environment
$ cd install/bin
$ pwd
$ vi ~/./. bashrc
export PATH=$PATH:/osmocombb/ install/bin
$ source ~/.bashrc
六:Download and compile osmocomBB
back osmocombb download osmocom
$ git clone git://git.osmocom.org/libosmocore.git
$ git clone git://git.osmocom.org/osmocom-bb.git
When installing libosmocore execute ./configure many people will encounter
No package 'talloc' found such a mistake , because they can not talloc, Here
is the solution
$ wget https://www.samba.org/ftp/talloc/talloc-2.1.7.tar.gz
$ tar -zxvf talloc-2.1.7.tar.gz
$ cd talloc-2.1.7/
$ ./configure
$ make
$ sudo make install
install libosmocore
$ cd libosmocore/
$ autoreconf -i
$ ./configure
$ make
$ sudo make install $ cd ..
Compile osmocombb
$ cd osmocom-bb
$ git checkout --track origin/luca/gsmmap
$ cd src
$ make
七:Modify the problem file ( if you are gnu-arm-build.2.sh and no cell
scanning immobile problem , skip this step )
Enter osmocom-bb find these files and modify them
vi osmocom-bb/ src/target/firmware/board/compal/highram.lds
vi osmocom-bb/ src/target/firmware/board/compal/ram.lds
vi osmocom-bb/ src/target/firmware/board/compal_e88/flash.lds
vi osmocom-bb/ src/target/firmware/board/compal_e88/loader.lds
vi osmocom-bb/ src/target/firmware/board/mediatek/ram.lds
Found inside this string of code
KEEP(*(SORT(.ctors)))
In the following is added
KEEP(*(SORT(.init_array)))
Listed as:
To save , all changes well in entering osmocom-bb / src recompile
$ make -e CROSS_TOOL_PREFIX=arm-none-eabi-
八:Insert your brush into the firmware 118
in osmocom-bb directory
$ cd src/host/osmocon
$ sudo ./osmocon -m c123xor -p /dev/ttyUSB0
../../target/firmware/board/compal_e88/layer1.compalram.bin
Enter appear so wait when you click c118 power button , click on it
If this is the brush into failure , look at your c118 cable, if you are
buying a new phone line proposed to insert a little tight . . Best to shell
removed
九:Scanning station information
Open a new terminal or in osmocom-bb directory
$ cd src/host/layer23/src/misc
$ sudo ./cell_log -O
Then enter
$ sudo ./ccch_scan -i 127.0.0.1 -a ARFCN
ARFCN is circled out above that value , such as column
$ sudo ./ccch_scan -i 127.0.0.1 -a 59
十:install wireshark
Open a new terminal
$ sudo apt-get install wireshark
$ sudo wireshark -k -i lo -f 'port 4729'
In the filter input gsm_sms Then quietly wait for it。。。
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/smocombb-c118-gsm-sniffer-tp4026…
Sent from the baseband-devel mailing list archive at Nabble.com.
I have fernvale-nuttx running on a couple of MTK6260-based watch phones and plan on working on porting layer1 to these devices.
https://www.kosagi.com/forums/viewtopic.php?id=407
I saw the most recent activity on nuttx-bb seems to be http://cgit.osmocom.org/nuttx-bb/log/?h=gnutoo/layer1-2015-wip
wondering if anyone else is working on this elsewhere that we can coordinate?
If there are any particular suggestions/hints/warnings please chime in so I make better progress and have less trouble when I submit pull requests and such.
Cheers,Craig
Greetings,
I have been working with OsmocomBB with C155 model.
After a lot of reading and understanding issues on mailing list, following
the right instructions I am unable to understand where the problem is -
cable or the locked tracfone C155 or my setup.
I was successfully able to build the project.
I am stuck on executing the following command
~/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c155
../../target/firmware/board/compal_e99/layer1.compalram.bin
<No output at all>
<Even on slight push on power button no output>
Please find my specifications and findings below:
1. C155 locked tracfone.
2. FTDI adapter USB serial from - Fonefunshop
Is there a way to test the FTDI adapter ?
dmesg - list that FTDI adapter attached to ttyUSB0.
FTDI VCP driver is built into the Linux kernel. Do I need D2XX driver ?
3. I'm trying to write the firmware (layer1) with a working GSM sim inside
and not tracfone sim card.
4. strace gives me no trouble other than this access("/etc/ld.so.nohwcap",
F_OK) = -1 ENOENT (No such file or directory) - Is it a worry ?
5. When I execute ./osmocon with all necessary params.
I open a new console and type the following ./osmoload memdump 0x000000
0x2000 dump. - Is this valid at this point? just to see where the actual
firmware is located at?
Dumping 12288 bytes of memory at 0x0 to file dump - Nothing gets dumped into
file dump
Although, I see some output - 'got 2 bytes from modem... ' in the osmocon
window - ./osmocon
It would be very kind if someone could guide me.
How do I verify there is a cable issue <Any software to test TX> since I
have bought these and if not the cable them am I doing something wrong ?
Looking forward to the reply!
Thanks,
Gerard.
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/OsmocomBB-C155-stuck-at-flashing…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi,
My advice you is to stop waiting for someone, who will help you.
Just try to dig into the source code yourself, it's interesting!
And in case of any successes, patches are welcome.
With best regards,
Vadim Yanitskiy.
Hey, I finally watched Nico's talk "let me answer that for you" and heard him say he ported layer2/3 to target.
Also found a mailing list message about him cleaning it up and putting it up on git and sending it to a few folks.
Did that code ever get shared? Would be cool to play around with and is certainly something I would eventually want to accomplish for my project of making a phone that works by itself.
-Craig
Dear all,
I have been testing the mobile app for some time but I faced a small problem where not all my sim cards work fine when listening to paging messages. I have seen the patch presented by Harald Welte and I printed the value of ‘tn’ and found out that it is always 0 whatever the IMSI of the sim card is. Did I miss something or is the paging group part still not implemented in the mobile app.
I really appreciate any help.