irclog2html for #openjtag on 20050608

03:15.58*** join/#openjtag pjames (~jcouzens@mail.lost-carrier.com)
03:48.35*** join/#openjtag ka6sox (~ka6sox@adsl-66-159-198-116.dslextreme.com)
07:49.44*** join/#openjtag purl (ibot@apt.bot.TimRiker.active.supporter.pdpc)
07:49.44*** topic/#openjtag is This is the place to discuss development of Open JTAG tools and Bootloaders
08:42.24*** join/#openjtag JMunakra (~JMunakra@dsl-084-059-203-092.arcor-ip.net)
10:31.52*** join/#openjtag jamie__ (~jamie@softmodem.org)
10:42.49*** join/#openjtag ep1220 (~NN@gate.epatec.at)
10:45.20*** join/#openjtag [g2] (~g2@g2.nslu2-linux)
10:45.54ep1220[g2]: Hi
10:46.06[g2]ep1220, Hi!
10:46.53ep1220I first used the FTDI JTAG lib, but it has a nasty bug
10:47.03ep1220So i write my own now.
10:47.09[g2]really ?  what is it ?
10:47.27ep1220in a few case they count the bits from the wrong direction.
10:48.01ep1220reault. It is impossible to read out the ID of a chip
10:48.03[g2]that's not good :(
10:48.18ep1220Well, it is Win only, and  closed source anyway
10:48.29ep1220just had saved some time upfront
10:49.17ep1220And they are also missing functionality needed for JTAG debug
10:49.35ep1220So a write-my-own was inevitable anyway
10:49.40[g2]ep1220, is the MAN!
10:50.15[g2]I got my 1st unit back last week
10:50.22[g2]Memory and serial are good
10:50.34[g2]I've been running with 64MB for many days now
10:51.16ep1220NSLU2 or RV042 ?
10:54.17[g2]nslu2
10:54.41ep1220Nice. Did they add a JTAG ?
10:54.47[g2]They did
10:55.07[g2]I think that added the 0 ohm connector that's on TMS
10:55.18[g2]I don't know if they added the pull-down
10:55.43ep1220there is a 0 Ohm at TRST and they should remove it
10:56.08ep1220It is R135
10:56.51[g2]that may be it
10:57.17ep1220You maybe could add a pull-down directly at the JTAG connector.
10:57.27ep1220if You do not add it:
10:57.41ep1220You might have to reset the CPU after attaching a JTAG probe
10:58.36[g2]yeah I need to double check that stuff
10:58.47[g2]and probably check with a hw guy :)
10:59.58ep1220My SW is making good progress
11:00.15[g2]excellent
11:00.41ep1220Needs a few hours more, for testing.
11:01.04ep1220There are some tricky shift bit into right place, read bit from right place situations in there.
11:01.19ep1220Just writing a test-suite
11:01.32[g2]that's a good plan
11:01.57ep1220You remember we talked about writing a small program to out into the chache ?
11:02.04ep1220s/out/put
11:03.11[g2]ep1220, yes. I spoke with beewoolie about that
11:03.23[g2]we didn't think it would be too difficult
11:03.38[g2]I'm guessing you are ready now
11:03.58ep1220tomorrow I will be
11:05.09[g2]Ok... I'll try to have the LED program ready
11:05.28ep1220Great.
11:05.50ep1220using a gcc cross compiler ? which version ?
11:06.28[g2]well for the led code I'd imagine it's just a dozen or so instructions
11:06.58ep1220likely
11:06.59[g2]so wanted binary and a .c equivalent
11:07.05[g2]plus source
11:07.25[g2]We're currently using gcc 3.4.4 with OpenSlug
11:08.46ep1220source + an object/binary or the hexcodes in a .c (array of int or similar)
11:08.57ep1220source only would be helpfull as well
11:09.16ep1220Just as You guys find time
12:17.05*** join/#openjtag Tiersten_ (tman@Tiersten.nslu2-linux)
12:19.45*** join/#openjtag jamie (~jamie@softmodem.org)
12:20.46*** join/#openjtag jamie (~jamie@softmodem.org)
15:29.27*** join/#openjtag prpplague (~billybob@72.22.142.204)
16:41.30*** join/#openjtag purl (ibot@apt.bot.TimRiker.active.supporter.pdpc)
16:41.30*** topic/#openjtag is This is the place to discuss development of Open JTAG tools and Bootloaders
17:07.43prpplague~seen beewoolie
17:07.44purlbeewoolie <~beewoolie@florence.buici.com> was last seen on IRC in channel #openjtag, 3d 23m 40s ago, saying: 'jacques: ping.'.
17:09.39*** join/#openjtag purl (ibot@apt.bot.TimRiker.active.supporter.pdpc)
17:09.39*** topic/#openjtag is This is the place to discuss development of Open JTAG tools and Bootloaders
17:16.16*** join/#openjtag [g2] (~g2@g2.nslu2-linux)
18:03.53*** join/#openjtag beewoolie-afk (~beewoolie@florence.buici.com)
18:04.25beewoolie-afkprpplague: yo
18:04.41prpplaguebeewoolie: hey
18:04.49prpplaguepl110 driver
18:04.59prpplaguebeewoolie: i've had hell with getting my display working
18:05.08beewoolieWhat sort of panel.
18:05.23prpplaguebeewoolie: 160x160 4bit monochrome
18:05.46beewoolieDid you get RMKs patch for grayscape?
18:05.53beewoolies/grascape/grayscale/
18:06.04prpplaguenegative, didn't know there was one
18:06.14prpplagueurl?
18:06.17beewoolieIt was posted to the arm list a few weeks back.
18:06.22beewoolieSearch marc.
18:06.29prpplaguethat was for 2.6 though right?
18:06.33beewoolieYeah.
18:06.38beewoolieAre you still in 2.4 land?
18:07.52prpplagueyea
18:07.53prpplaguelegacy stuff
18:07.55prpplaguei can't seem to find any good examples of using a grayscale with the pl110
18:08.27beewoolieNot much I can offer for 2.4.  Based on my previous experience, I'm skeptical that it works with anything not already supported.
18:08.29prpplagueall my settings appear correct, but its like nothing is going from the sdram fb to the lcd controler
18:08.44beewooliedid you try sram?
18:09.09prpplagueyea, i tried mapping to sram, but i don't know if it was correct
18:09.25prpplaguei'm kinda suspecting that my lcd controler is toast at the momment
18:10.07prpplaguebeewoolie: i'll have a look at rmk patch
18:10.16prpplaguebeewoolie: any other suggestions?
18:11.56beewoolieprpplague: Nothing I can think of.  I've not spent much time with LCD stuff.  In fact, it's always worked straight away for me.  Even when I adapted a custom panel.
18:12.16beewoolieprpplague: Can you measure the frequency of the pixel clock?
18:13.37prpplaguebeewoolie: yea, we have a scope on it
18:13.45prpplaguebeewoolie: all the timing looks good
18:13.48beewoolieSo, that's it's ok.
18:14.00prpplaguebeewoolie: just don't get anything when we send data to the the fb
18:14.51beewoolieI'd start with SRAM.
18:15.10[g2]beewoolie, how goes ?
18:15.22beewoolieI'd also try programming the controller outside of the kernel.
18:15.26beewoolie[g2]: hey man
18:15.35[g2]did you get my latest e-mail ?
18:15.51beewoolieprpplague: Taking the MMU out of the loop may help illuminate problems.
18:16.00beewoolieprpplague: There is LCD initialization code in APEX for this purpose.
18:16.05beewoolie[g2]: ...loooking
18:16.19[g2]sorry... I thought you were done with prpplague
18:16.25beewoolie[g2]: I got one that told me prpplague was looking for me.
18:16.26prpplague[g2]: np
18:16.46prpplaguebeewoolie: is the code in apex using the sram?
18:17.14[g2]nod that's the one
18:17.40beewoolieprpplague: No.  It uses sdram.  But you can change the pointer easily.
18:18.10beewoolie[g2]: did you get my reply?
18:18.47[g2]beewoolie, nod.
18:23.08prpplaguebeewoolie: have you used the pl110 with a 4bit grayscale before?
18:23.57beewoolieprpplague: No.  I've only used a couple of color panels.
18:24.38prpplagueany 4bit?
18:25.12beewoolieI think maybe.  I don't remember.  I've used the 3.5" standard display and another wierd custom display.
18:25.30beewoolieI don't recall the details on the custom panel.  It had a really wierd output format.
18:25.51prpplaguehmm, i've got rmk's original pl110 patch, but i'm not seeing a grayscale patch
18:26.13beewoolieprpplague: Let me see if I can find the email.
18:32.31[g2]beewoolie, lennert stopped by in nslu2-linux :)
18:34.20beewoolie[g2]: Who is that?
18:36.22[g2]lennert from the arm-linux ml
18:36.29beewooliehttp://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-April/028564.html
18:36.36beewoolieprpplague: I think that this is the patch.
18:44.39prpplaguebeewoolie: ok thanks, that looks like some of the issues i've already corrected, but i look further
18:56.50*** join/#openjtag JMunakra (~JMunakra@dsl-084-059-203-092.arcor-ip.net)
19:23.01[g2]beewoolie, what's the latest status with jffs2 and loading the kernel ?
20:07.40beewoolie[g2]: It's waiting for me to have a chance to look at it again.  I understand the scope of the problem and have a solution.  It's a matter of implementation and test.
20:08.02[g2]beewoolie, thx
20:08.42[g2]jbowler has a tool used in the turnup proceedue that can replace the jffs2 and kernel from within OpenSlug
20:12.09beewoolieNoce
20:12.11beewoolieNice
20:12.23beewoolieI may be able to do some work on this today.
20:13.00[g2]I reflash jffs2 from the /dev/sda1 today and rebooted
20:13.05[g2]it's nice :)
20:13.46[g2]I think for me I probably won't be reloading redboot for quiet a while
20:27.51beewoolie[g2]: I'm clearing my plate as we speak.  It looks like I can carve out a couple of hours to work on the JFFS2 driver.
20:27.52[g2]beewoolie, what's the celebration ? not using redboot ?
20:28.00beewoolieUh huh.
21:24.22prpplaguejeeze just when i had a question
23:07.56*** join/#openjtag beewoolie-afk (~beewoolie@florence.buici.com)
23:16.31*** join/#openjtag Tiersten (tman@Tiersten.nslu2-linux)

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.