| 00:24.35 | *** join/#openjtag prpplague^2 (~billybob@72.22.141.31) |
| 00:43.13 | *** join/#openjtag beewoolie-afk (~beewoolie@florence.buici.com) |
| 00:43.48 | [g2] | beewoolie-afk, HEY! |
| 00:43.58 | beewoolie-afk | [g2]: greetings. |
| 00:44.04 | beewoolie-afk | Been busy with moving a client. |
| 00:44.18 | [g2] | moving a client ? |
| 00:44.19 | beewoolie-afk | This is the first day when I wasn't in the machine room, burried beneath a pile of cat5. |
| 00:44.27 | beewoolie-afk | Yeah. They moved offices. |
| 00:44.34 | [g2] | cool |
| 00:44.36 | beewoolie-afk | How's the good fight? |
| 00:44.59 | [g2] | it's not a good fight it's an ass-kicking on our side :) |
| 00:45.57 | [g2] | you've been missing the big JTAG stuff |
| 00:46.24 | [g2] | ep1220 has been doing lots |
| 00:46.46 | beewoolie | What's the latest? Do we have a piece of HW? |
| 00:47.01 | [g2] | We should very soon |
| 00:47.09 | beewoolie | Excellent. |
| 00:47.11 | [g2] | The parts were supposed to be in yesterday |
| 00:48.11 | [g2] | ep1220 has made good progress with both the USB 2.0 device chip for the S3 boards (he's reprogrammed the on-board eeprom) |
| 00:48.18 | [g2] | and with the FTDI chip |
| 00:48.39 | [g2] | We were discussing loading up the I cache directly from JTAG |
| 00:48.50 | beewoolie | Interesting idea. |
| 00:48.59 | [g2] | so we could put APEX in the i cache and then wake up the chip |
| 00:49.05 | beewoolie | that means that we store a program in cache and then execute from there. |
| 00:49.16 | beewoolie | Hey! That has an awesome consequence! |
| 00:49.19 | [g2] | kitno455 is checking if the RESET_IN_N line AC13 comes out |
| 00:49.33 | beewoolie | One of the problems with writing to flash is that byte-by-byte programming is slow. |
| 00:49.36 | [g2] | well should know by tomorrow morning |
| 00:49.51 | [g2] | and it's only 33bits/word :) |
| 00:50.08 | beewoolie | If we can write the data to the cache, then we can program flash without initializin SDRAM. |
| 00:51.21 | [g2] | beewoolie, nod. |
| 00:56.40 | [g2] | so beewoolie I've got a question for you |
| 00:56.50 | beewoolie | otp...hold on |
| 00:56.53 | [g2] | np |
| 01:34.43 | beewoolie | ok. back. |
| 01:34.46 | beewoolie | Whatsup |
| 01:34.50 | beewoolie | [g2]: ping. |
| 01:35.03 | [g2] | pong |
| 01:35.07 | beewoolie | BTW, I like this writing to cache idea. |
| 01:35.21 | beewoolie | It's great for machines that have separate I and D cache. |
| 01:35.33 | [g2] | well we'll find out tomorrow if the line comes out |
| 01:35.37 | beewoolie | It does mean we have to setup the MMU on most systems. |
| 01:35.55 | beewoolie | Oh. I see. This is an issue for the scan chain? |
| 01:36.04 | beewoolie | BTW, what is 33bits/word? |
| 01:36.28 | [g2] | instead of 498 I think |
| 01:36.40 | beewoolie | It's a separate chain? |
| 01:36.40 | [g2] | it doesn't use the BSR |
| 01:36.59 | beewoolie | Hmm. Interesting. |
| 01:37.11 | [g2] | LDIC |
| 01:37.23 | [g2] | and DCSR |
| 01:37.43 | [g2] | Load Instruction cache and Debug Control Status Register |
| 01:37.57 | beewoolie | I need to get back on the telephone here. Is there something quick you want to ask? |
| 01:38.08 | [g2] | we can talk later |
| 01:38.12 | beewoolie | OK. |
| 01:38.14 | [g2] | or I'll send e-mail |
| 01:38.15 | [g2] | cheers |
| 01:38.23 | beewoolie | ttfn |
| 01:39.11 | [g2] | beewoolie-afk, FYI see chapter 20 in the Intel Developer's Manual Pub 25248005.pdf |
| 01:39.24 | beewoolie-afk | thx. |
| 01:39.37 | [g2] | go yak on the phone! |
| 01:39.42 | beewoolie-afk | already am |
| 01:40.29 | *** join/#openjtag prpplague (~billybob@72.22.141.232) |
| 03:51.59 | *** join/#openjtag beewoolie-afk (~beewoolie@206.124.142.27) |
| 03:57.18 | [g2] | beewoolie-afk, hey |
| 04:23.38 | *** join/#openjtag dyoung-web (www-data@netblock-66-159-209-60.dslextreme.com) |
| 04:24.12 | ka6sox-away | ping pang pong |
| 04:25.50 | dyoung-web | gu go a |
| 04:26.09 | ka6sox-away | he he |
| 04:27.01 | ByronT | that should have been "gu go ga" or even more correct would have "gi ga go" |
| 05:55.43 | *** join/#openjtag beewoolie-afk (~beewoolie@florence.buici.com) |
| 06:12.56 | *** join/#openjtag ka6sox (~tking@adsl-66-159-198-116.dslextreme.com) |
| 07:45.59 | *** join/#openjtag beewoolie-afk (~beewoolie@florence.buici.com) |
| 08:58.52 | *** join/#openjtag Tiersten_ (tman@Tiersten.nslu2-linux) |
| 10:11.28 | *** join/#openjtag prpplague (~billybob@216.110.100.27) |
| 10:20.13 | dyoung-zzzz | Yo G. |
| 11:23.28 | *** join/#openjtag [g2] (~g2@g2.nslu2-linux) |
| 11:46.14 | *** join/#openjtag prpplague (~billybob@216.110.100.96) |
| 11:47.03 | *** join/#openjtag ep1220 (~ep1220@gate.epatec.at) |
| 13:04.24 | *** join/#openjtag kitno455 (~man@tfhs.net) |
| 13:04.49 | kitno455 | ping ep1220 |
| 13:43.39 | ep1220 | kitno455: I am here now |
| 13:55.51 | *** join/#openjtag [g2] (~g2@g2.nslu2-linux) |
| 13:57.05 | kitno455 | ep1220, g2 get you the data about reset pin? |
| 13:57.40 | ep1220 | kitno455: Just saw You updated the wiki |
| 13:57.45 | ep1220 | Thank You !! |
| 13:58.02 | kitno455 | i am only 85% sure of the data |
| 13:58.13 | ep1220 | OK. Do You have a scanner ? |
| 13:58.20 | kitno455 | i sanded some of those traces off when i cleaned the board |
| 13:58.45 | kitno455 | i write scanner software for a living, and am the SANE fujitsu backend maintainer. yes, i have scanners :) |
| 13:59.09 | ep1220 | Could you scan the 2 sides an post as TIFF ? |
| 13:59.16 | ep1220 | of the PCB I mean |
| 13:59.40 | kitno455 | sure, board is a little warped, so it may be out of focus, but i can try |
| 13:59.53 | kitno455 | also, some traces sanded off |
| 14:00.10 | ep1220 | Anyway, I than could overlay them in Photoshop |
| 14:00.13 | kitno455 | does it make sense to you that RESET_IN_N is connected to pin 15 on flash? |
| 14:01.00 | ep1220 | is puzzling me. Maybe disable programming while in reset ? |
| 14:01.20 | kitno455 | i guess |
| 14:01.29 | ep1220 | I try to identify Q8. Could be a reset Chip - so this makes sense |
| 14:01.36 | kitno455 | you think bus outputs are unstable during reset? |
| 14:01.45 | kitno455 | want to avoid accidental write? |
| 14:02.05 | ep1220 | something like this. |
| 14:02.39 | kitno455 | i could try to figure out where rest of Q8 pins go |
| 14:02.53 | ep1220 | I will verify Q8/1 reset functionality with an oscilloscope. |
| 14:03.15 | ep1220 | Q8 could be: http://www.jlink.com.tw/Datasheet/EM/EM6325_ds.pdf |
| 14:03.20 | kitno455 | right, have not touched slug with my scope yet |
| 14:04.25 | kitno455 | huh, a swatch watch |
| 14:04.42 | ep1220 | <PROTECTED> |
| 14:04.58 | kitno455 | the company that makes q8, swatch |
| 14:05.12 | ep1220 | I see. |
| 14:05.31 | kitno455 | you might be too young to remember those :) |
| 14:06.16 | ep1220 | Old enough to know them :-) |
| 14:06.25 | kitno455 | can you tell me (in laymans...) why RESET_IN_N is needed as a part of JTAG? |
| 14:06.48 | ep1220 | JTAG allows to write code into the Xscale cache. |
| 14:07.03 | ep1220 | For this to work the CPU must be held in reset during the write. |
| 14:07.25 | kitno455 | wonder why you cant do that thru jtag itself? |
| 14:08.21 | ep1220 | I can assert a "keep-reset" in JTAG. but the doc says RESET_IN must be active at this time |
| 14:08.34 | kitno455 | ok, follow the doc |
| 14:08.43 | ep1220 | Maybe the CPU could crash/hang/.. |
| 14:09.02 | ep1220 | esp. in casese were there is no working FLASH/RAM |
| 14:09.03 | kitno455 | if you are right about q8, pin 4 is a manual reset |
| 14:09.36 | ep1220 | Yes. |
| 14:09.40 | kitno455 | pull it low, and see what happens :) |
| 14:10.01 | kitno455 | i noticed last night TP1 on back of slug |
| 14:10.06 | kitno455 | you seen that? |
| 14:10.19 | ep1220 | No |
| 14:10.30 | kitno455 | under processor on back |
| 14:10.37 | kitno455 | i had not noticed it till now |
| 14:10.50 | kitno455 | connected to AD12 (PLL something) |
| 14:11.11 | ep1220 | see it now |
| 14:11.14 | kitno455 | not sure why you want that? |
| 14:11.54 | ep1220 | I believe it signals when the PLL is locked (?) |
| 14:12.13 | kitno455 | what does pll in cpu lock to |
| 14:12.38 | ep1220 | the external clock is lower than CPU clock. |
| 14:12.51 | ep1220 | There is a PLL to get the higher clock speed. |
| 14:13.07 | ep1220 | Some ops must not be done while the DLL is locked. |
| 14:13.27 | kitno455 | wonder if that explains the slugs apparent spee dproblem? |
| 14:13.56 | ep1220 | I am new to the slug. Bought yesterday, opened yesterday. |
| 14:14.02 | ep1220 | So i ca not say. |
| 14:14.25 | kitno455 | its a neat toy |
| 14:14.42 | kitno455 | though i intend to put it to work :) |
| 14:14.49 | ep1220 | likely, i am working on a JTAG controller. |
| 14:15.02 | ep1220 | And it is a cheap "victim" for tests. |
| 14:15.07 | ep1220 | and experiments |
| 14:15.22 | kitno455 | i am aware of your usb jtag project, i think |
| 14:16.05 | kitno455 | i have played a little with toys using opencores code |
| 14:16.25 | kitno455 | but i have very little useful HW experience |
| 14:16.48 | ep1220 | I doing HW a longer time |
| 14:17.20 | ep1220 | often with JTAG for debugging. |
| 14:17.45 | kitno455 | you use comercial jtag equipment? |
| 14:18.14 | ep1220 | I used several. Primarily did DSP |
| 14:18.43 | kitno455 | right. now you try for opensource jtag programmer? |
| 14:20.00 | ep1220 | I more into debugging. |
| 14:20.16 | ep1220 | and the JTAG hardware. |
| 14:20.29 | ep1220 | Hope someone else will add FALSH programming |
| 14:20.48 | prpplague | ep1220: flash programming is fairly easy |
| 14:20.49 | kitno455 | cool |
| 14:21.02 | prpplague | ep1220: especially when most of the chips are cfi compliant |
| 14:21.30 | ep1220 | prpplague: But still takes time to write and test :-) |
| 14:21.55 | prpplague | true, but it really straight forward work |
| 14:22.35 | ep1220 | prpplague: that is good, more likely someone might take it |
| 14:22.55 | kitno455 | well prpplague, i guess you got some code to write |
| 14:23.53 | prpplague | kitno455: hehe, well i'd be interested in doing it, however i'm currently 2 weeks behind on my BSP :( |
| 14:24.22 | kitno455 | ep1220, you need anything else, you let me know. anoah AT pfeiffer DOT edu |
| 14:24.23 | ep1220 | will take some time till HW is available anyway .. |
| 14:24.47 | ep1220 | kitno455: Thanks. I will take You up on this offer. |
| 14:24.58 | kitno455 | ep1220, send me email, i will notify you when i make tiffs of board |
| 14:25.03 | kitno455 | adios |
| 14:25.33 | ep1220 | will do |
| 14:25.35 | ep1220 | bye |
| 14:58.55 | *** join/#openjtag ByronT-Away (byrontodd@ByronT.nslu2-linux) |
| 16:32.14 | *** join/#openjtag Tiersten_ (tman@Tiersten.nslu2-linux) |
| 18:15.01 | *** join/#openjtag beewoolie-afk (~beewoolie@florence.buici.com) |
| 18:17.03 | beewoolie-afk | prpplague: hey man |
| 19:24.29 | *** join/#openjtag Tiersten_ (tman@Tiersten.nslu2-linux) |
| 19:44.55 | prpplague | beewoolie: hey |
| 19:48.05 | beewoolie | prpplague: Hey. We're on openslug talking about some things. |
| 19:48.23 | prpplague | ok |
| 19:48.34 | prpplague | sometime i would be interested in? |
| 19:48.37 | prpplague | thing |
| 21:45.33 | *** join/#openjtag kitno455 (~man@tfhs.net) |
| 22:07.13 | ka6sox-office | hiya kitno455 |
| 22:07.21 | kitno455 | re |
| 22:07.34 | kitno455 | whats up there |
| 22:08.00 | ka6sox-office | well...thinking about upgrades to the slug. |
| 22:08.05 | kitno455 | like? |
| 22:08.10 | kitno455 | ram/flash? |
| 22:08.21 | ka6sox-office | ya |
| 22:08.34 | ka6sox-office | and things like g2 and others are talking about |
| 22:08.35 | kitno455 | yeah, g2 asked me to look at traces |
| 22:08.45 | kitno455 | i have not had a chance |
| 22:09.06 | kitno455 | i dont really understand myself. |
| 22:09.28 | ka6sox-office | I definately don't understand myself.... |
| 22:09.35 | kitno455 | i like to play, but there are much easier ways to get small machine with 64 megs |
| 22:10.12 | ka6sox-office | stilll for under $100 (with mods) its pretty cheap. |
| 22:10.29 | kitno455 | sure |