| wpwrak | cladamw: heya ! i played a bit with board-m1 and got it to pass with 0 ERC problems. what i did was that i deleted FLASH_A0...A3 and drew them again. but i'm not sure this actually made the difference. | 00:29 |
|---|---|---|
| cladamw | yeah... | 00:29 |
| wpwrak | here's what changed in FPGA.sch: http://pastebin.ca/2139570 | 00:29 |
| wpwrak | i comitted my change. would be interesting to know if this causes any troubles on your end or of the ERC problems are gone for everyone | 00:30 |
| cladamw | when i modified somethings in eechema then DRC and modified back then DRC again, the results will be different sometimes, | 00:30 |
| wpwrak | hmm, scary. | 00:30 |
| wolfspra1l | just ran into the "zhaga consortium" which is developing mostly mechanical standards for future led lighting systems | 00:30 |
| wolfspra1l | quite nice of only the standards were more open... http://www.zhagastandard.org/specifications/book-7.html | 00:31 |
| pabs3 | wolfspra1l: I follow it because I'm aware that the hardware I rely on (Thinkpad) is completely secret/non-free (including the software before GRUB and various bits of "firmware"). for the same reasons as I use free software, I would like to be using free hardware. so I'm watching the free harware space | 00:31 |
| wolfspra1l | pabs3: yes ok, that is great. but I want to encourage you to step up a little, now that you are already here in Qi... | 00:31 |
| cladamw | and but the discoveries about FLASH_A0 ... A3, you are right too. I also found that from my DRC histories. :-) | 00:31 |
| wolfspra1l | what is 'hardware'? | 00:31 |
| wolfspra1l | dive in | 00:31 |
| wolfspra1l | there are things like baseband firmwares (say wifi) | 00:32 |
| wolfspra1l | mechanical | 00:32 |
| wolfspra1l | dsp | 00:32 |
| wolfspra1l | memory, flash | 00:32 |
| wolfspra1l | and and and | 00:32 |
| wpwrak | wolfspra1l: sebastien should like "book 7". finally a standard with no trace of overengineering ;-)) | 00:32 |
| wolfspra1l | well, I do think those standards could become relevant even for us, since if they really catch on, it would make sense to engineer small logic boards for those standards to be embeddable in furniture etc. | 00:33 |
| wolfspra1l | but unfortunately they think they will only open at the end, members pay 1000 EUR per year, etc. etc. | 00:33 |
| wolfspra1l | the usual industry stuff | 00:33 |
| wolfspra1l | if it takes off, thousands of companies will just copy the simple mechanical specs anyway :-) | 00:34 |
| wpwrak | (relevant) maybe ... not sure if it even makes sense to standardize at the level of furniture. rather at the level of components. like lamp sockets. | 00:34 |
| wpwrak | (copy) yeah :) | 00:34 |
| wolfspra1l | that's what this is I think | 00:34 |
| wolfspra1l | indoor, outdoor. just lots of mechanical standards to make interoperation between different companies easier. | 00:35 |
| cladamw | wpwrak, btw, about last Zero DRC results, i have an idea. :-) since I was pretty sure about J17's duplicated pins in my old KiCad version, at that time I removed pins and made sure they are gone, then added new then still got that same warnings(duplicated) But yesterday, after I used DRC function in newer Library Editor, it found there's duplicated there. so I much doubted it's my "OLD" KiCad versions in here. | 00:35 |
| wolfspra1l | given that LED lighting essentially frees up designers to shape things totally freely | 00:35 |
| wolfspra1l | but mechanically it still has to fit... | 00:36 |
| wolfspra1l | so there's need for new standards | 00:36 |
| wpwrak | wolfspra1l: hmm. or you could just include it in the design. if it's just a bunch of LEDs (in standard packages) and a standard power supply ... | 00:37 |
| wpwrak | cladamw: hmm. not sure what you mean :) i can confirm the duplicate entires - when i tried to delete a pin, i was given two choices, and after deleting, the pin was still there (that is, one of the two) | 00:38 |
| cladamw | wpwrak, i wanted to copy all files locally here( which generated by OLD 2448 KiCad), then use new 3494 KiCad to save them all again( by slightly move some pins then move back then save it), then compare OLD and New files. | 00:38 |
| wpwrak | xiangfu: i made a new gadget: http://projects.qi-hardware.com/index.php/p/wernermisc/source/tree/master/bin/pidiff | 00:39 |
| cladamw | wpwrak, yes, i knew there's two choices you can select in 3494 KiCad, like i said current board-m1 files mostly generated by my OLD 2448 KiCad. | 00:39 |
| wpwrak | it takes this sort of nightmare: https://github.com/milkymist/board-m1/commit/09871289563b0eaa79f8300a94235fbb4e86ecb1 | 00:39 |
| wpwrak | and turns it into this: http://pastebin.ca/2139570 | 00:40 |
| xiangfu | cladamw, I have install 3494 kicad. | 00:40 |
| wpwrak | cladamw: (compare old and new) okay, then pidiff may be useful for you, too :-) | 00:40 |
| cladamw | wpwrak, I used 3494 to select 'clear' choices it wanted me to pick yesterday to solve J17's duplicated pins. | 00:40 |
| cladamw | wpwrak, i need now to sync yours commit. moments :) | 00:42 |
| wpwrak | cladamw: i think you may just have accidently done a "copy block", which would duplicate everything | 00:42 |
| wpwrak | could of course also be a kicad bug that saved things twice. but i haven't run into anything like that so far. | 00:43 |
| cladamw | wpwrak, yes, but like i said I was thought they are duplicated and tried to move pins in J17, but actually it DIDn't, but alll this confirmation was done by my OLD 2448 KiCad, then yesterday used new 3494, I successfully discovered and removed those duplicated, so super strange, that's why i now want to compared all files. :-) | 00:44 |
| wpwrak | hmm, could also be that the old kicad just moved both pins | 00:45 |
| cladamw | wpwrak, "could of course also be a kicad bug that saved things twice." <<< about this, i can pretty sure I met them when I just clicked DRC button used 2448. :) | 00:46 |
| wpwrak | at least some time ago, it did such things. later, it started to ask. | 00:46 |
| wpwrak | okay, good :) | 00:46 |
| wpwrak | well, let's see if the problem is gone now. then we can worry about it when and if it strikes again. | 00:46 |
| cladamw | btw, since we all already synced now to use 3494, so I should to use it to save all files then compare to see if any difference, otherwise I have no confidence to move on further, especially in my laptop it installed at least two times KiCad, so i'll ask xiangfu to help me uninstall them to avoid collision among KiCads. i don't know. But at least to remove them or then reinstall 3494 again. | 00:49 |
| wpwrak | yeah, can't hurt to remove the old one | 00:50 |
| wpwrak | once schhist is up, it'll also be easier to track changes | 00:51 |
| xiangfu | cladamw, do you need me run 'Test Erc' in my computer? | 00:51 |
| wpwrak | xiangfu: at least i would be curious :) | 00:51 |
| cladamw | xiangfu, why not ! :-) | 00:51 |
| xiangfu | Warnings Count: 8 | 00:51 |
| xiangfu | Errors Count: 0 | 00:52 |
| wpwrak | yeah ! :) | 00:52 |
| cladamw | xiangfu, did you git pull latest ones ? :-O | 00:52 |
| xiangfu | let me check. | 00:53 |
| xiangfu | there is r4/FPGA.sch update. | 00:54 |
| xiangfu | let me do TestErc again. | 00:54 |
| xiangfu | after update kicad-libs/board-m1 'Test Erc' give nothing. | 00:54 |
| xiangfu | all 0. | 00:54 |
| wpwrak | even better :) | 00:54 |
| xiangfu | 'Markers:' NONE. | 00:54 |
| cladamw | ha | 00:54 |
| cladamw | wpwrak, xiangfu this is the one I got yesterday by 3494 : http://downloads.qi-hardware.com/people/adam/m1/tmp/kicad/m1.erc | 00:55 |
| wpwrak | xiangfu: is there a *cache*lib ? | 00:55 |
| wpwrak | xiangfu: if yes, please kill it and try again | 00:55 |
| xiangfu | wpwrak, no. | 00:55 |
| xiangfu | git clean -xdf | 00:55 |
| cladamw | now after update, still Zero. :-O | 00:55 |
| wpwrak | excellent :) | 00:55 |
| cladamw | xiangfu, what does "git clean -xdf" mean ? | 00:56 |
| xiangfu | remove everything that git not track, ignore. | 00:57 |
| xiangfu | like the .bak. m1-cache.lib etc. | 00:57 |
| xiangfu | cladamw, I got the same report: http://pastebin.com/T2JaAyvq | 00:57 |
| xiangfu | wpwrak, so pdiff is for file like .sch? | 00:58 |
| xiangfu | cladamw, 'git clean -xdf' is like the a fresh git clone. if there are no change/commit locally. | 00:59 |
| cladamw | wpwrak, seems now results/trouble turn to your site. Amazing ... :-) btw, I still need to compare and do uninstallation. | 01:00 |
| xiangfu | wpwrak, we still have the m1-cache in some .sch files: http://pastebin.com/1b4Bhprf | 01:00 |
| wpwrak | i think the cache keeps coming back. not sure what exactly produces it. just delete the local copy from time to time. | 01:01 |
| cladamw | so maybe m1-cache.lib in each *.sch caused that different results when DRC ? don't know. | 01:03 |
| xiangfu | cladamw, no. | 01:04 |
| wpwrak | it shouldn't matter | 01:04 |
| xiangfu | wpwrak, if I remove m1-cache.lib and click save whole project. it give me: pastebin.com/VAxxEmXz | 01:05 |
| cladamw | xiangfu, later, when you are free, could we skype sometime to help me uninstall KiCad ? | 01:05 |
| xiangfu | cladamw, sure. | 01:05 |
| wpwrak | cladamw: looks reasonable | 01:06 |
| xiangfu | wpwrak, I think I can commit this change. | 01:06 |
| cladamw | wpwrak, yeah, the results from just xiangfu gave us was what I met before. Sorry that I should have described more clear. :( | 01:07 |
| cladamw | but I didn't notice they could caused troubles. :( | 01:08 |
| wpwrak | oh, that was for xiangfu :) | 01:08 |
| wpwrak | yes, commit is good | 01:08 |
| wpwrak | that way, we have that out of the way | 01:08 |
| wpwrak | you usually get a lot of changes without much meaning when saving with a significantly different version of kicad. so it's good to have them all in the same commit, and not get them bit by bit scattered over the next week or so | 01:10 |
| xiangfu | new version kicad have BIG icon. good. | 01:12 |
| wpwrak | and opening FPGA.sch is super-slow :-( | 01:13 |
| wpwrak | about 4-5 seconds | 01:13 |
| xiangfu | wpwrak, no. | 01:13 |
| xiangfu | wpwrak, something wrong in your side. | 01:14 |
| xiangfu | wpwrak, super faster. same with other .sch files. | 01:14 |
| wpwrak | hmm | 01:14 |
| cladamw | will m1-cache appear in each *.sch after we modify sch ? or after xiangfu's commit, they won't be committed 'forever' even .sch has them ? | 01:14 |
| wpwrak | xiangfu: do you have 3D hardware acceleration ? | 01:15 |
| xiangfu | wpwrak, yes. I think so. I use the NVIDIA driver. | 01:15 |
| wpwrak | cladamw: i don't think you need to worry about the m1-cache in *.sch. as far as i remember, kicad only writes this information but never uses it when reading | 01:15 |
| wpwrak | xiangfu: ah nice. no kernel hacking for you then :) | 01:16 |
| cladamw | wpwrak, okay, nice ! | 01:16 |
| xiangfu | wpwrak, download from nvidia website. then install. no kernel hacking. the ben kernel already take me too much time. :) | 01:17 |
| wpwrak | no atusb then :) | 01:18 |
| xiangfu | no. not yet. | 01:18 |
| xiangfu | I use 2 atBen for test for now. | 01:18 |
| kristianpaul | wpwrak: do i need recent version kicad to avoid this http://paste.debian.net/164769/, when opening m1-board sch ? | 02:32 |
| kristianpaul | or.. | 02:32 |
| kristianpaul | ah, 3494 kicad ! | 02:33 |
| cladamw | kristianpaul, no, you need this http://projects.qi-hardware.com/index.php/p/kicad-libs/source/tree/master/components | 02:36 |
| kristianpaul | ahh | 02:36 |
| kristianpaul | own libs interesting :) | 02:37 |
| cladamw | kristianpaul, we created specific KiCad compoents for our own from now on, and will not use KiCad's sytem libs., so please git clone them. :-) | 02:37 |
| kristianpaul | sure sure | 02:39 |
| kristianpaul | now where i put it after type make.. | 02:39 |
| xiangfu | kristianpaul, ? | 02:40 |
| kristianpaul | /usr/share/kicad/library/ ? | 02:41 |
| xiangfu | kristianpaul, no | 02:41 |
| kristianpaul | ah easy, root dir for m1 projects :) | 02:42 |
| xiangfu | put those components under "board-m1/rc4/../../kicad-libs/components" | 02:42 |
| xiangfu | kristianpaul, but this is better : "board-m1/rc4/../../kicad-libs/components" :) | 02:42 |
| kristianpaul | yes works now | 02:44 |
| cladamw | xiangfu, thanks for your helps on my uninstallations on previous versions | 03:18 |
| cladamw | wpwrak, now yes, i still got Zero Err from 3494 KiCad. nice ! | 03:18 |
| xiangfu | cladamw, :-) | 03:26 |
| wpwrak | cladamw: very good ! :) | 06:39 |
| wpwrak | kristianpaul: the libs are in the git project kicad-libs. the idea is that board-m1 and kicad-libs (as well as all the other qi-hw projects) are checked out under the same parent directory. e.g., i use /home/qi/ | 06:40 |
| wpwrak | kristianpaul: the various kicad-using projects then access the libs with relative paths, ../../kicad-libs/... or similar | 06:40 |
| JCGsp | hi everyone | 07:22 |
| JCGsp | a pygame package from an older build will install and work con newest software image? | 07:26 |
| xiangfu | JCGsp, maybe. not 100% sure about that. | 07:45 |
| JCGsp | thanks, after the reflash I'll try to install it and I'll tell if it works. | 07:46 |
| JCGsp | xiangfu, the reset command on "usbboot" needs any argument? | 07:47 |
| xiangfu | JCGsp, no argument is fine. | 07:49 |
| JCGsp | strange thing then. I try to run it with no argument, but stays with black screen and doesn't boot. I have to unplug usb and remove battery as usual xD | 07:50 |
| JCGsp | xiangfu, I've tested pygame and works, but i can't create the data partition (other things work flawlessly) | 08:23 |
| xiangfu | JCGsp, there is a mtd.nn command for format or mount data partition. | 08:24 |
| JCGsp | anybody knows how to use mtd.nn to mount data partition? | 08:31 |
| JCGsp | nevermind, I managed to mount it after fighting | 08:47 |
| zhai | JCGsp: good luck to you | 09:28 |
| JCGsp | to install a package on open wrt is "opkg install PACKAGE_NAME"? | 10:22 |
| wolfspraul | yes, sounds right | 12:22 |
| --- Wed Apr 25 2012 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!