02:31.04 | *** join/#handhelds phizz (phizz@we.are.not.el1t3.org) |
02:47.59 | *** join/#handhelds mzb (~mzb@ppp108-88.static.internode.on.net) |
04:27.55 | *** join/#handhelds yann (~dwitch@nan92-1-81-57-214-146.fbx.proxad.net) |
05:20.45 | *** join/#handhelds mzb (~mzb@ppp108-88.static.internode.on.net) |
07:08.21 | *** join/#handhelds MattEMatt (~matt@cpe-67-246-101-212.twcny.res.rr.com) |
07:09.07 | MattEMatt | joshua_ not sure if you got my email, but yeah I have an analog scope... nothing crazy (my other scope is on my workbench (doh!)) |
07:13.16 | MattEMatt | I also have attempted a dump (yesterday) and went through about the first 2MB of the memory... and its all blank |
07:21.18 | joshua_ | yeah I haven't had time to formalize a next step for you |
07:21.31 | joshua_ | I would scope the ALE and CLE pins on the flash and make sure they are toggling |
07:21.31 | MattEMatt | lol okay |
07:21.43 | joshua_ | if you can find a pinout and do that, then that might be interesting to try |
07:21.49 | joshua_ | otherwise I can find the pinout for you |
07:22.04 | MattEMatt | I'll see what I can dig up |
07:22.36 | MattEMatt | question though... how can I tell if the solder bridge that I made is correctly setup |
07:23.30 | joshua_ | if you mean the pins near the JTAG TAP? I think that you wouldn't get any results at all if it were wrong |
07:24.03 | MattEMatt | yeh, the solder bridge on the 2 pads (thats a pain to get to...) |
07:26.14 | MattEMatt | so its the samsung chips I want the ALE and CLE pins on correct? |
07:26.36 | joshua_ | the samsung flash chip |
07:26.50 | MattEMatt | thats what I was thinking. okay |
07:39.11 | MattEMatt | http://pdf1.alldatasheet.com/datasheet-pdf/view/84836/SAMSUNG/K4S561633C-RL.html |
07:39.41 | MattEMatt | looking at the pinouts I dont see those pins you mentioned |
07:45.15 | MattEMatt | and I think I would have to trace them along the board.... I can't seem to find where the BGA would line up for either on the other side of the board.... which I didn't really think I could but its always worth a shot |
07:55.07 | MattEMatt | ... Thinks.... |
07:55.36 | MattEMatt | okay, whenever I run into a complex issue like this, I always take it back to basics and re-examine the simple stuff... |
07:56.31 | MattEMatt | joshua_ i know there is a length of cable I should not exceed.... we'll start with that. |
07:57.09 | MattEMatt | what should be the maximum cable length |
07:57.53 | MattEMatt | (I currently kept it under 12" (30cm) |
09:18.29 | *** join/#handhelds dijenerate_ (~dijenerat@204.212.240.159) |
09:28.51 | *** join/#handhelds diJenerate (~dijenerat@204.212.240.159) |
09:44.09 | aquadran | MattEMatt: why you not try flash any data ? |
09:46.33 | aquadran | and blank is still data |
09:46.43 | aquadran | if you get random data, some that could be something wrong |
09:46.54 | aquadran | but you get all 0xff |
09:51.10 | aquadran | so flash is erased |
09:51.42 | MattEMatt | I have tried, it fails |
09:53.08 | aquadran | maybe software is broken |
09:53.26 | aquadran | if you get dumping works |
09:53.34 | MattEMatt | could be |
09:53.49 | aquadran | and i would be not suprised |
09:54.26 | MattEMatt | ::nods:: |
09:54.35 | aquadran | it still not dumping correclty here |
09:54.46 | aquadran | only partialy |
09:55.01 | MattEMatt | hmmm |
10:04.17 | MattEMatt | what kind of data are you getting? |
10:12.04 | MattEMatt | aquadran, this is the kind of stuff I get when I try to flash: |
10:12.26 | MattEMatt | ./hamcop -b |
10:12.26 | MattEMatt | Found HAMCOP on h2210 (ID: 6401324B) |
10:12.26 | MattEMatt | Now bricking... |
10:12.26 | MattEMatt | Error while bricking! |
10:12.26 | MattEMatt | ./hamcop -d pocketpc.rescue |
10:12.27 | MattEMatt | Found HAMCOP on h2210 (ID: 6401324B) |
10:12.29 | MattEMatt | Now debricking... |
10:12.31 | MattEMatt | Error while debricking! Offset: 00000000 |
10:16.19 | aquadran | put some debug info |
10:18.12 | aquadran | hmm, it seems it get error after get nand status |
10:19.42 | MattEMatt | okay, let me see what I can get |
10:20.21 | MattEMatt | how do i turn on debugging? |
10:27.09 | aquadran | not good thing is it's even not erase |
10:28.06 | aquadran | brick should erase, but you get error |
10:28.15 | MattEMatt | yeah when I verify the nand, this is what I get: |
10:28.17 | MattEMatt | root@RITSUKO-Linux:/home/matt/Desktop/hamcop# ./hamcop -n |
10:28.17 | MattEMatt | Found HAMCOP on h2210 (ID: 6401324B) |
10:28.17 | MattEMatt | ID: FFh/FFh (Manufacturer: Unknown, Device name: Unknown) |
10:28.17 | MattEMatt | Reading byte: 528 / 528 |
10:28.17 | MattEMatt | Data: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |
10:29.12 | MattEMatt | the rest of the page looks like that too... |
10:29.21 | aquadran | hmm |
10:29.45 | aquadran | after power off/on the same ? |
10:29.54 | MattEMatt | yup |
10:30.18 | aquadran | did you get toshiba id anywhere ? |
10:30.22 | MattEMatt | would it happen to do with the TRST pin at all? |
10:30.43 | aquadran | trst is jtag |
10:31.09 | aquadran | h2200 can have two flash, toshiba and samsung |
10:31.19 | aquadran | kind |
10:31.22 | MattEMatt | nope I have all samsung chips |
10:31.35 | aquadran | hamcop only support one |
10:31.41 | MattEMatt | and all i have gotten has been samsung and intel related |
10:32.47 | aquadran | let me verify |
10:33.28 | MattEMatt | okay |
10:33.38 | aquadran | ah, not current hamcop support both i think |
10:33.46 | aquadran | i mean software |
10:34.12 | aquadran | at least id info |
10:34.20 | MattEMatt | so the most current version does support samsung? |
10:34.53 | aquadran | that is most current |
10:35.51 | aquadran | both flash should be compatible |
10:36.01 | aquadran | but you get 0xff for id |
10:36.06 | aquadran | bad |
10:36.26 | aquadran | maybe nand is dead |
10:36.33 | MattEMatt | damn |
10:36.55 | MattEMatt | well here's the data sheet I found on the chips on the board |
10:36.56 | MattEMatt | n> that is most current |
10:36.56 | MattEMatt | <aquadran> both flash should be compatible |
10:36.56 | MattEMatt | <aquadran> but you get 0xff for id |
10:36.56 | MattEMatt | <aquadran> bad |
10:37.04 | MattEMatt | oops |
10:37.20 | MattEMatt | http://dl.dropbox.com/u/25239089/Samsung%20Flash%20%28IPAQ%29%20datasheet.pdf |
10:37.33 | aquadran | dump code doesn't have error checking i think |
10:38.15 | MattEMatt | joshua_ was saying that some of the stuff I was getting is normal... but I was looking for some pins on that datasheet to see if I could scope them... but I couldn't find them. |
10:41.39 | MattEMatt | maybe dead nand is why this whole thing happened in the first place... |
10:50.24 | aquadran | try without -DNO_TIMING |
10:51.10 | MattEMatt | so the command: |
10:51.24 | MattEMatt | ./hamcop -dno_timing |
10:52.43 | aquadran | in makefile |
10:53.03 | MattEMatt | ahh I see |
10:54.38 | aquadran | i have toshiba flash |
11:02.18 | MattEMatt | still getting the same ID |
11:08.07 | MattEMatt | http://dl.dropbox.com/u/25239089/build%20DNO_TIMING |
11:08.15 | MattEMatt | this is what I get for the build... |
11:08.57 | MattEMatt | everything is the same as before |
11:13.38 | MattEMatt | aquadran, would me having a 64-bit version of my OS running be affecting anything? |
11:14.14 | MattEMatt | I wouldn't think that it would, but I figured I would pose the question |
11:31.10 | aquadran | i also have running this on 64bit |
11:31.24 | aquadran | you mean still 0xff id ? |
11:31.24 | MattEMatt | ok |
11:31.44 | MattEMatt | I was referring to the OS. |
11:31.56 | MattEMatt | I am still getting the 0xFF as the ID though |
11:31.58 | aquadran | yes |
11:40.32 | MattEMatt | i'm off to bed... talk to you soon. |
12:58.34 | *** join/#handhelds diJenerate (~dijenerat@204.212.240.159) |
16:15.00 | *** join/#handhelds Takapa (vegard@svanberg.no) |
17:29.33 | *** join/#handhelds dijenerate (~dijenerat@204.212.240.159) |
18:59.32 | *** join/#handhelds MattEMatt (~matt@cpe-67-246-101-212.twcny.res.rr.com) |