IRC log for #handhelds on 20110616

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.07MattEMattjoshua_ 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.16MattEMattI also have attempted a dump (yesterday) and went through about the first 2MB of the memory... and its all blank
07:21.18joshua_yeah I haven't had time to formalize a next step for you
07:21.31joshua_I would scope the ALE and CLE pins on the flash and make sure they are toggling
07:21.31MattEMattlol okay
07:21.43joshua_if you can find a pinout and do that, then that might be interesting to try
07:21.49joshua_otherwise I can find the pinout for you
07:22.04MattEMattI'll see what I can dig up
07:22.36MattEMattquestion though... how can I tell if the solder bridge that I made is correctly setup
07:23.30joshua_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.03MattEMattyeh, the solder bridge on the 2 pads (thats a pain to get to...)
07:26.14MattEMattso its the samsung chips I want the ALE and CLE pins on correct?
07:26.36joshua_the samsung flash chip
07:26.50MattEMattthats what I was thinking. okay
07:39.11MattEMatthttp://pdf1.alldatasheet.com/datasheet-pdf/view/84836/SAMSUNG/K4S561633C-RL.html
07:39.41MattEMattlooking at the pinouts I dont see those pins you mentioned
07:45.15MattEMattand 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.07MattEMatt... Thinks....
07:55.36MattEMattokay, whenever I run into a complex issue like this, I always take it back to basics and re-examine the simple stuff...
07:56.31MattEMattjoshua_ i know there is a length of cable I should not exceed.... we'll start with that.
07:57.09MattEMattwhat should be the maximum cable length
07:57.53MattEMatt(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.09aquadranMattEMatt: why you not try flash any data ?
09:46.33aquadranand blank is still data
09:46.43aquadranif you get random data, some that could be something wrong
09:46.54aquadranbut you get all 0xff
09:51.10aquadranso flash is erased
09:51.42MattEMattI have tried, it fails
09:53.08aquadranmaybe software is broken
09:53.26aquadranif you get dumping works
09:53.34MattEMattcould be
09:53.49aquadranand i would be not suprised
09:54.26MattEMatt::nods::
09:54.35aquadranit still not dumping correclty here
09:54.46aquadranonly partialy
09:55.01MattEMatthmmm
10:04.17MattEMattwhat kind of data are you getting?
10:12.04MattEMattaquadran, this is the kind of stuff I get when I try to flash:
10:12.26MattEMatt./hamcop -b
10:12.26MattEMattFound HAMCOP on h2210 (ID: 6401324B)
10:12.26MattEMattNow bricking...
10:12.26MattEMattError while bricking!
10:12.26MattEMatt./hamcop -d pocketpc.rescue
10:12.27MattEMattFound HAMCOP on h2210 (ID: 6401324B)
10:12.29MattEMattNow debricking...
10:12.31MattEMattError while debricking! Offset: 00000000
10:16.19aquadranput some debug info
10:18.12aquadranhmm, it seems it get error after get nand status
10:19.42MattEMattokay, let me see what I can get
10:20.21MattEMatthow do i turn on debugging?
10:27.09aquadrannot good thing is it's even not erase
10:28.06aquadranbrick should erase, but you get error
10:28.15MattEMattyeah when I verify the nand, this is what I get:
10:28.17MattEMattroot@RITSUKO-Linux:/home/matt/Desktop/hamcop# ./hamcop -n
10:28.17MattEMattFound HAMCOP on h2210 (ID: 6401324B)
10:28.17MattEMattID: FFh/FFh (Manufacturer: Unknown, Device name: Unknown)
10:28.17MattEMattReading byte: 528 / 528
10:28.17MattEMattData: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
10:29.12MattEMattthe rest of the page looks like that too...
10:29.21aquadranhmm
10:29.45aquadranafter power off/on the same ?
10:29.54MattEMattyup
10:30.18aquadrandid you get toshiba id anywhere ?
10:30.22MattEMattwould it happen to do with the TRST pin at all?
10:30.43aquadrantrst is jtag
10:31.09aquadranh2200 can have two flash, toshiba and samsung
10:31.19aquadrankind
10:31.22MattEMattnope I have all samsung chips
10:31.35aquadranhamcop only support one
10:31.41MattEMattand all i have gotten has been samsung and intel related
10:32.47aquadranlet me verify
10:33.28MattEMattokay
10:33.38aquadranah, not current hamcop support both i think
10:33.46aquadrani mean software
10:34.12aquadranat least id info
10:34.20MattEMattso the most current version does support samsung?
10:34.53aquadranthat is most current
10:35.51aquadranboth flash should be compatible
10:36.01aquadranbut you get 0xff for id
10:36.06aquadranbad
10:36.26aquadranmaybe nand is dead
10:36.33MattEMattdamn
10:36.55MattEMattwell here's the data sheet I found on the chips on the board
10:36.56MattEMattn> that is most current
10:36.56MattEMatt<aquadran> both flash should be compatible
10:36.56MattEMatt<aquadran> but you get 0xff for id
10:36.56MattEMatt<aquadran> bad
10:37.04MattEMattoops
10:37.20MattEMatthttp://dl.dropbox.com/u/25239089/Samsung%20Flash%20%28IPAQ%29%20datasheet.pdf
10:37.33aquadrandump code doesn't have error checking i think
10:38.15MattEMattjoshua_ 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.39MattEMattmaybe dead nand is why this whole thing happened in the first place...
10:50.24aquadrantry without -DNO_TIMING
10:51.10MattEMattso the command:
10:51.24MattEMatt./hamcop -dno_timing
10:52.43aquadranin makefile
10:53.03MattEMattahh I see
10:54.38aquadrani have toshiba flash
11:02.18MattEMattstill getting the same ID
11:08.07MattEMatthttp://dl.dropbox.com/u/25239089/build%20DNO_TIMING
11:08.15MattEMattthis is what I get for the build...
11:08.57MattEMatteverything is the same as before
11:13.38MattEMattaquadran, would me having a 64-bit version of my OS running be affecting anything?
11:14.14MattEMattI wouldn't think that it would, but I figured I would pose the question
11:31.10aquadrani also have running this on 64bit
11:31.24aquadranyou mean still 0xff id ?
11:31.24MattEMattok
11:31.44MattEMattI was referring to the OS.
11:31.56MattEMattI am still getting the 0xFF as the ID though
11:31.58aquadranyes
11:40.32MattEMatti'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)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.