Hi,
I've got 4 C115 phones (all same firmware). One is not loading and
reporting the ftmtool error. The others are loading fine.
Could this be caused by a blown RX input on the chip? Or could there
other reasons why it does not work. I tried both an FTDI cable and a
buspirate.
Best regards,
Job
output:
./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/loader.compalram.bin
got 2 bytes from modem, data looks like: 04 01 ..
got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A
got 1 bytes from modem, data looks like: 01 .
got 1 bytes from modem, data looks like: 40 @
Received PROMPT1 from phone, responding with CMD
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin):
file_size=17132, hdr_len=4, dnload_len=17139
got 1 bytes from modem, data looks like: 66 f
got 1 bytes from modem, data looks like: 74 t
got 1 bytes from modem, data looks like: 6d m
got 1 bytes from modem, data looks like: 74 t
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 6c l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65 e
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 72 r
On Sat, 25 Jun 2011 23:13:10 +0530, "R M" <rm.engineer84(a)gmail.com> wrote:
>
> Can you please provide me the patch for the present version of
> osmocon.c as you mentioned in the mail as I am unable to apply the
> patch manually.
I don't have a patch for the current version as I currently don't
work with OsmocomBB.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Harald,
On Sat, 4 Jun 2011 08:46:50 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote:
>
> i have never heard of somebody doing this on windows 7. Almost everyone
> here uses Linux or MacOS. And the only prominent Windows user involved
> in the project is working with Windows XP.
At least on my Cygwin installation under Windows XP the serial port
is accessible as "/dev/ttySx" (x is "0" for COM1, "1" for COM2 and
so on). All the USB to serial converters I am aware of are virtual
COM ports on Windows which means that they are accessible the same
way, e.g. if the virtual COM port is "COM7" it can be be accessed
as "/dev/ttyS6",
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello,
since I am new to this list, I want to take the opportunity to thank
your for your efforts. It is just awesome that one can do phonecalls
with an open-source baseband stack.
I'm new to the project and I'm searching a method to send prepared
packets (Layer 3) to my basestation in my lab. I'm searching now for
the best way to do so, is there already a script allowing me to
perform that task? I couldn't find one when I searched. If there is
none available I would try to build one using code located in layer23.
I would be glad if you could point me to the method if there is
already something available.
With best regards
Hi list,
with a bit of help from Harald, I finally managed to push my commits.
Hence, we have:
- platform support for Calypso (timers, irq, ...)
- char device driver for keypad (/dev/keypad)
- some hacks reusing old drivers for SPI/poweroff and sercomm
The console currently outputs in osmocon while you have to write to the
loader interface with a python script. Flushing is kind of a problem
too. Haven't checked how to fix those two, so any volunteers?
Bye,
Stefan
Hello List,
as part of my research, I'm trying to use the 'mobile' app to send and
receive data on traffic channels. That is, I want to replace the audio
stream from the phone's microphone/speaker by something else supplied
by the computer attached to the phone. I realize this feature isn't
fully implemented in osmocom-BB currently, and I'm willing to write
some code to make it work (and share my results with this list if
there's any interest). Here's what I've done so far:
- merged the sylvain/traffic and jolly/voice branches
- added some code to mobile that writes the payload of downlink frames
to a user-specified file once a call has been established
As far as the receiving end goes, this seems to work. I'm still
unclear as to where I should start on the sending side -- I do expect
it to be somewhat more complex. Any pointers -- or a rough outline of
what is left to be done to make this work -- would be much
appreciated.
Kind regards,
Michael Voelske
> Because you're using a C123 that doesn't require a 'MAGIC' marker when
> doing the code download.
netbook ~ # osmocom-roaming/src/host/osmocon/osmocon -p /dev/ttyUSB0 -m c140xor osmocom-roaming/src/target/firmware/board/compal_e88/layer1.compalram.bin
got 1 bytes from modem, data looks like: 00 .
does not seem so. but anyway: it is not a problem of the application "mobile". the process of one phone gets stuck while waiting for power measurement replay. the process of the other phone waits for the RACH confirm but never receives it. it looks pretty much like a broken layer1 or serial connection.
-----Ursprüngliche Nachricht-----
Von: Sylvain Munaut [mailto:246tnt@gmail.com]
Gesendet: Mittwoch, 15. Juni 2011 13:31
An: Andreas.Eversberg
Cc: Basem Ahmed; baseband-devel(a)lists.osmocom.org
Betreff: Re: Facing issues in using OSMOCOM
On Wed, Jun 15, 2011 at 11:35 AM, Andreas.Eversberg
<Andreas.Eversberg(a)versatel.de> wrote:
> mine is >50k. why am i not getting the same warning?
Because you're using a C123 that doesn't require a 'MAGIC' marker when
doing the code download.
But when using the c140xor, osmocon will have to insert a specific
marker at a specific address for the bootloader to accept the file and
if the file is > 15 k, that marker will overwrite part of the binary
which will lead to something that can crash at any time (because
whatever code is overwritten will vary depending on a bunch of
factors)
Sylvain