Hi,
I could not resist buying a C116 for 15 euro, so I compiled osmocombb and connected a 3.3V serial cable.
Of course the C116 was not in the supported list, but I was hoping it would work as it seems that it is very similar to the C115.
Here is my load attempt: (used -m c123 ) but there's no loading of the image. I am not using TX mode, also I don't have a SIM installed.
Anything I can try to get it working?
./osmocon -p /dev/ttyS0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 00 81 .. got 4 bytes from modem, data looks like: 1b f6 02 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(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16788, hdr_len=4, dnload_le n=16795 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 . got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: 66 f 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
Regards,
Henk
Hi
Am 23.02.2011 um 23:52 schrieb Henk:
Anything I can try to get it working?
./osmocon -p /dev/ttyS0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 00 81 .. got 4 bytes from modem, data looks like: 1b f6 02 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(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16788, hdr_len=4, dnload_le n=16795 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
I had the same behavior with other phones when I tried it on a slow machine.. As the boot loader is VERY time critical I commented out the printf statements which print the 'got x bytes from modem, data looks like' messages. Then it worked even on my slow computer:-)
Regards Matthias
Hi,
On 24.02.2011 00:33, Thatsit wrote:
I had the same behavior with other phones when I tried it on a slow machine.. As the boot loader is VERY time critical I commented out the printf statements which print the 'got x bytes from modem, data looks like' messages. Then it worked even on my slow computer:-)
Yes, agreed. But instead of removing the printf's (which really shouldn't consume that much time), not re-loading the file should save more time.
Here's a small patch for trying that: http://www.steve-m.de/projects/osmocom/0001-osmocon-dont-reload.patch
With this patch, the file will only be loaded when starting osmocon, and not after receiving PROMPT1.
Regards, Steve
Hi Steve
Am 24.02.2011 um 01:05 schrieb Steve Markgraf:
Yes, agreed. But instead of removing the printf's (which really shouldn't consume that much time), not re-loading the file should save more time.
Here's a small patch for trying that: http://www.steve-m.de/projects/osmocom/0001-osmocon-dont-reload.patch
With this patch, the file will only be loaded when starting osmocon, and not after receiving PROMPT1.
Regards, Steve
When I experimented fixing this problem some time ago, I also thought that loading the file in the time critical phase isn't a good idea. But the I realized that the most critical phase is between receiving the PROMPT1 and sending the CMD, and thats before reading the file. So that didn't helped me a lot.
Regards Matthias
Hi, * Steve Markgraf steve@steve-m.de [2011-02-24 13:54]:
On 24.02.2011 00:33, Thatsit wrote:
I had the same behavior with other phones when I tried it on a slow machine.. As the boot loader is VERY time critical I commented out the printf statements which print the 'got x bytes from modem, data looks like' messages. Then it worked even on my slow computer:-)
Yes, agreed. But instead of removing the printf's (which really shouldn't consume that much time), not re-loading the file should save more time.
Here's a small patch for trying that: http://www.steve-m.de/projects/osmocom/0001-osmocon-dont-reload.patch
Tried your patch since I suffer from the same problem. Doesn't fix this for me though :/
read_file(../../target/firmware/board/compal_e88/layer1.e88flash.bin): file_size=49196, hdr_len=4, dnload_len=49203 got 2 bytes from modem, data looks like: 00 81 .. 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 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/49203) handle_write(): 4096 bytes (8192/49203) handle_write(): 4096 bytes (12288/49203) handle_write(): 4096 bytes (16384/49203) 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: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( 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 .
Any other idea? Kind regards Nico
Thanks you all for the responses. I have disabled the printf's and using -m C123 did the trick.
Did some tests hello_world, layer1, loader, And made a backup of the 2MB flash.
Strings in flashrom: 0x00800 BOOT.90.04 0x02000 MOTOROLA_E88 0x02020 1.0.17.E
Here are some of the logs:
OSMOCOM Layer 1 (revision osmocon_v0.0.0-780-gb7a4d8d-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: 168f2c10cb001251 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== 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
OSMOCOM Compal DSP Dumper (revision osmocon_v0.0.0-780-gb7a4d8d-modified) ====================================================================== DSP bootloader version 0x0100 DSP dump: Registers [00000-0005f] 00000 : 0386 0008 0008 0008 0000 0000 181f 2900 0000 0000 0000 0060 0000 0000 0000 28a1
I had seen same behaviour on C121. It turned out, that UART RxD path was somehow broken between jack and processor. Saved the day connection to the test points TP13 and TP14 instead of earphone jack, as described here: http://bb.osmocom.org/trac/wiki/MotorolaC123#Testpointsaccessiblefrombattery...
On 23/02/11 23:52, Henk wrote:
Hi,
I could not resist buying a C116 for 15 euro, so I compiled osmocombb and connected a 3.3V serial cable.
Of course the C116 was not in the supported list, but I was hoping it would work as it seems that it is very similar to the C115.
Here is my load attempt: (used -m c123 ) but there's no loading of the image. I am not using TX mode, also I don't have a SIM installed.
Anything I can try to get it working?
./osmocon -p /dev/ttyS0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 00 81 .. got 4 bytes from modem, data looks like: 1b f6 02 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(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16788, hdr_len=4, dnload_le n=16795 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 . got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: 66 f 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
Regards,
Henk
I face the same problem on my c118, thanks4u information help me quick fix it.
-- View this message in context: http://baseband-devel.722152.n3.nabble.com/Motorola-C116-experiment-tp256403... Sent from the baseband-devel mailing list archive at Nabble.com.
baseband-devel@lists.osmocom.org
-
André Černâk -
goodgod -
Henk -
Nico Golde -
Steve Markgraf -
Thatsit