Hi list,
I'm an information engineering student interested in working on
embedded systems and tlc (especially I would like to get deep into
firmware coding and dsp). In the last years I have been an active
member of the italian openmoko community so I'm familiar with gta0X
phones (I owned a gta02, now I have only a gta01). Two years ago I've
worked at the Trento's research center on the n900 while today I'm
working at a tlc company in Padua.
Even if it's not what I'm working on at the moment, I'd like to spend
some of my time by working on the GSMTAP integration of the Sagem
OT-290.
Is there any news about that? Since the last message on this thread
was posted more than 2 months ago I wanted to know whether anyone was
already working on it.
Thanks,
Thomas Bertani
Hi,
I flashed the rssi application into my C118. The app is really great. But
now I want to flash the original fireware back.
I saved the orignal loader by
host/osmocon/osmoload memdump 0x000000 0x20000 compal_loader_orignal.bin
But when I tried to flash this loader back using
host/osmocon/osmoload fprogram 0 0x000000 compal_loader_orignal.bin,
The phone can't power on.
What did I do wrong?
regards,
wenyao
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/How-to-flash-the-original-firewa…
Sent from the baseband-devel mailing list archive at Nabble.com.
As already mentioned, the Osmocom Meeting will
take place this Saturday, 1.9.2012 at 10:00.
Three people have confirmed that they will come,
I have send them an email with the location details.
Harald is not yet sure if he can attend.
A few suggestions for the meeting:
- I will run a GSM-1800 network with my test license so
you can try out OsmocomBB. If you are interested to
do so please bring your Osmocom phone plus Laptop with
the already installed OsmocomBB software.
- We can do some experiments with SIMtrace if there is any
interest.
- There should still be enough time for other things, we
can decide what to do during the meeting.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
I have now selected the day for the meeting which should
match for all who have send me their preferred days. The
first Osmocom meeting in Bavaria near Pfarrkirchen will
be held on:
Saturday, 1. September, starting at 10:00
If you are going to come, please let me know until
next Wednesday (29. August). I will then send you
a private email with the details of the location.
The agenda is not yet set, but it seems that at least
those who send me their areas of interest are mainly
targeted towards GMS (OpenBSC/OsmocomBB). We can
of course also talk about other stuff, e.g. RTL-SDR,
but for this it would be nice if one of the RTL-SDR
experts would join us (here you have the chance to
receive a nearly clean/empty spectrum without much
noise from other sources ;-).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi all!
This is the announcement for the next Osmocom Berlin meeting.
Aug 22, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin
There is no formal presentation scheduled for this meeting. However,
updates will be provided on various current developments, such as
* Progress on the CC32RS512 smart card (osmo-cos)
* Possibly: Status of current attempts to get CSD implemented in OpenBSC
If you are interested to show up, feel free to do so. There is no
registration required. The meeting is free as in "free beer", despite
no actual free beer being around.
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)
Dear Ellen,
On Mon, Aug 20, 2012 at 04:26:04PM +0200, Ellen Apolinar wrote:
> btw. where is the location when it is 630 km away from Berlin?
As Dieter wrote in his original post:
> at my place in the south-east of Bavaria near Pfarrkirchen
So if you just type "Pfarrkirchen, Germany" into your favorite internet
map service, you should get a pretty clear idea.
As there seems to be frequent misconception: This is _not_ a developer
conference or anything like that. Just an informal user group meeting,
like those we have in Berlin every two weeks.
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)
Hi all!
There are some signs that the supply of Motola C1xx phones is not
endless, after all.
As such, sysmocom has decided to manufacture some custom boards with the
typical TI Calypso/Iota/Rita design. The RF PA will be RFMD RF3166, and
the combined NOR + SRAM will be a Samsung K5A3281. All parts are
still available from the surplus market.
Schematics will be published in PDF form only, Gerber/PCB files will not
be released (so basically the same like the OsmoSDR situation). All
software used is already available as OsmocomBB under a *GPL license.
Any help and input from the community will of course be appreciated.
The design will be more or less a standard tri-band calypso phone design
(900/1800/1900), with possibly a placement option for having
850/1800/1900. We'll be targetting a modem as opposed to a phone
design, so no built-in keypad / display / battery, but external
connections.
At one edge there should be a PCB edge connector, possibly with
mechanical form-factor of PCIe (sinc they're cheap). This connector
should allow the module to be plugged into a back-plane with a number of
other modems.
I've crated an initial Wiki page about the possible / intended
modifications from a classic phoned design at
http://bb.osmocom.org/trac/wiki/Custom_Calypso_Board :
* expose JTAG
* board-edge connector for plugging many boards into one backplane
* external clock input / buffered clock output
* RF connector standard u.fl or SMA or optionally separate Rx/Tx?
* I2C/SPI and both UARTs available on headers
* on-board EEPROM for storing persistent data, even beyond NOR flashing
* SIM card slot, SIM interface also present on header
* additional / unused TPU ports
* header for TSP / TPU and all data/control interfaces between iota/rita/calypso
* RTC crystal and footprint for lithium backup battery
* version of the board with uplink / downlink filters switched
Feel free to discuss other extensions/modifications you may have in
mind. Please note that fundamentally we are still heading for a calypso
based design, so this will not be a board that just contains the
Iota/Rita and some FPGA or general purpose DSP, as some people have
proposed in the past. However, it may be possible to have connector
footprints for the TSP / BSP interfaces and make some boarde that don't
contain the calypso/ram/nor parts.
Pricing will definitely not be anywhere near to the price of current
phones. You cannot even source all the components for the price of
those refurbished phones, let alone the fairly complex 6-layer PCB.
Also, the quantities will be low, we may be manufacturing something like
100 units a batch only.
This is a low-effort / side project, so I'm conservative with any
estimates and would say that we're happy to have boards shipping by the
end of this year.
Regards,
Harald (waiting for the e-mail flood)
--
- 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)
Hello everyone
In one of the ML I have read that, BCCH-SDCCH-BCCH-TCH is required for
listen to the TCH.
In my case(Test N/w) I receive an IMM ASS, go to (SDCCH/4 + SACCH/4) TS:0
subchannel 2.
As soon as I find an ASS_CMD I send a l1ctl_tx_dm_est_req with new channel
parameters and jump to a TCH/F+SACCH/F+FACCH/F TS 4. I am receiving bursts
after this.
They contain SACCH SI5/6 as I see them in Wireshark and also some bursts (I
hope a mix of FACCH and TCH). Is it necessary to do BCCH again. If I don't
do Won't I receive TCH frames.? Will the be good TCH frames. ?
But I see the tch_schedule_set working good. I receive once UL and next DL
bursts. and sometimes SACCH.
Can someone explain me.
Thank You
Altaf
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Moving-to-TCH-without-doing-a-BC…
Sent from the baseband-devel mailing list archive at Nabble.com.
hello list
i have been trying to sniff FR codec traffic from OpenBTS network.i tried
to modify patch of bob with little help of airprobe.
but when i try to play file toast says bad frame no.
can any one help me with that
here is app link
http://pastebin.com/GwmB7UGK
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
Hi,
I have make a patch for the Pirelli DP-L10 created. You can enable and
disable the patch in the makefile (src/target/firmware/Makefile).
The Keypad layout is tested with rssi.bin app. Only the power button
is not available.
regards
Marco
