| 00:24.07 | *** join/#openjtag ka6sox (n=tom@nslu2-linux/ka6sox) |
| 00:49.28 | *** join/#openjtag beewoolie-afk (n=beewooli@206.124.142.26) |
| 01:05.04 | *** join/#openjtag vmaster_ (i=vmaster@p549B6DBE.dip.t-dialin.net) |
| 01:13.43 | beewoolie-afk | [g2]: yo |
| 01:13.49 | beewoolie-afk | dyoung-away: yo |
| 01:13.59 | beewoolie-afk | ka6sox: yo |
| 01:14.21 | beewoolie-afk | Guess it's kinda late for yall. |
| 01:15.43 | lennert | 2:15AM |
| 01:16.22 | lennert | time for me to go to bed too |
| 01:16.24 | lennert | g'nite all |
| 01:16.51 | ka6sox | nite lennert |
| 01:17.04 | ka6sox | lennert: before you go |
| 01:17.21 | ka6sox | is there ameb-softfpu emulation? |
| 01:17.24 | ka6sox | in qemu? |
| 01:17.39 | ka6sox | beewoolie-afk: yo! |
| 01:19.54 | beewoolie-afk | hi lennert |
| 01:19.54 | beewoolie-afk | hi ka6sox |
| 01:19.55 | beewoolie-afk | I've been away from it for a while. |
| 01:45.52 | ka6sox | me too...I've moved and am still in the throws of figuring out where the sock drawer got off to! |
| 01:46.08 | ka6sox | bbiaf....taking my wife out and picking up my Son. |
| 02:54.41 | ka6sox | back |
| 02:56.03 | beewoolie-afk | ka6sox: have you populated your JTAG boards yet? |
| 02:57.08 | ka6sox | yes |
| 02:57.27 | ka6sox | I need to test a little more...I have programmed the eeprom already however |
| 03:08.43 | beewoolie-afk | Nice. |
| 03:08.56 | beewoolie-afk | ka6sox: did you buy from digikey? Mouser? |
| 03:12.09 | ka6sox | digikey |
| 03:12.19 | beewoolie-afk | What was the total? |
| 03:12.22 | ka6sox | and I think one thing from mouser |
| 03:12.57 | ka6sox | I can't remember as I had somethings here and ordered about 6 weeks ago before I bought the house...since then I can't even remember my own name! |
| 03:29.31 | beewoolie-afk | ka6sox: congrts on the dome. |
| 03:29.34 | beewoolie-afk | ttfn |
| 03:54.54 | *** join/#openjtag dot (n=ka6sox@pool-71-102-140-145.snloca.dsl-w.verizon.net) |
| 06:08.15 | *** join/#openjtag ka6sox-office (n=tking@nslu2-linux/ka6sox) [NETSPLIT VICTIM] |
| 06:15.35 | *** join/#openjtag cpage_ (n=cpage@netblock-68-183-40-134.dslextreme.com) [NETSPLIT VICTIM] |
| 06:19.55 | *** join/#openjtag purl (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 06:19.55 | *** topic/#openjtag is This is the place to discuss development of Open JTAG tools and Bootloaders |
| 06:20.00 | *** join/#openjtag NAiLZzZ (n=repvik@nslu2-linux/pdpc.active.repvik) |
| 08:45.07 | *** join/#openjtag toi (n=pleemans@d5152D12D.access.telenet.be) |
| 10:22.59 | lennert | ka6sox: qemu emulates the FPA floating point unit |
| 10:23.08 | lennert | ka6sox: which means you can use both hardfloat and softfloat binaries |
| 12:05.19 | *** join/#openjtag prpplague (n=billybob@72.22.141.111) |
| 13:31.47 | *** part/#openjtag dwery-away (n=dwery@nslu2-linux/dwery) |
| 14:53.43 | *** join/#openjtag ulf_k_ (n=ulf_kypk@p54BDBEEC.dip0.t-ipconnect.de) |
| 16:21.07 | [g2] | ka6sox ka6sox-office ping |
| 16:21.33 | [g2] | I'm wondering what's up with the board |
| 18:28.08 | *** join/#openjtag beewoolie-afk (n=beewooli@206.124.142.26) |
| 18:30.46 | beewoolie-afk | [g2]: hey man |
| 18:30.55 | beewoolie-afk | prpplague: yo |
| 18:31.25 | prpplague | beewoolie-afk: hey |
| 18:31.30 | prpplague | beewoolie-afk: whats cookin? |
| 18:31.50 | beewoolie-afk | prpplague: Adding MMU enabling code APEX at the moment. |
| 18:31.53 | prpplague | beewoolie-afk: btw, the lnode80 goes into full production monday |
| 18:32.09 | beewoolie-afk | It turns out to be necessary (desirable) for splash screen decode. |
| 18:32.15 | beewoolie-afk | prpplague: kudos |
| 18:32.25 | prpplague | beewoolie-afk: i've got a complete kit set aside to send you |
| 18:32.43 | beewoolie-afk | prpplague: sweet. Did we finish with the patch? |
| 18:32.52 | prpplague | beewoolie-afk: for the lnode80 yea |
| 18:32.57 | prpplague | beewoolie-afk: not for the s3c2410 |
| 18:33.02 | beewoolie-afk | k. |
| 18:33.04 | prpplague | beewoolie-afk: i got pulled off for a fire |
| 18:33.14 | prpplague | beewoolie-afk: major $$$ project |
| 18:33.20 | beewoolie-afk | Always a good ting. |
| 18:33.29 | prpplague | beewoolie-afk: 3500 very expensive handhelds |
| 18:33.46 | prpplague | s/very/VERY |
| 18:34.31 | prpplague | beewoolie-afk: how stable is the usb slave on the 79524/5 series? |
| 18:34.52 | beewoolie-afk | prpplague: I don't think that the slave has ever been coded. |
| 18:35.00 | prpplague | wow |
| 18:35.02 | beewoolie-afk | At least, I've not noticed it. |
| 18:35.08 | beewoolie-afk | No one has asked for t. |
| 18:35.19 | prpplague | interesting |
| 18:35.45 | prpplague | seems odd, but then i guess the 79524/5 isn't geared for handhelds |
| 18:36.09 | beewoolie-afk | Well, no one has asked for the client (slave) interface for any of the LH processors. |
| 18:36.22 | prpplague | interesting |
| 18:36.27 | prpplague | seems very odd |
| 18:36.40 | beewoolie-afk | It's possible someone has done it as I recall that there was some gadget work. Isn't that usually on the slave? |
| 18:36.40 | prpplague | that would be one of the first things we'd have looked for |
| 18:36.50 | *** join/#openjtag Tiersten (i=tman@nslu2-linux/Tiersten) |
| 18:37.20 | prpplague | yea |
| 18:37.50 | beewoolie-afk | Then I think there has been something written for it. |
| 18:38.26 | prpplague | ahh |
| 18:38.32 | beewoolie-afk | There is a file i the tree...drivers/usb/gadget/lh7a40x_udc.c |
| 18:38.51 | prpplague | well, i was kinda thinking about doing a small board for own stuff |
| 18:39.13 | prpplague | but as far as work goes, sharp really shot themselves in the foot with us |
| 18:39.25 | beewoolie-afk | So you said. |
| 18:39.36 | prpplague | i still like the 79520 for small stuff |
| 18:39.52 | prpplague | thats one reason we still went forward with the lnode80 board |
| 18:40.01 | beewoolie-afk | Is it really better than the samsung parts for that? |
| 18:40.26 | prpplague | beewoolie-afk: no not really |
| 18:40.37 | prpplague | jsut we'd already put alot of work into the design |
| 18:40.43 | beewoolie-afk | I'm not advocating, here, I'm jus curious. |
| 18:41.03 | beewoolie-afk | If you already have a design, what is it that Sharp isn't doing for you? |
| 18:41.31 | prpplague | beewoolie-afk: well we have about 6 designs we were gonna do |
| 18:41.40 | prpplague | beewoolie-afk: only 1 survived with the lh79520 |
| 18:41.49 | prpplague | beewoolie-afk: the rest got moved to samsung |
| 18:42.04 | beewoolie-afk | because...? |
| 18:42.44 | prpplague | beewoolie-afk: mainly because we weren't getting any help with the initial board bringing |
| 18:42.54 | prpplague | beewoolie-afk: there were tons of things that were missing from the docs |
| 18:43.01 | beewoolie-afk | Hmm. |
| 18:43.04 | prpplague | beewoolie-afk: and we had to find them out ourselves |
| 18:43.06 | beewoolie-afk | LPD or Sharp? |
| 18:43.11 | prpplague | beewoolie-afk: sharp |
| 18:43.34 | beewoolie-afk | Interesting. I've not found the LH79520 docs to be lacking, but I haven't done any hardware design for it. |
| 18:43.51 | beewoolie-afk | LPD OTOH has lots of gaps in their docs. |
| 18:44.20 | prpplague | tons of things, like info on the lcd interface timmings, the sdram inits, problems with the jtag |
| 18:45.07 | prpplague | like all the docs are geared for x32 sdram configs, and no information at all for running with a single x16 chip |
| 18:45.15 | beewoolie-afk | Hmm. I never found those things to be a problem. |
| 18:46.05 | beewoolie-afk | Ah. Right. I was always working with 32 bit memory. However, I did configure the lh79525 with 16bit memory. The docs were fine, tho. All I needed was a schematic so that I could get the right signals setup. |
| 18:46.46 | beewoolie-afk | prpplague: BTW, I did mention that I'd spoken with a customer who had dropped the LH chips because of these kinds of problems. |
| 18:47.02 | prpplague | beewoolie-afk: and what did they say? |
| 18:48.17 | beewoolie-afk | There was no specific response. They acknowledged that a transition on the marketing team had left some gaps in support. |
| 18:48.40 | beewoolie-afk | They said that they've added a forum to help customers get their questions answered. |
| 18:48.41 | prpplague | beewoolie-afk: i've got like 10 posts on their forum for the lh79520, all of which they say they will fix in the docs, however almost 9 months later, the docs haven't been updated |
| 18:48.48 | beewoolie-afk | On the Sharp site? |
| 18:48.51 | prpplague | yea |
| 18:49.05 | beewoolie-afk | Hmm. I'll look at them and see what is up. |
| 18:50.28 | prpplague | just have a look at how many times the sdram init problems are posted there |
| 18:51.02 | prpplague | beewoolie-afk: kinda like this one - http://forums.sharpsma.com/viewtopic.php?t=168 |
| 18:53.16 | prpplague | beewoolie-afk: btw, if it seems i'm blasting you for sharp's mistakes, i don't mean it |
| 18:53.38 | beewoolie-afk | NP. I know these people, so I think the situation looks different to me. |
| 18:53.43 | beewoolie-afk | Let me see if I understand the issue. |
| 18:53.46 | beewoolie-afk | ...in this case. |
| 18:54.06 | beewoolie-afk | When you use 16 bit SDRAM, you need to double the size of a burst because you need to fill a cache line. |
| 18:54.53 | prpplague | that is correct |
| 18:55.16 | beewoolie-afk | The burst of 4 is 4 accesses at the bus width. 128 bits or 16 bytes. On a 16 bit bus, the burst has to be 8 so that you get 16 bytes. |
| 18:55.34 | prpplague | beewoolie-afk: thats my understanding |
| 18:55.55 | beewoolie-afk | I guess that I don't see this as a big omission on their part. |
| 18:56.22 | beewoolie-afk | After all, that is what a burst is about. |
| 18:56.54 | prpplague | beewoolie-afk: well, you see, when i was running into trouble during the init problem i post and called about 20 times about the fact there was no example about how to calculate the proper burst rate |
| 18:57.06 | prpplague | beewoolie-afk: only after i posted the answer did someone respond |
| 18:57.23 | beewoolie-afk | That is definitely not good. |
| 18:57.31 | prpplague | beewoolie-afk: if you look at the sa-1110 manual |
| 18:57.41 | prpplague | beewoolie-afk: every register has a equation listed |
| 18:57.44 | beewoolie-afk | Sure, I can see how this would be frustrating. |
| 18:57.53 | prpplague | beewoolie-afk: there is no question about to calculate the value |
| 18:58.08 | beewoolie-afk | They added this sort of thing to the 79524 manual. |
| 18:58.22 | beewoolie-afk | In fact, they have a table with lots of memory combinations. |
| 18:58.35 | prpplague | beewoolie-afk: every one of them 32-bit |
| 18:58.48 | prpplague | beewoolie-afk: i dare you to find a 16-bit example |
| 18:58.55 | prpplague | beewoolie-afk: http://forums.sharpsma.com/viewtopic.php?t=142 |
| 18:59.00 | prpplague | beewoolie-afk: there is my first post |
| 18:59.17 | prpplague | beewoolie-afk: i sent out schematic and info as posted, never got a response |
| 18:59.31 | prpplague | beewoolie-afk: called them, they said they had gotten the info and would look |
| 18:59.36 | prpplague | beewoolie-afk: never heard a word back |
| 18:59.38 | *** join/#openjtag bullet (n=bullet@139.217.203.62.cust.bluewin.ch) |
| 18:59.38 | beewoolie-afk | Look at page 7-20 of the lh79524 manual. |
| 18:59.50 | prpplague | beewoolie-afk: called almost every day for 2 weeks |
| 19:00.08 | beewoolie-afk | prpplague: I think that they got the message...eventually. |
| 19:01.04 | beewoolie-afk | prpplague: I'm not saying that they were on it when you had your trouble. I'm just saying that they did get the message eventually. |
| 19:01.21 | beewoolie-afk | In the dialog that you had on the forum, you got a reply from Doug Jones. He was the fellow who hired me. |
| 19:01.59 | beewoolie-afk | He was consciencious and put a lot of effort into helping customers get what they needed. |
| 19:03.03 | prpplague | beewoolie-afk: granted that that was pretty much end of us trying to get help from sharp, as we had already made the decision not to use sharp for the other projects |
| 19:03.17 | beewoolie-afk | Understood. |
| 19:03.19 | prpplague | beewoolie-afk: they may have changed, i don't know |
| 19:03.37 | beewoolie-afk | Well, I wouldn't say they are 100%. |
| 19:04.04 | prpplague | beewoolie-afk: have a look on the forum about how many ppl are still having jtag issues |
| 19:04.05 | beewoolie-afk | I suspect that they're like a lot of places where the only advocates the customers have are the sales folks. |
| 19:04.12 | beewoolie-afk | will do... |
| 19:04.49 | prpplague | beewoolie-afk: it wouldn't take sharp much to post a nice linux wiggler app that would be generic enough to fit alot of the flash needs |
| 19:06.45 | beewoolie-afk | It would require someone writing one. |
| 19:06.48 | prpplague | beewoolie-afk: i mean, think of it like my boss, where his questions to me are like, "well if we are having this much trouble jtag flashing this device during development, what kind of problems will we have during production?" |
| 19:07.20 | beewoolie-afk | it's funny that those folks are having these problems because I know that the OCD and BDI software work. |
| 19:07.34 | prpplague | beewoolie-afk: duh, i already have one that i've sent to lij |
| 19:08.03 | prpplague | beewoolie-afk: we there are a ton of issues with the lh7952x jtag |
| 19:08.25 | beewoolie-afk | Yeah. I get that. It also isn't quite fair since it's like saying: "I'm driving this car with home-made gasoline and it's missing and sputtering. What other sorts of problems will I have?" |
| 19:08.46 | beewoolie-afk | I'll as Jun about it... |
| 19:09.20 | prpplague | beewoolie-afk: sorry that doesn't fly with me due to the fact that if the lh79520 jtag was IEEE compliant these wouldn't be issues |
| 19:09.52 | prpplague | all of the issues are due to that fact |
| 19:09.55 | beewoolie-afk | As I said, it works with the ARM hardware, the BDI hardware, and the Wiggler's software. |
| 19:10.10 | beewoolie-afk | so, I was never aware of an issue. |
| 19:11.06 | prpplague | beewoolie-afk: yea, thats because sharp worked with them to fix the issue(as i understand it from a friend who works a macgraigor) |
| 19:11.44 | beewoolie-afk | prpplague: They didn't do anything special for Abatron. |
| 19:12.23 | vmaster | are the sharp arms -S cores? or hard cores? |
| 19:12.35 | beewoolie-afk | vmaster: Don't know. |
| 19:12.46 | beewoolie-afk | vmaster: Where would one find that info? |
| 19:12.51 | prpplague | beewoolie-afk: i don't see how they couldn't have |
| 19:13.12 | vmaster | mhh, what core do they use? |
| 19:13.18 | prpplague | beewoolie-afk: http://document.sharpsma.com/Handler/getfile_handler2.asp?nodeid=Documents&fileid=88EDF5CF792946AF93D03CEC1DF1872E |
| 19:13.28 | beewoolie-afk | prpplague: I'm certain that Abatron hadn't heard of the LH79520 before I bought a BDI2000 to use with it. |
| 19:14.01 | prpplague | beewoolie-afk: hmm, and it worked out of the box? |
| 19:14.32 | beewoolie-afk | prpplague: That page isn't working for me. |
| 19:14.43 | beewoolie-afk | and yeah, it worked out of the box. |
| 19:14.53 | prpplague | beewoolie-afk: thats interesting |
| 19:15.17 | beewoolie-afk | I mean, I had to ask for help with the config because I was being a dumb-ass. But they made no FW changes for me. |
| 19:18.06 | prpplague | beewoolie-afk: hmm, it seems i can't directly link to that doc |
| 19:18.20 | beewoolie-afk | How did you get there? |
| 19:18.27 | prpplague | beewoolie-afk: http://tinyurl.com/dn6b8 |
| 19:18.29 | prpplague | try that |
| 19:18.33 | prpplague | should be a pdf |
| 19:18.59 | beewoolie-afk | It wants a login but it doesn't accept my sharp login. |
| 19:19.19 | prpplague | beewoolie-afk: its on the lh79520 page, Errata 07/11/05 |
| 19:20.15 | prpplague | beewoolie-afk: my lauterbach had to have a firmware update for it work with the lh79520 for which they reference the errata |
| 19:21.04 | vmaster | they only talk about boundary scanning |
| 19:21.31 | vmaster | beewoolie-afk: go there first: http://www.sharpsma.com/part.php?PartID=173 |
| 19:21.49 | vmaster | looks like a deep-link protection |
| 19:21.51 | beewoolie-afk | I got the erratum. |
| 19:21.56 | prpplague | this is the main kicker "the LH79520 outputs change state on the rising edge of TCK. The IEEE 1149.1 specification states that signals driventhe LH79520 outputs change state on the rising edge of TCK out of the component via the boundary scan logic must change state relative to the falling edge of TCK." |
| 19:22.40 | lennert | oooh, bad bad |
| 19:22.42 | prpplague | thats the item that has broken almost every app i tried |
| 19:22.54 | lennert | you can _not_ change TDO on rising_edge(TCK) |
| 19:23.02 | vmaster | hehehe, you shouldn't at least |
| 19:23.07 | vmaster | that's when the tap master samples tdo |
| 19:23.10 | prpplague | the other one is this "The test mode select pins nTSTA, TEST1, and TEST2 are included in the boundary scan chain. These pins, when set to 101 (respectively) before a rising edge of nRESETIN, are used to activate the JTAG interface. However, boundary scan vectors that are generated using the BSDL file float these inputs because they are part of the boundary scan chain. As a result, the JTAG interface enters an undefined state when the vectors a |
| 19:23.10 | prpplague | re exercised, causing the boundary scan to be non-functional." |
| 19:23.34 | vmaster | prpplague: yes, but that only refers to boundary-scanning, i.e. around all the device pins |
| 19:23.35 | beewoolie-afk | I read that. |
| 19:23.36 | lennert | vmaster: tap master can sample TDO anywhere between falling_edge + delta and raising_edge - delta |
| 19:23.52 | prpplague | vmaster: correct which is how alot of flash apps work |
| 19:24.18 | prpplague | vmaster: AND my last check the BSDL file that sharp distrubtes DOESN'T have those pins set properly |
| 19:24.33 | lennert | vmaster: actually, anywhere between falling_edge + delta and falling_edge - delta |
| 19:24.51 | beewoolie-afk | I'll query them about this. It looks like it's just a bug in the silicon. |
| 19:25.13 | prpplague | "Solution: Permanent erratum; this will not be fixed." |
| 19:25.23 | beewoolie-afk | prpplague: as there is a work-around. |
| 19:25.34 | lennert | they can't claim JTAG compliance then |
| 19:25.35 | vmaster | prpplague: yeah, but that explains why abatron works |
| 19:25.59 | prpplague | beewoolie-afk: exactly my point, if you are gonna use a f'd up jtag, you should atleast provide some code that helps people use your f'd up jtag |
| 19:26.21 | beewoolie-afk | lennert: the erratum states that they aren't compliant. |
| 19:26.41 | beewoolie-afk | prpplague: they do indicate some products tha work. |
| 19:26.42 | prpplague | beewoolie-afk: but they don't advertise that fact |
| 19:26.48 | beewoolie-afk | prpplague: It sounds like you really just want to hate them. |
| 19:26.56 | prpplague | beewoolie-afk: hehe, no |
| 19:27.10 | beewoolie-afk | I'm hearing a lot of hate. |
| 19:27.34 | prpplague | beewoolie-afk: i got frustrated because i was collecting all this info and trying to help sharp make their items better, and all i got on the other end was a dead line |
| 19:27.36 | beewoolie-afk | After all, they're not claiming that there are weapons of mass desctruction. |
| 19:27.36 | lennert | i hear a lot of frustration, rather |
| 19:28.05 | prpplague | beewoolie-afk: i'm still willing to provide them help |
| 19:29.00 | vmaster | prpplague: they really can't do a lot more than admitting that they blew it |
| 19:29.34 | prpplague | vmaster: i disagree, providing clear documentation and sample code would go a long way in my book |
| 19:30.00 | prpplague | vmaster: and i have a list of about 20 items like this |
| 19:30.29 | vmaster | prpplague: yeah, regarding the other things you've mentioned, but not the jtag part |
| 19:30.32 | beewoolie-afk | Sounds like prplague has some 'letting go' to do. |
| 19:30.39 | prpplague | hehe |
| 19:30.40 | beewoolie-afk | :-) |
| 19:30.49 | prpplague | yea i get passionate about stuff |
| 19:31.48 | vmaster | philips lpc are just the same - several debugger vendors contacted them about a problem with their devices, but their remarks didn't even make it into the erratas |
| 19:32.20 | vmaster | i contacted their support, and they didn't even know there was a problem |
| 19:32.34 | beewoolie-afk | I believe that a better solution than trying to get the vendors to comply is to produce a hardware/software jtag solution... |
| 19:32.41 | beewoolie-afk | Oh right. this is openjtag.... |
| 19:32.45 | vmaster | ;) |
| 19:32.51 | prpplague | hehe |
| 19:33.17 | prpplague | beewoolie-afk: its not like off the shelf code doesn't work, just got to make the nessary changes |
| 20:12.44 | prpplague | beewoolie-afk: didn't mean to sound so harsh |
| 20:13.01 | prpplague | beewoolie-afk: hehe, you still get an lnode80 if you want one |
| 20:13.25 | beewoolie-afk | prpplague: NP. No offense taken. |
| 20:13.29 | beewoolie-afk | And yeah, I'd like one. |
| 20:13.47 | beewoolie-afk | It means I can test on another target. |
| 20:15.10 | prpplague | beewoolie-afk: the entire main board is just a little bigger than a 802.11b CF card |
| 20:15.29 | beewoolie-afk | Nice. |
| 20:16.35 | prpplague | beewoolie-afk: has two leds, reset button, 2x7 jtag header, mmc/sd slot, onboard regulator, 4MB flash, 16MB ram, all with .1" headers |
| 20:17.09 | beewoolie-afk | What about that MMC code you were going to send my way? |
| 20:17.29 | prpplague | beewoolie-afk: thought i did already |
| 20:17.36 | beewoolie-afk | Let me check again... |
| 20:18.32 | prpplague | i show i sent it, right before i sent the first round of s3c2410 patches for apex |
| 20:18.43 | prpplague | i think that might have been when you had some email server issue |
| 20:18.47 | prpplague | i'll resend |
| 20:18.55 | beewoolie-afk | prpplague: That could be. |
| 20:19.03 | beewoolie-afk | Last I have is that you wanted to wait. |
| 20:20.42 | prpplague | ahh |
| 20:21.03 | prpplague | i'll resend it |
| 20:21.14 | prpplague | its still pretty ugly but you can get a feel for it |
| 20:21.26 | beewoolie-afk | I just want to see something that works. |
| 20:21.27 | prpplague | its a nasty hack right now |
| 20:21.41 | beewoolie-afk | I spend some time trying to get the ID phase working and never succeeded. |
| 20:28.21 | [g2] | hey beewoolie-afk ! |
| 20:28.33 | beewoolie-afk | [g2]: yo |
| 20:29.25 | [g2] | happy holidays beewoolie-afk |
| 20:29.36 | beewoolie-afk | Likewise. |
| 20:29.40 | [g2] | thx |
| 20:29.51 | beewoolie-afk | How's the fam? |
| 20:30.02 | [g2] | fine thx |
| 20:30.22 | [g2] | I hope you and yours are well too |
| 20:30.48 | beewoolie-afk | Whenever I say that I've been on chat, doll face asks if I've talked to you, [g2]. |
| 20:31.00 | [g2] | heh |
| 20:31.22 | [g2] | I hope doll face it well too |
| 20:31.26 | beewoolie-afk | Indeed. |
| 20:31.46 | beewoolie-afk | She's become a fan of the TV show Lost. |
| 20:32.21 | [g2] | I haven't seen that one |
| 20:32.37 | prpplague | beewoolie-afk: interesting show |
| 20:33.14 | beewoolie-afk | Reminds me of Twin Peaks. spooky at first and then evolves into something seriously wierd. |
| 20:33.58 | [g2] | I missed that one too |
| 20:34.15 | vmaster | took me some time to get into lost, but then i started missing it after the season ended |
| 20:34.20 | [g2] | beewoolie-afk before I forget there some new hw will be playing with |
| 20:34.44 | beewoolie-afk | [g2]: What |
| 20:34.50 | beewoolie-afk | [g2]: what's up? |
| 20:34.54 | [g2] | www.glomationinc.com |
| 20:35.00 | [g2] | 9312-sx |
| 20:35.08 | [g2] | I've got a hw sponsor |
| 20:35.17 | [g2] | we'll be getting 5 boards to begin with |
| 20:35.20 | lennert | wheee |
| 20:35.28 | beewoolie-afk | [g2]: my head is spinning. |
| 20:35.42 | [g2] | glomation isn't the sponsor |
| 20:35.52 | beewoolie-afk | [g2]: now it's really spinning. |
| 20:35.58 | [g2] | heh |
| 20:36.48 | [g2] | lennert dyoung-away rwhitby me dwery are in the first pass |
| 20:37.22 | [g2] | If the boards look good I can probably get some more (I'm sure you'd qualify if you wanted one :) |
| 20:37.28 | beewoolie-afk | I do. |
| 20:37.41 | [g2] | well we have to see how the boards look |
| 20:37.48 | beewoolie-afk | I like the slugs, but the lack of RAM is causing some grief. |
| 20:38.04 | [g2] | The Loft's have 64MB :) |
| 20:38.06 | beewoolie-afk | I've been unable to get them stable with more than file sharing. |
| 20:38.15 | [g2] | I've got a 128 and 256MB sample too |
| 20:38.21 | beewoolie-afk | [g2]: I was hoping for one of those but for some reason... |
| 20:38.33 | beewoolie-afk | My slug crashes when I added NTP. |
| 20:38.55 | [g2] | hmmm odd, I've run NTP for a long time |
| 20:39.00 | beewoolie-afk | I know. |
| 20:39.12 | [g2] | You'll have to let me know your setup |
| 20:39.13 | beewoolie-afk | It doesn't crash right away, but it does so reliably. |
| 20:39.22 | [g2] | do you do DHCP ? |
| 20:39.26 | beewoolie-afk | I need to upgrade the kernel. |
| 20:39.27 | [g2] | with Debian ? |
| 20:39.34 | beewoolie-afk | Debian, but older kernel. |
| 20:39.36 | beewoolie-afk | No dhcp. |
| 20:39.46 | beewoolie-afk | I need modules that the package feed doesn't supply. |
| 20:39.55 | beewoolie-afk | I've been doing other things so I haven't had time to build a newer kernel. |
| 20:39.57 | [g2] | Ok... I was seeing an issue with the dhcpclient after like 12-14 hours |
| 20:40.12 | beewoolie-afk | Not good either. |
| 20:40.27 | [g2] | it's with the IAL driver |
| 20:40.31 | [g2] | IAL/CSR |
| 20:40.36 | [g2] | it's not that bad actually |
| 20:41.10 | beewoolie-afk | I expect more. |
| 20:41.17 | [g2] | I haven't tried with the latest versions of the drivers |
| 20:41.27 | lennert | beewoolie-afk: is your ram buggered? |
| 20:41.30 | [g2] | and it only lock up the ethernet on that port |
| 20:41.38 | lennert | beewoolie-afk: my slug's ram is buggered |
| 20:41.49 | beewoolie-afk | lennert: I don't think so. It runs fine for weeks without NTP. |
| 20:41.57 | lennert | mine too |
| 20:42.00 | beewoolie-afk | I've been writing a lot of data and never had a glitch. |
| 20:42.01 | [g2] | lennert what's up with your RAM ? |
| 20:42.02 | lennert | mine runs fine for weeks |
| 20:42.13 | lennert | but if i untar a kernel tarball, i get bzip2 corruption errors |
| 20:42.13 | beewoolie-afk | I gues we need a ram test? |
| 20:42.16 | lennert | yeah |
| 20:42.25 | beewoolie-afk | I don't see anything like that. |
| 20:42.32 | beewoolie-afk | I unpack lots of packages. |
| 20:42.40 | lennert | okay, it's probably okay then |
| 20:42.46 | beewoolie-afk | I'll try a kernel tarball just for kicks. |
| 20:43.22 | [g2] | lennert are you still playing with the slug ? |
| 20:45.45 | [g2] | beewoolie-afk BTW lennert gave me some code to test the speed of the GPIO and it looks like we could bit bang JTAG pretty fast from a Loft |
| 20:46.04 | beewoolie-afk | Interesting. |
| 20:46.10 | beewoolie-afk | Faster than USB dongle trick? |
| 20:46.35 | [g2] | Well writing is at 11M/s |
| 20:46.46 | beewoolie-afk | Holymackerel! |
| 20:46.47 | [g2] | so on writes we could toggle around 4.5M |
| 20:47.01 | [g2] | M/s |
| 20:47.14 | beewoolie-afk | IIRC, that's about the same speed as the USB device. |
| 20:47.22 | lennert | [g2]: i don't play with my slug as much as i should.. as it's kind of buggered |
| 20:47.23 | beewoolie-afk | Only advantage of USB would be overall cost. |
| 20:47.31 | lennert | [g2]: it kind of sucks that my last slug also had buggered memory :( |
| 20:47.47 | vmaster | beewoolie-afk: the ft2232c has a tck maximum of 6mhz, but effectively you wont get more than 1-2mhz |
| 20:47.56 | lennert | [g2]: i'd be happy to send it to someone who can do something else with it |
| 20:48.09 | [g2] | maybe dyoung-away |
| 20:48.26 | beewoolie-afk | vmaster: I thought that it could write the scan chain that fast, ~5MHz. |
| 20:48.40 | [g2] | vmaster also pointed out that the phillps can bit bang around 15M |
| 20:48.40 | beewoolie-afk | vmaster: are you talking about the scan-chain delay? |
| 20:49.04 | vmaster | beewoolie-afk: i'm talking about real-life debugging of arm7 and arm9 cores |
| 20:49.17 | vmaster | beewoolie-afk: at some point, you're waiting for the results |
| 20:49.48 | beewoolie-afk | vmaster: I was just asking about an equivalent comparison. |
| 20:50.29 | vmaster | beewoolie-afk: hmm? |
| 20:50.31 | beewoolie-afk | vmaster: if the scan chain clock is XMhz on one and YMHz on another, doesn't that give similar results? Or are you adding in a latency for the USB transfer? |
| 20:50.57 | vmaster | beewoolie-afk: yes, it's mostly latency |
| 20:51.25 | beewoolie-afk | Hmm. |
| 20:51.57 | beewoolie-afk | Seems like we still haven't found the right combination of inexpensive hardware and efficient (very fast) operation. |
| 20:52.16 | vmaster | beewoolie-afk: i've heard from olimex that they're working on atmel sam7 based jtag device |
| 20:52.24 | beewoolie-afk | [g2]: Also, doesn't the IEEE standard limit the clock speed to about 8MHz? |
| 20:52.46 | vmaster | beewoolie-afk: no, the standards places no limits at all |
| 20:53.01 | vmaster | beewoolie-afk: individual devices specify minimum high-low times for the tck |
| 20:53.05 | [g2] | beewoolie-afk dunno, I here the IXP42x's max out around 10M |
| 20:53.22 | beewoolie-afk | vmaster: ah, good. |
| 20:54.53 | vmaster | the at91rm9200 specifies a minimum tck period of 20ns |
| 20:54.59 | vmaster | that would be 50mhz jtagging |
| 20:55.10 | [g2] | that'd be fun :) |
| 20:55.24 | beewoolie-afk | vmaster: So it would be nice if we could get something capable of that sort of speed. |
| 20:55.36 | [g2] | lennert do you know voltage ouput levels for the S3 I/O pins ? |
| 20:55.51 | beewoolie-afk | Which is why, IIRC, we were looking into the sparton. |
| 20:56.12 | lennert | [g2]: 3.3V ? |
| 20:56.19 | ka6sox-office | 3.3v |
| 20:56.22 | ka6sox-office | max |
| 20:56.25 | [g2] | hey |
| 20:56.28 | [g2] | hey ka6sox-office |
| 20:56.32 | ka6sox-office | heya |
| 20:56.46 | lennert | [g2]: the pins are 5V tolerant though, i think |
| 20:56.57 | ka6sox-office | sorta here...just trying to unbury myself from all this paperwork that has been piling up in my absense |
| 20:56.58 | [g2] | Ok.. so Digilent has these flying lead connectors for < $5 |
| 20:57.08 | ka6sox-office | yep |
| 20:57.15 | ka6sox-office | I use flying lead. |
| 20:57.21 | [g2] | They plug right into the board |
| 20:57.46 | [g2] | I think we could plug from the S3 I/O pins straight into the Loft with the S3 board |
| 20:58.00 | [g2] | and 6 or 12 leads would do the trick |
| 20:58.13 | vmaster | heh, 50mhz with flying leads? |
| 20:58.25 | [g2] | vmaster I was thinking 10M |
| 20:58.26 | lennert | impedance... |
| 20:58.56 | vmaster | arm's realview tools use differential signaling down to the target connector |
| 20:59.01 | vmaster | iirc |
| 21:00.01 | [g2] | lennert what about impedance |
| 21:00.34 | lennert | 50mhz can be problematic if you don't use impedance matched stuff |
| 21:00.58 | [g2] | Oh sure, but what about 5-10Mhz |
| 21:01.17 | vmaster | the cable is critical at that speed |
| 21:01.26 | vmaster | i've had problems with cable-length at 6mhz |
| 21:01.49 | [g2] | vmaster how long a cable are we talking ? |
| 21:02.00 | vmaster | [g2]: 20cm caused problems, <10cm worked fine |
| 21:02.13 | vmaster | that was the standard arm layout, e.g. a gnd between every signal |
| 21:02.54 | vmaster | on the lpc mailing list, people report problems even at wiggler speed |
| 21:03.38 | vmaster | bdi comes with ~10cm cable |
| 21:03.50 | [g2] | 10cm is like 3.9 Inches right ? |
| 21:04.03 | vmaster | yeah |
| 21:06.58 | [g2] | one of the problems with the impedeance mismatch is the relfection of the signal back down the line right ? |
| 21:07.13 | lennert | yeah |
| 21:09.57 | vmaster | anyway, this can be solved |
| 21:10.04 | vmaster | but first we need to achieve that speed |
| 21:10.09 | [g2] | lennert do you know offhand how much power the S3 draws ? |
| 21:10.25 | lennert | kind of depends what you do with it :) |
| 21:11.07 | lennert | there is a power analyser with in the xilinx webpack |
| 21:12.58 | [g2] | I'm wondering if put an S3 right on top (or .5/1 inch) away and powered it from the board |
| 21:13.19 | beewoolie-afk | lennert: BTW, no problems with untar of kernel. I wish that that had been the case. |
| 21:13.27 | [g2] | And then talked some other protocol off S3 |
| 21:14.05 | vmaster | beewoolie-afk: you wished your device had broken ram? ;) |
| 21:14.05 | lennert | beewoolie-afk: i can't even complete "bunzip2 < linux-2.6.14.tar.bz2 > /dev/null" successfully once |
| 21:14.05 | beewoolie-afk | vmaster: yeah. That would have explained my problems. :-) |
| 21:14.30 | [g2] | beewoolie-afk you are probably no aware of jacques work lately |
| 21:14.37 | [g2] | s/no/not |
| 21:14.40 | beewoolie-afk | [g2]: hit me |
| 21:14.57 | [g2] | I think he was running debian arm in QEMU |
| 21:15.06 | beewoolie-afk | I read about thay. |
| 21:15.18 | [g2] | and his perl tests ran faster than a 266Mhz slug |
| 21:15.23 | beewoolie-afk | I saw a thread about building packages that way. |
| 21:15.35 | beewoolie-afk | Kinda sweet. |
| 21:16.11 | [g2] | I think that means the 95% of all program synchronuous problems can be resolved in the emulator if reproducable |
| 21:16.53 | beewoolie-afk | Hmm. Depends on what type of problem. I thought that most of our troubles have been with the IAL and the NPEs. |
| 21:17.22 | [g2] | I think there's only 1 outstanding issue there |
| 21:17.28 | [g2] | the one I mentioned earlier |
| 21:17.38 | [g2] | other than just general Open Source issues |
| 21:17.55 | lennert | i think those are being worked on |
| 21:18.03 | beewoolie-afk | I haven't been aware of many (if any) ARM specific issues. In fact, that has been discussed on the Debian lists. |
| 21:18.03 | [g2] | The glomation board is _fully_ open from my understanding |
| 21:18.14 | beewoolie-afk | Most of the arch issues are really issues with *all* arches. |
| 21:18.24 | beewoolie-afk | Which CPU is glomation using? |
| 21:18.32 | [g2] | Cirrus 93xx |
| 21:18.50 | beewoolie-afk | I think I got a link about that... |
| 21:19.05 | [g2] | ARM 920 based with a hw FP instructions |
| 21:19.20 | beewoolie-afk | Yep. My stepdad asked about this. |
| 21:19.25 | beewoolie-afk | Nice. |
| 21:19.53 | beewoolie-afk | He wondered if it wouldn't be adequate for his needs. They have some reasonably priced boards. |
| 21:20.22 | [g2] | how the ethernet support in APEX going ? |
| 21:20.48 | beewoolie-afk | [g2]: I've got support for the SMC chip and the Sharp MAC. |
| 21:21.05 | beewoolie-afk | The IAL isn't happening because it's such a load of work *and* because of the licensing. |
| 21:21.24 | [g2] | I mean for the glomation board :) |
| 21:21.37 | lennert | beewoolie-afk: there is a copy of the IAL available under the GPL and/or BSD, i've heard |
| 21:21.38 | beewoolie-afk | I was thinking of buying one of the glomation boards so that I could implement support for the cs8900. |
| 21:21.59 | beewoolie-afk | lennert: DOH! really? Does it work in the kernel? |
| 21:22.12 | lennert | beewoolie-afk: see netdev@vger.kernel.org archives of today |
| 21:22.18 | lennert | beewoolie-afk: some guy wants to clean it up and integrate it |
| 21:22.25 | beewoolie-afk | That would rock! |
| 21:22.36 | lennert | beewoolie-afk: still a bunch of work though, as you said |
| 21:22.56 | beewoolie-afk | The licensing is the worst part. Once it's open, we can do the work once. |
| 21:23.34 | [g2] | lennert knows all the juicey stuff :) |
| 21:24.23 | lennert | [g2]: i'm on all the interesting mailing lists :) |
| 21:24.32 | [g2] | it is kinda cool that the slug has 3 cores on it and the loft had 4 cores really |
| 21:24.50 | [g2] | lennert it's that you actuallly _read_ the ml's :) |
| 21:26.52 | beewoolie-afk | lennert: You know, I saw your post about putting it in the kernel and I didn't believe it. |
| 21:27.10 | beewoolie-afk | I thought that I was hallucinating about IAL code going into the kernel. |
| 21:27.17 | lennert | beewoolie-afk: hehe |
| 21:27.32 | lennert | beewoolie-afk: well, the IAL code is kind of.. how to say.. |
| 21:27.40 | beewoolie-afk | DON'T! |
| 21:27.40 | lennert | beewoolie-afk: 'not up to the standards' |
| 21:27.45 | beewoolie-afk | EEK! |
| 21:27.47 | lennert | oops, sorry, too late |
| 21:27.58 | beewoolie-afk | The secret has been revealed. |
| 21:28.13 | lennert | well |
| 21:28.15 | beewoolie-afk | I'll take another look. Do I just download from the normal place at intel? |
| 21:28.20 | lennert | i don't think it was a well-kept secret |
| 21:28.26 | beewoolie-afk | STOP! |
| 21:28.27 | lennert | not sure, i've not looked into it for a while |
| 21:28.37 | beewoolie-afk | What version are you looking at? |
| 21:28.45 | beewoolie-afk | Or, are they looking at? |
| 21:28.51 | lennert | not sure |
| 21:28.53 | lennert | it should be in the thread |
| 21:29.34 | beewoolie-afk | He just says that he 'has a version'. |
| 21:29.43 | lennert | one guy 'has a version' under BSD |
| 21:29.55 | beewoolie-afk | Perhaps I should wait until he posts apatch. |
| 21:30.02 | lennert | the other guy says that there's a downloadable version on the intel site that is eCos-GPL licensed, and gives a link (iirc) |
| 21:31.07 | [g2] | I'm looking on lkml ? what's the date ? |
| 21:31.13 | lennert | [g2]: netdev |
| 21:31.22 | beewoolie-afk | I've been looking at the netdev archive in MARC. |
| 21:32.04 | [g2] | that'll make a big difference :) |
| 21:32.09 | [g2] | thx guyx |
| 21:32.14 | lennert | http://marc.theaimsgroup.com/?t=113516654600005&r=1&w=2 |
| 21:32.25 | lennert | http://marc.theaimsgroup.com/?l=linux-netdev&m=113524802815054&w=2 says: |
| 21:32.30 | lennert | FWIW, the parts of the IXP400 Access Library relevant to ethernet |
| 21:32.30 | lennert | (except the microcode which could be made into a binary blob for loading |
| 21:32.30 | lennert | by the firmware loader) are available (from Intel) under the eCos |
| 21:32.30 | lennert | variant of the GPL. |
| 21:32.31 | lennert | --- |
| 21:32.35 | lennert | but he didn't give a link |
| 21:33.14 | [g2] | I had heard that Intel was going to do that |
| 21:33.52 | [g2] | but it would be great if that was really true |
| 21:38.57 | lennert | okay, help me out.. fluke 112 or fluke 177? :) |
| 21:40.19 | [g2] | I'm not much help there |
| 21:40.52 | beewoolie-afk | lennert: 177 |
| 21:41.12 | beewoolie-afk | lennert: Actually, I bought the 179 |
| 21:41.23 | beewoolie-afk | One of the best tools I have. |
| 21:41.25 | lennert | beewoolie-afk: why the 177? |
| 21:42.12 | lennert | 177 is E70 more.. for 0.09% accuracy instead of 0.7%, 50Mohm instead of 40, 100kHz instead of 50, and lifetime warranty |
| 21:43.09 | beewoolie-afk | The data sheet shows the accuracy being thesame. |
| 21:43.13 | beewoolie-afk | I got a temp probe. |
| 21:43.24 | lennert | sorry, i mean, the difference between the 177 and the 112 |
| 21:43.34 | beewoolie-afk | http://www.fluke.com/Download/DigitalMultimeters/2155a.pdf |
| 21:43.37 | lennert | the 179 has a temperature probe while the 177 hasn't |
| 21:43.43 | lennert | accuracy of the 177 and 179 is the same |
| 21:43.48 | beewoolie-afk | Oh. I don'tknow the 112. |
| 21:43.51 | beewoolie-afk | let me see... |
| 21:43.51 | lennert | the 112 has 0.7% accuracy, the 177 has 0.09% |
| 21:44.11 | lennert | i'm trying to convince my wife as well as myself.. |
| 21:44.22 | lennert | my wife is already convinced, i think, i just need to convince myself.. :) |
| 21:45.44 | beewoolie-afk | The 17x series has hold measurement features. I use them more than I thought I would. |
| 21:45.52 | lennert | ah |
| 21:46.22 | beewoolie-afk | Also MIN MAX AVG. |
| 21:46.32 | lennert | right |
| 21:46.35 | lennert | that sounds useful |
| 21:47.04 | beewoolie-afk | What does the wife say? |
| 21:47.15 | lennert | they all look good :) |
| 21:47.26 | beewoolie-afk | BTW, backlight is really important, too. Both have it. |
| 21:47.26 | lennert | and i must say i agree |
| 21:48.19 | beewoolie-afk | If I were at a company and I was buying 100 units and I didn't think we needed HOLD,then I'd probably buy the 112. For me, I hang onto these things for a long time. |
| 21:48.39 | beewoolie-afk | $US80 is nothing compared to frustration of not having it when I need it. |
| 21:48.47 | lennert | yeah |
| 21:49.02 | lennert | they sell DMMs for as low as E5 here |
| 21:49.08 | lennert | but i really want something proper |
| 21:49.23 | beewoolie-afk | I have bought one ofthe cheaper models to do something on my car |
| 21:49.38 | beewoolie-afk | I was really disappointed because it wasn't as well designed. |
| 21:49.52 | beewoolie-afk | It had the features on the checklist, but it didn't feel good to use it. |
| 21:50.11 | lennert | something that's E5 must really be crap |
| 21:50.13 | beewoolie-afk | I needed a clamp ammeter. |
| 21:50.33 | beewoolie-afk | Depends on what you need. Are you just checking that power outlets are live? |
| 21:50.41 | beewoolie-afk | Then E5 is great. |
| 21:51.08 | lennert | E4,50 is the cheapest one on conrad.nl |
| 21:51.43 | lennert | well, no, for power outlets i have a screwdriver with a tiny little lamp in it |
| 21:51.58 | lennert | which was like E0,50 :) |
| 21:52.34 | beewoolie-afk | What about this? |
| 21:52.36 | beewoolie-afk | http://www1.nl2.conrad.com/scripts/wgate/zcop_nl2/~flN0YXRlPTE4MTUyODkxMzU=?~template=PCAT_AREA_S_BROWSE&glb_user_js=Y&shop=NL2&p_init_ipc=X&~cookies=1 |
| 21:52.56 | lennert | oooh |
| 21:53.00 | lennert | scopemeter |
| 21:53.06 | lennert | 2.5GS/s |
| 21:53.07 | lennert | yummy |
| 21:53.22 | beewoolie-afk | Hmm. It doesn't say that...I think. |
| 21:53.39 | lennert | fluke 199[BC] -- maximum real-time sample rate: 2.5GS/s |
| 21:53.48 | beewoolie-afk | I really would like a good scope-meter, but my specs put me *way* out of a reasonable price range. |
| 21:54.03 | lennert | actually, how about this: |
| 21:54.05 | lennert | http://www.fluke.be/comx/show_product.aspx?pid=300&locale=nlnl&product=SCM |
| 21:54.07 | beewoolie-afk | Which gives you almost 1GHz. |
| 21:54.22 | lennert | that gives you 'everything' |
| 21:54.28 | lennert | for a mere E1864 |
| 21:54.33 | lennert | ahem |
| 21:54.46 | beewoolie-afk | Yeah. and I would onlybuy onethat had 4 channels. |
| 21:55.03 | lennert | you need at least 32 channels |
| 21:55.08 | lennert | 64 is better |
| 21:55.15 | beewoolie-afk | I thought that I was unreasonable. |
| 21:55.19 | lennert | lol |
| 21:56.16 | lennert | well, sometimes you simply _need_ to be able to sample all the pins on your PCI bus at 1Ghz |
| 21:56.46 | lennert | the 199C/S is only E4460 anyway =p |
| 21:57.24 | beewoolie-afk | *cough* |
| 21:57.28 | lennert | should we start a class action suit against fluke for making too many nice devices that we can't afford, making us depressed? |
| 21:57.45 | beewoolie-afk | I'll sign. |
| 21:58.21 | [g2] | hey we need to get on there beta testing program :) |
| 21:58.30 | lennert | i have a long list of other manufacturers to sue, then.. |
| 21:58.48 | lennert | national semiconductor because of their 2GS/s ADCs, for example |
| 21:59.00 | lennert | (actually, 1.5GS/s) |
| 21:59.34 | lennert | [g2]: you're good at getting hardware, so please get us signed up :) |
| 21:59.57 | [g2] | lennert one vendor at at time :) |
| 22:00.07 | lennert | hmmm ok :) |
| 22:00.18 | [g2] | I see no real reason you guys shouldn't have _lots_ of cool hw |
| 22:00.20 | lennert | i'm crap at getting hardware |
| 22:00.31 | beewoolie-afk | hear hear |
| 22:00.33 | lennert | ajeco were going to send me a board.. then they didn't |
| 22:00.40 | lennert | ADI were going to send me a board.. then they didn't |
| 22:00.47 | lennert | atmel were going to send me a board.. then they didn't |
| 22:01.02 | beewoolie-afk | dood. You must be depressed. |
| 22:01.19 | beewoolie-afk | ~praise lennert |
| 22:01.20 | purl | All hail lennert! |
| 22:01.20 | lennert | depressed enough to almost sue fluke |
| 22:02.54 | lennert | having accepted the sad reality of my existance, i think i'll go and get a fluke 179 |
| 22:04.26 | beewoolie-afk | :-) |
| 22:44.04 | lennert | [g2]: what freq does the A/D and D/A converter on the glomation board run at? |
| 22:45.46 | lennert | ok, the ADC at 3.75kHz |
| 22:47.34 | lennert | hmm |
| 22:47.40 | lennert | you can make a poor man's scope out of that |
| 22:47.45 | lennert | well |
| 22:47.50 | lennert | make that a broke man's scope |
| 22:57.35 | ka6sox-office | broke...broke...did somebody call my name? |
| 22:58.22 | lennert | ka6sox-office: at least you have nice toys :) |
| 22:59.54 | ka6sox-office | I'm a poor homeowner. |
| 23:00.15 | lennert | at least not a poor lonesome cowboy a long long way from home |
| 23:00.20 | ka6sox-office | I owe the Bank $200K! |
| 23:00.22 | ka6sox-office | yep |
| 23:00.40 | lennert | only $200k |
| 23:00.45 | lennert | hmm |
| 23:02.08 | lennert | that's a whole lot of fluke kit |
| 23:05.18 | beewoolie-afk | lennert: I'm suspicious about the IAL stuff. The license appears to be the same as always. |
| 23:05.42 | beewoolie-afk | lennert: there is a component of it that has been GPLd, an adapter component for the kernel. |
| 23:05.54 | beewoolie-afk | The library itself seems to be the same ol' thing. |
| 23:06.18 | beewoolie-afk | ka6sox-office: I think I owe more than that. |
| 23:06.28 | beewoolie-afk | ka6sox-office: and I got a good deal. |
| 23:06.50 | ka6sox-office | we got a great deal here....the others in the same area are going for 4X what we paid |
| 23:06.50 | lennert | beewoolie-afk: so maybe post on netdev? |
| 23:07.25 | beewoolie-afk | All I can say at the moment is that I'm suspicious. I'm going to review the files a bit later. It turns out that I had the latest files already. |
| 23:10.55 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
| 23:18.07 | lennert | beewoolie-afk: might be that mr. Vrabel just misunderstood |
| 23:20.49 | lennert | i've asked VIA for the datasheet for the VT8235 datasheet on my EPIA board |
| 23:23.07 | lennert | actually, googling for vt8235.pdf works too ;) |
| 23:45.10 | lennert | they keep talking about PMIO in the datasheet -- what's that? |
| 23:45.49 | *** join/#openjtag nslu2-log (n=nslu2-lo@nslu2-linux/dyoung) |
| 23:49.59 | *** join/#openjtag ulf_k__ (n=ulf_kypk@p54BD8F8F.dip0.t-ipconnect.de) |
| 23:50.55 | lennert | Power Management I/O |
| 23:51.01 | lennert | now how to access them.. |
| 23:51.42 | lennert | oh |
| 23:51.46 | lennert | it's a non-PCI address range |
| 23:51.53 | lennert | you have to map it in by poking into the southbridge |
| 23:51.57 | lennert | ugly |
| 23:54.57 | lennert | BIOS puts it at 0x400 (I/O space) by default |
| 23:55.00 | lennert | from there you can access the GPIOs |
| 23:55.49 | vmaster | heh, what do you want to use your epia's gpios for? |
| 23:56.24 | lennert | what do you think ;) |
| 23:56.33 | vmaster | noooooooo |
| 23:56.39 | vmaster | not bitbanging |
| 23:56.40 | vmaster | please ;) |
| 23:56.43 | lennert | hey, the board is only $99 ;) |
| 23:56.47 | ka6sox-office | he he |
| 23:56.56 | ka6sox-office | bit banging...MMMMMMMMM |
| 23:57.20 | lennert | bang bang bang |
| 23:57.54 | lennert | bitbanging is fun ;) |
| 23:58.40 | vmaster | there should be laws against that kind of thing |
| 23:58.46 | lennert | agreed |
| 23:58.56 | lennert | there should be an fpga in every southbridge |
| 23:59.01 | vmaster | hehehe, yeah |