<wpwrak> we've had boards with trouble on NOR DQ5 and DQ7. that would be W4 and Y7, relatively far away
<wpwrak> lekernel_: one test to prove the DQ8-PROGRAM_B contamination hypothesis would be to pull PROGRAM_B high through ~100 Ohm. that should visibly affect DQ8 if the two are linked
<wpwrak> and the battle continues ! :)
<wpwrak> aw: i described the funny things o PROGRAM_B to joerg and he thinks this looks like ESD damage (or similar). he also thinks regular xray wouldn't show us anything. you'd need xray combined with a very good microscope to really identify such an issue.
<wpwrak> aw: so there's probably no use in taking the boards to be xrayed. that is, unless we find something else.
<aw> wpwrak, hmm....all good info to be considered. ;-) so a reset circuit would be likely as ESD damage or other circuits?
<wpwrak> aw: now, yesterday, we reached the "comfortable" conclusion that some of the I/O pads of the FPGA are damaged/fused. "comfortable", because this can explain pretty much anything. but i think we can easily verify whether there's really a "connection" from DQ8 to PROGRAM_B
<aw> wpwrak, btw, I'm keep on reworks, maybe needs another 1.5 hours can be done this morning firstly. Once I start to test, I'll go for 0x3c.
<wpwrak> aw: maybe the board was improperly handled at some point in time, apparently when some of the rework was done. as i understand it, both the fab and you had done part of the rework, so it may be difficult to track down the origin of the problem.
<aw> wpwrak, hmm..okay..a word of "comfortable" is good to explain that "connection".
<wpwrak> aw: before 0x3c, please have another look at 0x77. there's one test that should tell us if our analysis so far is correct: monitor TP36/PROGRAM_B and NOR pin 34, as before. then reproduce the "pulses" on PROGRAM_B.
<aw> wpwrak, i see. but don't forget your idea on removing D16 to checking the thinking of feedback of system transfer.
<aw> wpwrak, alright, I'll ping you once start to test though. ;-)
<wpwrak> aw:  and then, connect TP36 through 100 Ohm to 3V3. this should pull up PROGRAM_B. if DQ8 the signal that manipulates PROGRAM_B, then DQ8 should also be pulled up a bit
<aw> wpwrak, okay
<wpwrak> aw: (d16) removing d16 may make the problem disappear without solving it. so if we go to the point of removing components, i'd first remove the reset IC, then see if the problem still happens (i expect that it will)
<wpwrak> aw: only then remove d16 and see what happens. if the problem goes away, we may not have learned anything, because it may then simply happen too quickly to notice (and setting up the equipment to find the very first occurrence may be hard). only if it doesn't go away.
<wpwrak> tataa, my M1 is in brazil now (near sao paulo). getting close ;-)
<kristianpaul> wpwrak: :-)
<wpwrak> M1 has reached buenos aires ! now customs will sit on it for a day ...
<aw> wpwrak, sorry that I've not tested yet, just were interrupted from other tasks. the "available" of fix2 boards are all became "fix2b" ver. I'll start to test after lunch.
<aw> roh, hi, you sent me totally 21 pcs of case top cover (with m1 logo) in second shipment, right?
<wolfspraul> aw: should be 20 sets (packaged separately in plastic bags), plus some spare parts including an additional top acrylic, yes
<aw> mm...spare though...thanks.
<wpwrak> aw: ready for poking 0x77 ?
<aw> wpwrak, not yet
<wpwrak> time to crawl to bed ...
<errordeveloper> hello hello
<errordeveloper> lekernel_: did you know of this thing http://orcc.sourceforge.net/
<errordeveloper> looks like yet another HDL-related use of LLVM
<larsc_> errordeveloper: the llvm and hdl parts of that project seem to be orthogonal
<errordeveloper> ok ...
<errordeveloper> lekernel_: hm, anyhow .. that was a random thing I bumpend into
<errordeveloper> lekernel_: have you done any work with qemu ?
<errordeveloper> I'm trying to find some docs on how to code virtual devices for it and possibly co-simulate say a simple device in HDL and it's driver
<errordeveloper> larsc_: I just noticed that it was your reply, not lekernel_'s .. :)
<errordeveloper> larsc_: how are you doing anyway ?
<lekernel_> hmm, interesting
<lekernel_> except it's eclipse-based
<lekernel_> Orcc requires the Eclipse environment, which runs on the Java platform. I
<lekernel_> beuargh
<lekernel_> why didn't they simply write a stand-alone command-line compiler? ...this whole focus on Eclipse looks like a warning sign to me
<lekernel_> first, Eclipse (and Java) are bloated and poorly designed, second, they are irrelevant to writing an efficient code generator
<lekernel_> but well... maybe it's simply poorly documented and there's good stuff in it
<Fallenou> is Eclipse more bloated than ISE ?
<lekernel_> ah, it's academic... that helps explain the eclipse/java crap
<lekernel_> yes
<lekernel_> the bloat/functionality ratio of eclipse is much higher than that of ise
<Fallenou> wow
<Fallenou> impressive
<lekernel_> it seems serious, maybe the authors simply have read too much Sun propaganda
<Fallenou> is it a C program that looks like a java program ? :p
<Fallenou> yes it is
<Fallenou> nice :)
<Fallenou> funny the two imports does not make an error
<lekernel_> http://opendf.org
<lekernel_> http://opendf.org/lib/exe/fetch.php?media=howto:cal_language_report.pdf
<larsc> i recently read somebody arguing that linux kernel developers should switch away from comandline gcc and vi/emacs and use a proper tool like eclipse.
<larsc> and that was not academi
<lekernel_> Eclipse as a text editor/IDE isn't too bad (except for the massive bloat ofc), but I really don't understand people building complete programming tools _depending_ on it
<azonenberg> Except for the massive bloat? Lol
<azonenberg> And i dont usually do command line editing
<azonenberg> i normally use an X11 based editor like geany (with IDE features disabled) or gedit
<azonenberg> and then manually compile in command line gcc
<wpwrak> /nick richelieu
<wpwrak> azonenberg: so, an X11-based editor ? i wonder if that's enough to make the heresy charge stick ...
<azonenberg> lol
<azonenberg> I do use nano on a routine basis
<azonenberg> but i like my mouse tyvm
<azonenberg> for editing
<larsc> i prefer vim, because i don't have to switch between mouse and keyboard
<wpwrak> mouse, n.: computer peripheral to set the input focus to the xterm of the user's choice
<errordeveloper> lekernel_: I'm not an eclipse supporter either ...
<larsc> wpwrak: i though that's what 'ctrl+a n' is for
<wpwrak> larsc: ;-)
<azonenberg> wpwrak: The big thing i like about X based editors is the ability to respond to a mouse scroll wheel
<azonenberg> as well as higher resolution than any of my framebuffer modes support
<wpwrak> azonenberg: oh, i like the ability to have multiple xterms in view at the same time. i have a triple-head setup. usually have ~6-12 xterms visible at any given moment. each head (screen) has a 4x4 array of virtual screens. e.g., xchat shares its space with a few xterms with mutt reading my inbox, plus a few xterms for very short-liven activities (kinda post-its). the next virtual screen has 6 large xterms with mutts reading various threa
<wpwrak> ds of the qi-hw lists. another has a web browser. etc. that's the left screen. the middle screen has the editing/development i do. e.g, right now, six xterms, one kicad, and fped overlaid (it's a bit crowded).
<kristianpaul> likes a lot his byobu + vim
<kristianpaul> but yeah with a larger screen ratpoison will fit very well :-)
<aw_> rc3: 5 boards - 0x30, 0x33, 0x35, 0x37, 0x38 with fix2b are happy from previous "available" with fix2 version.
<wpwrak> aw_: any boards that regressed after fix2b ?
<aw_> since the notes may hard to realize/understand easily, you can just see the http://en.qi-hardware.com/wiki/Milkymist_One_run_3_schedule#Test_Results
<aw_> I collected those PASSs and FAILs with two catagory , so you can see it.
<aw_> wpwrak, so far no regressed happened yet. ;-)
<aw_> I'll follow MAC address number to test, so you can know it.
<wpwrak> ah, nice summary
<aw_> wpwrak, tomorrow morning let's go for a little experiments on 0x77 or 0x3c firstly but not whole day even not half day.
<aw_> and sorry that other tasks to be done so that didn't go through that failed board.
<wpwrak> alright, i'll be around. your morning is good. i can't stay up all night for it anyway. not with fedex coming the next day :)
<aw_> and i gotta go sleep.
<aw_> wpwrak, yup
<aw_> wpwrak, you should get fedex one probably by tomorrow. Good luck.
<errordeveloper> title is supposed to be self-explanatory :)
<errordeveloper> lekernel_: that's follow-up to my earlier qemu question
<errordeveloper> well, I think I found the answer ;)
<wpwrak> M1 cleared customs ! tomorrow it'll be mine :)
<kristianpaul> wpwrak: :_D
<kristianpaul> wpwrak: You'll have more colored/animated parties after M1 arrival ;-)
<wpwrak> i'm counting on it ;-) i'll probably have to get a projector and paint the terrace walls a nice white. the old paint is dirty and fissured anyway.