19 Jul
2013
19 Jul
'13
5:39 p.m.
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
19 Jul
19 Jul
11:09 p.m.
Hi,
On 19.07.2013 17:39, Craig Comstock wrote:
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
Yes, the instructions are out of date. Meanwhile the chainloader has
been integrated into osmocon, you just need to run:
./osmocon -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/layer1.highram.bin
Regards,
Steve
20 Aug
20 Aug
3:39 p.m.
I tried but seem to be getting an error...
pi@raspberrypi ~/osmocom-bb/src/host/osmocon $ ./osmocon -d tr -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/hello_world.highram.bin
got 1 bytes from modem, data looks like: 00 .
got 6 bytes from modem, data looks like: 66 74 6d 74 6f 6f ftmtoo
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
I tried a different computer that is definitely faster and that didn't solve it. I am
using a different serial cable, this one a home wired cp2102 where before I think I got
this working with a direct wire to the raspberry pi alt serial pins.
Are there any links to describe what is going on at the beginning when you press the power
button?
I found these links as well...
http://lists.osmocom.org/pipermail/baseband-devel/2011-February/001407.html (didn't
try this, but can)
http://lists.osmocom.org/pipermail/baseband-devel/2011-January/001053.html (tried this...
same result)
Thanks,
Craig
________________________________
From: Steve Markgraf <steve(a)steve-m.de>
To: Craig Comstock <craig_comstock(a)yahoo.com>
Cc: "baseband-devel(a)lists.osmocom.org" <baseband-devel(a)lists.osmocom.org>
Sent: Friday, July 19, 2013 4:09 PM
Subject: Re: chainload.compalram.bin missing?
Hi,
On 19.07.2013 17:39, Craig Comstock wrote:
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
Yes, the instructions are out of date. Meanwhile the chainloader has
been integrated into osmocon, you just need to run:
./osmocon -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/layer1.highram.bin
Regards,
Steve
4:13 p.m.
Craig Comstock wrote:
I tried but seem to be getting an error...
pi@raspberrypi ~/osmocom-bb/src/host/osmocon $ ./osmocon -d tr -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/hello_world.highram.bin
got 1 bytes from modem, data looks like: 00 .
got 6 bytes from modem, data looks like: 66 74 6d 74 6f 6f ftmtoo
got 1 bytes from modem, data looks like: 6c l
Received FTMTOOL from phone, ramloader has aborted
Communications problem. Try different cables. If you had rpi working
then go back to using that, rather than introducing new unknowns.
//Peter
21 Aug
21 Aug
8:48 p.m.
I got things working for both C115 and C139 w/ rpi, osmocom built natively on debian and a
cheap cp2102 usb raw stick direct from china/ebay.
For C139
./osmocon -d tr -p /dev/ttyUSB0 -m c140xor -c
../../target/firmware/board/compal_e86/rssi.highram.bin
For C115
./osmocon -d tr -p /dev/ttyUSB0 -m c123xor -c
../../target/firmware/board/compal_e88/rssi.highram.bin
Sorry for the trouble... looks like "xor" and chainloading via -c were my two
problems.
-Craig
22 Aug
22 Aug
6:30 p.m.
New subject: C139 loading problems - different flash/layout the reason?
So I looked and there seem to be two board layouts involved here. The one's with the
Intel flash seem to work fine. The others that have the MemoCom? flash don't work. The
one's with MemoCom are missing several test points visible from the battery
compartment as visible on the images on the webpage:
http://bb.osmocom.org/trac/wiki/MotorolaC140
So maybe there is something different about these other C140 that makes them not work with
osmocon.
I get:
pi@raspberrypi ~/osmocom-bb/src/host/osmocon $ ./osmocon -d tr -p /dev/ttyUSB0 c140
../../target/firmware/board/compal_e86/hello_world.compalram.bin
got 7 bytes from modem, data looks like: 66 74 6d 74 6f 6f 6c ftmtool
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
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
3909
days inactive
3943
days old
baseband-devel@lists.osmocom.org
5 comments
3 participants
participants (3)
-
Craig Comstock -
Peter Stuge -
Steve Markgraf