> > I'm writing some UI/firmware [...]
> That sounds neat... are you doing it in some visible git repository perchance?
I'm just hacking on layer1/main.c right now. Not even sure I would put in a repo since I want to implement some form of t-9 character and word fanciness. Maybe I could make that a module or think of an open-source/free paradigm for entering text w/ the keypad.
http://www.google.com/patents?id=PmgCAAAAEBAJ (T9)
http://www.google.com/patents/US3967273 (funny bell labs method using two key presses always)
(the list goes on and on I think...)
My thinking is that I might start with this hacked layer1 and gradually try to bring bits of mobile into the firmware/ui.
Also just wanting to fiddle around with how the phone will "feel" with a console interface. aka UI prototyping.
Cheers,
Craig
Was wondering if anyone has tried to use qemu to make a device emulator? I'm writing some UI/firmware and it seems like it might be a nice way to iterate on code.
Also was thinking I would need to rework keypad.c so that I can get key hold/repeat events since I want to know when a key is being held down at some fairly short interval. Any suggestions/previous work/cautions?
Thanks,
Craig
I was trying to load some apps to a Motorola C139 and found that after building osmocom-bb that there were no chainload image files built. Am I using the wrong branch somehow? Are the instructions out of date on this page:
http://bb.osmocom.org/trac/wiki/MotorolaC140
./osmocon -p /dev/ttyUSB0 -m c140 -c ../../target/firmware/board/compal_e86/layer1.highram.bin ../../target/firmware/board/compal_e86/chainload.compalram.bin
The page mentions something about a magic value that must be placed into memory for the bootloader... could that be added to osmocon somehow so that specifying -m c140 takes care of it?
"After the download has completed, it expects the magic string "1003" (0x31 0x30 0x30 0x33) at the RAM address 0x803ce0"
Thanks,
Craig
Dear all,
I was wondering if uplink sniffing is enabled by default in latest firmware as file "osmocom-bb/src/target/firmware/layer1/prim_sniff.c" has been modified and does not hold "#if 0" bit at line 288 anymore.
Thanks,
George Andguladze
Peter Stuge <peter(a)stuge.se> wrote:
> > Actually my hope is to build a quad-band phone
> That would be neat too.
> [...]
> I was thinking about phone-as-BTS, but same principle, no
> (or just the appropriate) filters.
Unfortunately these two goals (quad-band support on the one hand, and
filter hackability on the other hand) seem to be in conflict. It
seems to me that trying to build a quad-band phone using separate
antenna switch and Rx SAW filter components would be very messy,
probably too messy for an RF-clean PCB layout - hence necessitating
the use of an integrated RF front-end part that has all that mess
hidden inside. (See ftp.ifctf.org/pub/GSM/Calypso/M034F.pdf for an
example of wha I mean.)
But using an integrated RF FEM like that M034F would surely preclude
the possibility of filter hacking...
Once again, my goal is to produce a Totally Free Phone for everyday
use in one's pocket/purse, not GSM hacking - and I reason I must not
be the only person on this list who desires such; I reason that there
must be other lurkers on this list who watch with frustration as the
years go by, there are all kinds of hacks made, but virtually zero
progress toward an end-user-usable Free phone.
It's obvious that OsmocomBB and FreeCalypso will always be two separate
projects: the former focused on GSM hacking and security research, the
latter on everyday-phone end-user needs. All I'm hoping for is that
the two projects could be at least somewhat amicable, and cooperate in
things like amassing hardware knowledge - rather than be all-out
hostile.
SF
Sylvain Munaut <246tnt(a)gmail.com> wrote:
> And why exactly should we help you when you publicly stated [1] that
> you'd rather shoot us then yourself
> [1] http://lists.openmoko.org/pipermail/community/2012-March/066565.html
A little clarification is in order:
* In my past negative interactions with certain individuals who have
previously served as employees or contractors of Openmoko-Inc and
who currently serve as lead developers of OsmocomBB, the crux of the
dispute was those individuals' unwillingness to share with all
Humanity (yes, *all Humanity*, *not* "me" - I could be dead tomorrow
and nothing will change) those COFF object files with symbolic
information which Om-Inc had received from TI, and/or their voluntary
choice to live and/or accept voluntary citizenship in a country that
deems such sharing to be illegal - obviously a voluntary choice which
I have NOT made.
* There has been one major change in the year and a half since that
post of mine quoted by Sylvain - I have discovered this:
http://scottn.us/downloads/peek/
[In case ScottN, whoever he is, takes the ware down from his website,
it's already archived on my mini-Wikileaks at
ftp.ifctf.org/pub/GSM/LoCosto - but for as long as ScottN's copy is
up, it should be much faster.]
The discovery of the above source (which is almost complete source
with very little in object-only form) makes it now unnecessary for me
to sacrifice my life in a gunfire exchange with German or Russian
police in order to free Openmoko's COFF objects - I'm pretty confident
in my ability to recreate something very similar, but full-source from
this recently discovered "peek" ware and other more recently discovered
leaks, also on my FTP site.
> than help us in any way ...
It is true that I have chosen to use a different Free Software GSM
stack (plus UI etc) implementation for my personal use, hence any
contributions from me to the software side of the OsmocomBB project
are indeed unlikely.
However, I am hoping that the project to build new free phone hardware
can be done as a joint project between the two camps. The hardware
design files will be free for anyone to download and do with as s/he
pleases, and obviously each user is free to run whatever software s/he
likes: OsmocomBB, FreeCalypso, or some 3rd or 4th or other choice that
may exist in the future.
SF
Hello fellow Calypso phone hackers,
Not having found an already-existing Calypso phone that is exactly to
my liking (of the ones supported by OsmocomBB, the Pirelli comes
closest to my ideal, but even that one has a few things I don't like,
and most important of all, the availability of these phones on the
market has already shrunk down to zilch - so the day is near when it
will be just as legendary-unobtainium as the TSM30), I am setting out
to build my own.
I am setting out to design and build a new Calypso/Iota/Rita phone,
one that will be specifically designed to run Free Software as its
firmware: either OsmocomBB or FreeCalypso (my own personal alternative
free GSM firmware implementation), up to each user's individual choice.
My design will be a phone, not a modem (i.e., complete with the
essential UI elements, as in LCD and keypad), and it will be a
dumb/plain/feature phone, i.e., the Calypso will be the main/sole CPU -
not a smartphone like Openmoko etc.
Before I tackle the difficult problem of either making a new plastic
case or choosing some existing one, I will start out by building a
bare GSM development board - basically a complete phone sans case,
built on a non-form-factor-controlled PCB. This development board
will probably end up being very similar to the one which Harard Welte
has announced here a little over a year ago, but with one major
difference: *all* hardware design source files (as in schematic, BOM
and PCB layout source) will be openly released, with absolutely nothing
withheld, and in fact the development itself will take place in a
public source control repository. Therefore, regardless of whether I
succeed or fail in the ultimate goal of producing a complete phone
packaged in a plastic case, there will be an Open Source Hardware
design for a working Calypso GSM board which others will be able to
use as a starting point - something that wouldn't be possible (or at
least less convenient) with Harald's PDF-schematics-only version.
However, the above vaporware announcement is not the real purpose of
my post. Instead, I am currently in the negotiations with several
Chinese sellers of Calypso/Iota/Rita/etc chips, and I'm soliciting
advice on exactly which variant of each chip I should use:
* The Calypso chip in both GTA02 and Pirelli DP-L10 (the two existing
designs I use as references to be copied whenever it makes sense) is
PD751992AZHH. I can easily get this exact part, but I can also get
ones with GHH or AGHH suffixes. I'm venturing a guess in that the A
seems to go with the 751992 number, i.e., it's part of the die
revision, and as to the difference between GHH and ZHH, I'm guessing
that it's the RoHS difference: I'm guessing that GHH has balls made
of real SnPb solder, whereas ZHH has the "lead-free solder" junk
substituted instead. Because I'm very fortunate to NOT live in the
EU or anywhere near, I'm not subject to any EU-nian laws like the
RoHS idiocy, and I generally prefer to use real SnPb solder whenever
possible. So I wonder: can someone confirm if indeed PD751992AGHH
is the exact same Calypso chip as the PD751992AZHH used in the GTA02
and Pirelli phones, but with real non-RoHS solder balls instead, or
is it something different?
* Which Iota variant is better: TWL3014 or TWL3025? I'm thinking
TWL3025, reasoning that it being newer probably means having some
internal bugfixes or minor improvements, but perhaps the older
TWL3014 is better instead?
* As to the Rita, the base part number appears to be TRF6151C in all
phones currently supported by OsmocomBB, so I'm sticking with this
base part number. But there are additional suffixes after the 'C'
in that P/N - would anyone happen to know what these suffixes mean,
and which variant I should use?
* For the RF PA, I see that the GTA02 uses RF3166 from RF Micro
Devices (one of Harald Welte's posts regarding his planned Calypso
board also mentioned him planning to use the same PA), whereas the
Pirelli and most other feature phones supported by OsmocomBB tend to
use Skyworks parts instead. Which is better? I'm currently leaning
toward the RF3166, but if someone has a recommendation that is
actually backed by some knowledge/reason rather than just a guess
like mine, I'll listen. :-)
* If I do go with the RF3166, any idea as to what the different suffix
versions are?
TIA for any input,
SF
