#milkymist IRC log for Saturday, 2011-08-27

wpwrakkristianpaul: hmm ? which comments ?00:09
wpwrakah, L19 is our old friend. didn't remember the number.00:24
kristianpaulwpwrak: kristianpaul why rc3 worst run? more hardware more issues pop, that is not a hiden secret i guess21:3100:44
wpwrakkristianpaul: oh, but it is like this. more boards, deeper testing, new users. this inevitably brings out more bugs.00:45
kristianpaulwpwrak: sure00:45
wpwrakand M1 is a complex device, which means many opportunities for issues00:47
wpwrakwolfspraul: hey, how was clubbing ?02:05
wpwrakdid the crowd give standing ovations, clapping their hands and shouting "emm-one ! emm-one !" ? :)02:06
wolfspraulha02:06
wolfspraulI think you don't want to hear me characterize the event :-)02:06
wolfspraulno but it's ok. Jon and I just showed our faces, and we will demo the m1 at a meeting in a restaurant where the nightlife guys meet regularly to 'be real' in a few days02:07
wpwrakwhat was it ? the local cumbia-reggaton fusion event ?02:07
wpwrak;-)02:07
wolfspraulit was the opening of a club, from that records company02:07
wolfspraulthe speakers were 'pathetic' (jon's words)02:07
wolfspraulno DJ there02:07
wpwrakheh ;-)02:07
wolfspraulthe audience was 20-30 'vip' guests (i.e. random friends and acquaintances of record label staff)02:08
wpwraka records company needs no dj. they have records ! ;-)))02:08
wpwrakall 50+ ? :)02:08
wolfspraulkeep in mind it's china...02:08
wolfsprauloh no, all young02:08
wpwrakyeah, i begin to imagine :)02:08
wolfspraulbut no magazine journalists02:08
wolfspraula super prime location though02:08
wpwrakat least the right age group then :)02:08
wpwrakwas there a bar ?02:08
wolfsprauland this label is serious, they do all sorts of things02:09
wolfspraulyes sure02:09
wolfspraullots of alcohol02:09
wolfspraulfree too :-)02:09
wpwrakexcellent02:09
wpwrakeven better ! :)02:09
wolfspraulbut I only had a bottle of water02:09
wpwrakeek02:09
wolfspraulthis was just to show up and say hi. Jon and i left after an hour and will demo the m1 at daylight asap.02:09
wolfspraul(that was the plan before)02:09
wpwrak:)02:10
wolfspraulthe record label is doing electronic music, very rare in china02:10
wolfspraulthey are essentially the only one such label in China :-)02:10
wpwrakstill no reason not to have a drink or five. there's a lot you can do in one hour :)02:10
wpwrakwow02:10
wolfspraulhttp://www.acupuncture-records.com/?lang=en02:11
wolfspraulso maybe they could buy some m1, yes. and once it's in their clubs or events, others would see them, etc.02:11
wolfspraulbut it's China, and my expectations are realistic. it's far more important that we sell in the US and Europe.02:12
wolfspraulthe scene here is small (but growing)02:12
wpwrakalways nice if you can sell locally02:12
wpwrakwell, meanwhile, we've had a bit of a party here, too02:12
wpwrakbefore, i had used my battery-powered kaossilator to feed sound to the M102:13
wpwrakthen i connected my stereo. M1 didn't show any response to the audio signal.02:13
wpwraki went back to the kaossilator. and now it didn't respond either. hmm.02:14
wpwrakso i power-cycled02:14
wpwrakthat brought audio in back. so i disconnected the kaossilator and tried the stereo again. this time the M1 simply froze. (no reaction to mouse or such)02:15
wolfspraulgo on :-) should I act surprised? :-)02:16
wpwrakagain, power-cycling brought it back to life. a third attempt left me without audio again, and also no audio with the kaossilator.02:16
wpwrakpower-cycling solved that, too. well, as it turns out, audio has its own part of the ground plane, just like video has.02:16
wpwrakand it's connected via a bead (L3), just like video was (L19)02:17
wpwraknow i can refer to L3 in my M1 in the past tense as well, and i'm happy to report that it now works flawlessly with audio from the stereo :)02:17
wolfspraulexcellent02:18
wolfspraulanother rework, and that IS GREAT!02:18
wolfspraulso we remove L3 as well?02:18
wolfspraulshort it?02:18
wpwrakyup :) better now than later ;-)02:18
wpwrakshort it02:18
wolfsprauloh absolutely02:18
wolfspraulthank you so much!02:18
wpwrakit's easy reach and quite isolated02:18
wpwraks/easy/easy to/02:19
wolfspraulI am not surprised, knowing how we got here. there will be more bugs...02:19
wolfspraulbut this one is great, definitely (the fix)02:19
wpwraknp. sebastien figured out the culprit actually even while i was still describing the symptoms. we're getting quicker ;-)02:19
wolfspraulwell it's perfect02:20
wolfspraulanything else you found not working so far?02:20
wpwraksome usability issues that are probably just software. and a narrowly missed opportunity for a nicer keyboard solution (should be sw-fixable, though)02:21
wpwrakhaven't tried either yet. and i don't have MIDI nor DMX.02:21
wolfspraulin general we need to be on the lookout for more hardware bugs02:22
wolfspraulif something acts weird, even just once, there's a good chance it could be improved in hardware02:23
wpwrakah, and I got joerg to look at the schematics. he did some grumbling about ESD protection and we had some fun imagining various catastrophic failures due to mismatched grounds coming in from the various peripherals02:23
wolfspraulany suggestions for improvement?02:23
wpwrakyes ... he thinks R11 should be 0R02:24
wolfspraulI think it's good that we leave jtag-serial in for all rc302:24
wolfspraulwe don't know how many will be bought by developers, how many by pure users02:24
wolfspraulthat's a logistical problem02:24
wolfspraulideally we get 50% devs, 50% pure users02:24
wpwrakwith the current R11, you lose stereo separation on the CD input (from the header)02:24
wolfsprauland the devs give solid feedback, unlike how we mismanaged 90% of rc202:25
wolfspraulif we can get that going, it'll be a great product in a little while02:25
wpwrakwhy do you think the devs now will give better feedback than the ones who bought rc2 ?02:25
wolfspraulyou think we should 0R 11R for rc3 already?02:25
wolfspraulit's a matter of management, following up with people02:25
wolfspraulalso with the accessories the product becomes more usable, lowering the boundaries of having fun with it02:26
wpwrakjoerg also suggests to add about 2 x 50 pF to line in (R and L), for ESD and HF protection. that's a little trickier. you could just piggy-back them on the resistors, though.02:27
wolfspraulI meant 0R for R11. did you do it on your board?02:27
wpwrak(R11) no, i didn't do it. so far, i don't have a CD in scenario, so it doesn't matter02:27
wpwraki don't know how important CD in is in the overall picture02:28
wolfspraulis there any reasonable risk in removing R11?02:28
wolfspraulwhat do you mean with "CD input"?02:28
wpwrakif it was me, i'd probably just document the problem and no spend time on it :)02:28
wolfsprauloh, the expansion header. got it.02:28
wpwrakthere are input signals for "CD"02:29
wpwrakyes02:29
wolfspraulwe can do that in rc402:29
wolfspraulwait, lemme take notes somewhere02:29
wpwrakyeah, sounds good to me. it's a simple fix but still02:29
wpwrakjoerg would put ~50 pF in parallel to R23 and R24, to filter HF and to absorb ESD (there's no ESD protection on line in)02:31
wolfspraulhttp://en.qi-hardware.com/wiki/Milkymist_One_RC3_Known_Issues02:32
wolfsprauladded at the top02:32
wpwrakin fact he'd change the whole line to an active circuit, with a transistor to provide better GND decoupling and acting as a victim component in case of a major ESD mishap02:32
wpwrakit may be worth noting that ground loops on audio, which the M1 should welcome rather eagerly, can be avoided with a "DI box": http://en.wikipedia.org/wiki/DI_unit02:34
wpwrakin its simplest form, that's basically a transformer, providing nice galvanic isolation02:34
wpwrakpeople who do stage work apparently know these little devices very well02:35
wpwrakbut it may be a good FAQ item to have anyway. until the audio circuit is perhaps improved02:36
wpwrakhe suggests to use a Zener for D4, to also add overvoltage protection02:37
wpwrakdo you know why there are two Zeners on the 5 V input (D14 and D15) and not just one ?02:37
wolfspraulthat was the overvoltage protection I think02:38
wolfspraulone wasn't enough02:38
wolfspraulwell all suggestions are welcome, especially in forms that they become action items for me. i.e.: dumbed down :-)02:39
wpwrakwhy was one not enough ?02:39
wolfspraultoo bad the electrical is still in Altium02:39
wpwrak(D4) consider replacing with 2V2 zener :)02:40
wpwrak(altium) oh yes02:40
wolfspraulhttp://en.qi-hardware.com/wiki/Protection_of_Reversed_Polarity_on_DC_plug-in02:40
wpwrakhe also found the buttons suspicious: they have some ESD protection of the case with C122 and R47, yet the button signals themselves aren't protected. what makes them so much safer, if you already expect something to jump into the button ? :)02:41
wolfspraulI want to avoid collecting all sorts of 'opinions' unless they are condensed into real action items02:43
wolfspraulwhat I've found is that in electrical, you ask 10 ee's, and they all have slightly different preferences to tweak the circuit this or that way02:43
wolfspraulquite annoying. even worse than writer only code.02:43
wolfspraulso whenever a new EE comes in, there's all these 'improvements' that have to be done here and there, because of the experience of that EE02:44
wolfspraulbut that will never stop :-)02:44
wolfspraulwhenever a new ee looks at it there is more02:44
wolfsprauland it's changed and changed and changed. seems ee's cannot easily agree on what is 'best'02:44
wpwrakyeah :) i already distilled things a little, down to the things that seem mysterious or those that look like real issues02:44
wpwrakEE is no exact science ;-)02:44
wolfsprauloh sure it's ok, just after my years I've noticed this02:44
wolfspraulat the beginning I still thought you make multiple ees work together for the best result02:45
wolfspraulnow I know that will never happen02:45
wpwrak;-))02:45
wolfspraulthey will change and overwrite each others suggestions at infinite02:45
wpwraklock them in a room, take the advice of the one who survives ;-)02:45
wolfspraulso I need action items :-)02:45
wolfspraulwhat do we want to change, and when02:45
wolfspraulL3 is for rc3 - perfect02:46
wolfspraulR11 and maybe R23/R23 for rc402:46
wolfspraulhttp://en.qi-hardware.com/wiki/Milkymist_One_RC3_Known_Issues02:46
wolfspraulthose sound like small and clear improvements to me02:46
wolfspraulthen... DI box? that's external I guess02:46
wolfsprauldo something with D4?02:46
wolfspraulothers?02:46
wpwrakthe two zener diodes (D14+D15) seem dubious. most likely, one conducts and the other is just idle. if the loaded one blows, and it fails open (not shorted), then the other one gets roasted02:46
wolfspraulme: wait and see :-)02:46
wolfspraulAdam spent an ungodly amount of time on that protection circuit02:47
wolfspraulthere's no way he will get back to it unless someone else comes up with the 'perfect one' and we just switch to that02:47
wolfspraulin fact the protection circuit was one of the main mistakes between rc2 and rc302:47
wolfspraullots of time waste with little value added02:48
wpwrakyeah, we would be good to know the full story. the purpose still seems a little unclear. if it's just to have a backup, fine. if they're both needed, that sounds like trouble.02:48
wolfspraulthat wiki page I linked lists some of the painful history and experiments02:48
wpwrakoh, i think it's essential. people will connect incorrect power supplies.02:48
wolfspraulmost (false) measurements got deleted, luckily02:48
wolfspraulit's all here: http://en.qi-hardware.com/wiki/Protection_of_Reversed_Polarity_on_DC_plug-in02:49
wolfspraulAdam will not go back to touch this.02:49
wpwrakalas, the explanations on Protection_of_Reversed_Polarity_on_DC_plug-in stop at version C. the 2nd diode was added in D :)02:50
wpwrakanyway, joerg also suggested fuses for USB downstream power and ESD protection for VGA02:51
wpwraknone of this rc3 items, obviously02:51
wolfspraulI need patches02:52
wolfspraulare those 3 what we have now? http://en.qi-hardware.com/wiki/Milkymist_One_RC3_Known_Issues02:52
wolfspraul(at the top)02:52
wolfspraulshould we add more?02:52
wpwrak(DI box) yes, external. if you get ground hum with the M1, then you'll need such a box to make the humming stop. (or rearrange your equipment, but good luck with that :)02:53
wolfspraulbut once it moves to opinions, I suggest to wait until it's real02:53
wpwraks/loose/lose/ :)02:53
wolfspraultrying to act upon opinions will only confuse others02:53
wpwrakyup these are the reworkable items02:53
wolfspraulso either it's a proper schematic diff, or we cannot act upon it02:53
wolfspraulseems the D4 idea is next in line?02:53
wolfspraulfor the protection circuit, I really don't want Adam to sink any more time into that02:55
wolfspraulbetter or not, if someone has an idea for improvement, they have to send an actionable patch. otherwise it stays the way it is.02:55
wpwrak(opinion) well, there are two general directions: a) add ESD to anything that goes in and out, and b) apply galvanic separation liberally. M1 sits like a spider in a net of widely distributed devices. some of them will have very different ground potentials. it's bad to rely that all of _them_ do their homework and have galvanic separation.02:55
wolfspraulthat's because already 1-2 months were sank, and wasted, into this02:55
wpwrakwow ;-)02:55
wolfspraulyes sometimes one gets stuck. that's ok, but then someone needs to come in with a fresh view and clean it up. or it stays where it is, which I believe at least 'sort of' works.02:56
wolfspraulplus the typical 'ee override' problem02:56
wolfspraulevery ee comes in and says "all of a, b, c, d has to be changed urgently" :-)02:57
wolfspraulproblem is: it never stops, like you said ee is an unprecise science02:57
wolfspraulI'm fine with either esd or separation, it's all a matter of how real those problems are, and how big/expensive the components are that would address the issues inside m102:58
wolfspraullooking at other equipment might give indications02:58
wpwraki think these are all the things. if you want to fix the ground on audio, there's a more involved circuit he suggested. nothing too crazy, but some extra components. not sure if this could be an rc4 item, or something for later.02:58
wolfspraulsounds like something for later03:00
wpwrakDMX is a little scary. M1 has nothing there in terms of ground separation. all the USB-to-DMX boxes mention they're galvanically separate. which makes a lot of sense if we consider that lighting if usually far away and may even be on a completely different branch of the electrical installation03:00
wolfspraulmost important in rc4 is still the reset circuit (gates), adv7181c, L3/L1903:01
wpwrakyeah. probably better not to have new circuits in rc403:02
wolfsprauloh I'm fine, but it needs to come as a verified patch, not as an opinion03:02
wolfspraulas an opinion, I cannot process it03:02
wolfspraulso it just won't happen :-) no resources...03:02
wolfsprauljust staying real and giving honest feedback and expectations03:03
wolfspraulwe can add tons of ground, esd and what not protection on all i/o03:03
wpwrakoh, if you look at the backlog of the #qi-hw channel, you'll find joerg's detailed description of the audio circuit ;-)03:03
wolfspraulquestion is always: how real is the problem being addressed (compare to other devices in the market), size of components, price of components, who verifies the design and turns it into a clean schematics patch03:04
wpwrakbut i think it all depends on your schedule. if you have urgent things that need to go into rc4, then it would be a bad idea to add changes that have a risk of causing delays03:04
wolfspraullet's see it the other way round03:05
wolfspraulMilkymist One must never go out of stock anymore03:05
wpwrakthe risk is real. ground loops are a well-known and ages-old problem03:05
wpwrakhehe :)03:05
wolfspraulso the rcX schedule depends on sales03:05
wolfspraulif sales are slow, we can fit more and more into rc403:05
wolfspraulbecause rc4 will not happen :-)03:05
wolfspraulif sales are fast, rc4 will happen fast and things will be pushed into rc503:05
wolfspraulin general I try to start with the most valuable things first03:06
wolfspraulL3 being a good example :-)03:06
wolfspraulor the still badly designed reset circuit03:06
wpwrakthey're also relatively safe03:06
wolfsprauladv7181c supposedly 'drop in'03:06
wolfspraulI already know it will not be just 'drop in', but we have to get over it03:06
wpwrakprobably best to alternate "safe" with "potentially unsafe"03:07
wolfspraul'protection' is a relative thing, you know that03:07
wpwrakif things go wrong, you can always go back to the last "safe" version, without too much trouble03:07
wpwrakyes yes, protection is tricky03:07
wolfspraulsomeone wants to improve the overvoltage & polarity protection on DC in: great, do it. waiting for patch :-)03:07
wpwrakdo you need it ? will it be good enough ? etc.03:07
wolfspraulsomeone wants to improvem protection on line in/out, dmx, whatever: same. patch welcome.03:08
wolfspraulsee above. how real? what are others doing? size and price of components? solution verified or just 'an idea'? translated into clean schematics diff, or just 'rough idea'?03:09
wolfspraulI've learnt to not ask EEs for too many opinions. it's like asking for trouble.03:09
wolfspraulbecause you ask them, they have to say something03:09
wolfspraul"you could improve X"03:09
wpwrak;-)03:09
wolfspraulseriously03:09
wolfspraulthat's what I've learnt03:09
wolfspraulit's like you say, it's an unprecise science03:10
wolfsprauleverybody has their own experience, it's subtle03:10
wolfsprauldon't ask an ee for opinions03:10
wolfspraulinstead, always distill hard data and then see whether things can be improved03:10
wpwrakanyway, that's the list of things i got from joerg. maybe the buttons need clarification. something doesn't quite add up there. but maybe someone's just a little over-cautious on the button shell.03:10
wolfspraulfor the DC jack protection, we had a very clear goal03:10
wolfspraulwe wanted to make the m1 safe from people accidentally plugging the 12V camera supply into it03:11
wolfspraulwhich has the same mechanical jack03:11
wolfsprauland which we ship in the same box03:11
wolfspraulI think we achieved that. if you accidentally plug in the 12V supply, the M1 will not boot but should be safe. sort of. better don't try. :-)03:11
wolfspraulfor the other protection things you mentioned, I think best is if we can first demo the problem.03:11
wpwrakregarding the NOR things, adam did some 100 cycles without trouble. what we're not sure about is whether this was with standby locked (in which case the test might show that this helped, or maybe it just shows that nothing happened), or it was without locking (in which case the test shows that 100 tries are not enough to make things happen)03:11
wpwrak(12 V) yes :)03:12
wolfspraulwhy are we not sure? I'm pretty sure it was with a locked standby03:12
wolfspraulwe doubt that the locking worked?03:12
wpwrak(not sure) because adam vanished before we could ask him ;-)03:12
wolfsprauladam reflashed and locked both 4C and 7C03:12
wolfspraulit's logged, one sec03:13
wpwrakokay, then it must have been locked03:13
wolfspraulhttp://downloads.qi-hardware.com/hardware/milkymist_one/production/rc3/test_results/log/urjtag_lock_4C.log03:13
wolfspraulwell, I also wondered how we can be sure that it was locked03:13
wolfspraul:-)03:13
wpwraknow a good test would be to unlock, do 100 cycles, and see how often a corruption happens03:13
wolfspraulfirst Adam will do 100 cycles with 7C03:14
wolfspraullet's see how that goes03:14
wpwrak(once it happens, reflash and proceed)03:14
wpwrak(7c) fine03:14
wpwrakbut the test is meaningless without baseline03:14
wolfspraulthen maybe do the L3 rework on all boards?03:14
Action: xiangfu (locked test) I have tested my code with 'erase' command inside flickernoise.03:14
wpwrak(l3) sounds good03:15
wolfsprauland then go through all now available boards, lock partitions (without reflashing), run 10 render cycles03:15
wolfspraulI need to find a way to start sales03:15
wolfspraulso I know the nor corruption is not fully understood, not fully made reproducible and fixed03:15
wolfspraulbut if we are lucky and something just passes, we can start to ship boards out and then we have time for more fundamental tests03:16
wolfspraulI'm hoping that the locking will be such a 'lucky' thing ;-)03:16
wpwrakif no board turn up with the "pulse" failure (0x77 and friends) or some new NOR symptoms, then it's probably safe to start selling03:16
wolfsprauldefinitely03:16
wpwrakjust keep back the ones with more severe NOR weirdness than the stray zeroed word03:17
wolfsprauloh sure03:17
wpwraki think a boundary scan may be the best test for the ones with severe NOR issues. otherwise, adam can voltmeter himself to death ...03:18
wolfspraulxiangfu: remember you shorted L19 to fix the camera signal loss problem?03:18
xiangfuwolfspraul, yes03:18
wolfspraulnow you can also short L303:18
wpwrakfor the single-word corruption, an automated test would be good to have to determine what's really going on03:18
wolfspraulwe may also loose the audio signal03:18
wpwrakxiangfu: every 1-2 weeks, there will be another component to short ;-)03:19
xiangfuwpwrak, finally we will direct send 12V to VGA :)03:20
wpwrakxiangfu: that will be fun. no longer milky mist, but colorful smoke ;-)03:20
xiangfuthe L3 fixed the not-boot problem? (needs read log)03:21
wolfspraulxiangfu: no. just a problem of loosing audio signal (line-in), similar to the camera signal loss.03:22
wolfspraulnow that we know that fix2b is good, what's the latest idea for the reset circuit using gates and 4.4v ic ?03:23
wolfspraulstill 2 reset ics? one? no more diodes?03:23
xiangfuwolfspraul, ok.03:24
wolfspraulor we wait a little longer until the dust settles, then think about it?03:24
wolfspraulxiangfu: yeah it's a great catch. werner lost the audio signal right on his first experiments :-)03:24
wolfsprauldid you ever loose the audio signal (m1 rendering becoming unresponsive to audio)? I don't remember this ever happening to me, but who knows, it could have been.03:25
xiangfuwolfspraul, yes. great catch.03:25
wolfspraulwhen I have a problem, typically I just reboot.03:25
wpwrakthe 2 reset ics idea was stupid. i realized that it would just make the system completely unpredictable.03:25
xiangfuwolfspraul, never pay attention to audio-in.03:26
wolfspraulwell I'm sure you do03:26
wolfspraulyou run m1, and the rendering won't react to audio.03:26
xiangfuwolfspraul, if I meet it. I  may can not find out it's audio problem.  :(03:26
wpwrakso i'd change the reset IC to one tied to 5 V, with ~4.3 V threshold, plus a gate to replace the evil D1603:26
wolfspraulyes, I also don't clearly remember seeing it, but it might have been.03:27
wpwrakxiangfu: it's audio in. the symtoms are: 1) no video response to audio and sometimes 2) M1 just hangs. you'll notice, don't worry ;-)03:27
wolfspraulone gate only now?03:28
wolfsprauldo you think you are clear on the circuit, or we need some experiments?03:29
wolfspraulI've seen a lot of variants over the weeks, so I'm a little cautious now ;-)03:29
wolfspraulI think slowly every possible combination was proposed at some point...03:29
wpwrak(1 gate) one for each diode. after fix2b, only one is left :)03:33
wpwrakof course experiments should be made. never expect a circuit to work before you've actually tried it :)03:34
wolfspraulso just replace the reset ic with a 4.4v variant (powered from 5V), and D16 with a gate?03:36
wpwrakyes, that's basically it. C238 will no longer be necessary. and we should check the value of R30, for compatibility with the new chip.03:38
wpwrakand, of course, R30 will _still_ connect to 3V3 ;-)03:38
wpwrakanyway, time for a nap. tomorrow, i'll see if i can get my little switch box to work and later invoke NOR amnesia in the M1 :)03:43
wolfsprauln803:46
wolfspraulthanks a lot for the super helpful feedback!03:46
wpwrakalways fun to find bugs :)  (specially if they're easy to fix :)03:50
rejonman, we really need http://en.wikipedia.org/wiki/720p04:28
rejoni keep showing off my m1 on flat screens and people keep asking about the artifacts04:29
rejonif we get 720p working, we will be able to sell more m104:29
rejoni guess many flat screens can auto stretch at SVGA04:30
rejon1024x76804:30
rejonlekernel, how is that work going btw?04:30
xiangfuhere: http://downloads.qi-hardware.com/people/xiangfu/tmp/m1-L3.png is the L3, the top of J3, the right of J21, pretty small05:10
Action: xiangfu will short the L3 now. 05:11
wolfspraulnice05:11
xiangfu:( I have to glue all those three buttons.05:43
xiangfuI remove the small middle piece, replace with thick glue. seems works better then before.05:45
wolfspraulwhy do you have to glue buttons?05:47
xiangfuit break. the buttons drop from m1.05:48
xiangfuone is broken today. the another one is broken Monday I think. so i just re glue them all.05:49
wolfspraulhmm05:51
wolfspraulyes not surprised05:51
wolfspraulI'm really curious to see the new rc3 buttons05:51
wolfspraulhopefully it's a big step forward (should be)05:51
xiangfuhmm... now the ftp is not stable. not sure if this is my new system problem.05:54
xiangfuI always use 'ftp://192.168.0.42' in 'nautiles' copy file from/to m1.05:55
xiangfunow it freeze in my system. m1 is works fine.05:55
wolfspraulI don't understand05:57
xiangfusound like my system app 'nautiles' problem.05:58
wolfspraulwhat freezes exactly? can you connect back to the m1 without rebooting m1? maybe you have to experiment/try a little to find the cause05:59
xiangfuI use a GUI tools to access m1's ftp for copy files from/to m105:59
xiangfunow this GUI tools in my new ubuntu 11.04 freeze when copy file to m1.06:00
xiangfuI can connect back to m1 without rebooting m1.06:00
xiangfutry 'ftp' command now.06:00
xiangfuftp command works fine.06:06
xiangfukeey my eyes on if my m1 will freeze in future after short L19 and L306:14
wolfspraulno no, that's unrelated06:28
lekernelwpwrak, CD input is totally unimportant; in fact, I suggested the header and resistors connected to it be DNP'd08:41
lekerneljust don't touch it on rc308:41
wolfspraulsure we all agree, no worries :-)08:41
wolfspraulthe only important new finding is L3, a great catch and immediate improvement08:42
lekernelwpwrak, the ESD protection circuits were there before the case was designed... and I was imagining we could have a large metal plate touching the shells of the buttons08:43
lekerneland when we had bare boards, the user would typically touch the button shells all the time08:54
lekernelalso, it's probably easier for arcs to jump on the shell than inside the button08:55
rejon720p10:08
stekernrejon: what kind of 'artifacts' are you speaking about? is it because the output is lowres (i.e. pixelated) or because the display has to rescale the picture?10:15
lekernelthe only noticeable artifact on M1 is banding, but this has to do with color depth, not resolution10:20
stekernah, I see10:20
stekerndon't see what the poinr of 720p would be then10:21
stekern*point10:21
lekernelI don't know if that is what rejon is talking about ...10:21
rejonyah, banding from stretching and is lowres10:22
rejonon projector not as bad10:22
rejonbut on a new screen, is worse10:22
rejoni think there is a sales factor of at least having HD10:22
lekernelbanding has nothing to do with stretching10:23
wpwraklekernel: (CD in) yeah, i thought treating it as a documentation issue would be adequate :) (i.e., put it on the errata. the whole header isn't tested anyway, so who knows what else may be wrong there. e.g., SMT sometimes "loses" components)12:15
wpwraklekernel: (button protection circuit) ah, that makes sense then. thanks !12:15
lekernelwe'll probably DNP it... I wanted to DNP on run3 already, but wolfspraul wanted to keep it12:15
lekernelalso it's done this way on the LM4550 "typical application" circuit (see qihw channel)12:16
wpwrakwhy not keep it ? just say that it's untested. a little extra for those who want to experiment.12:16
lekernelthere are probably 0.001% of users who will actually do this experiment, and those can probably solder a few 0402 parts themselves ...12:17
wpwraklekernel: it takes some courage and confidence to solder such small stuff on an USD 500+ device. there are not a lot of people who'd be ready to do this. that's probably the difference between your 0.001% and an exact 0% ;-)12:20
lekernel0402 isn't small12:21
wpwrakwolfspraul: oh, and we found an error in the WM9707 data sheet: they give the maximum analog voltage as AVDD +/- 0.3 V. they probably mean AVSS -0.3 V to AVDD + 0.3 V. had me puzzled for a while :)12:22
wpwraklekernel: (0402) you should get out more ;-))12:23
wolfspraulDNP what?12:28
lekernelJ3 and the resistors connected only to it12:28
wolfspraullekernel: what did I want to keep?12:28
wolfspraulthe audio/video expansion header?12:29
lekernelyes, but it's only audio12:30
wolfspraulwhy would I want to keep that?12:30
lekernelI don't know, but you were opposed to DNPing it when I suggested that12:30
lekernelbeing a trivial issue I didn't insist12:30
wolfspraulmust have been a misunderstanding12:30
wolfspraulwhere did I say that?12:30
wolfspraulI mean I need to ask you: what can people do with the J3 expansion header? :-)12:31
wolfspraulI don't even know12:31
wolfspraulthe fpga expansion header I have some ideas12:31
wolfspraulbut not for J312:31
lekernelyes, we keep the FPGA expansion12:31
lekernelbut J3 can go12:31
wpwrakmake fragile extension boards/connectors for more audio inputs.12:31
wolfsprauldefinitely12:31
wolfspraulwell since I hardly can imagine that J3 can be good for, if I ever said I want to keep it there must have been some misunderstanding12:32
wolfsprauls/that J3/what J3/12:32
lekernelalso, J3 made more sense when we used the LM4550, which had a built in headphones amp12:32
wpwrakand what else ... ah, SPDIF12:32
lekernelit was nice to connect headphones directly to the board12:32
lekernelyeah, now there's SPDIF instead :)12:32
wolfspraulwe can schedule j3 removal for rc412:32
wolfspraulout with it12:32
lekerneltotally unsupported/untested though12:33
wpwrak(headphone output) heh, nicely confusing :) you have LNLVLOUT on the codec, going to HP OUT, going to J3, but all the components are DNP :)12:33
lekernelthat's just a second line out12:33
wolfspraulwpwrak: you think removing J3 is ok, or you would keep it?12:34
lekernelbut it cannot drive headphones correctly (I tried it)12:34
lekernelthe LM4550 had more punch on that output12:34
wolfspraulcan we complete the resistor list to be removed with J3? J3 and ?12:35
wpwrakwolfspraul: (j3) dunno. if you expect people to play with audio extensions, it may be nice to have. adding to it if DNP, would be hard/scary. but ... i'm somewhat unconvinced about the whole expansion header situation. i think mechanical issues need a bit more attention.12:36
wolfspraulI agree about mechanical. we are just starting. now we talk about J3 first.12:36
lekernelR6 to R1212:36
wolfspraulI am 100% neutral on it, because I have no clear understanding what J3 could be used for.12:36
wolfspraulif someone wants to keep it, fine by me. if someone wants to remove/DNP, also fine. Just both at the same time doesn't work :-)12:37
lekernelbut keep R2 to R5 and R14 to R1612:37
wpwrakwolfspraul: seems we have one vote against it and two abstentions :)12:37
wolfspraulok, that means DNP in rc412:37
wolfspraulthanks! saves me a little money, no way I could not agree with that :-)12:38
stekerni don't think 0402 is any harder to solder than 1206, as long as you've got some room around it. but usually that's the reason of putting the 0402 there, lack of space12:41
wpwrakstekern: it's also a question of equipment and vision. also, details of 0402 contacts are hard to see even if your eyes are good, so you need experience to be able to find the right clues.12:49
wpwrakstekern: besides, a LOT of people consider SMT just the devil's work in general ;-) they'd rather drill and solder a thousand through-hole pins than one puny little 0805.12:50
wpwrakbtw, i wish the M1 was about 5 mm shorter. then i could mill my own side plates ;-) (my mill does only up to 150 mm. i think M1 is ~151 mm. and i need a bit of slack.)12:54
wpwrakrejon: (720p) is the issue aspect ratio or really the pixel density ? if it's just aspect ratio, maybe some less demanding wide mode, 800x480 or such, could help13:03
wpwrakrejon: or maybe the video signal should just have black bars left and right for a "wide" screen. these don't consume memory bandwidth ;-)13:03
wpwrakrejon: in general, i think the "out of box experience" of M1 could be better. right now, it's fairly obscure what it does, with long pauses and very little feedback.13:08
lekernelotoh, displaying "Loading" screens on beamers is unwelcome13:13
lekernelbut we could display a black picture instead of sending no signal13:13
lekernelit could also improve a bit the perceived boot time, since some screens take a few seconds to acquire the signal13:14
wpwrakcould you have a configurable "loading" screen ? e.g., have a "tutorial" mode with lots of feedback and such, and a "stage" mode with a much more austere interface ?13:15
wpwrakand yes, i think a black picture would be preferable over no signal in any case. a lot of video equipment acts funny when the signal drops. i suppose even "pro" devices may have their unwelcome "smart responses" to such events13:16
lekernel"tutorial mode" sounds like a lot of work13:18
wpwrakyes, unfortunately :-(13:18
wpwrakwhat would be really great for a tutorial mode is a drawing of the M1 and its I/O, with indicators on their status13:19
wpwrake.g., have a small camera image next to video in, have audio level indicator bars, maybe display DDC information on vga, show what has enumerated on USB ("keyboard", "mouse"), etc.13:21
wpwrakyou could even make it an overlay and display effects underneath. but yes, someone would have to spend a bit of time on that.13:22
wpwrakmaybe something to mention when there are a few more users. someone may look for an opportunity to contribute. and it's not the kind of thing that would require an excessive amount of expert knowledge. easier than MMU or speeding up the RAM ;-)13:22
lekernelit's not the kind of things that open source developers often do either ...13:24
wpwrakoh, they do. think KDE, Gnome :)13:24
wpwrakyou'd have to explain the concept, though, because many such developers would look more for something where they can they can copy the concept than inventing something completely new13:26
wpwrakmaybe make a few drafts of the visual design. then they have something they can work with.13:27
wpwrakbut first more ... Developers ! Developers ! Developers !:)13:30
lekernelif people continue to only post crap like that raspberry pi all over the place, this isn't going to happen13:31
wpwraklet them chatter :)13:32
wpwraklekernel: when you process those USB descriptors, do you only use the first interface descriptor ? or all of them ? e.g., if a HID device has kbd and mouse, all on the same device and in the same configuration, but on different interfaces, would M1 use both or just one ?13:54
lekernelit uses only one13:54
lekernelthis is probably the problem you have, since other communications seem to work13:54
lekernelyou can patch the AVR firmware in softusb-input in the soc distribution13:55
lekernelthen debug with the demo firmware, and finally update the xxd-generated header in the RTEMS driver13:55
wpwrakyeah, i still have to set up any development environment13:55
lekernelin next sw version we should try to have a small readonly filesystem that comes with the application binary13:56
lekernelit could be useful to store fonts, icons, and that USB firmware13:56
lekernelthe demo firmware has a little "paint" application to demonstrate mouse13:57
lekerneland it can take USB keyboard input into the console (like the BIOS)13:58
wpwrakhmm, do these things change more often than the rest of FN ?14:00
wpwrakor does FN have to be read-write ?14:01
wpwrakheh, they shrank the keyboard: http://riitek.en.made-in-china.com/product/lMOEQJwDgbUL/China-Rii-Mini-Bluetooth-Keyboad-With-Backlight-Rii-518-.html14:02
lekernelit's simply easier to have one large binary that gets flashed14:34
wpwrakyeah, agreed14:38
wpwrakso you meant something like initramfs on linux. not kind of yet another partition. good :)14:38
lekernelprobably just a small FAT filesystem concatenated at the end of the application binary14:45
wolfspraulI have a question about web update running from the rescue image. We always say that that's what users can do to fix a CRC problem.22:54
wolfspraulBut how does it actually behave as implemented today? Will it check for a newer version first, and only download and flash when it finds a newer version?22:55
wolfspraulOr will it always download and overwrite the nor?22:55
wpwrakmaybe integrate an IRC client that log into #milkymist, so that users can scream for help ;-)22:55
wolfspraulI'm wondering whether what we ship today will actually let people do what we say, or it's just a theory22:57
wolfspraulwe could also implement it in such a way that if web update is run from the rescue image, it will always download/reflash, but when it's run from the normal image, only if there is an update?22:57
wpwrakyes, i understand. don't know the answer. just try it ?22:57
wpwrak(i haven't set up ether yet)22:57
wolfspraulyes, will try. I have dodged testing web update because I'm pretty sure I will find a problem :-)22:58
wolfspraulthat one just came to my mind because we always say "users can run web update to fix nor corruption"...22:58
wolfspraulso I was wondering whether that actually works :-)22:58
wolfsprauland we cannot update such a feature into the rescue image either, because those are not getting updated right now...22:59
wpwrakit would get updated in the field only after the problem struck once :)23:00
lekernel_wolfspraul, if you have booted in rescue mode, it will always flash no matter what23:13
lekernel_it skips the version check23:13
--- Sun Aug 28 201100:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!