| 00:00.24 | *** join/#openjtag dwery (n=dwery@nslu2-linux/dwery) |
| 00:04.44 | *** join/#openjtag ulf_k_ (n=ulf_kypk@p54BD9B52.dip0.t-ipconnect.de) |
| 00:50.45 | ka6sox-office | how many here are on the xilinx s3e board w/l? |
| 00:52.36 | [g2] | not me, but it's interesting |
| 01:10.06 | ka6sox-office | yes it is. |
| 01:10.26 | ka6sox-office | I want to use the interface that ep1220 has designed for I/O |
| 01:11.19 | *** join/#openjtag vmaster_ (i=vmaster@p549B5452.dip.t-dialin.net) |
| 01:11.36 | ka6sox-office | vmaster: is your code available? |
| 04:04.00 | *** part/#openjtag rwhitby (n=c058a223@nslu2-linux/rwhitby) |
| 06:23.09 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
| 09:17.32 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
| 09:19.40 | vmaster_ | ka6sox: you mean my openocd? sure |
| 09:19.57 | ka6sox | :) |
| 09:20.20 | vmaster | openocd.berlios.de |
| 09:21.37 | ka6sox | thanks! |
| 10:50.06 | *** join/#openjtag bullet (n=bullet@138.218.62.81.cust.bluewin.ch) |
| 12:44.31 | *** join/#openjtag prpplague (n=billybob@72.22.152.142) |
| 20:51.25 | *** join/#openjtag dwery (n=dwery@nslu2-linux/dwery) |
| 21:14.07 | *** join/#openjtag beewoolie-afk (n=beewooli@206.124.142.26) |
| 21:14.45 | beewoolie-afk | doodz |
| 21:15.35 | ka6sox-office | yo |
| 21:15.36 | lennert | d00dz |
| 21:15.41 | lennert | wh4t'5 up |
| 21:15.43 | lennert | y0 |
| 21:16.01 | beewoolie | I've been reading about BSDL and such. |
| 21:16.15 | beewoolie | I've written a parser for bsdl that works, but I'm sad to realize that it is of littl euse. |
| 21:16.39 | beewoolie | It is handy, tho, for getting IDCODES for different CPUs. |
| 21:18.13 | ka6sox-office | the latest word on the website is february now for the S3e |
| 21:18.33 | lennert | BSDL, well.. i mostly just read BSDL myself |
| 21:18.52 | ka6sox-office | is that like reading sanskrit? |
| 21:19.19 | beewoolie | sanskrit is harder because it isn't machine parseable. |
| 21:21.05 | ka6sox-office | :) |
| 21:27.55 | lennert | lithuanian is in the same family as sanskrit, apparently |
| 21:28.20 | ka6sox-office | interesting |
| 21:34.03 | ka6sox-office | http://direct.xilinx.com/bvdocs/appnotes/xapp476.pdf <<< BSDL file information for S3 |
| 21:37.24 | beewoolie | Access to their bsdl files requires a login and I'm feeling lazy. |
| 21:37.45 | ka6sox-office | I think that lennert might have some of them. |
| 21:39.27 | beewoolie | I have plenty to work on in the mean time. It looks like no one uses the boundary scan for debug or flash programming. Instead, there are alternative interfaces on each core to make things more efficient. |
| 21:40.02 | vmaster | what cores are you talking about? |
| 21:40.18 | beewoolie | So far, the arm7/9 and the xscale. |
| 21:40.51 | beewoolie | You've used the ixp stuff, so you know what I'm talking about. |
| 21:41.27 | vmaster | mhh, i have only arm7/arm9s |
| 21:41.37 | vmaster | but of course, you're right |
| 21:41.59 | beewoolie | Really? I thought that you were loading programs into the xscale icache. |
| 21:42.13 | vmaster | ep1220 did, iirc |
| 21:42.19 | beewoolie | Ah. |
| 21:43.09 | vmaster | if you're interested in arm7/9 debugging have a look at openocd.berlios.de ;) |
| 21:43.20 | beewoolie | k. |
| 21:44.21 | beewoolie | Is that your project? |
| 21:44.38 | vmaster | yeah |
| 21:45.42 | beewoolie | Cool. I'll take a whack at it when I get the 2232 running. |
| 21:47.06 | beewoolie | I received confirmation that the parts have shipped. |
| 21:47.44 | beewoolie | vmaster: btw, what parts do you have? I'm wondering about the specific manufacturer's part numbers. |
| 21:49.19 | vmaster | mhh, i had someone build the device for me, i'm not so much a hardware guy |
| 21:49.34 | beewoolie | I mean, what CPUs are you using to test the JTAG software. |
| 21:49.43 | vmaster | ah |
| 21:49.58 | vmaster | a philips lpc2294, a atmel at91rm9200 and a hynix hms30c7202 |
| 21:50.07 | beewoolie | K. thanks. |
| 21:50.11 | vmaster | arm7tdmi-s, arm920t and arm720t |
| 22:12.42 | lennert | the bsdl files come with ise, and i have a copy of ise 7.1i |
| 22:13.06 | lennert | i can tar up all the bsdl files i have? |
| 22:13.58 | beewoolie | lennert: I'dd appreciate whatever you can make available. |
| 22:14.22 | lennert | ok, hang on |
| 22:14.41 | beewoolie | The BSDL parser makes it easy to add/recognize a part from the JTAG idcode |
| 22:14.58 | beewoolie | Drag and drop. |
| 22:16.03 | lennert | yeah, that's a plus |
| 22:16.25 | lennert | it would be nice to have a database of (idcode, IR length, max TCK rate) parameters somewhere |
| 22:16.49 | lennert | as you can't really 'ignore' an unknown device in a scan chain if you don't have at least the IR length |
| 22:17.20 | vmaster | figuring ir length out is easy |
| 22:18.11 | vmaster | bits [1:0] have to be b01 |
| 22:18.39 | lennert | but the other bits can be b01 too :) |
| 22:19.07 | vmaster | mhh... trying to remember what that algorithm looked like |
| 22:19.27 | lennert | are you confusing with determining the length of the scan chain, maybe? |
| 22:19.37 | vmaster | mhh... maybe |
| 22:20.02 | lennert | all IDCODEs are 32 bits but it's easy to spot an invalid IDCODE |
| 22:20.11 | lennert | so you can determine the number of devices in the chian |
| 22:20.25 | lennert | but the IR length of an unknown device.. well, i don't know an algorithm for that |
| 22:20.38 | lennert | beewoolie: http://www.wantstofly.org/~buytenh/ise_7.1i_bsdl.tar.bz2 |
| 22:21.53 | lennert | 1225 bsdl files for your parsing pleasure |
| 22:21.56 | beewoolie | lennert: AFAICT, there isn't a way to guess the length of the instruction register. |
| 22:22.07 | beewoolie | ~praise lennert |
| 22:22.10 | purl | All hail lennert! |
| 22:22.10 | qbot | All Hail lennert! |
| 22:22.24 | ka6sox-office | ~lart ka6sox-office |
| 22:22.34 | lennert | lol |
| 22:22.40 | beewoolie | rotfl |
| 22:24.26 | beewoolie | Hey, a new bit type. |
| 22:24.42 | lennert | bit type? |
| 22:24.56 | beewoolie | yeah, I'd not seen a 'buffer bit'. |
| 22:28.23 | [g2] | anyone got an md5/sha1 on that bsdl tarball ? |
| 22:29.23 | lennert | md5: 72e56f861f09e9ea97c5980a2ee5d82f |
| 22:29.31 | lennert | sha1: 33db0a1ec606b506efc90ca4c6385f530a60b181 |
| 22:30.10 | [g2] | thx |
| 22:31.56 | beewoolie | That's what I've got. |
| 22:33.29 | [g2] | me too :) |
| 22:33.34 | lennert | http://www.ipfabrics.com/pdf/Double_Espresso_Datasheet.pdf |
| 22:33.37 | lennert | that would make a nice buildd |
| 22:33.40 | beewoolie | Yeah, yeah. Wise guy. |
| 22:35.25 | beewoolie | lennert: what the heck is that thing for? Cracking crypto? |
| 22:36.09 | lennert | routing and firewalling and stuff |
| 22:36.18 | lennert | but you can of course use it for building debian packages too ;) |
| 22:36.30 | beewoolie | Hmm. that's an idea. How spendy? |
| 22:36.35 | beewoolie | <$300? |
| 22:36.40 | lennert | dunno. i guess around $4k. :) |
| 22:37.22 | beewoolie | With QEMU is it really worth spending that much? |
| 22:37.31 | beewoolie | A fast AMD64 can build a lot of packages. |
| 22:37.33 | lennert | it's certainly not worth spending that much :) |
| 22:37.52 | beewoolie | I wonder if they'll sample one of them... |
| 22:38.04 | lennert | or give me one to port linux 2.6 ;p |
| 22:38.51 | [g2] | hm looks insteresting |
| 22:38.56 | lennert | radisys was kind enough to send me one of their boards |
| 22:57.45 | lennert | okay, and now i'm trying to find the HDLC specs (ISO 3309 and ISO 4335) |
| 22:57.55 | lennert | all these standards keep referencing each other |
| 22:57.58 | lennert | it's like a conspiracy |
| 22:58.25 | lennert | all I.xxx ITU standards reference each other, so you get all I.xxx standards |
| 22:58.39 | lennert | then, the most interesting I.xxx standards reference Q.xxx standards |
| 22:58.54 | lennert | so you get all Q.xxx standards |
| 22:59.06 | lennert | those reference even different ITU standards, plus a bunch of ISO standards |
| 22:59.14 | lennert | now i bet those ISO standards will reference ANSI standards |
| 22:59.21 | lennert | and the ANSI standards will reference ETSI standards |
| 22:59.30 | lennert | and before you now, you're broke and still without the info you need |
| 22:59.39 | lennert | s/now/know/ |
| 23:00.59 | [g2] | lennert did you see that PCI-E DDR RAM disk card ? |
| 23:01.09 | lennert | nope? |
| 23:01.36 | [g2] | http://www.ddrdrive.com |
| 23:02.40 | lennert | is that an fpga? |
| 23:02.49 | [g2] | 8G DDR2 with PCI-E card, bootable and external power supply |
| 23:03.00 | [g2] | I think it's "upgradable" so maybe |
| 23:04.15 | lennert | looks like a nice little board |
| 23:04.35 | lennert | but i'd rather plug that memory in my mobo |
| 23:05.09 | [g2] | I think that 8G card and your ixp2350 PCI-E card you'd have one hell of a exterior BGP routers eh ? |
| 23:06.12 | lennert | for an eBGP router, 1G is more than enough, really :) |
| 23:06.32 | lennert | hang on |
| 23:06.33 | [g2] | only 1 stick then and room for growth :) |
| 23:07.04 | lennert | this router now has 557813 routes.. that's about three times a full internet routing table |
| 23:07.21 | lennert | 'top' shows that the routing protocol daemon (rpd) takes up 180M of memory |
| 23:07.30 | lennert | <PROTECTED> |
| 23:07.31 | lennert | <PROTECTED> |
| 23:07.41 | lennert | this is a juniper M7i |
| 23:11.50 | beewoolie | lennert: I've been able to get some standard from the local university. It's worth a look. |
| 23:12.31 | lennert | i work at the local university :) |
| 23:16.18 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
| 23:17.55 | [g2] | hey beewoolie are you doing any JTAG hacking ? |
| 23:18.08 | beewoolie | [g2]: That's the flavor of the week. |
| 23:18.21 | beewoolie | [g2]: I'm investigating how to do it efficiently. |
| 23:18.39 | beewoolie | I should have a working 2232 board in a week or so. |
| 23:19.20 | [g2] | are you planning on using it for debugging or flashing ? |
| 23:21.03 | beewoolie | Both. I've determined how to make the IXP do some nice debug tricks. The idea would be to create something that can do both. Flash is important, but it isn't the only thing. In fact, I don't use it much any more since APEX works. |
| 23:21.33 | beewoolie | But, getting apex into memory still requires something. JTAG is preferrable if I can make it fast. |
| 23:21.39 | [g2] | are you using the PMU |
| 23:22.21 | lennert | i couldn't get the ixp2000 pmus to work (there are 2 pmus) |
| 23:22.21 | beewoolie | PMU? I've not seen that acronym. |
| 23:22.21 | [g2] | I think it's the PMU performance management unit |
| 23:22.26 | beewoolie | I don't know that one. Sounds like xscale. |
| 23:22.42 | beewoolie | There are special registers in the IXP scan chain that give us good access to the core. |
| 23:23.01 | beewoolie | In fact, the xscale seems to be easier than arm7/9, but I just haven't found the right piece yet. |
| 23:23.08 | [g2] | are you just talking about the normal debug regs ? |
| 23:23.28 | lennert | yeah, PMU is an xscale thing, although the intel PMUs are CHAP type |
| 23:23.42 | beewoolie | I remember that someone, I believe ep1220, has loaded instructions into the Icache. I know how to do this on the xscale. I'm seeing if I can get this functionality on the arm7/9. |
| 23:23.55 | lennert | beewoolie: IXP debug is done easiest by icache access, right? |
| 23:23.56 | lennert | right |
| 23:24.22 | beewoolie | [g2]: There are special registers in the JTAG scan chain that are only accessible from JTAG. Some are accessible internally, too, through the CP15. |
| 23:24.37 | beewoolie | lennert: Icache is super slick and should be efficient. |
| 23:25.06 | beewoolie | It turns out that the arm7/9 cores have a short scan chain for fast access to the data and address busses. |
| 23:25.17 | [g2] | LDIC is for loading the I-cache right ? |
| 23:25.22 | beewoolie | I don't yet know how well this will support debug. |
| 23:25.24 | beewoolie | [g2]: Yeah. |
| 23:25.41 | [g2] | that's what ep1220 got working |
| 23:25.42 | beewoolie | There is the added hassle that we cannot load immediate operands that are larget than 8 bits. |
| 23:25.58 | beewoolie | But, I think I have a way to mitigate that. |
| 23:26.58 | [g2] | are you going to be debugging the slug ? |
| 23:27.27 | beewoolie | xscale is important. |
| 23:28.12 | [g2] | are you thinking ixp or pxa or obth |
| 23:28.29 | beewoolie | The only hassle with starting with xscale is that I have only one with jtag and it's running a file server at the moment. |
| 23:28.48 | beewoolie | [g2]: I don't know if there is much difference from the JTAG POV. Do you have a PXA device? |
| 23:28.53 | [g2] | that's why you need a Loft :) |
| 23:29.10 | beewoolie | I thought my invoice was backordered. |
| 23:29.21 | beewoolie | Besides, I thought that the loft was IXP? |
| 23:29.26 | lennert | i have two PXAs, actually, but i don't think they have accessible jtag ports |
| 23:29.31 | lennert | i.e., two gumstix 400 boards |
| 23:29.54 | beewoolie | lennert: Are you sure? Last I read, the gumstix advertised the JTAG port. |
| 23:30.15 | lennert | i have a really ancient model? |
| 23:34.41 | lennert | i _think_ i have the model that came before the waysmall basix 400ax |
| 23:34.46 | lennert | i do have the mmc slot |
| 23:34.56 | lennert | and the hirose connector |
| 23:35.06 | lennert | but i don't think the jtag lines are brought out to a connector on mine |
| 23:35.12 | lennert | so i probably need a daughterboard or something |
| 23:36.07 | lennert | JTAG isn't mentioned on their expansion board page, http://www.gumstix.com/spexExpnsion.html |
| 23:37.37 | beewoolie | It's on the hirose connector. |
| 23:37.50 | beewoolie | http://www.gumstix.org/tikiwiki/tiki-index.php?page=I%2FO |
| 23:38.02 | lennert | yeah, i saw that |
| 23:38.09 | lennert | but it's not brought out on any of the boards |
| 23:38.16 | lennert | so i'd have to solder tiny wires to the connector myself |
| 23:38.22 | lennert | which is just right out :) |
| 23:38.54 | beewoolie | [g2]: to answer your question, I doubt that there will be many changes between the two. I'll find out as soon as I get a PXA board to test with. |
| 23:39.10 | [g2] | beewoolie are you going to be driving the 2232 with usb ? |
| 23:39.15 | beewoolie | Yeah. |
| 23:39.25 | beewoolie | I'm assembling the board that ep1220 designed. |
| 23:39.32 | [g2] | nod |
| 23:39.41 | [g2] | You've got a circuit board ? |
| 23:40.49 | beewoolie | [g2]: 2 |
| 23:41.02 | ka6sox-office | [g2]:2 |
| 23:41.13 | beewoolie | [g2]: me 2 |
| 23:41.29 | ka6sox-office | [g2] me 2 too |
| 23:41.33 | beewoolie | [g2]: 2 me 2 me 2 2222222222 |
| 23:41.33 | [g2] | is that so you can send 1 to the soldered-challenged ? :) |
| 23:41.35 | ka6sox-office | :) |
| 23:42.01 | beewoolie | *cough* and I still wonder where that loft board is... |
| 23:42.17 | [g2] | I thought you wanted a case |
| 23:42.30 | beewoolie | Is it still on order? |
| 23:42.42 | [g2] | the Loft board or the cases ? |
| 23:42.52 | [g2] | I get 5 more tomorrow |
| 23:43.01 | beewoolie | I don't know. Last you told me there weren't any cases. |
| 23:43.20 | [g2] | I've got 2 cases not and 5 more tomorrow |
| 23:43.55 | [g2] | I"ve got 15 boards but I think 7 are sold |
| 23:44.08 | beewoolie | Well, the question that my pal asked is whether or not it is better to get the cirrrus based board since it is a more open platform. |
| 23:44.14 | [g2] | There's 100 in the queue |
| 23:44.33 | beewoolie | 100 sold, or on order? |
| 23:44.38 | [g2] | built |
| 23:45.06 | [g2] | there may be 100s on order on 1000s in seveal months |
| 23:45.38 | [g2] | but we'll see how it turns out |
| 23:45.58 | [g2] | I think Jan 15th is next batch of Glomation boads |
| 23:46.19 | beewoolie | I feel like I've got too many choices. |
| 23:46.34 | lennert | just in time for jan 16th when i come home |
| 23:46.48 | ka6sox-office | you are in .lt? |
| 23:46.55 | lennert | yeah, right now i am |
| 23:47.10 | ka6sox-office | ah cooolies |
| 23:47.31 | beewoolie | You guys heard of IEEE 1500? |
| 23:48.05 | ka6sox-office | nope |
| 23:48.07 | beewoolie | Looks a lot like JTAG, but it's for SoCs and multi-core devices. |
| 23:48.42 | lennert | so that's not IEEE 1532? |
| 23:48.54 | beewoolie | http://www.arm.com/pdfs/IEEE1500_compliant_wrapper_cell_defensive_pub.pdf |
| 23:50.09 | lennert | it looks kind of odd at first sight |
| 23:53.35 | beewoolie | They also have something that professes to give JTAG functionality with a two-wire interface...they say one wire, but the diagrams show two wires. |
| 23:54.13 | lennert | GND doesn't count ;) |