#milkymist IRC log for Wednesday, 2011-12-28

GitHub130[flickernoise] sbourdeauducq pushed 1 new commit to master: http://git.io/_ujjeQ00:01
GitHub130[flickernoise/master] ptest: default to relative path for MMDIR - Sebastien Bourdeauducq00:01
wpwrakmassively parallel patching :)00:02
lekerneland thanks for the patches. did you find something?00:12
wpwrakno, nothing new. everything works here :)00:14
wpwrakwhen you do a "make test" under src/compiler/, or even "make valgrind", does it pass ? there should be a total of 125 tests00:15
lekernelpatch: Unchained - A Matter Of Taste (Remix).fnp: FAILED (patches)00:16
lekernelfailed to add equation to per-vertex footer: FPVM, line 57: Failed to allocate renamed register for variable00:16
wpwrakexcellent ! so it's not just lm32 :)00:17
wpwrakis this the same fpvm.c you have ? http://downloads.qi-hardware.com/people/werner/tmp/fpvm.c00:20
wpwrakand was that "make test" or "make valgrind" ?00:21
lekerneland make valgrind shows something too00:21
lekernelhttp://pastebin.com/r979kxzC00:22
lekernelthat bug should soon be dead :)00:22
wpwrakdoes your infra-fnp.h look like this ? http://downloads.qi-hardware.com/people/werner/tmp/infra-fnp.h00:28
lekernelyes, exact same00:30
wpwrakwhat does lemon -x say ? mine is Lemon version 1.000:31
wpwrakand  re2c -v  ->  re2c 0.13.500:32
lekernelsame00:33
wpwrakhmm. the error is at the last line. this may try to tell us something ...00:35
wpwrakFPVM_MAXERRLEN is to small for the entire error message. that's why it gets truncated. doesn't necessarily mean the variable name is bad00:41
cladamw( M1rc3 yield = 88 / 90)04:05
GitHub65[scripts] xiangfu pushed 1 new commit to master: http://git.io/MVuDmg05:42
GitHub65[scripts/master] remove the .git folder extension - Xiangfu Liu05:42
GitHub58[scripts] xiangfu pushed 2 new commits to master: http://git.io/OHb1Eg06:13
GitHub58[scripts/master] compile-milkymist-firmware.sh: cleanup the .git exitention - Xiangfu Liu06:13
GitHub58[scripts/master] compile-flickernoise: using relative paths, 80 rule cleanup - Xiangfu Liu06:13
GitHub122[scripts] xiangfu pushed 1 new commit to master: http://git.io/NsDVQw06:21
GitHub122[scripts/master] compile-lm32-rtems: 80 rule cleanup - Xiangfu Liu06:21
wpwrakxiangfu: i was quicker ;-)06:33
xiangfuwpwrak, yes. :D06:38
xiangfuwpwrak, ok. then I try to work on rtems-yaffs2. :D06:47
GitHub1[rtems-yaffs2] xiangfu pushed 3 new commits to master: https://github.com/milkymist/rtems-yaffs2/compare/07a447d...9f52f4506:51
GitHub1[rtems-yaffs2/master] Merge branch 'upstream' - Xiangfu Liu06:51
GitHub1[rtems-yaffs2/master] fix the redefined warning - Xiangfu Liu06:51
GitHub1[rtems-yaffs2/master] remove hardcode app name for nor-mkyaffs2image - Xiangfu Liu06:51
cladamw( ultrasonic cleaner) yesterday went to Victory Source Industrial Corp. SMT manufacturer to discuss  with their experience.08:11
cladamw1. they also rarely use ultrasonic cleaner, since they don't like to rework the parts (switches, quartz) after ultrasonic.08:14
cladamw2. i brought 0x67/0x6d and discuss firstly their histories, and they thought it's original temperature settings on pcb pads didn't meet profile while smt reflowing at the beginning. I told that it could be that. Since I survived few boards after I used heat air.08:17
cladamw3. so they didn't suggest me to do ultrasonic clean, but i still did one (0x6d). And still can't be bootup though08:19
cladamw4. the picture and video about ultrasonic clean I requested them to take is still waiting them to send me, they don't want me to see more thought while i was waiting there. I hoped they will send me video & pic. not purely openness.08:22
cladamw5. so far I may request minbo to do remount fpga chip again with those two boards, but not now. So I'll send a report about rc3 firstly.08:25
cladamw6. current yield is 88/90. not 100%. :(08:26
wpwrakcladamw: interesting. what else do they use to clean the boards then ?08:56
mumptaiwater + iso + optionally a bit "soap"   and that at raised temperatures and possibly ultrasonics09:01
cladamwwpwrak, that Victory they said that usually tried to set parameters well while pre-process tasks doing. (i.e. 1. control the smt reflow machine temp. as good as possible, 2. to reduce reworks as possible, 3. to use high volatility cleaner as possible but few times to clean since such cleaner will erode the protection of flux from soldering. etc.)09:02
cladamwwpwrak, from i saw their ultrasonic cleaner was took from like storehouse, and long time no use though.09:03
cladamwso this fact from here factories (Minbo and Victory), they rarely not use ultrasonic but still can't imagine how they clean reworked boards.09:05
mumptaisome components don't take ultrasonics well09:07
cladamwseems that they both don't want to face the other failures and to do extra-reworks caused by ultrasonic. But for diy, you can.09:07
cladamwmumptai, yeah09:07
mumptaiwithout you more or less soak it in some cleaning liquid for a long time09:08
cladamwso I doubted Victory and Minbo both now. Even they used high-volatility liquid to clean their boards.09:09
cladamwI could only now seems that get like manufacturer official 'talking'. :(09:10
cladamwthere's one fact that 'few' boards from me I heated fpga then pass all function.09:11
mumptaisounds like a bad ball09:11
cladamwSo I very doubted that temperature measuring was bad while smt reflow09:12
mumptaicould also be a crack in the pcb09:12
mumptaior the bga-package09:13
cladamwmumptai, there's one 0x74 I took back to let minbo to do remount fpga, then all functions still work even this board doesn't bad/worse histories like nor-corruption.09:13
mumptaihave you tried pressing on or flexing the bga/pcb of the "damaged" units?09:16
cladamwmumptai, well...from 88 / 90 pass ratio, it seems could not be crack in pcb, I would be guessed that those two was the victims from varied/shifted temperature heating in reflow machine. even this is also rarely. so far I've not booted Minbo to remount. so don't know yet.09:16
cladamwmumptai, i tried to press by hand. not in success. :-) Imagine that it's 488 balls. the force from balls are quite the same/balance I think.09:17
cladamwso if there's one ball with cool soldering under fpga, pressing fpga chip probably don't have effect. :-)09:18
cladamwsorry. it's 484 balls.09:19
mumptaii once had such a board, re-reflowing helped, but we replaced it as soon as possible09:20
cladamwregarding to if "flexing" bga chip while reworks? we guessed it could be. But from 88 / 90 ratio is pass, it seems not. Even we knew reworker used a small size heat blower (rework station) to blow the corner of fpga chip. (i.e. the area of 'reset' circuit), but they blew the whole batch of 89 pcs though. if the effect of flexing was happened, the yield ratio probably can't be 88/99.09:25
mumptaidunno, actually its a mature technology, it takes some abuse to break it ;)09:27
mumptaiyou might want to have a x-ray done09:27
wpwrak(cleaning) interesting. i think the standard process for "water soluble" flux is some sort of "dishwasher". without ultrasound, but hot water under pressure.09:59
wpwrakwhat's trickier is "no clean" flux. supposedly, it should just evaporate. alas, what's left behind can still cause trouble. i've had that with atusb, too. there, flux resistance made the reset signal rise very slowly and the whole system got out of sync.10:00
cladamwthat could explain the fact that "no clean" flux supposedly. If factory or EMS they really don't do that, would this be interesting that consumer product goes freakish after long time? I didn't pay more attentions on "water soluble" while stayed at factory.10:12
wpwrakflux residues can cause all sorts of fun. if you have salts (= residues) lying around, a bit of humidity can turn them into conductors. what happens then, well ... :)10:36
--- Thu Dec 29 201100:00

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