irclog2html for #openjtag on 20060915

00:53.48*** join/#openjtag rwhitby (n=rwhitby@nslu2-linux/rwhitby)
02:28.31*** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox)
08:45.53*** join/#openjtag NAiL (n=repvik@nslu2-linux/pdpc.active.NAiL)
09:03.17*** join/#openjtag [TEHb]_ (n=nickolay@mail2.lanck.net)
09:40.49*** join/#openjtag bullet (n=bullet@206.59.77.83.cust.bluewin.ch)
12:33.31*** join/#openjtag vmaster_ (n=vmaster@p549B4EB6.dip.t-dialin.net)
13:06.24*** join/#openjtag prpplague (n=billybob@69.73.222.167)
13:22.36prpplaguevmaster: morning
13:23.40vmasterhey prpplague
13:24.10prpplaguevmaster: you said you used your dlpdesign module without any buffers correct?
13:25.17vmasteryeah
13:25.47vmasterjust a 3v3 regulator from the 5v usb, but vref would probably have been an even better choice
13:35.11prpplaguevmaster: yea, just let the voltage from the target board provide the voltage
13:35.29prpplaguevmaster: you got a schematic done up?
14:06.27vmasterit's the one in my thesis, on the openocd page (openocd.berlios.de/web/)
14:06.31vmasterUSBJTAG-1
14:10.29prpplaguevmaster: ok thanks
14:14.43prpplaguevmaster: you said you had to make some changes to the eprom config using that schematic?
14:25.14vmasteryeah, the default is to drive with something like 5ma, but you can enable a high-drive mode with 10 or 15ma
14:26.07prpplaguevmaster: ahh ok
14:28.50prpplaguevmaster: not gonna hurt to try it with the current settings?
14:38.54vmasterno, not at all
16:30.40prpplaguevmaster: ping
16:39.03vmasterprpplague: pong
16:40.32prpplaguevmaster: on the m5960 schematic
16:40.48prpplaguevmaster: i removed r9 and 9
16:40.52prpplagueand c9
16:41.00prpplaguevmaster: works with no errors now
16:41.08prpplaguevmaster: getting about 50kbps
16:41.25vmasterto flash? that's probably as good as it gets with the ft2232
16:42.01prpplagueyea
16:42.13vmastermhh, what were r9 and c9 supposed to do?
16:42.21prpplaguevmaster: jtag_speed set to 1 seems the best
16:42.44prpplaguevmaster: i spoke to our ee, according to him it was for use with flexible cables, per ieee standards
16:43.12prpplaguevmaster: but after showing him several other schematics we decided that was cause the tdo to bleed off incorrectly
16:43.29vmasterheh, guess you should tell your cable to read the ieee standards then
16:43.35prpplagueyea
16:44.00prpplaguedoing some speed tests now
16:44.15prpplaguevmaster: so i can start openocd with a script and exit correct?
16:44.20vmasteryeah
16:44.39prpplaguelovely
16:45.02prpplaguevmaster: ever tried running multi copies of openocd on one pc?
16:45.03vmastertarget_script <target#> <event_name> <script_file> binds a script to a particular event
16:45.17vmasterprpplague: yeah, it works, but the USB controller might become a bottleneck
16:45.31vmasterlatency is critical, not sure how multiple devices are going to behave
16:45.37prpplaguevmaster: yea, we got a pc with 4 seperate controllers
16:45.43vmasterah, ok
16:46.02vmastercurrently, the only event is "reset", which would better be called "init"
16:46.21vmasterit's delivered after the target entered debug state in case of "reset_init" or "run_and_init"
16:46.56vmasterif the s3c behaves good in reset (most arm9 do), you can use "reset_init" to halt the target right at the reset vector
16:47.03vmasterand execute the script
16:47.13prpplaguevmaster: yea, seems so
16:47.14vmasteras the last command in the script issue a shutdown
16:47.31vmasterwait_halt allows you to pause script execution until debug was actually reached
16:49.04prpplagueahh cool deal
16:49.06prpplaguethats perfect
16:49.39prpplaguevmaster: we'll be able to do some basic tests, then flash the unit and we'll be done
16:49.55vmasteryep
16:50.13prpplaguerun a full speed test now
16:50.24vmasterwell, there's no error handling in the script support so far
16:50.25prpplaguethe flash erase doesn't seem any faster, but the flash process does
16:50.42vmasterflash erase time is mostly dictated by the device
16:50.47prpplagueyea
16:50.51vmasteri.e. the openocd is polling faster than the device erases anyway
16:51.28prpplaguemy guess is that it will take 90 seconds to do 4mb
16:51.41prpplague94 seconds
16:52.14prpplaguevmaster: the dcc downloads process, that do any type of error checking?
16:52.26vmasternone at all
16:52.31prpplaguehmm
16:52.34vmasterit just pretends that the target is always faster than the jtag
16:53.50vmastera verify stage would be easy to implement - reading is >50kbyte/s
16:55.12prpplagueyea, thats what i was thinking
16:55.46prpplague72 seconds for 16mb flash erase, 94 seconds flash programming, 10 misc
16:56.29vmasterah, the cfi code is not endianess safe yet - you'll definitely run into problems with big endian targets or hosts
16:56.44vmasterit's not a lot that's required, but i've had no time yet, and nothing to test with anyway
16:56.54vmastereverything else should work with either endianness
16:57.37prpplaguevmaster: yea, we are little endian
17:09.48prpplaguevmaster: i do seem to get some verification errors with fast_memory_access
17:12.43vmasteri'd have to do some calculations, but maybe 12mhz and 3mhz jtag clock are too close
17:12.58vmasteryou could try enabling the pll
17:13.17vmasterthat should be scriptable, too
17:14.44prpplaguevmaster: yea i'm running with the pll enabled
17:15.16prpplaguevmaster: i'm not see that big of a difference with the fast memory access anyway
17:33.55vmasteryeah, it's only used to upload the DCC code anyway
17:34.13vmasterand chunks of less than 128 byte, which is a rare when doing flash writes
17:36.00prpplaguewell, looks good
17:36.05prpplaguevmaster: thanks for the help
17:36.17prpplaguevmaster: we will be making this available soon along with the schematic
17:36.29prpplaguevmaster: we have a line of small dev boards coming out as well
17:36.59prpplaguevmaster: hhoegl's web page seems defunct
17:37.20prpplaguevmaster: i made a pdf of just the usbjtag-1 schematic from your thesis
18:07.12*** join/#openjtag muasch|swiss10 (n=muasch@31.14.3.213.fix.bluewin.ch)
18:15.30*** join/#openjtag muasch|swiss11 (n=muasch@31.14.3.213.fix.bluewin.ch)
18:22.07*** join/#openjtag muasch|swiss12 (n=muasch@31.14.3.213.fix.bluewin.ch)
18:23.27prpplaguemuasch|swiss12: d00d
18:23.34prpplaguemuasch|swiss12: whats the story?
18:23.44prpplaguethere are three of you now?
18:24.07muasch|swiss12prpplague, sorry. i have some problems with one of my wlan-routers :(
18:24.32prpplaguemuasch|swiss12: ok just wanted to make sure it wasn't some sort of bot trying to do a take-over
18:25.04muasch|swiss12ah no. i'will disconnect from irc the next time i play with my router ;-)
19:02.12*** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox)
19:26.35rwhitbyvmaster: ping
19:28.08vmasterrwhitby: pong
19:36.28rwhitbyvmaster: we have a guy at work who is now modifying openocd to support the processor arch we discussed previously
19:36.44rwhitbyWill you have some time this week to review our changes to make sure we're on the right track?
19:37.11rwhitby(We expect, lawyers willing, that the changes will be contributed back to openocd)
19:38.34rwhitbyThe lawyers should be fine, cause they should be able to understand our GPL commitments (quite apart from our true desire to contribute back, but lawyers never understand that)
19:42.25vmasterrwhitby: yeah, sure
19:42.58vmasterrwhitby: if questions from his side arise i'm here to answer
19:45.24rwhitbyvmaster: thx
19:45.34rwhitbywill talk on Monday
21:01.29*** join/#openjtag muasch|swiss12 (n=muasch@31.14.3.213.fix.bluewin.ch)
21:14.01*** join/#openjtag muasch|swiss13 (n=muasch@31.14.3.213.fix.bluewin.ch)

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.