From bastienbaranoff at gmail.com Fri Dec 14 14:41:10 2018 From: bastienbaranoff at gmail.com (Bastien Baranoff) Date: Fri, 14 Dec 2018 15:41:10 +0100 Subject: sms_request and clone sim function on mobile app on osmocombb Message-ID: hello video where you see sms_request function and Virtual machine with clone function from this link could tell which branche does provide these function? Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From craig at unreasonablefarm.org Wed Dec 19 13:30:30 2018 From: craig at unreasonablefarm.org (Craig Comstock) Date: Wed, 19 Dec 2018 07:30:30 -0600 Subject: MT6260 Datasheet available Message-ID: <20181219133030.GA48590@localhost.localdomain> Hi all, Somoene shared what looks like a quite useful datasheet for MT6260 at the kosagi/fernvale forum. I have downloaded it and looked a bit and it looks very helpful. I have linked to it in the wiki at: https://osmocom.org/projects/baseband/wiki/MT6260 Original post at kosagi forum: https://www.kosagi.com/forums/viewtopic.php?pid=3313#p3313 I hope to rejoin my effort on porting layer1 firmware to fernvale in about 1 month. Cheers, Craig From haiderali91 at protonmail.com Wed Dec 26 13:43:52 2018 From: haiderali91 at protonmail.com (haiderali91) Date: Wed, 26 Dec 2018 13:43:52 +0000 Subject: Loading HelloWorld firmware in Motorolla C118 Message-ID: <4ry_Pn3vs9s2F02bznpd9fc80T36kQEHS4Y8o7oAPXU7-QzWBC0x_mscf5mmTiAvFnsqICc8kKd58J7wSq-gFjmEBZY0IfTTXi-rRgW5uME=@protonmail.com> Hello, I am trying to load helloworld firmware into my phone (Motorolla C118) using sysmocom CP2102-25 cable by executing the following command sudo ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin But I am not getting any response on pressing power button briefly. The command keeps on executing without any message. What can be the issue and how to deal with/debug this issue. I have also attached a cu terminal by using following command. $ sudo cu -l /dev/ttyUSB0 -s 115200 The cu terminal displays this message on pressing power button. ??A at ftmtoolerror -------------- next part -------------- An HTML attachment was scrubbed... URL: From mychaela.falconia at gmail.com Wed Dec 26 16:16:44 2018 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Wed, 26 Dec 2018 08:16:44 -0800 Subject: Loading HelloWorld firmware in Motorolla C118 In-Reply-To: <4ry_Pn3vs9s2F02bznpd9fc80T36kQEHS4Y8o7oAPXU7-QzWBC0x_mscf5mmTiAvFnsqICc8kKd58J7wSq-gFjmEBZY0IfTTXi-rRgW5uME=@protonmail.com> References: <4ry_Pn3vs9s2F02bznpd9fc80T36kQEHS4Y8o7oAPXU7-QzWBC0x_mscf5mmTiAvFnsqICc8kKd58J7wSq-gFjmEBZY0IfTTXi-rRgW5uME=@protonmail.com> Message-ID: > I have also attached a cu terminal by using following command. > $ sudo cu -l /dev/ttyUSB0 -s 115200 > The cu terminal displays this message on pressing power button. > [garbage characters]ftmtoolerror The series of non-printable-ASCII characters followed by "ftmtoolerror" is exactly what Compal's bootloader emits on boot (the non-printable- ASCII characters constitute PROMPT1 for a possible external code download), so the fact that you are seeing these characters with your cu terminal proves that your phone is good (has an unlocked bootloader) and that your serial cable is good at least in the phone to PC direction. It is possible that your cable may be broken in the PC to phone direction, or that the headset jack connection inside the phone itself is broken in that direction - I have seen such broken headset jack connections on some busted-up phones. However, this other part of your report raises other concerns: > sudo ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin > > But I am not getting any response on pressing power button briefly. > The command keeps on executing without any message. Are you saying that absolutely *no messages whatsoever* appear in the console window where you run osmocon as you press thr power button on the phone? If so, then you must have some other problem, as osmocon should at least report that it got PROMPT1 from the phone, even if it is not successful in talking back to the phone. M~ From haiderali91 at protonmail.com Fri Dec 28 05:19:03 2018 From: haiderali91 at protonmail.com (haiderali91) Date: Fri, 28 Dec 2018 05:19:03 +0000 Subject: Loading HelloWorld firmware in Motorolla C118 In-Reply-To: References: <4ry_Pn3vs9s2F02bznpd9fc80T36kQEHS4Y8o7oAPXU7-QzWBC0x_mscf5mmTiAvFnsqICc8kKd58J7wSq-gFjmEBZY0IfTTXi-rRgW5uME=@protonmail.com> Message-ID: Thanks Mychaela for replying in detail. Yes, there is no response on executing the whole command: $ sudo ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin However, when i execute the following: $sudo ./osmocon -p /dev/ttyUSB0 It returns: Cannot open serial device /dev/tty/USB0 Trying to figure out the problem.. ??????? Original Message ??????? On Wednesday, December 26, 2018 9:16 PM, Mychaela Falconia wrote: > > I have also attached a cu terminal by using following command. > > $ sudo cu -l /dev/ttyUSB0 -s 115200 > > The cu terminal displays this message on pressing power button. > > [garbage characters]ftmtoolerror > > The series of non-printable-ASCII characters followed by "ftmtoolerror" > is exactly what Compal's bootloader emits on boot (the non-printable- > ASCII characters constitute PROMPT1 for a possible external code > download), so the fact that you are seeing these characters with your > cu terminal proves that your phone is good (has an unlocked bootloader) > and that your serial cable is good at least in the phone to PC > direction. It is possible that your cable may be broken in the PC to > phone direction, or that the headset jack connection inside the phone > itself is broken in that direction - I have seen such broken headset > jack connections on some busted-up phones. However, this other part > of your report raises other concerns: > > > sudo ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin > > But I am not getting any response on pressing power button briefly. > > The command keeps on executing without any message. > > Are you saying that absolutelyno messages whatsoever appear in the > console window where you run osmocon as you press thr power button on > the phone? If so, then you must have some other problem, as osmocon > should at least report that it got PROMPT1 from the phone, even if it > is not successful in talking back to the phone. > > M~ From haiderali91 at protonmail.com Fri Dec 28 06:57:00 2018 From: haiderali91 at protonmail.com (haiderali91) Date: Fri, 28 Dec 2018 06:57:00 +0000 Subject: Loading HelloWorld firmware in Motorolla C118 In-Reply-To: References: <4ry_Pn3vs9s2F02bznpd9fc80T36kQEHS4Y8o7oAPXU7-QzWBC0x_mscf5mmTiAvFnsqICc8kKd58J7wSq-gFjmEBZY0IfTTXi-rRgW5uME=@protonmail.com> Message-ID: I tried to execute the osmocon command (sudo ./osmocon -p /dev/tty/USB0) using strace. The output is as follows: ====== strace output starts======== execve("./osmocon", ["./osmocon", "-p", "/dev/tty/USB0"], [/* 74 vars */]) = 0 brk(NULL) = 0x1b7c000 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=164422, ...}) = 0 mmap(NULL, 164422, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb924694000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/usr/lib/x86_64-linux-gnu/libtalloc.so.2", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\35\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0644, st_size=80144, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb924693000 mmap(NULL, 2175248, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb924284000 mprotect(0x7fb924297000, 2093056, PROT_NONE) = 0 mmap(0x7fb924496000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12000) = 0x7fb924496000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libosmocore.so.11", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0 \230\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=710920, ...}) = 0 mmap(NULL, 2264912, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb92405b000 mprotect(0x7fb924080000, 2097152, PROT_NONE) = 0 mmap(0x7fb924280000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fb924280000 mmap(0x7fb924282000, 8016, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fb924282000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0 mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb923c91000 mprotect(0x7fb923e51000, 2097152, PROT_NONE) = 0 mmap(0x7fb924051000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c0000) = 0x7fb924051000 mmap(0x7fb924057000, 14752, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fb924057000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\r\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0644, st_size=14608, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb924692000 mmap(NULL, 2109680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb923a8d000 mprotect(0x7fb923a90000, 2093056, PROT_NONE) = 0 mmap(0x7fb923c8f000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7fb923c8f000 close(3) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb924691000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb924690000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb92468f000 arch_prctl(ARCH_SET_FS, 0x7fb924690700) = 0 mprotect(0x7fb924051000, 16384, PROT_READ) = 0 mprotect(0x7fb923c8f000, 4096, PROT_READ) = 0 mprotect(0x7fb924496000, 4096, PROT_READ) = 0 mprotect(0x7fb924280000, 4096, PROT_READ) = 0 mprotect(0x605000, 4096, PROT_READ) = 0 mprotect(0x7fb9246bd000, 4096, PROT_READ) = 0 munmap(0x7fb924694000, 164422) = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x7fb923cc64b0}, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGALRM, {SIG_IGN, [ALRM], SA_RESTORER|SA_RESTART, 0x7fb923cc64b0}, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGHUP, {0x7fb924070800, [HUP], SA_RESTORER|SA_RESTART, 0x7fb923cc64b0}, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGIO, {SIG_IGN, [IO], SA_RESTORER|SA_RESTART, 0x7fb923cc64b0}, {SIG_DFL, [], 0}, 8) = 0 open("/dev/tty/USB0", O_RDWR|O_NOCTTY|O_NONBLOCK|O_SYNC) = -1 ENOTDIR (Not a directory) write(2, "Cannot open serial device /dev/t"..., 40) = 40 exit_group(1) = ? +++ exited with 1 +++ ====== strace output ends======== The output of $ sudo stty -F /dev/ttyUSB0 is === stty output starts=== speed 115200 baud; line = 0; -brkint -imaxbel === stty output ends=== Whereas setserial command (sudo setserial -a /dev/ttyUSB0) gives this error: Cannot get serial info: Inappropriate ioctl for device What can be wrong with my PC to phone communication ??????? Original Message ??????? On Friday, December 28, 2018 10:19 AM, haiderali91 wrote: > Thanks Mychaela for replying in detail. > > Yes, there is no response on executing the whole command: > > $ sudo ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin > > However, when i execute the following: > $sudo ./osmocon -p /dev/ttyUSB0 > > It returns: Cannot open serial device /dev/tty/USB0 > > Trying to figure out the problem.. > > ??????? Original Message ??????? > On Wednesday, December 26, 2018 9:16 PM, Mychaela Falconia mychaela.falconia at gmail.com wrote: > > > > I have also attached a cu terminal by using following command. > > > $ sudo cu -l /dev/ttyUSB0 -s 115200 > > > The cu terminal displays this message on pressing power button. > > > [garbage characters]ftmtoolerror > > > > The series of non-printable-ASCII characters followed by "ftmtoolerror" > > is exactly what Compal's bootloader emits on boot (the non-printable- > > ASCII characters constitute PROMPT1 for a possible external code > > download), so the fact that you are seeing these characters with your > > cu terminal proves that your phone is good (has an unlocked bootloader) > > and that your serial cable is good at least in the phone to PC > > direction. It is possible that your cable may be broken in the PC to > > phone direction, or that the headset jack connection inside the phone > > itself is broken in that direction - I have seen such broken headset > > jack connections on some busted-up phones. However, this other part > > of your report raises other concerns: > > > > > sudo ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin > > > But I am not getting any response on pressing power button briefly. > > > The command keeps on executing without any message. > > > > Are you saying that absolutelyno messages whatsoever appear in the > > console window where you run osmocon as you press thr power button on > > the phone? If so, then you must have some other problem, as osmocon > > should at least report that it got PROMPT1 from the phone, even if it > > is not successful in talking back to the phone. > > M~ From haiderali91 at protonmail.com Fri Dec 28 09:28:14 2018 From: haiderali91 at protonmail.com (haiderali91) Date: Fri, 28 Dec 2018 09:28:14 +0000 Subject: Loading HelloWorld firmware in Motorolla C118 In-Reply-To: References: <4ry_Pn3vs9s2F02bznpd9fc80T36kQEHS4Y8o7oAPXU7-QzWBC0x_mscf5mmTiAvFnsqICc8kKd58J7wSq-gFjmEBZY0IfTTXi-rRgW5uME=@protonmail.com> Message-ID: The previous issue is resolved. I was running cu on the /dev/tty/USB0 and at the same time i was executing osmocon command. Therefore, it was unable to access the device. After i stopped cu, and executed the command again; when i pressed power button i got this output: got 2 bytes from modem, data looks like: 04 81 .. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 65 e 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: 40 @ got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 41 A 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: 6f o got 1 bytes from modem, data looks like: 72 r However, it keeps on repeating the above output. No helloworld or any other success showing output is coming. Sent with ProtonMail Secure Email. ??????? Original Message ??????? On Friday, December 28, 2018 11:57 AM, haiderali91 wrote: > I tried to execute the osmocon command (sudo ./osmocon -p /dev/tty/USB0) using strace. The output is as follows: > > ====== strace output starts======== > execve("./osmocon", ["./osmocon", "-p", "/dev/tty/USB0"], [/* 74 vars */]) = 0 > brk(NULL) = 0x1b7c000 > access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) > access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) > open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 > fstat(3, {st_mode=S_IFREG|0644, st_size=164422, ...}) = 0 > mmap(NULL, 164422, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb924694000 > close(3) = 0 > access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) > open("/usr/lib/x86_64-linux-gnu/libtalloc.so.2", O_RDONLY|O_CLOEXEC) = 3 > read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\35\0\0\0\0\0\0"..., 832) = 832 > fstat(3, {st_mode=S_IFREG|0644, st_size=80144, ...}) = 0 > mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb924693000 > mmap(NULL, 2175248, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb924284000 > mprotect(0x7fb924297000, 2093056, PROT_NONE) = 0 > mmap(0x7fb924496000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12000) = 0x7fb924496000 > close(3) = 0 > access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) > open("/usr/local/lib/libosmocore.so.11", O_RDONLY|O_CLOEXEC) = 3 > read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0 \230\0\0\0\0\0\0"..., 832) = 832 > fstat(3, {st_mode=S_IFREG|0755, st_size=710920, ...}) = 0 > mmap(NULL, 2264912, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb92405b000 > mprotect(0x7fb924080000, 2097152, PROT_NONE) = 0 > mmap(0x7fb924280000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fb924280000 > mmap(0x7fb924282000, 8016, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fb924282000 > close(3) = 0 > access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) > open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 > read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 832) = 832 > fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0 > mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb923c91000 > mprotect(0x7fb923e51000, 2097152, PROT_NONE) = 0 > mmap(0x7fb924051000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c0000) = 0x7fb924051000 > mmap(0x7fb924057000, 14752, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fb924057000 > close(3) = 0 > access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) > open("/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3 > read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\r\0\0\0\0\0\0"..., 832) = 832 > fstat(3, {st_mode=S_IFREG|0644, st_size=14608, ...}) = 0 > mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb924692000 > mmap(NULL, 2109680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb923a8d000 > mprotect(0x7fb923a90000, 2093056, PROT_NONE) = 0 > mmap(0x7fb923c8f000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7fb923c8f000 > close(3) = 0 > mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb924691000 > mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb924690000 > mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb92468f000 > arch_prctl(ARCH_SET_FS, 0x7fb924690700) = 0 > mprotect(0x7fb924051000, 16384, PROT_READ) = 0 > mprotect(0x7fb923c8f000, 4096, PROT_READ) = 0 > mprotect(0x7fb924496000, 4096, PROT_READ) = 0 > mprotect(0x7fb924280000, 4096, PROT_READ) = 0 > mprotect(0x605000, 4096, PROT_READ) = 0 > mprotect(0x7fb9246bd000, 4096, PROT_READ) = 0 > munmap(0x7fb924694000, 164422) = 0 > rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x7fb923cc64b0}, {SIG_DFL, [], 0}, 8) = 0 > rt_sigaction(SIGALRM, {SIG_IGN, [ALRM], SA_RESTORER|SA_RESTART, 0x7fb923cc64b0}, {SIG_DFL, [], 0}, 8) = 0 > rt_sigaction(SIGHUP, {0x7fb924070800, [HUP], SA_RESTORER|SA_RESTART, 0x7fb923cc64b0}, {SIG_DFL, [], 0}, 8) = 0 > rt_sigaction(SIGIO, {SIG_IGN, [IO], SA_RESTORER|SA_RESTART, 0x7fb923cc64b0}, {SIG_DFL, [], 0}, 8) = 0 > open("/dev/tty/USB0", O_RDWR|O_NOCTTY|O_NONBLOCK|O_SYNC) = -1 ENOTDIR (Not a directory) > write(2, "Cannot open serial device /dev/t"..., 40) = 40 > exit_group(1) = ? > +++ exited with 1 +++ > > ====== strace output ends======== > > The output of $ sudo stty -F /dev/ttyUSB0 is > > === stty output starts=== > speed 115200 baud; line = 0; > -brkint -imaxbel > === stty output ends=== > > Whereas setserial command (sudo setserial -a /dev/ttyUSB0) gives this error: > > Cannot get serial info: Inappropriate ioctl for device > > What can be wrong with my PC to phone communication > > ??????? Original Message ??????? > On Friday, December 28, 2018 10:19 AM, haiderali91 haiderali91 at protonmail.com wrote: > > > Thanks Mychaela for replying in detail. > > Yes, there is no response on executing the whole command: > > $ sudo ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin > > However, when i execute the following: > > $sudo ./osmocon -p /dev/ttyUSB0 > > It returns: Cannot open serial device /dev/tty/USB0 > > Trying to figure out the problem.. > > ??????? Original Message ??????? > > On Wednesday, December 26, 2018 9:16 PM, Mychaela Falconia mychaela.falconia at gmail.com wrote: > > > > > > I have also attached a cu terminal by using following command. > > > > $ sudo cu -l /dev/ttyUSB0 -s 115200 > > > > The cu terminal displays this message on pressing power button. > > > > [garbage characters]ftmtoolerror > > > > > > The series of non-printable-ASCII characters followed by "ftmtoolerror" > > > is exactly what Compal's bootloader emits on boot (the non-printable- > > > ASCII characters constitute PROMPT1 for a possible external code > > > download), so the fact that you are seeing these characters with your > > > cu terminal proves that your phone is good (has an unlocked bootloader) > > > and that your serial cable is good at least in the phone to PC > > > direction. It is possible that your cable may be broken in the PC to > > > phone direction, or that the headset jack connection inside the phone > > > itself is broken in that direction - I have seen such broken headset > > > jack connections on some busted-up phones. However, this other part > > > of your report raises other concerns: > > > > > > > sudo ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin > > > > But I am not getting any response on pressing power button briefly. > > > > The command keeps on executing without any message. > > > > > > Are you saying that absolutelyno messages whatsoever appear in the > > > console window where you run osmocon as you press thr power button on > > > the phone? If so, then you must have some other problem, as osmocon > > > should at least report that it got PROMPT1 from the phone, even if it > > > is not successful in talking back to the phone. > > > M~ From babarbuttgrt at yahoo.com Sun Dec 30 06:31:07 2018 From: babarbuttgrt at yahoo.com (Babar Ali) Date: Sun, 30 Dec 2018 06:31:07 +0000 (UTC) Subject: Motorola C118 online buy In-Reply-To: <5bb87f1b.1c69fb81.61c5a.ea0a@mx.google.com> References: <20987889.102273.1538803590102.ref@mail.yahoo.com> <20987889.102273.1538803590102@mail.yahoo.com> <5bb87f1b.1c69fb81.61c5a.ea0a@mx.google.com> Message-ID: <590455088.4034557.1546151467146@mail.yahoo.com> Hi list ? I want to buy Motorola C118, from china, please share store link. Regards Babar Ali ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mychaela.falconia at gmail.com Sun Dec 30 06:45:18 2018 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Sat, 29 Dec 2018 22:45:18 -0800 Subject: Motorola C118 online buy In-Reply-To: <590455088.4034557.1546151467146@mail.yahoo.com> References: <20987889.102273.1538803590102.ref@mail.yahoo.com> <20987889.102273.1538803590102@mail.yahoo.com> <5bb87f1b.1c69fb81.61c5a.ea0a@mx.google.com> <590455088.4034557.1546151467146@mail.yahoo.com> Message-ID: On 12/29/18, Babar Ali wrote: > I want to buy Motorola C118, from china, please share store link. Why does it have to be from China, why is ebay not good enough for you? There are a few C118 phones available on ebay right now. And does it have to be C118, or would C139 work for you too? C139 is much more plentifully available, also on ebay. HTH, M~ From babarbuttgrt at yahoo.com Sun Dec 30 07:04:24 2018 From: babarbuttgrt at yahoo.com (Babar Ali) Date: Sun, 30 Dec 2018 07:04:24 +0000 (UTC) Subject: Motorola C118 online buy In-Reply-To: References: <20987889.102273.1538803590102.ref@mail.yahoo.com> <20987889.102273.1538803590102@mail.yahoo.com> <5bb87f1b.1c69fb81.61c5a.ea0a@mx.google.com> <590455088.4034557.1546151467146@mail.yahoo.com> Message-ID: <1231772458.4037723.1546153464363@mail.yahoo.com> I have searched on ebay, most of sellers do not offer international shipping i.e. to Pakistan,? Regards Babar Ali On Sunday, 30 December 2018, 11:45:20 AM GMT+5, Mychaela Falconia wrote: On 12/29/18, Babar Ali wrote: > I want to buy Motorola C118, from china, please share store link. Why does it have to be from China, why is ebay not good enough for you? There are a few C118 phones available on ebay right now. And does it have to be C118, or would C139 work for you too? C139 is much more plentifully available, also on ebay. HTH, M~ -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at freyther.de Sun Dec 30 15:26:53 2018 From: holger at freyther.de (Holger Freyther) Date: Sun, 30 Dec 2018 15:26:53 +0000 Subject: Scaling up virtual bts tests for the BTS test - how I hold it wrong? Message-ID: <079E0BD2-5621-4092-BEAD-EFB6A8E9D812@freyther.de> After a lot of work[1] the gsm tester can finally: * Start a virtual bts * Mobile/virtphy processes * Complete LUs for 10 MS. The next step (besides having a proper test verdict) is scaling this beyond what a simple physical set-up can provide. Let's go to 100+ BTS and 10k subscribers but somehow I am still holding it wrongly and would like to have feedback to see how to evolve the gsm tester. What do I need to change to scale this up and how to externally parameterize it? * suite.conf: Add one line per virtual bts to reserve (I would prefer to specify type+num) * resources.prod.conf: Add more Virtual BTS. I started to pick IPs from 127.0.1.0/24 as it avoids having to configure special IPs. * register_default_mass.py: I need to somehow know how many BTS (and NITBs) were reserved. Or in the long run the topology of how to connect M BTS to N BSCs? Currently I can run until I get an exception but that is not desirable. What's missing: * High-level API of the SuiteRun to get me the toplogy of the network. It seems undesirable in the specific suite to discover how many BTSs were reserved in suite.conf or what the topology is. * ARFCN usage. Besides the redundancy all my BTS currently have the same ARFCN. There should be an easy way to configure an band+arfcn pool. * IMSI/MSISDN pooling. I would like to specify pools of IMSI/MSISDN pairs (and size) and then draw from it. I needs these to program into the mobile, NITB/HLR/AuC and for client to client SMS transfers. * Configure these capacities from the outside. Changing from 1 to 256 BTS should be a single line (or even a parameter change). Any idea or comment on how to achieve this? cheers holger [1] Hindsight is 20/20 and the difficulty was not adding scripting to mobile but getting the GSM tester to spawn the network and we are unfortunately not done yet. From pespin at sysmocom.de Sun Dec 30 23:21:54 2018 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Mon, 31 Dec 2018 00:21:54 +0100 Subject: Scaling up virtual bts tests for the BTS test - how I hold it wrong? In-Reply-To: <079E0BD2-5621-4092-BEAD-EFB6A8E9D812@freyther.de> References: <079E0BD2-5621-4092-BEAD-EFB6A8E9D812@freyther.de> Message-ID: <72c0e399-c4dd-a08f-b6f7-bd25fc6dd4af@sysmocom.de> Hi Holger, On 12/30/18 4:26 PM, Holger Freyther wrote: > What do I need to change to scale this up and how to externally parameterize it? > > * suite.conf: > Add one line per virtual bts to reserve (I would prefer to specify type+num) You can already do that, by using the "times" attribute for each object in suite.conf. See for instance what's done in osmo-gsm-tester/suites/gprs/suite.conf: modem: - times: 2 features: - gprs - voice One can similarly do the same to request allocation of 100 sysmoBTS: bts: - type: osmo-bts-sysmo times: 100 > > * resources.prod.conf: > Add more Virtual BTS. I started to pick IPs from 127.0.1.0/24 as it avoids having to configure special IPs. > I'd like to be able to specifcy pools of objects in resources.conf so we don't need to add 1 line per object there. In the case of IP addresses, specifying a subnet range and let osmo-gsm-tester to expand that into a set of objects at runtime. > > * register_default_mass.py: > I need to somehow know how many BTS (and NITBs) were reserved. Or in the long run the topology of how to connect M BTS to N BSCs? Currently I can run until I get an exception but that is not desirable. > Yeah for now the way to do it is to ask for one until you get the specific exception thrown when there's no more objects of that type or matching the specifications. Fine for me to add more APIs to fetch this kind of information more easily. > > What's missing: > > * High-level API of the SuiteRun to get me the toplogy of the network. It seems undesirable in the specific suite to discover how many BTSs were reserved in suite.conf or what the topology is. See my last text above. > > * ARFCN usage. Besides the redundancy all my BTS currently have the same ARFCN. There should be an easy way to configure an band+arfcn pool. There's a task for that, see https://osmocom.org/issues/2230. Unfortunately the algorithm to allocate ARFCN from available ones is a bit complex (lots of restrictions) and wasn't really required so far, so it's not yet implemented. As a workaround, you may want to add a modifier for ARFCN, similar to what is already done for other variables in osmo-gsm-tester/example/scenrios/mod-bts0-*.conf So you could specify manually a different ARFCN for each bts (number of elements in object modifiers must match number of elements in the resources in suite.conf). Let's say you want 3 BTS with 3 differnet arfcn, 2 of them in 1800 band and 1 in 900 band: [suite.conf] resources: ip_address: - times: 4 #or as much as needed bts: - band: GSM-1800 times: 2 - band: GSM-900 modifiers: bts: - arfcn: 868 - arfcn: 870 - arfcn: 124 # or whatever is valid for GSM900 * Band attribute should actually be reworked to be a list of supported bands for that BTS, then each BTS in resources.conf have a list with all bands supported by that BTS. * I don't think arfcn modifier is there yet, but not sure now. Grep for "modifier" in suite.py and resource.py to see how it is implemented. > > * IMSI/MSISDN pooling. I would like to specify pools of IMSI/MSISDN pairs (and size) and then draw from it. I needs these to program into the mobile, NITB/HLR/AuC and for client to client SMS transfers. See my comments regarding IP addr pools. Fine for me, but I'm not sure if its needed in this case, since there's already methods to allocate sequentially incrementing MSISDN and IMSI. > > * Configure these capacities from the outside. Changing from 1 to 256 BTS should be a single line (or even a parameter change). > Unfortunately these kind of capacities are so far fixed by the suite.conf. If you want to do tests with different numbers, you can manually change the "times" attribute in there, or put a big number and only use a subset of them when running the test in the suite. Regards, Pau -- - Pau Espin Pedrol http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From laforge at gnumonks.org Mon Dec 31 16:43:00 2018 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 31 Dec 2018 17:43:00 +0100 Subject: OsmoDevCon 2019 registration Message-ID: <20181231164300.GN20066@nataraja> Dear fellow Osmocom developers, I'm a bit surprised to notice that not more people have signed up for OsmoDevCon 2019. I guess it was mostly an oversight when the date was originally announced, and not a lack of interest? ;) All details about the event are available at the related wiki page at: https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2019 Please enter your name at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2019#Requested in case you would like to attend. Registering early allows proper planning. Thanks! Looking forward to meeting old and new Osmocom developers in April 2019. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)