| 00:35.34 | *** part/#openezx angelox_123 (~angelo@201-92-240-70.dsl.telesp.net.br) |
| 05:36.48 | *** join/#openezx toi (~peter@193.191.148.194) |
| 07:56.06 | *** join/#openezx ao2 (~ao2@2001:1418:117::1) |
| 08:02.59 | *** join/#openezx florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 09:03.44 | *** join/#openezx bluelightning (~paul@83.217.123.106) |
| 09:03.44 | *** join/#openezx bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 09:04.35 | *** join/#openezx mickey|office (~Mickey@business-092-079-168-007.static.arcor-ip.net) |
| 11:03.20 | *** join/#openezx mickey|office (~Mickey@business-092-079-168-007.static.arcor-ip.net) |
| 11:45.13 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |
| 14:01.14 | *** join/#openezx lclaudio (~lclaudio@187.59.13.26) |
| 14:18.24 | *** join/#openezx kundan (~kundan@27.107.128.111) |
| 14:18.32 | kundan | ao2: Hi |
| 14:18.54 | ao2 | kundan, hi |
| 14:20.05 | kundan | well I was thinking that what will happen if I supply 1 as a address to moto-boot-usb while flashing |
| 14:20.14 | kundan | this will bypass that check or not |
| 14:20.27 | kundan | that prevents bootloader flashing ... |
| 14:21.10 | kundan | ao2: what do you say about this ? |
| 14:24.54 | ao2 | kundan, I think you are right, but is this a problem? I guess the user who load gen-blob already should be knowing what he is doing. And really, we have like what? 3 users? so I don't feel like spending too much time on moto-boot-usb when the kernel needs so many things |
| 14:25.34 | kundan | ao2: yes I just want to make sure that what I am thinking is not wrong |
| 14:26.03 | ao2 | kundan, if you come out with a patch to fix this I'd be happy to consider it |
| 14:26.37 | kundan | ao2: since you know I don't have a phone to test |
| 14:26.58 | kundan | and this tool can't be test without a connected phone |
| 14:27.35 | kundan | ao2: I think it will hardly take few min to fix this |
| 14:29.31 | kundan | if you can replace this comparison |
| 14:29.33 | kundan | if (addr == 0) { |
| 14:29.35 | kundan | with something like |
| 14:29.37 | kundan | if (addr > 60000) { |
| 14:29.39 | kundan | if it is comparing the hex values |
| 14:30.40 | kundan | we must check address until 393216 bytes |
| 14:31.04 | kundan | as I think after address 0x00060000 its safe to flash |
| 14:33.20 | kundan | ao2: is there any debug mode in moto-boot-usb ? |
| 14:33.33 | kundan | so that it can just give output without connecting the phone ? |
| 14:48.13 | kundan | ao2: |
| 14:48.21 | kundan | I created this sample code |
| 14:48.25 | kundan | #include <stdio.h> |
| 14:48.32 | kundan | #define ENDOFDANGER 393215 |
| 14:48.32 | kundan | int main(int argc, char *argv[]) |
| 14:48.32 | kundan | { |
| 14:48.32 | kundan | int x; |
| 14:48.34 | kundan | sscanf(argv[1], "%x", &x); |
| 14:48.36 | kundan | printf("%u\n", x); |
| 14:48.38 | kundan | if (x > ENDOFDANGER) |
| 14:48.40 | kundan | printf("%s is safe to use\n",argv[1]); |
| 14:48.43 | kundan | else |
| 14:48.45 | kundan | printf("%s is dangerous to use\n",argv[1]); |
| 14:48.47 | kundan | return 0; |
| 14:48.48 | kundan | } |
| 14:48.50 | kundan | this checks for address for safe and dangerous |
| 14:49.03 | kundan | if you can add same type to moto-boot-usb it will be good |
| 14:50.08 | kundan | let me know if you are going to add this check to moto-boot-usb or you are dropping this idea |
| 14:58.13 | ao2 | kundan, added to the todo list, not high priority tho |
| 14:58.39 | kundan | ok, Thanks :) |
| 14:58.59 | bluelightning | kundan: did you recover your phone yet? |
| 14:59.19 | kundan | no I have send my phone to a friend who repairs phones |
| 14:59.33 | bluelightning | ah ok, was just curious |
| 14:59.39 | kundan | he said there are no box or device available to recover it |
| 14:59.52 | kundan | he says that PCB needs to be replaced |
| 14:59.59 | bluelightning | hmm, that's not good :( |
| 15:00.09 | bluelightning | you're sure jtag is unavailable? |
| 15:00.34 | kundan | well I don't have JTAG and others are not enough good to work with JTAG |
| 15:00.54 | bluelightning | I would imagine that jtag repair is not a very common thing to need to do outside development, thus your friend might not be familiar with such techniques |
| 15:01.07 | kundan | I think they are going with simple repair process in which phone boots and they repair |
| 15:01.39 | kundan | ao2: yes now I too think so he is not familiar with JTAG regarding development |
| 15:01.55 | bluelightning | most people end up making their own JTAG cables AFAIK |
| 15:02.09 | bluelightning | does not claim to know much about such things though |
| 15:02.37 | kundan | I am not good in electronics to build my own cable |
| 15:02.55 | kundan | may be I can find someone around to build one for me |
| 15:03.11 | bluelightning | perhaps your phone-repairing friend could help there? |
| 15:03.53 | kundan | I have send my phone to his place and he leaves about 2000k away from my place |
| 15:04.13 | kundan | so I don't think he can help me |
| 15:04.50 | kundan | ao2: but the main problem is we don't know JTAG debug ports for E6 |
| 15:05.23 | kundan | if I manage to get a cable then also its hard to flash that PCB without debug port info |
| 15:06.05 | kundan | I wish if anyone on OpenEZX has E6 and can find those debug ports that will help me alot |
| 15:07.23 | kundan | ao2: have you tried JTAG flashing before ? |
| 15:08.34 | ao2 | <PROTECTED> |
| 15:09.04 | kundan | ao2: I would like to know about them , Please share with me :) |
| 15:10.01 | ao2 | <PROTECTED> |
| 15:11.37 | kundan | but they can be helpful to find same thing on E6 schematics |
| 15:21.17 | kundan | ao2: check this http://184.107.57.43/Screenshot.png |
| 15:21.35 | kundan | actually I fount this JTAG info in A1200 schematics |
| 15:21.54 | kundan | but there are not such JTAG info in E6 schematics |
| 15:32.14 | kundan | actually the .pdf is even better than that screenshot I gave the link to |
| 15:40.57 | ao2 | <PROTECTED> |
| 15:42.11 | ao2 | <PROTECTED> |
| 15:54.20 | *** join/#openezx angelox_123 (~angelo@201-13-186-64.dial-up.telesp.net.br) |
| 15:59.59 | kundan | ao2: do you mean to say for |
| 16:00.00 | kundan | U2000 Bulverde AP Processor | U2001 AP Memory ? |
| 16:09.11 | *** join/#openezx toi (~peter@91.183.49.188) |
| 16:22.32 | *** join/#openezx mickey|patio (~mickey@e180128048.adsl.alicedsl.de) |
| 16:37.17 | *** join/#openezx angelox_123 (~angelo@201-13-186-64.dial-up.telesp.net.br) |
| 17:07.56 | *** join/#openezx stefan_schmidt (~stefan@p4FC7672E.dip.t-dialin.net) |
| 17:38.53 | angelox_123 | ao2,you was correct again :) the information about in what device OpenEZX are runinng is at /proc/cpuinfo |
| 19:01.42 | *** join/#openezx stefan_schmidt (~stefan@p4FC7672E.dip.t-dialin.net) |
| 19:56.55 | *** join/#openezx florian (~fuchs@sign-4d091ecc.pool.mediaWays.net) |
| 19:56.55 | *** join/#openezx florian (~fuchs@Maemo/community/contributor/florian) |
| 20:36.43 | *** join/#openezx pixel____ (~root@p5B0E1A81.dip0.t-ipconnect.de) |
| 21:27.36 | *** join/#openezx angelox_123 (~angelo@201-13-186-64.dial-up.telesp.net.br) |
| 23:17.30 | *** join/#openezx angelox_123 (~angelo@201-13-186-64.dial-up.telesp.net.br) |
