| wolfspraul | wpwrak: aha, looks like full-speed USB is (almost) solved? | 00:46 |
|---|---|---|
| wpwrak | yeah, i think we're on a good track | 00:46 |
| wpwrak | how do you like the PR text ? (i just sent a patch) | 00:49 |
| wolfspraul | wpwrak: hmm. :-) I don't think it will achieve anything. | 01:09 |
| wolfspraul | a better text will not get it published | 01:10 |
| wolfspraul | but lemme read it thoroughly, now that it's written :-) | 01:10 |
| wpwrak | it's not so much about a better text but about having a bit of a narrative, and covering the essentials that make this project intersting | 01:16 |
| kristianpaul | hey, indeed a HHKB can save lot of space.. actually where is always hard have the M1 + logic analizer + +... next to you | 03:00 |
| kristianpaul | lars_: you manage to run that make timing ? | 04:21 |
| kristianpaul | interesting http://www.myhdl.org/doku.php/users:cfelton:projects:zpu?s[]=zpu | 04:26 |
| kristianpaul | okay, running 'trce -v 12 -fastpaths -o design_timing_report system.ncd system.pcf' inside boards/milkymist-one/synthesis/build seems generate the .twr file | 04:54 |
| kristianpaul | arggh, more non-free software we use :/ | 04:55 |
| kristianpaul | oh, http://pastebin.com/4Hup1djM slowest paths points mostly ddram/hpdmc | 04:57 |
| kristianpaul | notice this build was with ALL no esencial cores disabled | 04:58 |
| kristianpaul | he and same time fastest past is sdram. :_S | 04:58 |
| kristianpaul | better ignore this :) | 04:58 |
| wolfspraul | [05:27] [wolfspraul(+i)] [5:freenode/#milkymist [Act: 3,4,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,33,34,35,36,37,38,39,40,41,42,43] | 05:27 |
| wolfspraul | oops :-) sorry my notebook is breaking apart... speaker crackling, touchpad going crazy and mouse wildly selecting and clicking stuff, etc. | 05:28 |
| kristianpaul | wildly :-) | 05:36 |
| stekern | you have a lot of windows open in irssi at least ;) | 05:38 |
| kristianpaul | ;-) | 05:39 |
| kristianpaul | okay all settle for 65535000 Hz clock :-), including that libbase/board.c i missed before | 05:40 |
| Action: kristianpaul feels bad when writing CLOCK_DEDICATED_ROUTE = FALSE; :-| | 05:43 | |
| kristianpaul | but it should work anyway | 05:44 |
| kristianpaul | good now mm soc seems to work with gps receiver cloc :) | 06:32 |
| kristianpaul | indeed, using clk from memcard | 06:32 |
| kristianpaul | okay tomorrow try namuru soc and custom bios for it and see if the memory test pass ;-) | 06:33 |
| kristianpaul | s/soc/core ergg not yet | 06:34 |
| kristianpaul | hum mr 0xa0000000 system got freeze.. oh well, more todo :) | 06:42 |
| aw_ | lekernel, do you know what's the current choice of video decoder for rc4? still 7181B or another? | 08:05 |
| wolfspraul | 7181c | 08:24 |
| wpwrak | hmm. i've started to try to read this in "leet" :) "libic" ... ? | 08:26 |
| wolfspraul | aw_: definitely switch to 7181C, if you haven't sourced them yet please add to the list. should be a drop-in replacement plus removing the external antialias filter (capacitors and ferrite beads near the video connectors) | 08:27 |
| aw_ | wolfspraul, okay | 08:28 |
| wolfspraul | I am a bit confused as to the final reset circuit proposal now. I think it's the 4.0v reset ic plus new USB power switch. | 08:29 |
| wolfspraul | that definitely needs a thorough design verification | 08:30 |
| wpwrak | agreed :) | 08:30 |
| wpwrak | still needs lekernel's consent | 08:31 |
| wolfspraul | but it seems the 3-input reset ic idea is off the table right now? | 08:37 |
| xiangfu | wpwrak, can you post your latest flickernoise.fbi somewhere. I just want test my 2 itf keyboard and full-speed mouse. | 08:38 |
| wpwrak | unless someone wants to bring it back. the single-input seems sufficient, once we protect the 5 V rail. | 08:39 |
| wolfspraul | wpwrak: can we already safely assume we will not find USB-related electrical problems and improvements? | 08:39 |
| wpwrak | wolfspraul: no, not yet | 08:39 |
| wpwrak | xiangfu: this is for 2 itf (fs still broken): http://downloads.qi-hardware.com/people/werner/tmp/flickernoise.fbi.bz2 | 08:40 |
| wpwrak | xiangfu: i'll clean up the one with full-speed in a bit | 08:40 |
| wpwrak | bbiab | 08:40 |
| xiangfu | great. | 08:42 |
| aw_ | hmm..ADV7181CBSTZ is only available One piece in Digikey. Else vendor this time I need to try. like Verical, Avnet Express or Arrow. | 08:47 |
| wolfspraul | try octopart, you can get a quick overview who else might have it | 08:50 |
| aw_ | yes, tried octopart already and listed above i can source. ;-) | 08:51 |
| wolfspraul | looks available here and there | 08:51 |
| wolfspraul | arrow maybe? | 08:51 |
| xiangfu | wpwrak, (fs still broken) can't boot to GUI. stop at "I: Booting..." | 08:52 |
| aw_ | I can combine them to my cart, but not now. since my mouser cart had have some parts to be ordered. now I need to decide transfer those parts to that vendors who also have 7181C. | 08:53 |
| aw_ | no worries, but I just don't know the new USB power switch that if we need to prepare/source few pcs now? or still needs lekernel's consent? | 08:54 |
| aw_ | wolfspraul wpwrak so i think that I can stay for a while to place orders until USB-related problem becomes more clear then. | 09:05 |
| wpwrak | back | 09:09 |
| wpwrak | lemme see about that switch ... | 09:09 |
| wpwrak | ah wait. it's not thw switch but the codec. good :) | 09:10 |
| wolfspraul | aw_: you can get 5 of that USB power switch now | 09:10 |
| wolfspraul | it only costs a few USD, shipping costs will be far higher if that's the one thing missing one day | 09:10 |
| wolfspraul | a few USD for all 5 | 09:10 |
| wolfspraul | so even if it's only under consideration now, let's say likelihood to use 50%, it's already best to just include at the next good opportunity, just 3-5 or so | 09:11 |
| wolfspraul | the same may be true for the proposed 3-state power monitor ic, if it's easy to buy just include a few | 09:11 |
| wolfspraul | even if the likelihood of using that one in rc4 only looks like 10% to me now | 09:12 |
| wolfspraul | can you confirm the exact part numbers for those 2? | 09:12 |
| wpwrak | (3-way power monitor) we'd have to choose which one. depends on the tolerances of the various voltage rails, etc. | 09:12 |
| GitHub119 | [scripts] xiangfu pushed 1 new commit to master: http://git.io/ElwhoA | 09:13 |
| GitHub119 | [scripts/master] compile flickernoise: make clean before compile test image - Xiangfu Liu | 09:13 |
| aw_ | hmm...so seems that we can include few parts both 3-state power monitor and usb-related | 09:13 |
| wpwrak | aw_: you already have the 4.0 V version of the single input reset chip ? | 09:15 |
| wolfspraul | ok, sounds like leave the 3-state ic out now, too many uncertainties | 09:16 |
| wolfspraul | but the usb power switch is easier, and more likely to be used | 09:16 |
| aw_ | wpwrak, in my Mouser cart now. ;-) haven't clicked 'purchase' btn. ;-) | 09:17 |
| aw_ | wpwrak, do you think that what type of EN <enable pin> acted as HIGH or LOW? for http://www.diodes.com/datasheets/AP2142A_52A.pdf | 09:21 |
| aw_ | wpwrak, or still too far away to know it now. ;-) | 09:22 |
| wpwrak | what state are the FPGA's pins in after reset ? Z ? pull-up ? | 09:23 |
| aw_ | hmm..good question. don't know after reset. | 09:24 |
| wpwrak | if it's pull-up, pick active-low. if it's Z, toss a coin and add a pull up/down :) | 09:27 |
| aw_ | ha... | 09:30 |
| wpwrak | grmbl. and now xiangfu is hiding again :-( | 09:33 |
| wpwrak | anyway, here's a binary for double itf and fs: http://downloads.qi-hardware.com/people/werner/tmp/flickernoise-fs.fbi.bz2 | 09:33 |
| wpwrak | full-speed is very shaky. loses characters, can get garbage, can get endless auto-repeat. but if you type very slowly, it almost works ;-) | 09:34 |
| wpwrak | of course, all these problems are what a stack that now has zero error detection richly deserves :) | 09:35 |
| lekernel | yes, let's try the USB power switch | 09:46 |
| lekernel | but can it just power the ports all the time? | 09:46 |
| wpwrak | you mean you don't want to be able to switch them off ? | 09:47 |
| lekernel | why bother? | 09:47 |
| wpwrak | i'd keep them off when starting. make sure we don't have unnecessary drain | 09:47 |
| wpwrak | then flip them on (and keep them on) | 09:48 |
| lekernel | we can't detect the pull up resistor if we don't have VBUS | 09:48 |
| wpwrak | sure. first thing you'd do once you get out of standby would be to turn VUSB on | 09:48 |
| lekernel | why turn it after standby? | 09:49 |
| wpwrak | also, the ability to power-cycle troublesome devices may be handy at times | 09:49 |
| lekernel | just unplug/replug | 09:50 |
| wpwrak | (stby) well, or when entering the stby loop. though i see littler point in powering USB at this time. but okay, there are usb-powered gadgets you may want to use. LED fans and such ;-) | 09:50 |
| wpwrak | by software :) | 09:51 |
| lekernel | no, that's additional complications | 09:51 |
| wpwrak | c'mon :) | 09:51 |
| lekernel | many laptops don't even have this capability | 09:51 |
| wpwrak | but the mighty M1 will have it ;-) | 09:52 |
| lekernel | and some also immediately turn off if you short VBUS, btw :) | 09:52 |
| wpwrak | yeah. there are plenty of examples out there one better doesn't copy from ;-)) | 09:52 |
| lekernel | I don't want involvements with glitches etc. messing up devices when the FPGA reconfigures or such | 09:53 |
| lekernel | we power the ports all the time | 09:53 |
| lekernel | simpler | 09:53 |
| lekernel | this is what the current hardware does, and there hasn't been any problem with this | 09:53 |
| wpwrak | how about 0402 footprint to unused pins and pull-up/down at the switch. then the on/off can be added later. i.e., when we hit that situation where it is a problem ;-) | 09:54 |
| lekernel | that switch should simply act as an inrush current limiter | 09:54 |
| wpwrak | does that sound good ? that way, you get your "always on" switch, but if we ever think that we need a real switch, it's a 30 seconds upgrade | 09:57 |
| wpwrak | and all at a cost of a few picocents :) | 09:58 |
| lekernel | so, by default the switch won't be connected to the fpga? | 09:59 |
| lekernel | also, putting more traces under the BGA takes time | 09:59 |
| lekernel | and increases risk if there are other traces to be moved ... | 09:59 |
| aw_ | the two ENs for AP2142A/AP2152A yes needs low frequency(even stable as DC) control bins which traces added under BGA, yeah...surely it will have a risk if add. I don't think adding these two routes will get serious trouble if really think it's a great idea. | 10:15 |
| wolfspraul | I think we should remove standby altogether | 10:52 |
| Action: lekernel is packing bags for Norway | 10:58 | |
| wolfspraul | cool | 10:58 |
| wolfspraul | piksel? | 10:58 |
| wolfspraul | have you heard anything from the security conference and the m1 there? | 10:58 |
| lekernel | yes, piksel | 10:59 |
| lekernel | and no | 10:59 |
| kristianpaul | btw bios have gdb vesion or something? i wonder now how to debug hangs/freezes when running commands (like simple mr mw) from bios | 11:53 |
| wpwrak | sorry, needed one more nap. resume is difficult this morning :) | 12:17 |
| wpwrak | (switch) yes, unconnected by default. regarding the traces, there's major rerouting anyway with the DVI-I, so it shouldn't be a big deal. unless, of course, the overall complexity is already at the limit. | 12:18 |
| wolfspraul | yes I think for routing right now we just make a wishlist, then we see what the layout folks say | 12:23 |
| wolfspraul | there is also the idea of leds at the ports... | 12:23 |
| wpwrak | yes. blinkenlights ! :) | 12:24 |
| wpwrak | also on the full swing side of each path to a LED, add a TP | 12:24 |
| wpwrak | that way, we can use LEDs as scope triggers | 12:25 |
| wolfspraul | full swing side? | 12:25 |
| wpwrak | the side before the LED-R combo. where you get 0-3.3 V (or whatever the voltage) | 12:26 |
| wpwrak | as opposed to putting the TP right next to the LED, where it may only see ~2 V peak-to-peak (depends on how the LED is connected to the R) | 12:26 |
| lekernel | hmm, LED capacitance could be a little problem here | 12:27 |
| lekernel | at least if you want precise triggers without unsoldering the LEDs | 12:27 |
| wpwrak | was more thinking of "in the area" triggers | 12:28 |
| wpwrak | a few ns more or less don't matter there. even a few us would be fine. | 12:28 |
| wolfspraul | ok let's make it more real | 12:28 |
| wpwrak | things like "when is a SETUP being sent", because the scope can't tell a SETUP from a SOF :) | 12:28 |
| wolfspraul | can we enumerate the ports? | 12:29 |
| wolfspraul | which color? | 12:29 |
| wpwrak | which color looks good through the case ? | 12:29 |
| wpwrak | ideally, it would be one LED per external connector | 12:30 |
| wolfspraul | behind the connector? next to it? which side? | 12:31 |
| wolfspraul | on the bottom side of the pcb? :-) (just for completeness, I think we should not add more stuff to the bottom) | 12:31 |
| wolfspraul | can you take a board png and just mark all places where you want to have one? :-) | 12:32 |
| wpwrak | hmm, tricky. i need to compare this with the real device to see where there is room. and my M1 can't be moved at the moment, with lots of cables hanging out of its brain | 12:34 |
| wpwrak | and yes, next to the connector, so that it can be seen from the outside | 12:35 |
| wpwrak | lekernel: btw, doesn't the LV3 have USB in and out (for chaining) ? if yes, does this mean it has a hub inside ? | 12:42 |
| lekernel | no, it does not | 12:48 |
| lekernel | not everyone is this perverted :p | 12:48 |
| wpwrak | heh ;-) but it does have an USB out port ? or does it use some proprietary bus ? | 12:50 |
| wpwrak | (or was that chaining interface a misunderstanding of a reviewer) | 12:50 |
| wpwrak | ? | 12:50 |
| lekernel | it has nothing for chaining | 12:51 |
| wpwrak | ah, i see. good :) | 12:51 |
| lekernel | wpwrak: how about computing the crc byte per byte in usb_rx? instead of just busy waiting | 12:55 |
| lekernel | we have 32 AVR cycles per byte | 12:55 |
| lekernel | most instructions are 1 cycle | 12:55 |
| lekernel | and yes, it's messy, but doing these things in verilog would be worse | 12:56 |
| lekernel | the navre timing is 100% predictable, there's no DRAM, shared bus or interrupts | 12:59 |
| wpwrak | so navre runs at 48 Mhz ? | 13:00 |
| lekernel | yes | 13:00 |
| lekernel | and it might be possible to push the frequency a bit | 13:00 |
| wpwrak | ah, good. that's better than i expected. hmm. | 13:00 |
| wpwrak | heh, the fastest avr in all mexico ;-) | 13:01 |
| lekernel | maybe up to the 70-80MHz range | 13:01 |
| lekernel | but if we do that, we should also keep a frequency that is a multiple of 12, otherwise the timing becomes less predictable | 13:01 |
| lekernel | and we pick up some latency in slightly messy clock domain transfers | 13:02 |
| wpwrak | i suppose you could unroll usb_rx to solve problems one at a time. still a bit hairy, though. there's data FIFO, no ? | 13:02 |
| wpwrak | (12 Mhz) sure | 13:02 |
| lekernel | no, there's no FIFO | 13:03 |
| lekernel | just one byte of buffering | 13:03 |
| wpwrak | ah, interesting | 13:03 |
| lekernel | well, the CPU timing is totally predictable, and the devices only transmit when asked. so there should be no need for a FIFO | 13:03 |
| wpwrak | yes, as long as the latency is under control, that's right | 13:04 |
| wpwrak | also makes some of the timing easier to understand | 13:05 |
| wpwrak | e.g., it would get messy if you got into usb_rx already with half the packet backlogged in a FIFO | 13:05 |
| lekernel | plane time... bbl | 13:18 |
| sh4rm4 | is milkymist using an AVR cpu for usb ? | 16:41 |
| wpwrak | hmm, would be nice if "web update" would say from which date things will be. in fact, the version number seems kinda useless since the versions aren't being bumped | 16:43 |
| wpwrak | sh4rm4: yes. it has "hardware" for the bit-level operations, but once there are bytes, the avr takes over | 16:44 |
| kristianpaul | sh4rm4: yes and not is called navre and is scratch implementationto be compatible with gnu-avr, so usb is implemented in a kind of "microcode" | 16:45 |
| kristianpaul | from scratch* | 16:45 |
| kristianpaul | hardware is the SIE no? | 16:45 |
| sh4rm4 | so it is a custom softcpu ? | 16:45 |
| kristianpaul | dunno if there are custom instructions | 16:46 |
| sh4rm4 | custom as in IP-free | 16:47 |
| kristianpaul | i hope ;) | 16:48 |
| wpwrak | kristianpaul: the mega-confusingly named softusb_sie ? yes, that's part of it | 16:49 |
| kristianpaul | hey we can actually said then milkymist soc is three core,lm32, fpu and navre | 16:53 |
| wpwrak | 1, the only triple-core VJ workstation :) | 16:55 |
| wpwrak | s/1/M1/ | 16:55 |
| kristianpaul | yay | 16:56 |
| kristianpaul | wpwrak: oh, yes you pixel procesor sounds really nice | 16:58 |
| wpwrak | up north ? :) | 17:12 |
| sb0 | yes | 17:20 |
| sb0 | on the airport bus | 17:20 |
| wpwrak | do they have snow yet ? ;-) | 17:20 |
| sb0 | no, and it's actually a tad warmer than berlin | 17:22 |
| wpwrak | must be the sea | 17:23 |
| kristianpaul | 20 C are always perfect :) | 17:28 |
| juliusb | not sure if this has been asked before, but are you guys able to run the Arduino/Wiring stuff on navre? | 20:29 |
| juliusb | I'm not too up on the AVR ISA and what the Navre supports, but that would be interesting | 20:29 |
| kristianpaul | i think papillio boards are better example for such compatiblity/example | 20:30 |
| juliusb | what are those things? google just brings up links to birkenstocks :P | 20:33 |
| juliusb | i think i've heard of what you mean, but it's not papillio | 20:33 |
| juliusb | it's similar... | 20:33 |
| kristianpaul | he, sorry typos | 20:35 |
| kristianpaul | juliusb: http://papilio.cc/ | 20:35 |
| kristianpaul | i think that what you want | 20:35 |
| juliusb | ah right yeah | 20:36 |
| juliusb | ok that looks cool, but I mean, could the Wiring stuff, as it is, run on say, the Navre in milkymist? Support for it it might make the M1 a good buy as an educational tool for beginners | 20:37 |
| juliusb | would basically give you the simple IDE to push the LEDs/IOs/analog around | 20:38 |
| juliusb | anyway, just a thought, but I reckon it's pretty good, and the way it has drawn in a lot of users under the guide of the Arduino is impressive | 20:38 |
| kristianpaul | i think already with wiring or not milkymist have a LOT of stuff for been an educational tool | 20:43 |
| juliusb | yep, but with Wiring you can basically piggy-back onto the Arduino bandwagon in a way | 20:43 |
| kristianpaul | but may be you mean been able to run processing on the M1, that will be killer, but kinda hard to port currently (java, c++, etc..) | 20:43 |
| juliusb | i think the accessibility, and simplicity of the interface is a winner, and has to be shown to be so | 20:44 |
| juliusb | mmm yeah actually id on't fully understand the Wiring/processing thing | 20:44 |
| juliusb | afaict the Wiring stuff provides the IDE and the I/O drivers | 20:45 |
| juliusb | what does processing do then? | 20:45 |
| kristianpaul | sure, simplify FN is important i think in the ML wpwrak mentioned something about aliases or self adjust to make things easier, | 20:46 |
| juliusb | ah i see, processing is very java oriented | 20:49 |
| juliusb | mm, I guess I don't quite understand how it does what it does at the moment | 20:49 |
| kristianpaul | visuals | 20:51 |
| kristianpaul | effects, shapes,, drawing and lots of libraries to make rich the process | 20:51 |
| kristianpaul | not couting the examples and clean documentation in the web page | 20:51 |
| juliusb | mmm, fair enough | 20:53 |
| mwalle | just for the logs: +1 for software controlled USB enable signals | 23:13 |
| mwalle | s/w controlled stuff makes test automation easier :) | 23:14 |
| wpwrak | mwalle: since sebastien isn't listening: my evil plan is to make it really easy to just drop in the connecting 0Rs. basically just one mouse click when preparing the fab files ;-) | 23:14 |
| mwalle | if its possible, just add the lines to an IO, and don't use it, so per default its always on | 23:16 |
| mwalle | hopefully, this makes seb happy :) | 23:16 |
| wpwrak | sebastien doesn't want it connected to the FPGA. he's concerned about glitches and such. | 23:16 |
| mwalle | use some pullup or pulldown? | 23:18 |
| mwalle | external ones :) | 23:18 |
| wpwrak | what i proposed is to run the traces to the FPGA by have an unpopulated 0402 footprint in series with them. then add pull-up/down on the switch side to enable. | 23:19 |
| wpwrak | well, 2 x 0402 footprint | 23:20 |
| Action: mwalle votes for the same with popupated 0R resistors :) | 23:21 | |
| wpwrak | heh :) | 23:22 |
| roh | usb-enable signals? | 23:53 |
| roh | you mean for the 1.5k pullups? | 23:54 |
| --- Fri Nov 18 2011 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!