problems on ubuntu (64bit?)

classic Classic list List threaded Threaded
5 messages Options
mki
Reply | Threaded
Open this post in threaded view
|

problems on ubuntu (64bit?)

mki
if i boot the c118 from a ubuntu 10.04 lts (64bit) or a g20 arm minipc i get this here

/opt/osmocom/bin/osmocon -m c123 -p /dev/ttyUSB0 /opt/osmocom/firmware/board/compal_e88/layer1.compalram.bin

got 2 bytes from modem, data looks like: 2f 81  /.
got 5 bytes from modem, data looks like: 00 f6 02 00 41  ....A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
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
got 1 bytes from modem, data looks like: 00  .

if i boot it from my mac book or a ubuntu (32bit) i get this:
osmocon -m c123xor -p /dev/tty.usbserial sylvain/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin
got 6 bytes from modem, data looks like: 00 00 00 00 00 00  ......
got 1 bytes from modem, data looks like: 2f  /
got 1 bytes from modem, data looks like: 81  .
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: 01  .
got 1 bytes from modem, data looks like: 40  @
Received PROMPT1 from phone, responding with CMD
read_file(sylvain/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin): file_size=54152, hdr_len=4, dnload_len=54159
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(): 1023 bytes (1023/54159)
handle_write(): 1024 bytes (2047/54159)
handle_write(): 1024 bytes (3071/54159)
handle_write(): 1024 bytes (4095/54159)
handle_write(): 1024 bytes (5119/54159)
handle_write(): 1024 bytes (6143/54159)
handle_write(): 1024 bytes (7167/54159)
handle_write(): 1024 bytes (8191/54159)
handle_write(): 1024 bytes (9215/54159)
handle_write(): 1024 bytes (10239/54159)
handle_write(): 1024 bytes (11263/54159)
handle_write(): 1024 bytes (12287/54159)
handle_write(): 1024 bytes (13311/54159)
handle_write(): 1024 bytes (14335/54159)
handle_write(): 1024 bytes (15359/54159)
handle_write(): 1024 bytes (16383/54159)
handle_write(): 1024 bytes (17407/54159)
handle_write(): 1024 bytes (18431/54159)
handle_write(): 1024 bytes (19455/54159)
handle_write(): 1024 bytes (20479/54159)
handle_write(): 1024 bytes (21503/54159)
handle_write(): 1024 bytes (22527/54159)
handle_write(): 1024 bytes (23551/54159)
handle_write(): 1024 bytes (24575/54159)
handle_write(): 1024 bytes (25599/54159)
handle_write(): 1024 bytes (26623/54159)
handle_write(): 1024 bytes (27647/54159)
handle_write(): 1024 bytes (28671/54159)
handle_write(): 1024 bytes (29695/54159)
handle_write(): 1024 bytes (30719/54159)
handle_write(): 1024 bytes (31743/54159)
handle_write(): 1024 bytes (32767/54159)
handle_write(): 1024 bytes (33791/54159)
handle_write(): 1024 bytes (34815/54159)
handle_write(): 1024 bytes (35839/54159)
handle_write(): 1024 bytes (36863/54159)
handle_write(): 1024 bytes (37887/54159)
handle_write(): 1024 bytes (38911/54159)
handle_write(): 1024 bytes (39935/54159)
handle_write(): 1024 bytes (40959/54159)
handle_write(): 1024 bytes (41983/54159)
handle_write(): 1024 bytes (43007/54159)
handle_write(): 1024 bytes (44031/54159)
handle_write(): 1024 bytes (45055/54159)
handle_write(): 1024 bytes (46079/54159)
handle_write(): 1024 bytes (47103/54159)
handle_write(): 1024 bytes (48127/54159)
handle_write(): 1024 bytes (49151/54159)
handle_write(): 1024 bytes (50175/54159)
handle_write(): 1024 bytes (51199/54159)
handle_write(): 1024 bytes (52223/54159)
handle_write(): 1024 bytes (53247/54159)
handle_write(): 912 bytes (54159/54159)
handle_write(): finished
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: 03  .
got 1 bytes from modem, data looks like: 42  B
Received DOWNLOAD ACK from phone, your code is running now!


OSMOCOM Layer 1 (revision osmocon_v0.0.0-737-ga4e3431-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: c1900c14ae021565
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:
Assert DSP into Reset
Releasing DSP from Reset
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 1880!

-- its working :-)

I have tried to copy the firmware from the working machine to the bad machines but the result is the same.
Is it possible that the usb driver from ubuntu 10.04 lts 64bit is silly????
cable (akku-king) phone all is the same on every plattform.
Have some body an Idea?

mki
Reply | Threaded
Open this post in threaded view
|

Re: problems on ubuntu (64bit?)

mki
some more informations:
sometimes it is running, e.g. after a fresh reboot,
but not after a rmmod pl2303 and modprobe pl2303.
It seems it is something with the timing.
Other people has also problems with programmers/chipreaders
based on the pl2303 chipset and new ubuntu installations.
Any ideas??
Reply | Threaded
Open this post in threaded view
|

Re: problems on ubuntu (64bit?)

Sylvain Munaut
Hi,


> some more informations:
> sometimes it is running, e.g. after a fresh reboot,
> but not after a rmmod pl2303 and modprobe pl2303.
> It seems it is something with the timing.
> Other people has also problems with programmers/chipreaders
> based on the pl2303 chipset and new ubuntu installations.
> Any ideas??

The bootloader inside the phone is sensitive to timing ... not really
anything we can do about it. (basically if there is a 'gap' too big
between two chars, the bootloader will fail).

You can try the mode -m c123xor  instead of -m c123  (which mods a
small detail).

Also make sure you don't use a virtual machine, that screws up the
timing almost certainly.


Cheers,

    Sylvain

mki
Reply | Threaded
Open this post in threaded view
|

Re: problems on ubuntu (64bit?)

mki
i have tried both modes on a fresh installed ThinkPad T61,
on a slower Atom based machine it is working,
but on a embedded foxg20 with a arm cpu only sometimes.
really strange....
mki
Reply | Threaded
Open this post in threaded view
|

Re: problems on ubuntu (64bit?)

mki
so, i have connected the serial from the netus g20 board directly to the C118 and it is running but at the same machine with the akku-king adapter it is not :-(
but for now i am lucky to have a super small computer working with your great software