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.54 | ep1220 | [g2]: Hi |
10:46.06 | [g2] | ep1220, Hi! |
10:46.53 | ep1220 | I first used the FTDI JTAG lib, but it has a nasty bug |
10:47.03 | ep1220 | So i write my own now. |
10:47.09 | [g2] | really ? what is it ? |
10:47.27 | ep1220 | in a few case they count the bits from the wrong direction. |
10:48.01 | ep1220 | reault. It is impossible to read out the ID of a chip |
10:48.03 | [g2] | that's not good :( |
10:48.18 | ep1220 | Well, it is Win only, and closed source anyway |
10:48.29 | ep1220 | just had saved some time upfront |
10:49.17 | ep1220 | And they are also missing functionality needed for JTAG debug |
10:49.35 | ep1220 | So 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.16 | ep1220 | NSLU2 or RV042 ? |
10:54.17 | [g2] | nslu2 |
10:54.41 | ep1220 | Nice. 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.43 | ep1220 | there is a 0 Ohm at TRST and they should remove it |
10:56.08 | ep1220 | It is R135 |
10:56.51 | [g2] | that may be it |
10:57.17 | ep1220 | You maybe could add a pull-down directly at the JTAG connector. |
10:57.27 | ep1220 | if You do not add it: |
10:57.41 | ep1220 | You 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.58 | ep1220 | My SW is making good progress |
11:00.15 | [g2] | excellent |
11:00.41 | ep1220 | Needs a few hours more, for testing. |
11:01.04 | ep1220 | There are some tricky shift bit into right place, read bit from right place situations in there. |
11:01.19 | ep1220 | Just writing a test-suite |
11:01.32 | [g2] | that's a good plan |
11:01.57 | ep1220 | You remember we talked about writing a small program to out into the chache ? |
11:02.04 | ep1220 | s/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.58 | ep1220 | tomorrow I will be |
11:05.09 | [g2] | Ok... I'll try to have the LED program ready |
11:05.28 | ep1220 | Great. |
11:05.50 | ep1220 | using 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.58 | ep1220 | likely |
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.46 | ep1220 | source + an object/binary or the hexcodes in a .c (array of int or similar) |
11:08.57 | ep1220 | source only would be helpfull as well |
11:09.16 | ep1220 | Just 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.43 | prpplague | ~seen beewoolie |
17:07.44 | purl | beewoolie <~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.25 | beewoolie-afk | prpplague: yo |
18:04.41 | prpplague | beewoolie: hey |
18:04.49 | prpplague | pl110 driver |
18:04.59 | prpplague | beewoolie: i've had hell with getting my display working |
18:05.08 | beewoolie | What sort of panel. |
18:05.23 | prpplague | beewoolie: 160x160 4bit monochrome |
18:05.46 | beewoolie | Did you get RMKs patch for grayscape? |
18:05.53 | beewoolie | s/grascape/grayscale/ |
18:06.04 | prpplague | negative, didn't know there was one |
18:06.14 | prpplague | url? |
18:06.17 | beewoolie | It was posted to the arm list a few weeks back. |
18:06.22 | beewoolie | Search marc. |
18:06.29 | prpplague | that was for 2.6 though right? |
18:06.33 | beewoolie | Yeah. |
18:06.38 | beewoolie | Are you still in 2.4 land? |
18:07.52 | prpplague | yea |
18:07.53 | prpplague | legacy stuff |
18:07.55 | prpplague | i can't seem to find any good examples of using a grayscale with the pl110 |
18:08.27 | beewoolie | Not 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.29 | prpplague | all my settings appear correct, but its like nothing is going from the sdram fb to the lcd controler |
18:08.44 | beewoolie | did you try sram? |
18:09.09 | prpplague | yea, i tried mapping to sram, but i don't know if it was correct |
18:09.25 | prpplague | i'm kinda suspecting that my lcd controler is toast at the momment |
18:10.07 | prpplague | beewoolie: i'll have a look at rmk patch |
18:10.16 | prpplague | beewoolie: any other suggestions? |
18:11.56 | beewoolie | prpplague: 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.16 | beewoolie | prpplague: Can you measure the frequency of the pixel clock? |
18:13.37 | prpplague | beewoolie: yea, we have a scope on it |
18:13.45 | prpplague | beewoolie: all the timing looks good |
18:13.48 | beewoolie | So, that's it's ok. |
18:14.00 | prpplague | beewoolie: just don't get anything when we send data to the the fb |
18:14.51 | beewoolie | I'd start with SRAM. |
18:15.10 | [g2] | beewoolie, how goes ? |
18:15.22 | beewoolie | I'd also try programming the controller outside of the kernel. |
18:15.26 | beewoolie | [g2]: hey man |
18:15.35 | [g2] | did you get my latest e-mail ? |
18:15.51 | beewoolie | prpplague: Taking the MMU out of the loop may help illuminate problems. |
18:16.00 | beewoolie | prpplague: There is LCD initialization code in APEX for this purpose. |
18:16.05 | beewoolie | [g2]: ...loooking |
18:16.19 | [g2] | sorry... I thought you were done with prpplague |
18:16.25 | beewoolie | [g2]: I got one that told me prpplague was looking for me. |
18:16.26 | prpplague | [g2]: np |
18:16.46 | prpplague | beewoolie: is the code in apex using the sram? |
18:17.14 | [g2] | nod that's the one |
18:17.40 | beewoolie | prpplague: No. It uses sdram. But you can change the pointer easily. |
18:18.10 | beewoolie | [g2]: did you get my reply? |
18:18.47 | [g2] | beewoolie, nod. |
18:23.08 | prpplague | beewoolie: have you used the pl110 with a 4bit grayscale before? |
18:23.57 | beewoolie | prpplague: No. I've only used a couple of color panels. |
18:24.38 | prpplague | any 4bit? |
18:25.12 | beewoolie | I think maybe. I don't remember. I've used the 3.5" standard display and another wierd custom display. |
18:25.30 | beewoolie | I don't recall the details on the custom panel. It had a really wierd output format. |
18:25.51 | prpplague | hmm, i've got rmk's original pl110 patch, but i'm not seeing a grayscale patch |
18:26.13 | beewoolie | prpplague: Let me see if I can find the email. |
18:32.31 | [g2] | beewoolie, lennert stopped by in nslu2-linux :) |
18:34.20 | beewoolie | [g2]: Who is that? |
18:36.22 | [g2] | lennert from the arm-linux ml |
18:36.29 | beewoolie | http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-April/028564.html |
18:36.36 | beewoolie | prpplague: I think that this is the patch. |
18:44.39 | prpplague | beewoolie: 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.40 | beewoolie | [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.09 | beewoolie | Noce |
20:12.11 | beewoolie | Nice |
20:12.23 | beewoolie | I 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.51 | beewoolie | [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.00 | beewoolie | Uh huh. |
21:24.22 | prpplague | jeeze 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) |