<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi Lia,<br>
<br>
I have tested another cable (USB <-> 2,5 jack, speacial for
Compal phones) - it is the same chip (Prolific) and I am able to
load firmware too. Although it is the same chip, there is a
difference that this one makes the osmocon printing those messages
instantly when phone is not connected:<br>
<br>
<font face="Courier New, Courier, monospace"><small>got 1 bytes from
modem, data looks like: f5 .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: f5 .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: f5 .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: fd .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: f5 .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: fd .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: ea .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: ea .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: ea .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: ea .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: fd .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: ea </small></font><br>
<br>
If I connect phone, printing stops. Here is what happened when I
tried to load firmware without xor (-m c123) and pressed the button:<br>
<font face="Courier New, Courier, monospace">(This happened every
attempt without xor flag)<br>
<br>
<small>Received PROMPT2 from phone, starting download<br>
handle_write(): 1087 bytes (1087/50947)<br>
got 1 bytes from modem, data looks like: 1b .<br>
got 1 bytes from modem, data looks like: f6 .<br>
got 1 bytes from modem, data looks like: 02 .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: 45 E<br>
got 1 bytes from modem, data looks like: 53 S<br>
got 1 bytes from modem, data looks like: 16 .<br>
Received DOWNLOAD NACK from phone, something went wrong :(<br>
got 1 bytes from modem, data looks like: 66 f<br>
got 1 bytes from modem, data looks like: 74 t<br>
got 1 bytes from modem, data looks like: 6d m<br>
got 1 bytes from modem, data looks like: 74 t<br>
got 1 bytes from modem, data looks like: 6f o<br>
got 1 bytes from modem, data looks like: 6f o<br>
got 1 bytes from modem, data looks like: 6c l<br>
Received FTMTOOL from phone, ramloader has aborted<br>
got 1 bytes from modem, data looks like: 65 e<br>
got 1 bytes from modem, data looks like: 72 r<br>
got 1 bytes from modem, data looks like: 72 r<br>
got 1 bytes from modem, data looks like: 6f o<br>
got 1 bytes from modem, data looks like: 72 r<br>
got 1 bytes from modem, data looks like: 00 .</small></font><br>
<br>
<br>
If you have USB adapter (I guess you have), you dont need to check
model, check 'lsusb'<br>
<br>
<font face="Courier New, Courier, monospace"><small>[root@amilo
osmocon]# lsusb<br>
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
<b>Bus 002 Device 017: ID 067b:2303 Prolific Technology, Inc.
PL2303 Serial Port</b></small></font><br>
<br>
If you have Prolific, which is very common, I encourage you to use
xor flag. You can also try to switch on your phone to check if
original<br>
firmware boots. I experienced during my early tests, that phone
crashed (probably SRAM) and it was unable to boot even original fw.
In case phone is crashed, reconnect battery and it will fix itself.<br>
<br>
Here is the ACK after hello world load:<br>
<br>
<font face="Courier New, Courier, monospace"><small>handle_write():
768 bytes (17919/19787)<br>
handle_write(): 768 bytes (18687/19787)<br>
handle_write(): 768 bytes (19455/19787)<br>
handle_write(): 332 bytes (19787/19787)<br>
handle_write(): finished<br>
got 1 bytes from modem, data looks like: 1b .<br>
got 1 bytes from modem, data looks like: f6 .<br>
got 1 bytes from modem, data looks like: 02 .<br>
got 1 bytes from modem, data looks like: 00 .<br>
got 1 bytes from modem, data looks like: 41 A<br>
got 1 bytes from modem, data looks like: 03 .<br>
got 1 bytes from modem, data looks like: 42 B<br>
Received DOWNLOAD ACK from phone, your code is running now!<br>
<br>
<br>
OSMOCOM Hello World (revision
osmocon_v0.0.0-754-gb5abcb6-modified)<br>
======================================================================<br>
Device ID code: 0xb4fb<br>
Device Version code: 0x0000<br>
ARM ID code: 0xfff3<br>
cDSP ID code: 0x0128<br>
Die ID code: efce3b1ce1001255<br>
======================================================================<br>
REG_DPLL=0x2413<br>
CNTL_ARM_CLK=0xf0a1<br>
CNTL_CLK=0xff91<br>
CNTL_RST=0xfff3<br>
CNTL_ARM_DIV=0xfff9<br>
==============================================</small></font><br>
<br>
<br>
Looking forward your response,<br>
<br>
Tomas<br>
<br>
<br>
<blockquote
cite="mid:12961327.3754611295203226842.JavaMail.defaultUser@defaultHost"
type="cite">
<p>Hi Tomas, </p>
<p>thanks for your feedback.</p>
<p>Actually, I've tried both flags (woth/without xor extension),
but hte result is the same.</p>
<p>So, in your opinioni, the problem could depend on the cable?</p>
<p>I don't have the cable model now, but I can send you this
information Tuesday.</p>
<p>Thanks again.</p>
<p>cheers.</p>
<p>lia<br>
<br>
</p>
<blockquote>----Messaggio originale----<br>
Da: <a class="moz-txt-link-abbreviated" href="mailto:deacon@volny.cz">deacon@volny.cz</a><br>
Data: 16-gen-2011 4.26<br>
A: <a class="moz-txt-link-rfc2396E" href="mailto:list_mailing@libero.it"><list_mailing@libero.it></a><br>
ubut Ogg: Re: C115 loader.compalram.bin<br>
<br>
<!--
-->Hello,<br>
I have C115 too and I use '-m c123xor' switch, the phone mostly
boots on 1st button push (I never reacher full load with '-m
c123').<br>
<br>
<font face="Courier New, Courier, monospace">./osmocon -p
/dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/hello_world.compalram.bin<br>
./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/loader.compalram.bin</font><br>
<font face="Courier New, Courier, monospace">./osmocon -p
/dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/layer1.compalram.bin</font><br>
<br>
I have FTDI USB<->RS232 + Calypso serial. When load fails
(with xor), I have a feeling that it helps reconnection cable to
the phone.<br>
(I have also Calypso USB cable which I haven't tested yet, will
report later.)<br>
<br>
- Tomas<br>
<br>
<br>
<blockquote cite="mid:4D32648F.10404@volny.cz" type="cite">
<blockquote
cite="mid:30082936.3551511295024795318.JavaMail.defaultUser@defaultHost"
type="cite">
<pre wrap="">Hello.
I'm trying to load the loader.compalram.bin.
The behaviour is very strange because sometimes the download is complete and
successfull, sometimes; in particular, in this case, the download is complete,
but any ACK is sent back from the mobile phone (see below).
./osmocon -p /dev/ttyUSB0 -m c123 ../..
/target/firmware/board/compal_e99/loader.compalram.bin
got 2 bytes from modem, data looks like: 2e c8 ..
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_e99/loader.compalram.bin):
file_size=21752, hdr_len=4, dnload_len=21759
got 1 bytes from modem, data looks like: 1b .
got 1 bytes from modem, data looks like: f6 .
got 1 bytes from modem, data looks like: 02 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 41 A
got 1 bytes from modem, data looks like: 02 .
got 1 bytes from modem, data looks like: 43 C
Received PROMPT2 from phone, starting download
handle_write(): 4096 bytes (4096/21759)
handle_write(): 4096 bytes (8192/21759)
handle_write(): 4096 bytes (12288/21759)
handle_write(): 4096 bytes (16384/21759)
handle_write(): 4096 bytes (20480/21759)
handle_write(): 1279 bytes (21759/21759)
handle_write(): finished
The target phone is C115. I tried compal_exx and the result is the same :-(
Please, can someone help me to understand the reasons?
Thanks in advance.
</pre>
</blockquote>
<br>
</blockquote>
<br>
<br>
</blockquote>
<p><br>
</p>
</blockquote>
<br>
</body>
</html>