2012-03-26 00:00 Ayla: besides, unless you're really using 5.25" floppies and such, that choice isn't available anyway 2012-03-26 00:00 sigh 2012-03-26 00:00 just grab one of 1000s FAT access sample codes and declare it a day 2012-03-26 00:01 the standard sizes only works for floppies indeed, SD is a fake harddisk, which uses a single media ID code regardless of geometry 2012-03-26 00:01 Ayla: you'd still need to read the boot sector to determine the FAT entry size. and maybe also the beginning of the data. not entirely sure about the latter 2012-03-26 00:02 afaik you get FAT location and root dir location from the boot sector and data location from the FAT 2012-03-26 00:02 mth: pioneers of mobile computing :-) 2012-03-26 00:02 wpwrak: but why should I care about the entry size? 2012-03-26 00:02 I don't get it 2012-03-26 00:02 Ayla: the FAT entries can be 12, 16, or 32 bits 2012-03-26 00:02 ah 2012-03-26 00:02 Ayla: so unless your file is just one cluster short, you need to know the FAT entry size 2012-03-26 00:03 I do check it 2012-03-26 00:03 I simply exit the loading function when it's not FAT32 2012-03-26 00:03 mth: i meant the position of the data sector corresponding to FAT entry 0 (cluster 0). i think it's at a non-zero offset. 2012-03-26 00:05 hmm, my knowledge is a bit rusty I'm afraid 2012-03-26 00:06 here's (part of) my code: http://pastebin.com/ZEJYJ74B 2012-03-26 00:06 I used to do all kinds of nasty editing in the file system, like making a subdirectory point to its parent and watch PC-Tools crash when reading the disk 2012-03-26 00:07 sbi->data_start = sbi->dir_start + rootdir_sectors; 2012-03-26 00:07 and 2012-03-26 00:07 sbi->dir_start = sbi->fat_start + sbi->fats * sbi->fat_length; 2012-03-26 00:08 linux kernel, fs/fat/inode.c:fat_fill_super 2012-03-26 00:08 Ayla: you might need some attribute to tell the compiler not to pad the struct 2012-03-26 00:08 still there after all these years :) 2012-03-26 00:08 mth, I did check that, only the last one is padded 2012-03-26 00:08 mth: haha, on early linux you could create that with standard tools 2012-03-26 00:08 the "fsdata" structure 2012-03-26 00:09 but it's like that on the original code too, so I'm not sure if I should alter that 2012-03-26 00:09 Ayla: note that some programs, e.g. mkfs.vfat, sometimes create FAT16 and FAT12 volumes depending on the size of media 2012-03-26 00:09 the structures are from u-boot btw 2012-03-26 00:09 e.g. if you will point mkfs.vfat to something 1.44MB in size, then chances it'll format it as FAT12 2012-03-26 00:09 jekhor_ has joined #qi-hardware 2012-03-26 00:09 there's an option for forcing the type 2012-03-26 00:10 whitequark: I'm not planning to put a floppy on my dingoo ;) 2012-03-26 00:10 also there's an option to deal with inode size which changed from 128 to 256 eventually in mkfs and uBoot barfed up on that 2012-03-26 00:11 Ayla: there's the problem 2012-03-26 00:11 if you will format a 2MB NAND partition with mkfs.vfat, it can _too_ format it as FAT12 2012-03-26 00:11 so look out for that 2012-03-26 00:11 heh, come on 2012-03-26 00:11 (through using FAT on NAND partitions is an exceptionally bad idea anyway) 2012-03-26 00:11 I'm writing code to boot from SD only 2012-03-26 00:12 ok, on a 2MB SD partition ;) 2012-03-26 00:12 or it can be 10MB and FAT16 2012-03-26 00:12 still a potential for a failure 2012-03-26 00:12 oops, of course the inode size wasn't for FAT 2012-03-26 00:12 whitequark: the main root file system won't even fit on that 2012-03-26 00:12 :-D 2012-03-26 00:12 up to 32MB can still be FAT12 2012-03-26 00:13 FAT16 goes quite a bit further and could actually exists on SD 2012-03-26 00:13 I don't want to support something we're sure we'll never see 2012-03-26 00:13 the code is not meant to go inside an OS, but is specific to the dingoo 2012-03-26 00:13 mth: I don't remember exact details of FAT implementations. but I've been bitten by that quirk and so I'm saying 2012-03-26 00:14 dang, I never tested if FR uboot actually would boot from an ext2/3 with 128bit inode size 2012-03-26 00:14 I just seem to remember it been supposed to bot from ext in early days of gta01 2012-03-26 00:14 in any case, let's first get it booting from FAT32 and later add FAT12/16 support if we might need it 2012-03-26 00:15 mth: Ayla: dump everything except FAT32. make a note in README. 2012-03-26 00:15 fat16 support isn't worth the time required for it 2012-03-26 00:15 yup 2012-03-26 00:15 support for users not caring to read README isn't, too 2012-03-26 00:18 esp if those users dare to repartition a SD that by default comes with VFAT 2012-03-26 00:20 Ayla: if you put filename and ext in one array, you can compare it to "VMLINUZ\0BIN" in one go 2012-03-26 00:21 mth: probably, I'm not there yet 2012-03-26 00:22 Ayla: seriously, why not take an existing FAT access code? 2012-03-26 00:22 it has been written way more times than it should be 2012-03-26 00:23 whitequark: I do have an existing FAT access code 2012-03-26 00:23 so what's wrong with it? 2012-03-26 00:23 I'm almost copying the u-boot code 2012-03-26 00:23 but there's so much stuff in there I don't need 2012-03-26 00:24 and I like to understand what I program 2012-03-26 00:25 yet another wheel reinvented out of pure curiosity 2012-03-26 00:25 * whitequark has a collection of those 2012-03-26 00:26 that's called evolution 2012-03-26 00:26 wheels used to be in wood 2012-03-26 00:27 it has still the same function; but now each wheel is made accordingly to the system it composes 2012-03-26 00:27 a wheel from a bike is not the one from a car 2012-03-26 00:27 I'll just go and look at rabbits. Funny little rabbits with black twitching noses. 2012-03-26 00:39 cladamw has joined #qi-hardware 2012-03-26 00:46 zumbi has joined #qi-hardware 2012-03-26 01:32 Ayla has joined #qi-hardware 2012-03-26 01:47 kyak: are you trying to compile in directfb support? 2012-03-26 01:47 building qt4 frequently and don't experience this issue 2012-03-26 01:52 wej has joined #qi-hardware 2012-03-26 01:53 xiangfu has joined #qi-hardware 2012-03-26 01:55 mirko: hey nice to see you! 2012-03-26 01:56 and thanks a lot for continued care about those things, I am still super happy about OpenWrt in general :-) 2012-03-26 01:57 if we can do things better for smoother integration, never hesitate to post it so we can learn 2012-03-26 01:57 will do, but have to figure out the actual problem before :) 2012-03-26 01:58 wolfspraul: currently in greece, attending the wireless battle mesh meeting 2012-03-26 01:58 sure that was not in reference to this particular issue, just in general 2012-03-26 01:58 greece, nice 2012-03-26 01:58 wireles battle mesh? wow 2012-03-26 01:59 I recently bought some of these little thingies, and of course OpenWrt on them - really good! http://wiki.openwrt.org/toh/tp-link/tl-wr703n 2012-03-26 01:59 hehe, yeah bought some as well 2012-03-26 01:59 16 USD, 0.5W. finally a worthy successor of my aging nslu2 2012-03-26 01:59 very neat devices 2012-03-26 01:59 they're not available in europe yet 2012-03-26 01:59 and openwrt really shines on them 2012-03-26 01:59 had to import them from HK 2012-03-26 01:59 well. the reason is that EU+US markets are 'too small' :-) 2012-03-26 02:00 I just lump them both together 2012-03-26 02:00 and not price sensitive enough, that is a product that is so cheap is not pulled forcefully enouhg because none of the distributors are interested to work for such tiny margins 2012-03-26 02:00 but they take off in the world's largest computer markets, starting with China, and then other huge and growing markets 2012-03-26 02:01 they are everywhere here in China, at every corner shop 2012-03-26 02:01 wolfspraul: there is also a different model - having a grey case instead of blue 2012-03-26 02:01 including low-cost variants (yes), like the 702n and even more lost-cost 'no-name' versions 2012-03-26 02:01 and kind of a display 2012-03-26 02:01 low-cost meaning another 1 USD less... 2012-03-26 02:02 the 702 has 2MB flash 2012-03-26 02:02 there are many variants 2012-03-26 02:02 it's hard to imagine that there is another 'no-name low-cost' white label essentially 2012-03-26 02:02 for a product that already retails at 16 USD 2012-03-26 02:02 but there is :-) 2012-03-26 02:02 :) 2012-03-26 02:02 you can only understand this from the perspective of a huge market like china with 1.3 billion people, which is also extremely price sensitive 2012-03-26 02:02 just for the record: http://battlemesh.org/BattleMeshV5 2012-03-26 02:03 they will get to EU/US later, if anyone there cares... 2012-03-26 02:03 (it's the distributors that don't care, not the consumers, since it doesn't even reach them) 2012-03-26 02:04 battle mesh, yes, reading 2012-03-26 02:04 very interested in anything rf, mesh, p2p 2012-03-26 02:04 sdr 2012-03-26 02:05 702, not be supported in OpenWRT !! oh 2012-03-26 02:05 yeah come on, stay away from those 'cost-down' versions 2012-03-26 02:05 like removing the USB connector to save, what, 10 cents? 2012-03-26 02:05 and then not having USB host because of that... 2012-03-26 02:06 kristianpaul: 2MB flash - you can strip openwrt down to fit in 2MB but it's just not worth it and fun 2012-03-26 02:06 mirko: and poor usefullness later.. 2012-03-26 02:07 mirko: so you are a 'mesh networking enthusiast and community networking activist'? cool! :-) 2012-03-26 02:09 battle rf could be fun ;) 2012-03-26 02:10 wolfspraul: well, it's all OpenWrt related as well 2012-03-26 02:10 since most nodes are running OpenWrt 2012-03-26 02:11 removing the USB connector, remenbers me some of nanonote history about usb host :) 2012-03-26 02:11 mirko: I think OpenWrt is doing just fine 2012-03-26 02:11 yeah, got most OpenWrt-devs to attend the event as well 2012-03-26 02:11 so I am serious when I worry about 'how can we integrate with upstream (owrt) better', 'how can we keep long-term maintenance costs down', etc. 2012-03-26 02:12 the future is bright :-) 2012-03-26 02:12 yesterday we had quite a long and productive meeting dedicated to openwrt 2012-03-26 02:12 mirko: havent seems rtl-sdr? 2012-03-26 02:12 see* 2012-03-26 02:12 ah hey, we need really good milkymist soc support in openwrt one day :-) 2012-03-26 02:12 but some homework to do on our end first, ahem. say a year or so :-) 2012-03-26 02:13 wolfspraul: well, i'm willing to assist but working full-time currently - bdesides my very own projects :) 2012-03-26 02:13 hehe 2012-03-26 02:13 sure sure 2012-03-26 02:13 first priority is to keep ben nanonote image from falling apart 2012-03-26 02:13 on the milkymist side a lot of groundwork is missing and slowly being created 2012-03-26 02:14 mirko: from router manufacturers, which do you think are the most openwrt-friendly, or the best supported by openwrt? 2012-03-26 02:15 rejon has joined #qi-hardware 2012-03-26 02:16 why do you need to bring ethernet cables, switches and hubs to a meeting that is all about wireless & mesh? :-) 2012-03-26 02:17 http://battlemesh.org/BattleMeshV5#What_to_bring 2012-03-26 02:28 in first instance it's drinking, partying, having no sleep and talking and hacking ;) 2012-03-26 02:33 wolfspraul: it's hard to tell which manufacturer is best currently.. - there's one great netgear router which however costs about 90 euros 2012-03-26 02:33 suprisingly tp-link routers are usually getting supported quite fast as well 2012-03-26 02:33 yes, I didn't mean more or less 'random' products that were found to be 'good' in a reverse way 2012-03-26 02:33 they even advertise currently with openwrt compatibility 2012-03-26 02:33 but I mean whether there are any manufacturers that have an active/proactive role wrt openwrt 2012-03-26 02:34 ah yes, that's interesting! [ads] 2012-03-26 02:34 their role in getting patches upstream is non-existent still 2012-03-26 02:34 are the firmware on those routers built with openwrt? 2012-03-26 02:34 depends on the models 2012-03-26 02:35 is there a manufacturer that realizes there is this thing openwrt and they should have a strategy to align their business with what is happening in openwrt? 2012-03-26 02:35 or not? 2012-03-26 02:35 but the number of manufacturers using a firmware by default based on openwrt is inrceasing 2012-03-26 02:35 wolfspraul: not that we know of currently 2012-03-26 02:35 yeah I would think so 2012-03-26 02:35 in my opinion thinks like the little 16 USD router is what is leading/most innovative economically 2012-03-26 02:35 wolfspraul: usually they just do it without notifying us - and usually their env is heaviliy patched and not based on some recent version of openwrt 2012-03-26 02:36 and those economics are tough 2012-03-26 02:36 at those pricepoints even the smallest engineering effort becomes a large percentage of their margin 2012-03-26 02:36 which should make them more interested in a smooth strategy that includes upstream 2012-03-26 02:36 mirko: are there any at all who commit their stuff upstream? 2012-03-26 02:37 but I hear you. thanks! just double-checking... 2012-03-26 02:37 all the same old story then :-) 2012-03-26 02:37 first we wait until the router costs 2 USD, then we see what we do :-) 2012-03-26 02:37 pabs3: not really - not as in: they provide useful patches ;) 2012-03-26 02:37 wolfspraul: got it - thanks :) 2012-03-26 02:37 they cannot afford the staff that would be able to do this 2012-03-26 02:38 'cannot' not as in cash liquidity, but as in being compatible with their business model 2012-03-26 02:39 maybe some will slowly become just like a regular openwrt user. look up their hardware in the 'toh', then flash the image recommended there :-) 2012-03-26 02:39 that would create an interesting chicken & egg problem :-) 2012-03-26 02:40 mirko: ah, one last thing. do you have any thoughts on qualcomm acquiring atheros? 2012-03-26 02:41 wolfspraul: i'm not that much into this wifi thing.. can't tell 2012-03-26 02:41 I'm asking because it seems there are 2 major makers of the SoCs inside a lot of routers: broadcom and atheros 2012-03-26 02:42 and atheros was acquired by qualcomm over a year ago, so I would think that tech is being integrated into future SoCs 2012-03-26 02:42 but I know too little there, just watching over time and trying to figure out where the interesting new things are happening 2012-03-26 02:43 look at a product like the tp-link TL-MR11U, a battery powered version of the 703n 2012-03-26 02:43 if it has gsm/lte built in? could be used for all sorts of things 2012-03-26 02:50 i know that atheros is restructering in way which goes away from the opensource efforts 2012-03-26 02:50 people are trying to hard to avoid this and try to convince them not giving up this path 2012-03-26 02:52 qualcomm has money to finance proprietary innovation, in fact the profitability of such investments in the past has made them what they are today 2012-03-26 02:53 I think you will have a hard time convincing them about anything open. they will only open the parts that have lost profitability for them. 2012-03-26 02:53 that's the theory 2012-03-26 02:53 but in reality the open routers we have today are cool, no? I only think about the value of the open part... 2012-03-26 02:55 lantiq is great 2012-03-26 02:56 they not producing routers but soc's and eval-boards 2012-03-26 02:56 they are really openwrt-friendly 2012-03-26 02:56 ah interesting. thanks! I will definitely check that out. 2012-03-26 02:56 and finance people writing opensource drivers for them 2012-03-26 02:56 that's what I meant :-) 2012-03-26 02:57 they're one of the few provising an abstracted API for voip/dsl support 2012-03-26 02:57 usually we just get *.ko-files 2012-03-26 02:57 I will read about them some more, very helpful thanks a lot! 2012-03-26 02:57 they encapsulated it into a firmware blob but the API from the kernel and userspace is kept the sam 2012-03-26 02:57 *same 2012-03-26 02:57 I'm trying to understand the companies and their business models, not just looking at products one by one. 2012-03-26 02:57 welcome 2012-03-26 02:58 need to get some sleep now :) 2012-03-26 02:58 see ya 2012-03-26 05:28 cladamw has joined #qi-hardware 2012-03-26 05:38 wolfspraul has joined #qi-hardware 2012-03-26 06:00 Jay7 has joined #qi-hardware 2012-03-26 06:07 jurting has joined #qi-hardware 2012-03-26 06:31 jluis has joined #qi-hardware 2012-03-26 06:37 xiangfu has joined #qi-hardware 2012-03-26 08:43 wolfspraul, please add me as happy member under http://projects.qi-hardware.com/index.php/p/kicad-libs/ Thanks a lot ! 2012-03-26 08:46 cladamw: added 2012-03-26 08:46 excellent let's take that on! 2012-03-26 08:47 nice ! 2012-03-26 09:06 antoniodariush has joined #qi-hardware 2012-03-26 09:12 xiangfu has joined #qi-hardware 2012-03-26 09:27 Ayla has joined #qi-hardware 2012-03-26 09:30 xiangfu has joined #qi-hardware 2012-03-26 09:49 [commit] Xiangfu: cgminer: increase the MAX_DEVICE to 64 (master) http://qi-hw.com/p/openwrt-packages/b96e10c 2012-03-26 09:49 [commit] Xiangfu: Merge branch 'master' of projects.qi-hardware.com:openwrt-packages (master) http://qi-hw.com/p/openwrt-packages/617627f 2012-03-26 09:49 [commit] Xiangfu: Merge branch 'master' of projects.qi-hardware.com:openwrt-packages (master) http://qi-hw.com/p/openwrt-packages/9a15361 2012-03-26 10:04 [commit] Adam Wang: Added WM9707SCFT/V symbol (master) http://qi-hw.com/p/kicad-libs/b4543b9 2012-03-26 10:25 jluis_ has joined #qi-hardware 2012-03-26 10:30 wpwrak, nice today I treated myself ! :-) 2012-03-26 10:30 very good ! :) 2012-03-26 10:30 wpwrak, http://projects.qi-hardware.com/index.php/p/kicad-libs/source/commit/b4543b9/ 2012-03-26 10:30 yes, ours version are different surely. One question: 2012-03-26 10:31 i'm looking at it right now ... 2012-03-26 10:32 perhaps it's time to switch to using git add the_file(s)_you_really_want_to_commit 2012-03-26 10:32 and only then git commit 2012-03-26 10:32 wpwrak, http://dpaste.com/721470/ 2012-03-26 10:33 that way, you can leave out all the "noise" kicad produces. e.g., your commit also changed things you didn't modify, for example because of the (stupid) timestamps 2012-03-26 10:33 (dpaste) yes, that far it was good. what went wrong after ? 2012-03-26 10:34 my question is why components.pro still has been committed ? 2012-03-26 10:34 it seems that I didn't use git add components.pro though 2012-03-26 10:36 it's the commit -a 2012-03-26 10:36 since you already did git add ... 2012-03-26 10:36 you would have needed only git commit 2012-03-26 10:37 git commit -a commits everything that has been added plus everything that already existed and that has changed 2012-03-26 10:37 so next time I don't need use '-a' just use git commit 2012-03-26 10:37 that's why you also commited "changes" to c8051f320.* 2012-03-26 10:37 is that right ? 2012-03-26 10:37 yes 2012-03-26 10:37 yeah...phew~ 2012-03-26 10:38 sorry that. that's why i felt wrong that why c8051f320.* still be modified. :( 2012-03-26 10:38 btw, there is a useful script in wernermisc/bin/purge 2012-03-26 10:38 it removes timestamp changes from .pro files :) 2012-03-26 10:38 phew~ so next time: I have to just use git add and git commit, right ? 2012-03-26 10:39 that is, if only the timestamp has changed, then it removes it. if anything else has changed, it leaves the change(s) there 2012-03-26 10:39 wow~ so could you change c8051f320.* back to previous ones ? 2012-03-26 10:40 after the commit, you should check if there are no other changes you want to commit. (git status or, better, git diff and git diff --cached) 2012-03-26 10:40 if there's nothing else, you can throw away unwanted changes with git stash 2012-03-26 10:41 "git stash" means that the changes are still around, so if you made a mistake, you can still recover them. but they're out of your way. 2012-03-26 10:42 phew~ those are may hard a bit for me to understand now. 2012-03-26 10:42 git is all about the workflow ;-) 2012-03-26 10:44 btw, when you use components.pro to add/modify symbols, will you always commit it ? or no need, since i think the components.pro is just for local laptop purpose. right ? 2012-03-26 10:45 i'll not commit it even I create new symbols. is it make sense to you ? 2012-03-26 10:45 i commit it, because that way, anyone can access the new component with eeschema 2012-03-26 10:45 otherwise, they'd have to add it manually 2012-03-26 10:45 (access it) from kicad-libs/components/ 2012-03-26 10:45 hmm...okay. i see now. 2012-03-26 10:45 you can make sch there 2012-03-26 10:46 and then invoke the component viewer 2012-03-26 10:47 aha...nice that make sch there. 2012-03-26 10:49 [commit] Werner Almesberger: a bit of meta-data cleanup after the wm9707scft commit (master) http://qi-hw.com/p/kicad-libs/6faf611 2012-03-26 10:49 wpwrak, well... so i'll keep to add symbols for m1r4 these days once i'm available... phew~ soon, we'll have KiCad m1r4 sch. ;-) 2012-03-26 10:49 you forgot to add yourself as author :) 2012-03-26 10:50 pin 46 is an input ? 2012-03-26 10:51 pin 12, too ? 2012-03-26 10:51 DocScrutinizer has joined #qi-hardware 2012-03-26 10:52 wpwrak, how can i edit "./wm9707scft" in the "Preference >> Library" ? 2012-03-26 10:52 (don't forget to git pull after my commit, before making any new changes. else, you'll have a merge conflict, e.g., on *.pro) 2012-03-26 10:53 (edit) you mean you want to rename it ? 2012-03-26 10:53 since I found that i tried to add "./" for it. yeah. 2012-03-26 10:53 but don't know how to use it 2012-03-26 10:54 i added the ./ 2012-03-26 10:54 so you edited the file directly not by EESchema ? 2012-03-26 10:54 i just edited the .pro file with a text editor :) 2012-03-26 10:54 oah.... got it. man 2012-03-26 10:54 yes, of course. it's much quicker that way ;-) 2012-03-26 10:55 also, kicad may try to change ./ back to nothing 2012-03-26 10:55 alright, i still have a lot of "git" to learn 2012-03-26 10:55 yeah...pin 46 is NC, no need an input, 2012-03-26 10:55 btw, do you know this one ? http://people.openmoko.org/werner/gta02-core/gta02-core-expanded-all.pdf 2012-03-26 10:55 that's still from gta02-core. an view of components with their pin types 2012-03-26 10:56 i guess it'll be useful to add something like this to kicad-libs now, too 2012-03-26 10:57 yeah...so you want me to add symbols as gta02 as possible for m1r4 ? 2012-03-26 10:58 not yet. let me set up the framework for it first ... 2012-03-26 10:58 hmm...yeah 2012-03-26 11:01 i think we need to set catagory for components, like different lib for like varistor, connector, etc. ? or after your framework. ;-) 2012-03-26 11:04 yes. just populating Logic - Single :) 2012-03-26 11:04 let's try two levels of category, and then 1, 2, 3... for now 2012-03-26 11:04 GNUtoo has joined #qi-hardware 2012-03-26 11:10 wpwrak, how to use git stash after my http://dpaste.com/721489/ 2012-03-26 11:10 are there any changes you want to keep ? (git diff / git diff --cached ?) 2012-03-26 11:11 wpwrak, i don't want to commit *.pro. so just git checkout -- *.pro ? 2012-03-26 11:12 not sure if this works. try it :) 2012-03-26 11:15 urandom__ has joined #qi-hardware 2012-03-26 11:15 nice, just git pull origin master and pulled your new commit. thanks ! phew~ fires on git for me. 2012-03-26 11:48 hmm, this calls for a new script ... 2012-03-26 11:52 wej has joined #qi-hardware 2012-03-26 11:58 and adam will need scriptable kicad soon :) wolfspraul, the procrastination will be short-lived :) 2012-03-26 12:05 cladamw has joined #qi-hardware 2012-03-26 12:20 cladamw_ has joined #qi-hardware 2012-03-26 12:32 wpwrak: oh I'm glad if we can step up, me included 2012-03-26 12:32 which procrastination? 2012-03-26 12:32 did you see the recent kicad-scripting patch on the kicad list? 2012-03-26 12:33 everybody seems to like that, and it will force the same way of code cleanup that will help cmdline processing 2012-03-26 12:40 I was thinking more specifically about kicad layout today 2012-03-26 12:41 so kicad has no autorouter, or semi-auto router 2012-03-26 12:41 but how bad is the manual one? 2012-03-26 12:41 how efficient or inefficient? 2012-03-26 12:41 mirko: yes, i'm building qt4 for directfb support (as by default for nanonote) 2012-03-26 12:41 can you annotate layout or save layout rules together with the traces? 2012-03-26 12:42 how reusable is a kicad layout if someone wants to make an improved or different board? 2012-03-26 12:43 I was looking at a new Intel board I got (DN2800MT) and I was admiring the traces I saw even on top & bottom. could be a lot of layers too. pretty much all traces seemed to be following a number of rules, lots of pairs, lots of length-matching or other irregular shapes like serpentines, weird angles, etc. 2012-03-26 12:44 so I was wondering how good the 'auto-router' even in the best EDA tools might be 2012-03-26 12:44 maybe in the end you will always need to do a lot of manual intervention on anything high-performance? 2012-03-26 12:44 that Intel board certainly looked like that... 2012-03-26 12:44 the autorouters of today are decent, but it's not trivial to set them up to do what you want to achieve 2012-03-26 12:44 mirko: it's a pity it's working fine for you :) so i guess i'll just wait till it hits buildhost (i guess it already did - all qt4 packages magically failed to build in the last "release"). For now buildhost is stuck building some xfce stuff, which needs to be disabled at all (xiangfu?) 2012-03-26 12:45 jonand: do you know anything about how good/bad/usable/reusable kicad layout is? 2012-03-26 12:47 I don't, I heard about kicad only a few weeks ago when I listened to theamphour podcast in my car. I use Cadence tools at work and I've done a few hobby projects in Eagle a few years ago, but I've never tried Kicad. 2012-03-26 12:48 kicad and geda seem to be the two most advanced free schematics and layout suites (geda is a collection that includes some other tools as well I believe) 2012-03-26 12:48 what is "theamphour podcast"? checking... 2012-03-26 12:49 mirko: another thing: qt4 lacks librt as a dependency. How to reproduce: build a minimal image with qt4 only and some app. When launching the app, it complains for missing librt.so. 2012-03-26 12:49 (scripting patch) lemme check ... 2012-03-26 12:52 I'm not a layout professional, but the rumors are that the Mentor tools are a step up from Cadence. Here is an article on driving the autorouter on a 400 diff pair 16 layer board. http://www.techdesignforums.com/pcb/pcb-topics/constraint-driven-design/learning-the-value-of-preparation-and-simulation-by-osmosis/ 2012-03-26 12:53 mirko: and the lastest thing: dejavu-fonts-ttf package been split into many packages (i think you did that). However, choosing the "dejavu-fonts-ttf" in menuconfig (or automatically via dependencies) doesn't select subpackages. Therefore, the package "dejavu-fonts-ttf" itself is an empty package and now i don't know how to make an application build with basic font support (unless i choose to depend on a specific font from dejavu-fonts-ttf-*) 2012-03-26 12:53 (sorry guys for interrupting... ) 2012-03-26 12:53 Ayla has joined #qi-hardware 2012-03-26 12:53 jonand: excellent link, thanks a lot. I will *definitely* read this. 2012-03-26 12:54 one thing I noticed over the years that as much as people talk about how much they prefer this or that tool, or this or that feature in a tools, or how much superior this or that tool or company is, in reality that mostly speaks for the experience of the speaker more than for the tool 2012-03-26 12:55 in other words - the tools can pretty much all 'achieve' the same results, but over often many years, users of tools get totally intertwined with one particular tool or approach, and then find many reasons to explain why that is so 2012-03-26 12:55 (scripting) sounds promising. let's hope it's not overly tied to having a window. 2012-03-26 12:56 I wouldn't look at anything past kicad or geda these days. 2012-03-26 12:57 (for those 2 pieces - schematic capture and layout) 2012-03-26 12:59 (router) the manual routing is pretty decent. when drawing a trace, it helps you find where to go: DRC will only make points on the same net accessible, "magnetic" pads will draw the trace to the center of the pad, "magnetic traces" will give you drop points off-grid at intersections, and traces can "hug" each other (caution: using this feature, you may have to rip up a number of traces if you want to change anything, since they'll be 2012-03-26 12:59 tightly packed) 2012-03-26 13:00 if werner had to layout such a board, he would write a small parametric tool just for that board :-) 2012-03-26 13:00 (talking about jonand's link, excellent read imho) 2012-03-26 13:00 the parts that are not so good are: traces can't push other traces out of the way (that would be semi-atomatic routing or a "push router"). also, undoing and redoing things needs a lot of clicks 2012-03-26 13:01 and again if you look at 'lessons learned', they didn't use HDI because nobody had experience and they felt they didn't have the time to learn about that 2012-03-26 13:01 and had they known their tool better (I/O Designer), they would have used it differently from the beginning :-) 2012-03-26 13:01 (board example) it does look quite parametric, doesn't it ? ;-)) 2012-03-26 13:02 yes, absolutely 2012-03-26 13:02 I think that would be the right approach to layout such a board 2012-03-26 13:02 actually that's what they are doing, just with tools they don't really know that much about (but learn as they try to throw the first problem at the tool) 2012-03-26 13:03 when I started to work as an electronics designer I soon found out that designing anything that is more advanced than microcontrollers with everything built in requires some knowledge in how boards are built up and why. 2012-03-26 13:03 (kicad routing) what's important is that i never ran into a situation where i felt kicad was abandoning me. you can always solve the problems, even if it's sometimes a bit circuitous 2012-03-26 13:03 jonand: absolutely 2012-03-26 13:03 there are some excellent books on the subject, like Howard Johnson "high speed design - a handbook of black magic", written in the 90s 2012-03-26 13:03 wpwrak: kicad would probably be terribly bad fit for a board like in jonand's text 2012-03-26 13:03 still very valid today - physics don't change... :) 2012-03-26 13:04 yeah. everything manual 2012-03-26 13:04 but then I believe for such a board you might really be best off to write a small meta-tool on top of a simpler base like kicad 2012-03-26 13:04 i mean, it does have autoroute and autoplace. but both are rather cruel jokes 2012-03-26 13:04 that said, I'd really advice anyone designing anything with say an FPGA plus external DDR or a CPU with memory to do some IBIS simulations 2012-03-26 13:05 last time i checked, you couldn't even stop the autoplace. it tightly packs the components right next to each other, without regard for routing, and at glacially slow speed. 2012-03-26 13:05 running SI simulations really make you understand a lot more about how layer buildup, (lack of) ground return paths, and vias will destroy your signals 2012-03-26 13:06 do you have recommendations which free software to use for IBIS simulations? 2012-03-26 13:06 I doubt there are any 2012-03-26 13:06 hmm, we don't have such things for kicad yet 2012-03-26 13:07 something that may be useful to add at some point in time would be a trace length comparison: tell pcbnew which traces should be length-matched, then let it show differences, if any are encountered. 2012-03-26 13:07 ok, one by one. First, you probably meant this book http://www.amazon.com/High-Speed-Digital-Design-Handbook/dp/0133957241/ 2012-03-26 13:07 the most popular commercial ones are mentor hyperlynx and cadence sigxplorer 2012-03-26 13:07 this would still be a manual aid, but i think it could help a lot 2012-03-26 13:08 we tend to blissfully ignore legacy software :-) 2012-03-26 13:08 that's the book, yes 2012-03-26 13:08 (I am joking, no worries, but it's just so much more fun if you can take the tools apart and it's all free and open... don't understand why any serious engineer can accept to work with blackbox tools, oh well :-)) 2012-03-26 13:08 (i firmly believe in automating the things that computers are good at while leaving the things that humans are good at to humans. so, in this example, let kicad do the boring trace length calculation, and let the human figure out what to do with that information) 2012-03-26 13:09 jonand: ok, thanks a lot for that link then, it may come in handy later 2012-03-26 13:09 now IBIS, let me see whether there is anything in FEL, just as a quick search 2012-03-26 13:10 http://www.eda.org/ibis/home/faq/#_1 <-- The parser is freely available in object code format <-- Stallman would explode if he read that line.. :) 2012-03-26 13:11 jonand: he must already have grown a meter of steel skin at that spot :) 2012-03-26 13:11 wait wait, let's see. and btw, the Milkymist One board has a spartan-6 fpga and ddr1 memory, and it's working nice and stable 2012-03-26 13:11 I'm not dismissing ibis, not at all, just happy that we got it this far already. 2012-03-26 13:12 woakas has joined #qi-hardware 2012-03-26 13:12 oh well, no mention of IBIS at all in http://chitlesh.fedorapeople.org/FEL/list.html 2012-03-26 13:13 so another thing to look at later :-) 2012-03-26 13:13 (kicad routing) you can save certain design rules: you can categorize nets and assign a track width, clearance, and via parameters to them. all a but crude, though. 2012-03-26 13:15 how is milkymist related to qi-hardware? 2012-03-26 13:15 thanks for asking 2012-03-26 13:15 Milkymist SoC first is an SoC project 2012-03-26 13:15 (cure) e.g., if you have a high-current trace and the trace for a level probe going to it, then both would be the same net and you therefor would have the same trace width for the probe. that is, without switching off DRC or inventing a magic component that splits the trace 2012-03-26 13:15 s/cure/crude 2012-03-26 13:15 wpwrak meant: "(crude) e.g., if you have a high-current trace and the trace for a level probe going to it, then both would be the same net and you therefor would have the same trace width for the probe. that is, without switching off DRC or inventing a magic component that splits the trace" 2012-03-26 13:15 uses the open LM32 core from lattice (about 25% of the codebase), and then a lot of gpl-licensed peripherals around that 2012-03-26 13:16 then there's a lot of stuff on top of the SoC to actually make it work in a practical environment 2012-03-26 13:16 namely a BIOS, rtems kernel, flickernoise app 2012-03-26 13:16 all of this then comes out as the Milkymist One video synthesizer 2012-03-26 13:16 I met sebastien at HAR2009 where he presented the milkymist, but I'm not up-to-date with what happened with the platform since then. 2012-03-26 13:16 a hardware product you can buy for 500 USD 2012-03-26 13:17 oh nice 2012-03-26 13:17 just checkout milkymist.org or https://sharism.cc/milkymist for the product 2012-03-26 13:18 I wish we can build more focus still, make the SoC stronger, get a really good Linux kernel to run on it, improve the toolchain, improve the Flickernoise app, improve the hardware, improve a lot of things 2012-03-26 13:19 and... it's one thing to get a digital design to work, it's another to get through regulative testing (especially radio interference testing) and to have margins for variations in board impedance, operating temperature, component tolerances and so on. 2012-03-26 13:19 sure 2012-03-26 13:19 but it's also nothing to be afraid of 2012-03-26 13:19 designing is fun, the rest is why they pay you the salary.. :) 2012-03-26 13:19 and from a lot of industry experience, I can tell you - not every company is run like Apple 2012-03-26 13:20 in other words - there is *lots* of junk out there selling in high volume, and nobody cares 2012-03-26 13:20 run like Apple? 2012-03-26 13:20 I am pretty sure the engineering & build quality of the Milkymist One is already in the top 50% of consumer electronics quality that is typically selling in eu/us 2012-03-26 13:21 well, if you are in the fire-and-forget business you can get away with a lousy design. If you have to deal with 20% returns you better have decent margins to be able to afford the bad quality products... 2012-03-26 13:22 I think it's not that easy 2012-03-26 13:22 most hardware manufacturers are under a lot of pressure, mostly cost pressure 2012-03-26 13:22 because that's what consumers care about the most, and it goes all the way through to the component makers 2012-03-26 13:23 jonand: (fire and forget) or have an efficient business card printing service, for when you make the weekly change of the company name ;-) 2012-03-26 13:23 i think you should get suspicious if a company has a day in its name :) 2012-03-26 13:24 lol 2012-03-26 13:24 nah, I'm talking about something else 2012-03-26 13:24 say you buy a computer from "HP" 2012-03-26 13:24 you think anyone at HP knows anything about this computer? 2012-03-26 13:24 in the shiny TV ads they do 2012-03-26 13:24 but only there 2012-03-26 13:25 in reality it is designed at some company A, which maybe using one or several reference designs from companies B and C 2012-03-26 13:25 and which are again outsourcing certification issues to companies D E and F 2012-03-26 13:25 "designed in america" ? :) perhaps some case parts ... 2012-03-26 13:25 then it's handed over to company G for manufacturing 2012-03-26 13:26 which is using subcontractors H I and J for parts of the volume 2012-03-26 13:26 and so on and so on 2012-03-26 13:26 and if you think that all of those really really care about operating temperaturs, board impedance variations, electromagnetic emissions, etc. oh well 2012-03-26 13:26 then you may not have seen all too much into the work of those companies :-) 2012-03-26 13:27 jow_laptop has joined #qi-hardware 2012-03-26 13:27 it's about having someone to blame. if you order 1000 laptops for your company and 20% are DOA, then you'll have a hard time explaining why you bought them from Happy Shenzen Wednesday Ltd. on the other hand, if you bought them from HP, even if they were still made by Happy Shenzen Wednesday, your ass is safe 2012-03-26 13:27 it's funny how company A proudly makes "a" board that passes an EMI test, and then hands over that board to company B for the "volume production" 2012-03-26 13:27 which will after a few days remove the 'unnecessary' parts that made the board pass the EMI test earlier 2012-03-26 13:27 and so on 2012-03-26 13:28 it's not just about returns, doa, 20% 2012-03-26 13:28 yeah, there's worse 2012-03-26 13:28 zenlunatic has joined #qi-hardware 2012-03-26 13:28 jonand: I'm working in greater china for about 5 years now, and I think I've pretty much seen all the pieces now :-) 2012-03-26 13:28 failure in the field. unstable operation. incompatibilities. and so on 2012-03-26 13:29 jonand: when wolfgang grows bored of computers, he'll become a successful writer of horror novels 2012-03-26 13:29 sure 2012-03-26 13:29 so some notebooks have an average life expectancy of 2 years, some more like 5 2012-03-26 13:30 it's just super hard to pin it down to a specific company or missing quality check or unqualified staff somewhere in the chain 2012-03-26 13:30 so how does Qi deal with these issues? 2012-03-26 13:30 don't understand 2012-03-26 13:30 what do you want to hear :-) 2012-03-26 13:31 marketing speak: Qi is making the absolute *best* hardware you can possibly, ever, find - in the WHOLE WORLD. 2012-03-26 13:31 for example I assume Qi is vulnerable to stuff like what you said above: which will after a few days remove the 'unnecessary' parts that made the board pass the EMI test earlier 2012-03-26 13:31 meaningless blurb, but it's what you hear from everybody else as well 2012-03-26 13:31 no, not at all 2012-03-26 13:31 we are extremely vertically integrated 2012-03-26 13:31 pabs3: qi doesn't have this sort of deep delegation 2012-03-26 13:32 as open hardware that's almost always included in the deal 2012-03-26 13:32 the only other company that vertically integrated I'm aware of is Apple 2012-03-26 13:32 pabs3: and wolfgang can probably smell a deal that's too good to be true by now 2012-03-26 13:32 althouhg there may be other smaller ones too, of course. in vertical industries. 2012-03-26 13:32 I see :) 2012-03-26 13:33 what deal? 2012-03-26 13:33 :-) 2012-03-26 13:33 hardware quality is difficult to explain 2012-03-26 13:33 and honestly I think most people don't care that much, they just want to hear some fluffy words that makes them believe that what they buy is "good quality" :-) 2012-03-26 13:33 the usual "it's chine, so it must be cheap" meme. not sure if it has died out yet or if there are still lots of western companies that fall for it 2012-03-26 13:34 fair enough, since the actual situation is so complex and subtle, you don't want to hear about it 2012-03-26 13:34 so we also just say: Qi is making great quality hardware 2012-03-26 13:34 <1% returns 2012-03-26 13:34 done 2012-03-26 13:34 :-) 2012-03-26 13:34 passes "all" certs 2012-03-26 13:34 of course 2012-03-26 13:34 our hardware is perfect, the best 2012-03-26 13:34 always 2012-03-26 13:34 drop it from an airplane, and it will still work! 2012-03-26 13:35 ... as long as it doesn't hit anything. but that's covered by a different clause in the warranty 2012-03-26 13:36 pabs3: btw, if you make Qi hardware, which of course you can, then you automatically fall under our quality guarantee 2012-03-26 13:36 how is that??? 2012-03-26 13:38 i think his question was more about avoiding the practical pitfalls :) 2012-03-26 13:38 actually it may sound like a joke, but the quality 'handover' in reality is often not much different 2012-03-26 13:39 i guess a lot is based on reputation and perhaps past experience 2012-03-26 13:39 people like werner who start to philosophize over ever last word and punctuation in a spec or standard are rare in the industry 2012-03-26 13:40 there are many cases where parts, standards, procedures are bouncing back and forth between a number of companies until "it fits" 2012-03-26 13:40 it's one thing to have to pay for expensive ferrites and common mode chokes because you try to filter your way below the EMI limit. It's another to have the correct series termination from start because you spent an hour or two simulating your address bus. 2012-03-26 13:40 I preach EMC compliance by design, not by filter/screening 2012-03-26 13:40 yep 2012-03-26 13:40 it won't survive the first day "on the line" 2012-03-26 13:40 which is really just band-aid when you've produced thousands of PCBs already 2012-03-26 13:40 well, mabe if the EE has a day off, on the first day it will stay there 2012-03-26 13:41 but on the second when he's back it will be removed 2012-03-26 13:41 US client to chinese engineer, in the telephone conference: "did you read the spec ?" "Yes." "does it comply ? "Yes." ... :) 2012-03-26 13:41 thing is that IMMUNITY noncompliance is what will kill you 2012-03-26 13:41 don't worry we are all on the same page here 2012-03-26 13:41 routers that hang when not resetted after a brownout will kill that router brand name 2012-03-26 13:41 I think one promise of open hardware is that we can go for *higher* quality than usual 2012-03-26 13:42 (that's more or less this sort of real life conference calls i've experienced. oh, and that was of course a non-affirmative "yes". the person in question didn't understand a single word :) 2012-03-26 13:42 because open designs can be shared and reused and better understood among more people 2012-03-26 13:42 we are not just dreaming about this, but making functioning high-performance gear 2012-03-26 13:43 which we sell and service and take back on failure, etc. etc. 2012-03-26 13:43 and which passes fcc/ce emi compliance, and what not 2012-03-26 13:43 higher quality and also actually explain what's needed and why. regulations are not made up of evil people, they are a compromise on what will work reliably out in the field. the sad thing is that they tend not to explain WHY they are needed, which make them appear like a penalty rather than a help 2012-03-26 13:43 I agree 2012-03-26 13:43 standards are important 2012-03-26 13:44 tracking the background of things is often rather hard indeed 2012-03-26 13:44 and once that chain is lost, you're in the merry land of cargo cult and voodoo engineering 2012-03-26 13:45 or standards-as-a-penalty 2012-03-26 13:45 I don't think like that 2012-03-26 13:45 a standard is either good and thus followed, or ignored 2012-03-26 13:46 naw you also get the bad ones you still have to follow. and some may actually be good, but they look bad 2012-03-26 13:46 and if enforcement is nasty enough, everybody follows them, even if they're bad 2012-03-26 13:46 of course I say this with the liberty of looking from Beijing, which means that if the 20% of the world population really doesn't want product A because they actually enforce standards, then we sell it to the other 80% only :-) 2012-03-26 13:46 no matter how much band aid you have to pour on that board 2012-03-26 13:46 and we make a version A+ with even higher margin for those 20% 2012-03-26 13:47 the high cost of those non-fake certificates :) 2012-03-26 13:47 those 80% can go reset their router every second day, I'm fine with that. 2012-03-26 13:47 sure, but that's how bad regulations are flushed out 2012-03-26 13:47 and I agree that most are good 2012-03-26 13:48 jonand: that's one minimum wage job. not too bad :) 2012-03-26 13:48 because if a regulation is meaningless, the 80% will find out and decide with their wallets 2012-03-26 13:48 so you are located in Beijing? 2012-03-26 13:48 don't underestimate those wallets 2012-03-26 13:48 yes 2012-03-26 13:48 how's the electronics industry there compared to shanghai? 2012-03-26 13:48 shanghai or suzhou? 2012-03-26 13:49 there's companies everywhere 2012-03-26 13:49 don't understand 2012-03-26 13:49 wolfspraul: i think it's more complex. people also attach different values to longevity, cost of failure, cost of replacement, etc. 2012-03-26 13:49 wolfspraul: as in "level of competence, level of wages" and so on 2012-03-26 13:50 sure, but I think we all agree on A) following regulations and going for good standards b) identifying the bad/meaningless/stupid standards as such and trying to at least advocate them as bad 2012-03-26 13:50 and I think for the most part the quality of standards is actually good 2012-03-26 13:50 wolfspraul: so if jonand really hates to have to rest his router, he may find having to spend 50% more a very good deal. meanwhile, the room full of routers in the Great Chinese Firewall may very well just have a few sidekicks that do nothing but look for lights that are "stuck" and press the little red button under it 2012-03-26 13:51 panda|x201 has joined #qi-hardware 2012-03-26 13:52 yeah but I think we are all on the same page 2012-03-26 13:52 we all like quality products that we deeply understand and that we know we can trust and are reliable and follow the best standards, and and and 2012-03-26 13:52 :) 2012-03-26 13:52 yet still at any moment we know any tiny resistor or cap on our super board may fail, for a variety of reasons 2012-03-26 13:53 and will we notice? 2012-03-26 13:53 depends :) 2012-03-26 13:53 will one of our beloved standards now not be met anymore without us noticing? 2012-03-26 13:53 that is very possible 2012-03-26 13:53 or do you check your home regularly for electromagnetic offenders? 2012-03-26 13:54 (for example) 2012-03-26 13:54 probably not 2012-03-26 13:54 so in reality complex hardware is always subtle, and may fail in subtle ways. no matter how well we design it, manufacture, test, etc. 2012-03-26 13:54 i'm probably the biggest of them within some 50 m bubble ;-) 2012-03-26 13:54 Actually, my spectrum analyzer is powered on most of the time.. :) 2012-03-26 13:55 there you go :-) 2012-03-26 13:55 typically not hooked up to any antenna though.. . 2012-03-26 13:55 jonand: even better for finding offenders ;-) 2012-03-26 13:56 GNUtoo-desktop has joined #qi-hardware 2012-03-26 13:56 GNUtoo-desktop has joined #qi-hardware 2012-03-26 13:57 but again, immunity is the important thing. if your device locks up just because someone is flipping the light switch, the fridge/ac compressor is starting or your neighbour is welding... you will get customer complains killing any margins/profit you thought you had on your design 2012-03-26 13:57 wolfspraul: component failure is random. but you can still influence how often it happens and what consequences it has. if you just say "anything can fail anytime anyway", then that's like saying that it's okay to sleep with a piece of radium under your cushion because anyone can get cancer anyway 2012-03-26 13:57 I am clear about that 2012-03-26 13:58 kyak: regarding librt and dejavu-font-package i'll take a look now 2012-03-26 13:58 but we speak in an open and logged channel, so it may be important to try to open up the minds of whatever unknown reader masses may read this one day 2012-03-26 13:58 and - every solder joint may fail at any time 2012-03-26 13:58 jonand: i think the most important thing in our case is that the community can also help itself 2012-03-26 13:59 and a device with bad signal integrity (lots of energy radiated as radio interference) is way more likely to be susceptible for say your cell phone transmitting at 1W peak 2012-03-26 13:59 more likely than a design with a proper layout 2012-03-26 14:00 so I see it the other way around. If a device is quiet (and not filled with screens and ferrites) I know it is solid 2012-03-26 14:00 modern computing hardware is just very subtle, and for the most part cannot self-analyze much if anything 2012-03-26 14:00 so there is always a huge variety coming off the production line, and from then on with every day that passes it only gets more diverse 2012-03-26 14:01 jonand: quiet? 2012-03-26 14:01 jonand: continuously improving our design processes is certainly part of the concept 2012-03-26 14:01 jurting has quit ["Leaving"] 2012-03-26 14:01 I also think we have to go *way* beyond just thinking about the perfect design 2012-03-26 14:02 to testing software, during production and after a product is sold, testing under all sorts of stress, seeing how designs look like after some time of usage, etc. 2012-03-26 14:02 jonand: even better, anyone can help. e.g., you know a lot about EMC. most people don't. we're not even sure how good the people to whom we outsource the M1 layout are in that regard. we believe they're good overall, but we might miss some weak spots. or a bad day, etc. 2012-03-26 14:03 jonand: but the results are openly accessible. (the design files as well, but they use proprietary tools. that's why we want to move to kicad.) so you could review them, and tell us if you find anything suspicious. 2012-03-26 14:04 a lot... well, I've learnt some the hard way by spending far too much time at regulatory test houses.. :) 2012-03-26 14:04 wolfspraul: quiet as in "does not max out my spectrum analyzer when I approach it with a near field probe" 2012-03-26 14:04 jonand: and once we learn some new rules, they can be shared with others who may not have much experience but still a good pair of eyes :) 2012-03-26 14:04 ah, quiet on the spectrum analyzer, got it 2012-03-26 14:05 jonand: what spectrum analyzer do you use if I may ask? 2012-03-26 14:06 jonand: (filled with screens and ferrites) you would have loved one project i bumped into in a former life. it had GPS and lots of interference issues. so piles of EMI filters were added and so on. 2012-03-26 14:06 I have an old hameg. Been thinking about upgrading but then again I'm not really an RF guy, more into the digital domain. Not that those are too wide apart these days though.. :) 2012-03-26 14:06 can you do us a favor and post the exact hameg model? 2012-03-26 14:07 we are a bit obsessed about learning here :-) 2012-03-26 14:07 jonand: (evil project) it also had another issue: USB would inexplicably fail from time to time. they thought it was a kernel issue. so i searched for that. didn't find anything overly suspicious. then we poked around signal integrity and such. nothing. 2012-03-26 14:08 jonand: (evil project) then we suspected power distribution: power entered at the top of the CPU and then went in a merry almost-circle around it. so we added beads, caps, etc., to fix that routing. still nothing. 2012-03-26 14:08 wolfspraul: http://www.hameg.com/0.45.0.html?0= <-- HM5014 2012-03-26 14:08 thanks! 2012-03-26 14:09 If you are to buy anything I would suggest to get one which covers up to 2.6G 2012-03-26 14:09 this one is intended for precompliance EMI tests and is limited to 1G 2012-03-26 14:10 jonand: (evil project) finally, on the day the EEs would sign off the layout for the next (and probably last) try, i stumbled into their layout review meeting. there, i saw the following: 2012-03-26 14:10 but then you miss out the 2.4g band and also the LNB downlink from your satellite dish 2012-03-26 14:10 950-2150 2012-03-26 14:11 jonand: (evil project) CPU had its XTAL connections in the 4 o'clock position. the crystal was located in the 10 o'clock position, with traces going all the way across the CPU, and even nicely to the other side of the PCB and back. 2012-03-26 14:12 wpwrak: did you laugh or cry? :) 2012-03-26 14:12 jonand: (evil project) to top this, right under the xtal traces, there were the DRAM signals. naturally, no ground in between or left or right. 2012-03-26 14:13 jonand: i was actually quite happy :) we had spent something like two months on that problem, and all the band aids we had thrown at it seemed futile. when i saw that mess, i know we had found it :) 2012-03-26 14:13 actually, routing clock traces across the board is not that bad, IF you 1. keep your signal return in a solid ground plane below the trace 2. stay on one layer 3. have proper termination 2012-03-26 14:14 jonand: here's a milkymikst one emi document, any feedback would be more than welcome http://en.qi-hardware.com/w/images/1/1a/Reichl_milkymist_one_tests_11000301.pdf 2012-03-26 14:14 and 4. stay away from board edges 2012-03-26 14:15 jivs has joined #qi-hardware 2012-03-26 14:15 jonand: we couldn't clean it up completely at that time, but we could at least remove the very worst offenses. like pushing the traces a few mm to the side. and that already was enough to make the thing work well enough to proceed. (the project died later for other reasons, so i think the design was never fully cleaned up, though) 2012-03-26 14:17 jonand: (routing clock) yeah, there were none of these niceties. plus, this was to the "naked" crystal. not some nice differential digital signal or such. 2012-03-26 14:18 jonand: that design was more or less a textbook example illustrating everything you should never do 2012-03-26 14:20 jonand: one problem was that all the EDA things were behind proprietary tools. so already getting printable schematics was difficult. and i hardly saw the layout at all (before that fateful day). why the EEs who had had all this right in front of their noses the whole time didn't see it is a bit of a mystery to me, though. 2012-03-26 14:28 wolfspraul: wow, pretty low emissions in that report! 2012-03-26 14:29 so is this the current layout? http://milkymist.org/mmone/rc3_gerber.tar.bz2 2012-03-26 14:33 kyak: hmm.. the font stuff gets complicated - it was tried to get fixed by mb however i reverted that commit since it broke other stuff 2012-03-26 14:34 the ksz8001 contains an ibis model... "let me download and have a look".. 2012-03-26 14:39 low enought to allow us easilly to add built-in antennas for GPS and posibly other RF aplicationsn? 2012-03-26 14:39 hi jonand :) 2012-03-26 14:39 rozzin has quit [#qi-hardware] 2012-03-26 14:46 jonand: yes from the name that looks like the current gerbers 2012-03-26 14:50 kristianpaul: to know that you need to know what you have at GPS and the other RF bands you are considering.. therefore my advice on getting a spectrum analyzer covering the popular bands... 2012-03-26 14:50 urandom__ has joined #qi-hardware 2012-03-26 15:09 now, where to find a cheap one :) 2012-03-26 15:11 rtl-sdr wont work for that?.. 2012-03-26 15:16 you mean something like USRP ? it does, but it has its limits 2012-03-26 15:19 mirko: i see.. probably it makes sense to combine it back into a single package? Usually the fonts wouldn't be installed on routers, so... 2012-03-26 15:21 wpwrak: yes 2012-03-26 15:21 e.g., lack of calibration, quite limited bandwidth, and you also need several RF frontends if you want to cover the whole spectrum to 2.x GHz (the latter aspect has gotten a bit better recently, though. now you only need two boards for most of the interesting frequencies) 2012-03-26 15:25 kyak: hmm.. not sure yet 2012-03-26 15:26 but yes, it's far better than nothing :) 2012-03-26 15:47 emeb has joined #qi-hardware 2012-03-26 16:08 kuribas has joined #qi-hardware 2012-03-26 17:54 rozzin has joined #qi-hardware 2012-03-26 19:04 LunaVorax has joined #qi-hardware 2012-03-26 19:55 infobot has joined #qi-hardware 2012-03-26 19:58 uwe_ has joined #qi-hardware 2012-03-26 20:07 antgreen has joined #qi-hardware 2012-03-26 20:28 viric_ has joined #qi-hardware 2012-03-26 20:33 * kristianpaul wonders if there are programable LNA's 2012-03-26 21:06 LunaVorax has joined #qi-hardware 2012-03-26 21:08 LunaVorax_ has joined #qi-hardware 2012-03-26 21:20 jekhor has joined #qi-hardware 2012-03-26 21:22 Ayla has joined #qi-hardware 2012-03-26 21:54 frankblues has joined #qi-hardware 2012-03-26 22:14 dvdk has joined #qi-hardware 2012-03-26 22:32 aisa has joined #qi-hardware 2012-03-26 22:56 aisa has joined #qi-hardware 2012-03-26 23:11 wpwrak: with rtl-sdr kristianpaul meant this one http://sdr.osmocom.org/trac/wiki/rtl-sdr 2012-03-26 23:11 it's a 10 USD usb dongle, which although receive-only seems to give you a good starting point into gnuradio & sdr 2012-03-26 23:11 tuner goes from 64mhz to about 1700mhz 2012-03-26 23:12 demodulator can be configured to send raw samples to the host 2012-03-26 23:12 oh dear :) 2012-03-26 23:12 USRP looks rather powerful in comparison ;-) 2012-03-26 23:13 but yes, the principle is the same. just that rtl-sdr doesn't cover some of the most interesting frequencies 2012-03-26 23:13 sure, but at 10 USD it allows people to first focus on the software side 2012-03-26 23:13 and then when they really understand the various subtleties, they can uptick their hardware as needed 2012-03-26 23:13 I do think that makes a lot of sense 2012-03-26 23:15 the price in unbeatable, agreed. and it's sufficient to, say, listen into FM or some GSM 2012-03-26 23:15 s/in/is 2012-03-26 23:15 wpwrak meant: "the price is unbeatable, agreed. and it's sufficient to, say, listen isto FM or some GSM" 2012-03-26 23:15 or local TV, its original purpose 2012-03-26 23:15 or maybe taxi radio, police radio? satellite phones? 2012-03-26 23:16 it's 20 USD by the time someone with some english skills has put it on an international shopping site 2012-03-26 23:17 :) 2012-03-26 23:19 pity it doesn't go a little higher. 800 MHz more and there would be lots of ISM band fun 2012-03-26 23:19 well, lots more ISM band fun 2012-03-26 23:19 maybe one or two ic gens later? :-) 2012-03-26 23:20 if they don't pull the feature :) 2012-03-26 23:20 there are 2 chips left now, a realtek demodulator/soc, and an elonics tuner although that one seems replacable with alternatives from fitipower, noxon, etc. 2012-03-26 23:20 sure they can, it's a more or less typical "found a chance" reverse engineering effort 2012-03-26 23:21 but so what, it gets people started, they learn, and then become more agile and more independent later 2012-03-26 23:22 when the products approach EOL, there may be an opportunity to buy up a lot of them and sell them with a nice margin once they get de facto unobtainable 2012-03-26 23:22 (they have another, I believe even s-6 fpga based osmosdr board in the making, including tx, but the discovery of this 10/20 USD dongle distracted them a little. so the alternatives are already in the making...) 2012-03-26 23:23 I'm not so pessimistic at all, no need to do that. 2012-03-26 23:23 (distraction) i can imagine :) 2012-03-26 23:23 it would be a service 2012-03-26 23:24 ics actually rarely go eol, most of the time the new chips are just better for everyone - and - a lot of ic companies are handing over old chips to specialized small companies that are making old chips 'from the archive' for as long as there are customers willing to pay the premium 2012-03-26 23:25 that's not always true, for example if a chip is closely tied to a particular manufacturing technology which is also being dismantled or upgraded as the new gen comes out 2012-03-26 23:25 yes, but once the boards don't get made anymore, the overall cost jumps up. even if you can still get the chips. 2012-03-26 23:25 but in a lot of cases it's true, smaller more niche chips 2012-03-26 23:25 oh sure, costs go up and up if you step outside of the big stream 2012-03-26 23:26 well, SDR is the future. good to see it get more accessible. 2012-03-26 23:26 yes