Flashing Problem: C117

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

Craig Comstock craig_comstock at yahoo.com
Sat Feb 18 13:19:30 UTC 2017


You know that generally flashing the phone isn't needed. You can load all of the different osmocom images just with the osmocon loader into ram and "do things". The flashing can brick your device.

Just my $0.02,
Craig



--------------------------------------------
On Sat, 2/18/17, Dennis Schneck <dennisschneck at web.de> wrote:

 Subject: Flashing Problem: C117
 To: baseband-devel at lists.osmocom.org
 Date: Saturday, February 18, 2017, 2:44 AM
 
  
 
 Hello,
 
 i try to Flash a Motorola C117. But did not work ...
 what did i wrong ?
 
  
 
 
 $ sudo host/osmocon/osmocon -p /dev/ttyUSB0 -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 00  ..
 
 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=27072, hdr_len=4, dnload_len=27079
 
 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/27079)
 
 handle_write(): 4096 bytes (8192/27079)
 
 handle_write(): 4096 bytes (12288/27079)
 
 handle_write(): 4096 bytes (16384/27079)
 
 handle_write(): 4096 bytes (20480/27079)
 
 handle_write(): 4096 bytes (24576/27079)
 
 handle_write(): 2503 bytes (27079/27079)
 
 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!
 
 Received DOWNLOAD ACK from phone, your code is running now!
 
 battery_compal_e88_init: starting up
 
 
 
 OsmocomBB Loader (revision
 osmocon_v0.0.0-1773-g0cdf4b0-modified)
 
 ======================================================================
 
 Running on compal_e88 in environment compalram
 
  
 
  
 
 
 $ sudo host/osmocon/osmoload memdump 0x000000
 0x2000 compal_loader.bin
 
 [sudo] password for builder:
 
 Dumping 8192 bytes of memory at 0x0 to file
 compal_loader.bin
 
 ...................................done.
 
 builder at buildervm:~/build/osmocom-bb/src$ sudo
 host/osmocon/osmoload funlock 0x010000 0x10000
 
 Unlocking 65536 bytes of flash at 0x10000
 
   requesting flash info to determine block layout
 
     chip 0 at 0x00000000 of 2097152 bytes in
 2 regions
 
       region 0 with 31 blocks of
 65536 bytes each
 
         block 0 with
 65536 bytes at 0x00000000 on chip 0
 
         block 1 with
 65536 bytes at 0x00010000 on chip 0
 
         block 2 with
 65536 bytes at 0x00020000 on chip 0
 
         block 3 with
 65536 bytes at 0x00030000 on chip 0
 
         block 4 with
 65536 bytes at 0x00040000 on chip 0
 
         block 5 with
 65536 bytes at 0x00050000 on chip 0
 
         block 6 with
 65536 bytes at 0x00060000 on chip 0
 
         block 7 with
 65536 bytes at 0x00070000 on chip 0
 
         block 8 with
 65536 bytes at 0x00080000 on chip 0
 
         block 9 with
 65536 bytes at 0x00090000 on chip 0
 
         block 10 with
 65536 bytes at 0x000a0000 on chip 0
 
         block 11 with
 65536 bytes at 0x000b0000 on chip 0
 
         block 12 with
 65536 bytes at 0x000c0000 on chip 0
 
         block 13 with
 65536 bytes at 0x000d0000 on chip 0
 
         block 14 with
 65536 bytes at 0x000e0000 on chip 0
 
         block 15 with
 65536 bytes at 0x000f0000 on chip 0
 
         block 16 with
 65536 bytes at 0x00100000 on chip 0
 
         block 17 with
 65536 bytes at 0x00110000 on chip 0
 
         block 18 with
 65536 bytes at 0x00120000 on chip 0
 
         block 19 with
 65536 bytes at 0x00130000 on chip 0
 
         block 20 with
 65536 bytes at 0x00140000 on chip 0
 
         block 21 with
 65536 bytes at 0x00150000 on chip 0
 
         block 22 with
 65536 bytes at 0x00160000 on chip 0
 
         block 23 with
 65536 bytes at 0x00170000 on chip 0
 
         block 24 with
 65536 bytes at 0x00180000 on chip 0
 
         block 25 with
 65536 bytes at 0x00190000 on chip 0
 
         block 26 with
 65536 bytes at 0x001a0000 on chip 0
 
         block 27 with
 65536 bytes at 0x001b0000 on chip 0
 
         block 28 with
 65536 bytes at 0x001c0000 on chip 0
 
         block 29 with
 65536 bytes at 0x001d0000 on chip 0
 
         block 30 with
 65536 bytes at 0x001e0000 on chip 0
 
       region 1 with 8 blocks of
 8192 bytes each
 
         block 31 with
 8192 bytes at 0x001f0000 on chip 0
 
         block 32 with
 8192 bytes at 0x001f2000 on chip 0
 
         block 33 with
 8192 bytes at 0x001f4000 on chip 0
 
         block 34 with
 8192 bytes at 0x001f6000 on chip 0
 
         block 35 with
 8192 bytes at 0x001f8000 on chip 0
 
         block 36 with
 8192 bytes at 0x001fa000 on chip 0
 
         block 37 with
 8192 bytes at 0x001fc000 on chip 0
 
         block 38 with
 8192 bytes at 0x001fe000 on chip 0
 
   confirmed operation on chip 0 address 0x00010000,
 status FAILED
 
   operation done
 
  
 
 
 Thanks
 
 



More information about the baseband-devel mailing list