| 00:04.53 | key2 | ? |
| 00:08.04 | key2 | AchiestDragon? |
| 00:10.21 | AchiestDragon | trying to sort out a way to configure the fpga via the pc104 bus |
| 00:11.05 | AchiestDragon | think i found one ,, just working out best way to impliment it |
| 00:14.43 | AchiestDragon | and looks like it will work in the following way |
| 00:16.24 | key2 | http://www.dspfpga.com/?page=eus_100lx |
| 00:17.12 | AchiestDragon | as the fpga will be using the memrd , memwr and only use 16 bit access so , this will allow for the 8 bit accessed to be used diferently |
| 00:18.13 | AchiestDragon | i am working on a simple 8 bit port that will allow us to bit bang the onboard fpga for config |
| 00:19.38 | AchiestDragon | but the design is looking good |
| 00:19.53 | key2 | AchiestDragon: did you have a look on the link ? |
| 00:19.59 | AchiestDragon | yes |
| 00:21.08 | key2 | what u think about it |
| 00:21.08 | key2 | ? |
| 00:22.04 | AchiestDragon | 2 bga packages for a start |
| 00:22.25 | beewoolie | key2: looks expensive for what we're looking to do. |
| 00:23.06 | AchiestDragon | yes and will still need the level translators and jtag adaptors |
| 00:24.10 | key2 | well I told u the best is a simple ARM7 + FPGA + FT2232 |
| 00:24.20 | key2 | you can bitbang at a very high rate |
| 00:24.33 | key2 | and you can program whatever you want in the ARM7 |
| 00:25.08 | AchiestDragon | yes but the ts7200 plus this bord gives us that and more |
| 00:25.33 | AchiestDragon | like ethernet |
| 00:28.06 | wookey_ | ah ts7200 - is that a board from embeddedarm.com? |
| 00:28.25 | wookey_ | (they are just sending us a ts7205 (because it's not playing nice with YAFFS2) |
| 00:28.29 | wookey_ | ) |
| 00:31.43 | AchiestDragon | yes |
| 00:32.54 | AchiestDragon | although they do a ts7250 and another new low power one that would all do the job , the ts7200 has the compact flash card on it that may be usefull for all the software needed |
| 00:33.19 | AchiestDragon | but a usb memory stick could also provide that |
| 00:33.29 | AchiestDragon | or usb hdd |
| 00:34.40 | AchiestDragon | as far as pc104 boards go there the best value ones i have come accross , all the others i have seen are at least dubble the cost of that |
| 00:55.43 | ka6sox-office | vmaster: ping? |
| 01:19.27 | [g2] | key2 any idea what eus_100lx costs ? |
| 01:20.58 | *** join/#openjtag vmaster_ (i=vmaster@p549B69E2.dip.t-dialin.net) |
| 01:54.03 | *** join/#openjtag cpage (n=cpage@netblock-68-183-40-90.dslextreme.com) |
| 01:54.10 | *** join/#openjtag lennert (n=buytenh@83.160.184.112) [NETSPLIT VICTIM] |
| 01:54.11 | *** join/#openjtag nslu2-log (n=nslu2-lo@nslu2-linux/dyoung) [NETSPLIT VICTIM] |
| 02:37.21 | [g2] | hey beewoolie lennert ping |
| 02:45.14 | *** join/#openjtag ByronT (n=byron-po@nslu2-linux/ByronT) |
| 03:26.03 | beewoolie | [g2]: hey. I was at the store. |
| 03:26.51 | [g2] | cool... food store or hw store ? |
| 03:28.29 | beewoolie | shopping for dinner |
| 05:33.49 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
| 05:46.23 | beewoolie | ka6sox: hey |
| 05:47.28 | ka6sox | yo |
| 05:48.11 | beewoolie | ka6sox: I had a little success with JTAG programming. |
| 05:48.30 | beewoolie | I can write to the flash on one of my board at about 1.45 seconds/K. |
| 05:48.45 | beewoolie | Which translates into 256K in 6.2minutes. |
| 05:48.59 | beewoolie | It's somewhat faster than the openwince jtag code |
| 05:49.04 | ka6sox | thats a lot faster than the 40 minutes thru teh wiggler. |
| 05:49.10 | ka6sox | s/teh/the |
| 05:49.22 | beewoolie | And that's unoptimized flash writing code. |
| 05:49.29 | ka6sox | what hardware? |
| 05:49.42 | beewoolie | Xilinx III and an ARM9 board. |
| 05:49.43 | ka6sox | JTAG |
| 05:49.47 | beewoolie | Yeah |
| 05:49.51 | ka6sox | ozky |
| 05:50.14 | ka6sox | well...that means that most of the code is unoptimized. |
| 05:50.17 | beewoolie | It's the first useful result I've gotten, so I thought I'd share. |
| 05:50.22 | beewoolie | Certainly. |
| 05:50.29 | ka6sox | that is a good benchmark. |
| 05:50.41 | ka6sox | how long is the bsdl file? |
| 05:50.45 | beewoolie | I am using the ARM code debug facilities which are faster than a rote boundaryt scan. |
| 05:50.47 | ka6sox | (how many bits) |
| 05:51.16 | ka6sox | ah |
| 05:51.35 | ka6sox | does it have an i-cache like the Xscale? |
| 05:51.40 | beewoolie | The boundary scan is over 593 bits., |
| 05:51.50 | beewoolie | No, I cannot write to the Icache as far as I can tel. |
| 05:51.59 | ka6sox | k |
| 05:52.09 | beewoolie | The Xscale has a really slick way to handle that. |
| 05:52.17 | beewoolie | However, I won't be able to use it with this JTAG dongle. |
| 05:52.25 | ka6sox | k |
| 05:52.32 | beewoolie | Actually, I take that back. |
| 05:52.49 | beewoolie | I may be able to use it, but not in the load-before-CPU-exec mode. |
| 05:52.59 | ka6sox | ah |
| 05:53.06 | beewoolie | With code in the cache, programming has to be way faster. |
| 05:53.25 | ka6sox | should be. |
| 05:53.28 | beewoolie | That will be closer to 32 TCK clocks per 32 bit write. |
| 05:53.39 | beewoolie | I |
| 05:53.45 | beewoolie | I'm working on arm7 at the moment. |
| 05:53.56 | beewoolie | It's proving to be harder than I expected. |
| 05:54.01 | ka6sox | same technique? |
| 05:54.17 | beewoolie | Yeah. There's somthing not working with the debug scan chain. |
| 05:54.33 | beewoolie | It's probably the same hitch I encountered before: incorrect documentation. |
| 05:54.45 | beewoolie | That is, I'm reading the wrong file or I misunderstand what I'm reading. |
| 05:57.05 | beewoolie | ka6sox: Are you planning to manufacture the PC104 board that will host the FPGA? |
| 05:57.14 | beewoolie | Or, find something off-the-shelf? |
| 05:58.18 | ka6sox | manuf |
| 05:58.53 | beewoolie | K. There was some chatter about this earlier. AchiestDragon ( think) was shopping a board to handle the FPGA. |
| 05:59.07 | beewoolie | Seemed like an expensive solution for what should be very simple. |
| 05:59.14 | ka6sox | I haven't found anything that has what we need except for a board that is in development |
| 05:59.37 | ka6sox | (has ARM9, 64MB ram,10/100,S3 |
| 06:03.24 | ka6sox | but I don't even know if I can get ahold of that. |
| 06:03.34 | ka6sox | its a 200mhz ATMEL part. |
| 06:04.19 | ka6sox | but its not real yet. |
| 06:35.42 | beewoolie | Isn't the ts7200 going to work? |
| 06:35.55 | beewoolie | ka6sox: Sorry, I've been debugging. |
| 06:38.34 | ka6sox | yes it is |
| 06:38.36 | ka6sox | :) |
| 06:38.56 | ka6sox | I think that the TS7200 will be an excellent platform. |
| 06:39.21 | beewoolie | Is you plan to have two boards as well as the ep1220 interface board? |
| 06:39.38 | ka6sox | yes |
| 06:39.57 | ka6sox | we might be limited in speed by the EP board only because of cable lengths. |
| 06:40.21 | beewoolie | So, what are you thinking of doing? |
| 06:40.33 | ka6sox | I'm going to talk to ep1220 about the situation. |
| 06:40.54 | ka6sox | what is your opinion on the FT2232 solution? faster or failure? |
| 06:45.05 | beewoolie | I don't yet know. I've been working on this code for handling the scans so that I have a way to measure performance. |
| 06:45.18 | beewoolie | The next step is to build the board and see how it compares. |
| 06:45.40 | ka6sox | k |
| 06:45.43 | beewoolie | vmaster has made the 2232 solution out to be a failure, as far as I can tell. |
| 06:45.59 | beewoolie | I'm the sort of person who needs to see it before I'll believe it. |
| 06:46.12 | ka6sox | you are certianly getting better performance out of the Parallel port solution. |
| 06:46.22 | ka6sox | Xilinx III |
| 06:46.29 | beewoolie | than openwince? |
| 06:48.08 | ka6sox | what interface did you use for your tests? |
| 06:48.38 | ka6sox | I thought it was the Xilinx III part. |
| 06:48.43 | beewoolie | Yeah. |
| 06:48.53 | beewoolie | It's the only one that is convenient at the moment. |
| 06:49.03 | ka6sox | k |
| 06:49.17 | ka6sox | that is a good benchmark as a lot of people have that one. |
| 06:49.19 | beewoolie | So, I suppose I'm going better with the Xilinx than openwince does. |
| 06:49.35 | beewoolie | But really, that code isn't particularly clever. It *is* very general. |
| 06:50.39 | ka6sox | did you optimize your code for the ARM9 target? |
| 06:51.14 | beewoolie | That's the only one that works right now. |
| 06:51.27 | beewoolie | It isn't exactly optimized for the target, tho. |
| 06:51.35 | ka6sox | k |
| 06:51.42 | beewoolie | I am using a special, short, scan chain to push instructions into the CPU. |
| 06:51.48 | beewoolie | It's only 67 bits long. |
| 06:51.55 | ka6sox | that should help alone |
| 06:52.07 | beewoolie | The full scan chain is really long, almost 600 bits. |
| 06:52.17 | beewoolie | So, I'm doing that, and I'm using buffered writes. |
| 06:52.29 | beewoolie | The one thing I want to try is removing the status checks. |
| 06:52.39 | beewoolie | Right now, I check the status of the flash after every write. |
| 06:52.51 | beewoolie | I *can* assume that the writes complete in the time specified by the CFI data. |
| 06:53.07 | beewoolie | And I believe that these times are far shorter than the time it takes to read the status. |
| 06:53.25 | beewoolie | So, right now the code is perfectly correct. |
| 06:53.42 | beewoolie | Some clever changes and it might be made faster. |
| 06:54.07 | ka6sox | maybe just do a block checksum. |
| 06:54.27 | beewoolie | Of course, a verify is needed. |
| 06:56.51 | ka6sox | sounds like there are optimizations still to come. this is going to help even when we have hardware assist. |
| 07:07.08 | beewoolie | Definitely. |
| 07:08.14 | ka6sox | the plan hasn't changed and things are still on track. |
| 07:09.20 | beewoolie | to be fair, doing better than openwince is like shooting fish in a barrel. |
| 07:09.44 | beewoolie | I kinda feel bad for the author(s) of that tool. |
| 07:12.45 | ka6sox | it probably works fine for smaller devices but when you try to do something like program up a 16MB flash it falls down. |
| 07:18.36 | *** join/#openjtag bullet (n=bullet@52.51.203.62.cust.bluewin.ch) |
| 07:39.35 | *** join/#openjtag dyoung-away (n=dyoung@nslu2-linux/dyoung) |
| 07:45.19 | beewoolie | NN |
| 07:45.32 | ka6sox | night night? |
| 07:45.46 | beewoolie | :-) |
| 07:45.51 | *** part/#openjtag beewoolie (n=beewooli@206.124.142.26) |
| 09:37.29 | lennert | pong [g2] |
| 11:17.02 | *** join/#openjtag dyoung-away (n=dyoung@nslu2-linux/dyoung) |
| 12:51.53 | *** join/#openjtag prpplague (n=billybob@72.22.143.75) |
| 14:51.33 | *** join/#openjtag ulfk (n=ulfk@62.206.114.34) |
| 14:51.37 | ulfk | hi |
| 14:51.54 | lennert | hi ulfk |
| 14:52.05 | lennert | ulfk: did you work for atmel? |
| 14:52.25 | ulfk | for the company? no |
| 14:52.33 | ulfk | why |
| 14:52.36 | lennert | i remember seeing your name somewhere |
| 14:52.54 | ulfk | intersil and xscale are my cpus haha |
| 14:53.03 | lennert | okay |
| 14:53.14 | lennert | maybe i'm confusing you with someone else |
| 14:53.34 | ulfk | i still try to use jtag to flashmem a amd flash chip on a xscale cpu |
| 14:54.20 | ulfk | but therefor i have to learn more about all this shit |
| 14:54.28 | ulfk | anyway |
| 14:56.22 | lennert | i've only used jtag for programming fpgas so far |
| 15:00.05 | vmaster | lennert: that was Ulf Samuelson |
| 15:00.28 | lennert | yeah, but i do know another ulf k. |
| 15:02.16 | vmaster | Atmel is funny - two of their developers wanted to send patches to the u-boot, but couldn't create them against top-of-cvs, as their company wont allow cvs accesses through their firewall |
| 15:02.44 | vmaster | i'm all for security - but you should be allowed to do your work... |
| 15:03.48 | lennert | yeah, silly corporates |
| 15:10.20 | NAiL | heh |
| 15:10.32 | NAiL | I'm considering applying for work at atmel |
| 15:11.11 | lennert | cool |
| 15:11.16 | lennert | they're in your area? |
| 15:11.36 | NAiL | they're going to open up 30 positions soon... I've just got some inside info ;-) |
| 15:11.43 | lennert | hehe |
| 15:11.50 | lennert | guess they don't allow people to work from home, eh :) |
| 15:13.53 | NAiL | hmm |
| 15:13.56 | NAiL | I can't access atmel.com |
| 15:14.44 | lennert | it works fine here |
| 15:14.58 | NAiL | I can't access slashdot.org either, so I think something is wrong :-P |
| 15:15.01 | lennert | Everywhere You Are(R) |
| 15:15.10 | lennert | NAiL: you'll ping out from irc soon.. :) |
| 15:15.10 | NAiL | actually, I can't *resolve* slashdot |
| 15:15.12 | NAiL | hehe |
| 15:15.20 | NAiL | no, I'm irc'ing from another box |
| 15:15.41 | NAiL | so it's my ISP that has a problem with intercontinental stuff again, I guess |
| 15:15.48 | *** join/#openjtag ByronT-Away (n=byron-po@nslu2-linux/ByronT) |
| 15:15.49 | NAiL | the box I'm on can resolve it just fine |
| 15:15.57 | lennert | try tracing to 132.229.8.6 |
| 15:16.24 | NAiL | 132.229.8.6 |
| 15:16.26 | NAiL | argh |
| 15:16.29 | NAiL | 15 sherlock.leidenuniv.nl (132.229.8.6) 40.468 ms 40.472 ms 40.978 ms |
| 15:16.45 | lennert | works fine then |
| 15:17.05 | NAiL | tracing atmel stops in NY |
| 15:17.17 | lennert | not your isp then |
| 15:19.14 | NAiL | no |
| 15:19.17 | NAiL | level4 |
| 15:19.18 | NAiL | eh |
| 15:19.19 | NAiL | level3 |
| 15:21.02 | lennert | right |
| 15:21.12 | lennert | the isp that lost the battle |
| 15:21.43 | NAiL | hehe |
| 15:29.33 | ka6sox | L3 is a walking corpse |
| 15:30.53 | lennert | the folks that keep overcharging for their bandwidth even in this day and age |
| 15:32.18 | vmaster | ka6sox: pong (14h30m RTT aint that bad...) |
| 15:33.20 | ka6sox | ya...not bad! |
| 15:33.41 | ka6sox | what kernel are you using for the box with the ISE in debian? |
| 15:33.53 | lennert | vmaster: sounds like a typical level(3) RTT |
| 15:34.16 | vmaster | 2.6.14 (though every 2.6.x worked for me) |
| 15:34.23 | vmaster | the new ise 8.1i is much nicer |
| 15:34.35 | vmaster | it got a native qt gui, no more wind/u |
| 15:35.08 | ka6sox | and what is the library that we have to drag in from etch? |
| 15:35.26 | ka6sox | something3 |
| 15:35.30 | vmaster | for 7.1, you need some openmotif library |
| 15:35.55 | ka6sox | what about 8.1i? |
| 15:36.23 | vmaster | didn't have to install anything extra |
| 15:36.28 | vmaster | guess qt libs are required |
| 15:37.45 | vmaster | mhh, maybe not even that - it comes with its own copy of the qt libs |
| 15:39.31 | ka6sox | cool |
| 15:39.39 | ka6sox | okay I'll download 8.1i |
| 15:40.18 | ka6sox | since I have kde that might get interesting |
| 15:40.30 | lennert | can i download 8.1i somewhere if i have a 7.1i license? guess not? |
| 15:40.57 | vmaster | the 8.1i webpack supports everything 7.1i BaseX supported |
| 15:41.13 | ka6sox | gotta check that one out |
| 15:42.01 | vmaster | if your 7.1i isn't older than a year you should get an update to 8.1i |
| 15:42.09 | ka6sox | thanks...must get kidlet off to school. |
| 15:42.16 | lennert | i'm using ISE for the v2pro |
| 15:42.18 | ka6sox | its under a year(like 7months) |
| 15:42.28 | vmaster | if your 7.1i BaseX isn't older than a year, you should get an upgrade to 8.1i foundation |
| 15:44.51 | NAiL | Atmel here lies right next to Nordic VLSI/Nordic Semiconductor ;-) |
| 15:47.47 | lennert | there isn't really any tech companies nearby here, i think |
| 15:48.55 | ka6sox | we have Cisco and Raytheon here |
| 15:49.06 | *** join/#openjtag velinp (n=velinp@c88-163.cable.netissat.bg) |
| 15:49.07 | lennert | i.e. the borg and the military |
| 15:49.17 | lennert | :) |
| 15:49.35 | ka6sox | (oh and gotomypc.com and gotomeeting.com) |
| 15:50.23 | lennert | pc anywhere and netmeeting? |
| 15:50.37 | ka6sox | similar |
| 15:50.39 | ka6sox | web based |
| 15:50.56 | lennert | vnc has java clients too |
| 15:51.25 | NAiL | iirc, gotomypc.com is much faster :) |
| 16:09.46 | AchiestDragon | morning |
| 16:10.11 | *** join/#openjtag bullet (n=bullet@138.61.203.62.cust.bluewin.ch) |
| 16:13.16 | AchiestDragon | i have a question re the jtag1, jtag2 and jtag3 pins on the i/f ,, at present jtag1 is input and the other 2 are programable input output , does this depend on the jtag adaptor , or do jtag2,3 need to be bidirectional |
| 16:15.48 | AchiestDragon | on the new design i can use jtag1,2 and 3 and provide seperate inputs and ouputs that the adaptor can be configured so if they require inputs thease pins are wired to input and outputs if outputs needed |
| 17:45.56 | *** join/#openjtag beewoolie-afk (n=beewooli@206.124.142.26) |
| 17:54.20 | [g2] | beewoolie-afk ping |
| 17:54.29 | beewoolie-afk | [g2]: hello |
| 17:54.52 | beewoolie-afk | Sleep is always good for fixing bugs. |
| 17:55.18 | [g2] | amen brother bee ! |
| 18:30.17 | lennert | ka6sox-office: email? |
| 18:39.02 | *** join/#openjtag Tiersten (n=tman@nslu2-linux/Tiersten) |
| 20:04.57 | *** join/#openjtag velinp (n=velinp@c88-163.cable.netissat.bg) |
| 20:05.39 | *** join/#openjtag velinp (n=velinp@c88-163.cable.netissat.bg) |
| 21:19.12 | *** join/#openjtag ByronT_ (i=byron-po@nslu2-linux/ByronT) |
| 21:20.46 | *** join/#openjtag velinp (n=velinp@c88-163.cable.netissat.bg) |
| 21:31.09 | *** part/#openjtag velinp (n=velinp@c88-163.cable.netissat.bg) |
| 21:48.49 | ka6sox-office | lennert, cool! |
| 21:48.57 | ka6sox-office | I hope that will speed things up. |
| 21:49.03 | lennert | the ep93xx stuff? |
| 21:49.05 | lennert | let's hope |
| 21:49.41 | ka6sox-office | ya..I hope so. |
| 21:52.20 | lennert | i'm inclined to bypass them.. but have been convinced not to |
| 21:52.29 | lennert | cause they mean well |
| 23:07.28 | *** join/#openjtag beewoolie-afk (n=beewooli@206.124.142.26) |
| 23:08.02 | beewoolie-afk | [g2]: ? |
| 23:08.31 | beewoolie-afk | [g2]: I know why you aren't receiving email from me. |
| 23:32.46 | [g2] | beewoolie-afk why's that ? |
| 23:33.57 | [g2] | beewoolie-afk you'll probably miss the shipping deadline today |
| 23:34.04 | beewoolie-afk | [g2]: Your mail server is rejecting me... |
| 23:34.19 | beewoolie-afk | telnet clmboh-01.mgw.rr.com 25 |
| 23:34.20 | beewoolie-afk | Trying 65.24.7.11... |
| 23:34.20 | beewoolie-afk | Connected to clmboh-mx-02.mgw.rr.com. |
| 23:34.20 | beewoolie-afk | Escape character is '^]'. |
| 23:34.20 | beewoolie-afk | 450-clmboh-mx-02.mgw.rr.com |
| 23:34.21 | beewoolie-afk | 450 #4.1.3 Relaying temporarily denied. Cannot resolve PTR record for 206.124.142.26 |
| 23:34.23 | beewoolie-afk | Connection closed by foreign host. |
| 23:34.37 | beewoolie-afk | your mail server has a policy that is not compliant with the RFCs. |
| 23:34.49 | [g2] | odd, I'm getting e-mail from others |
| 23:34.55 | beewoolie-afk | PTR records are controlled by my ISP and, it appears, they choose not to have one. |
| 23:35.10 | beewoolie-afk | [g2]: That just means that other ISP are publishing PTR records. |
| 23:40.47 | beewoolie-afk | Lots of ISPs do things that aren't valid as long as it 'works for me!' |
| 23:41.01 | beewoolie-afk | Doesn't make their behavior correct or a good idea. |
| 23:42.20 | vmaster | [07:46] < beewoolie> vmaster has made the 2232 solution out to be a failure, as far as I can tell. |
| 23:42.24 | vmaster | not really a failure |
| 23:42.40 | vmaster | but certainly not as good as 6 mhz tck rate suggest it could be |