#qi-hardware IRC log for Tuesday, 2010-08-24

qi-bot[commit] Andres Calderon: USB D routing started http://qi-hw.com/p/xue/bbf8fde00:11
kyakunclouded: hi, did you actually get nightsky working?01:48
kyakbecause 1) it won't build, but i fixed it with -rpath-link and 2) it runs, but hangs and does nothing01:49
uncloudedkyak: yes, I installed the package to my NN and it started01:50
kyakhm, that's strange01:50
uncloudeddoes it write anything to stdout before hanging?01:50
kyakdo you have the latest everthing?01:50
kyakno, it writes nothing01:50
kyakwhen i strace it, the last line is getuid() = 0 and then nothing01:51
uncloudedit's looking for the user's home directory01:51
kyakyeah, i know01:51
uncloudedthe next call should get getpwuid01:51
kyaki tried to change it (i.e. hardcode the path to yml file), but it still hangs01:52
kyakin a weirdest way01:52
kyakthere are two ioctl's, and after that - nothing01:52
Action: unclouded scratches head01:52
uncloudedis path_to_data set to some really long path or is it the default?01:54
uncloudedalso, I thought the Makefile used rpath-link already?01:56
uncloudedkyak, could it be RAM?  how much free RAM have you got?01:59
kyakfor the RAM, i have swap enabled, so should be no problem02:01
kyaki have warnings about rpath-link not enabled that prevent from building.. so i had to add it manually to TARGET_LDFLAGS in openwrt's Makefile02:02
kyakthen it builds.. i rememeber you use openwrt SDK instead of toolchain, could it be the difference between us?02:02
kyaki tried to printf path_to_data, but it won't output (i.e. it doesn't even call "write")02:03
kyakit hangs somewhere before02:03
kyakand the strangest thing is, when i uncomment this line where is checks for home dir, strace output is finished after getuid()02:04
kyakunfortunately, i can't check anything right now.. would be good to check this path_to_data before call to getuid()02:06
uncloudedwhich is the SDK and which is the toolchain?  Just now I did git pull on openwrt-xburst  and did package/nightsky/{clean,install} V=99, reinstalled in on the NN and that works02:06
kyakthan it's toolchain that you have02:06
kyaki me, too02:07
kyakwe should be on the same level then02:07
kyakwith the same hardware :)02:07
uncloudedexactly.  we shouldn't see any differences! :(02:07
uncloudedcould it being a glibc/uClibc thing?02:07
kyakdid you do make package/symlinks?02:08
kyaki think recently they switched to uClibc-0.9.3202:08
kyakdo you have it in your build_dir?02:08
uncloudedI don't remember.  probably not, just scripts/feeds update -a && scripts/feeds install -a02:09
uncloudedlet me check02:09
kyakah, this is the same02:09
uncloudedno, I've got: build_dir/toolchain-mipsel_gcc-4.3.3+cs_uClibc-
kyaknow this is the difference!02:10
kyaki've got02:10
uncloudedmaybe you used to use 0.9.31 and there are still bits of it around?02:11
kyakmm, i rememeber is cleaned up02:12
kyakbut a good idea, i will cleanup02:12
kyaki suggest you clean up, too :)02:12
uncloudeddidn't I read somewhere there's a separate toolchain clean?02:12
kyakthere's a make clean02:13
kyakalso make toolchain/clean etc02:13
kyakbecause i noticed that make clean doesn't clean everything02:13
uncloudedit will take me a while to rebuild.  old hardware02:14
kyakme too02:15
kyakalso, my CPU heats up to 92 C :)02:15
uncloudedwow.  what type of CPU?  Intel?02:16
uncloudedthere's a make distclean too apparently02:16
uncloudedI'm reading here: https://forum.openwrt.org/viewtopic.php?id=918002:16
uncloudedit says that "make clean" does not clean the toolchain.  is uClibc considered part of the toolchain?02:17
kyakdistclean is bad :)02:17
kyakit removes your downloaded packages02:17
uncloudedsure?  that page says "cleans up everything expect $(TOPDIR)/.config and $(TOPDIR)/dl/"02:17
kyaki did: make clean, make target/clean, make toolchain/clean, make tools/clean02:18
uncloudedmaybe it's out of date02:18
uncloudedok, I'll do the same02:18
kyakPentium(R) Dual-Core  CPU      E6500  @ 2.93GHz02:18
kyakmy CPU02:18
kyaknow to update and rebuild02:18
uncloudednot that old then!  I'm building on Mobile AMD Athlon(tm) 64 Processor 320002:19
kyak$ du -sh build_dir/02:19
kyak6,8G    build_dir/02:19
kyakstrange.. i think i'll just rm al manually02:20
kyakwhat is the machine you have there? a laptop?02:20
kyakold good laptop is living his last days somewhere under your bad :)02:21
kyakso i'm wondering.. maybe you're right and we need to make distclean02:22
kyaki don't like these leftovers in build_dir02:22
uncloudedit's pretty good as an Internet gateway.  doesn't use much electricity and runs OpenVZ and apache2 and so on just fine02:22
kyaki expected them to disappear02:22
uncloudednot so hot for building but better than my actual laptop, which is a Pentium4M - even slower02:23
uncloudedis build_dir there when you first "git clone"?02:23
kyakshould not be02:23
uncloudedmust be safe to remove then: it's all been generated02:24
kyakso i just made distclean02:24
kyakbe warned, dl/ dir disappeared02:24
kyaki'll re-download, that would compensate for my CPU "speed" and we should finish together :)02:25
uncloudedwhich command are you using to "make".  can I avoid compiling the kernel again?02:25
kyakbrb, sorry.02:25
uncloudedno worries02:26
kyaki just "make".. or what do you mean?02:35
kyakalso, distclean removed the .config.. i'll take the one from data/qi_lb60/conf/config02:35
kyakok, i used the default config, only chose "nightsky", now making02:40
uncloudedthat doc must be old then sorry.  it says it -won't- remove .config02:42
uncloudedalso, I could just give you an .ipk to see if that works on your NN.  then we'd know for sure that it's something in the build system02:43
kyakthat's a good idea02:45
uncloudeddoes that work on your NN?02:56
kyakunclouded: won't be able to try it for at least another 8 hours03:01
uncloudedthe build or the .ipk?03:02
kyakthe .ipk03:02
kyakbuilding now, but will also try later at home03:02
uncloudedok, no problem.  I'll leave the file up there then03:02
kyakok, thanks!03:03
qi-bot[commit] Werner Almesberger: Update IRQ_RF after reworking both boards. IRQ_RF was erroneously connected http://qi-hw.com/p/ben-wpan/738618a05:17
qi-bot[commit] Werner Almesberger: Finished and tested TX/RX. (LQ doesn't work yet, the rest does.) http://qi-hw.com/p/ben-wpan/73043a505:17
uncloudedkyak, I rebuilt my OpenWRT from clean with "make tools/install toolchain/install package/nightsky/install" and it built ok.  hope yours rebuilds ok from clean05:22
kyaktslib.cpp:42:19: error: tslib.h: No such file or directory05:25
kyakstupid qt4 won't compile again05:25
kyakClock.h:10:21: error: SDL/SDL.h: No such file or directory05:28
kyakthis is nightsky05:28
kyakactually, something is wrong with your toolchain05:28
kyakit should NOT compile nightsky05:28
kyakbecause it depends on sdl, and by make package/nightsky/install you don't  build dependcies05:29
kyakat what point exactly was your libsdl and sdl-image build exactly after cleanup?05:30
uncloudedtrue.  I didn't rm build_dir as you did05:34
uncloudedso libsdl must still have been lurking there05:34
kyaknow i'll just wait for someone to fix qt405:36
kyak(as usual)05:36
kyakdamn i get so pissed every time is is broken AGAIN upstream05:36
kyakhow are they testing??05:37
uncloudedcan you build libsdl and libsdl-image without building qt4?05:44
kyaki'd like to avoid it05:53
kyakit means manually building dependencies for libsdl and libsdl-image and dependencies of depenedcies.. and so on]05:54
uncloudednot fun05:55
uncloudedshame the build system can't do it auto.  the data is there05:55
uncloudedonce a package has been ported to openwrt-packages, what has to happen before it's available for installation via opkg?06:10
kyaki think it has to be included in the next build :)06:16
kyaki mean, next release of image for Ben06:17
qi-bot[commit] Werner Almesberger: Setting the transmit power was broken. (And LQ works, by the way.) http://qi-hw.com/p/ben-wpan/251480406:20
wolfspraulkyak: when you say qt4 is broken 'upstream' - where do you mean?10:14
wolfspraulin openwrt?10:15
wolfspraulI think mirko is quite active on all things qt410:15
wolfsprauldoes he know what is broken? what is broken? :-)10:15
kristianpaulwpwrak: hey11:03
kristianpaulyou planning use CPLD to interface SPI?11:03
kristianpaulhmm i have XC2C64A board from digilentic if you need try a core or something11:08
kristianpauli need SPI plus some glue logic too11:08
qi-bot[commit] Andres Calderon: USB A Phy has been routed http://qi-hw.com/p/xue/3eea34811:17
qi-bot[commit] Andres Calderon: minor routing progress http://qi-hw.com/p/xue/c3ab9ef11:17
wpwrakkristianpaul: i was inquiring about how hard/easy it would be to make an SPI to SPI bridge for the software-defined GPS wolfgang is considering. it would basically be a chip that outputs an SPI-like stream of quadrature samples at a few Mbps.11:29
wpwrakkristianpaul: since the ingenic cpu can only be an spi master, not an spi slave, we would need some glue logic with a (very) little buffer to translate between the two.11:30
wpwrakkristianpaul: my question is just if the simplest and cheapest CPLD is already good enough or this or if we need something more powerful. i'd leave the implementation to the experts ;-)11:31
wpwrak(well, if sebastien one day writes a free synthesis tool for fgpas and such, i might be interested to play with programmable logic. verilog looks kinda nice :)11:33
kristianpaulyeah is nice :)11:34
kristianpauli'm learning using the MM SoC11:34
wpwraknice way to get started ;-)11:35
kristianpauli can acept Xilinx for now is the only non-free stuff i use in electronics11:35
kristianpaulbtw are your aware of GPS signaniling and processign ?11:36
kristianpauli'm just learning too amazinf topic btw11:36
kristianpaulah i founded losts of free sofware projects involved around, great !11:36
wpwraki have one non-free thing crawling about on my systems, and that's the windows-only (and non-wine) 3d scanning application. that's already more than enough for my taste ...11:37
kristianpauli have my heekscad is okay for my 3d needs11:37
wpwrak(gps) i don't really know about. wolfgang just asked me a few questions about which rf frontends would generally fit, assuming you want to do as much as possible in software. there's someone else working on a dsp-based gps reciver we could then adapt. (or that's the theory)11:38
kristianpauli see11:39
wpwrakalas, heekscad doesn't speak the proprietary protocol my cnc mill uses when scanning :-( and reverse-engineering it isn't quite easy either. it's already hard to snoop it in a useful way :-(11:39
kristianpaul3d is hobbiest so i dont hurge for high advanced features11:40
wpwrakwell, one day i'll try ... but for now, i'll just live with having an enemy (i.e., a windows box) in my camp11:40
wpwrakvery high-end 3D gets expensive anyway ;-)11:41
kristianpaulif you can handle is okay11:41
kristianpaulbtw what do you think is the trugput that the Ben Xbust can support on its gpio pins?11:42
kristianpauli dint check datasheets in depth hoping find that info11:42
wpwrakhmm, you mean the highest frequency at which you can toggle a gpio ?11:43
kristianpaul(sorry my english dictionaary is small)11:44
wpwraki would expect a few dozen mhz. almost certainly < 100 MHz, though. the limiting factor should be cpu cycles and the internal busses.11:45
wpwrakyou can write a little assembler program that sets a gpio on and off. you probably need to unroll the loop, though, for an accurate measuement.11:45
kristianpaulany Xburst hacker around?11:46
kristianpaulywah i was thinking in asm right now11:46
kristianpauli need fast gpio response11:46
kristianpauland i dont trust linux for that !11:46
kristianpauli guess will be slow11:46
wpwraklinux will be slow :) my guess would be that a memory/register access costs you at least 2 cycles, so a "write 0" followed by "write 1", infinitely unrolled, would need 4 cpu cycles per cycle of the signal. so that's 84 Mhz.11:48
kristianpaulyeah i think i need check code examples from SIE  Unal guys did great work documenting gpio and low level stuff11:49
wpwrakif you want to, say, output some data in parallel, a la SPI, that would be  shift_data(1), write_carry(2), write0(2), write1(2) = 7 cycles or 48. this is quite optimistic. not sure if the xburst can be so efficient. if it needs an add or, worse, a jump in this case, expect even less11:50
kristianpaulwell may the CPLD save the day, just in case ;)11:51
wpwrakbit-banging serial protocols almost always sucks :)11:52
kristianpaulor a dual core Xburst :D11:52
kristianpaulyeah :(11:52
kristianpaulwell i pics (my previous experience) is okay for simple stuff but well protocols with Mhz is soemthing i need to deal with11:52
wpwrakhmm yes, i'll have to speed up the little spi in my rf board as well. right now, it should be crawling at less than 1 Mbps ... (not that it matters so far)11:59
wpwrakand then there's of course the frequency counter board that stubbornly refuses to do anything. that one should work up to 6 MHz, although with hardware support.12:00
kristianpauloh thats hihg12:01
wpwrakthe latter is for calibrating my crystals. the idea is to count the 1/2/4/... MHz clock derived from the crystal, then compare this with NTP time. after a day or so, i should have 1 ppm accuracy :)12:01
wpwraksaves me buying a USD 3000 frequency counter :)12:02
wpwrak(of course, the latter would still be nice to have. ah, prorities, priorities ...)12:02
kristianpaulmoney, money money..12:03
wpwrakyeah. so useless yet so important ...12:05
qi-bot[commit] Juan64Bits: Routing DDR-B http://qi-hw.com/p/xue/4edf66b12:44
qi-bot[commit] Andres Calderon: USB Phy re-routed http://qi-hw.com/p/xue/2e8564b19:45
qi-bot[commit] Andres Calderon: 2 new decoupling caps http://qi-hw.com/p/xue/7825f6920:12
qi-bot[commit] Werner Almesberger: f32xbase didn't build on ancient Gentoo due to missing include. http://qi-hw.com/p/f32xbase/bc3783920:15
qi-bot[commit] Werner Almesberger: Requests following a rejected SETUP requests failed too, which sometimes http://qi-hw.com/p/f32xbase/fd0965520:15
qi-bot[commit] Werner Almesberger: lib/usb.c (open_usb): libusb documentation claims that considerable http://qi-hw.com/p/f32xbase/a77a9a620:15
qi-bot[commit] Werner Almesberger: Added list of to do items and known bugs. http://qi-hw.com/p/ben-wpan/c01a5e020:15
qi-bot[commit] Werner Almesberger: Minor potential improvements of USB robustness. http://qi-hw.com/p/ben-wpan/8f744bb20:15
qi-bot[commit] Werner Almesberger: Literature consistently calls the Link Quality Indication LQI, not LQ. So do http://qi-hw.com/p/ben-wpan/bb7b04920:15
kristianpaulxiangfu: hello :-)22:09
xiangfukristianpaul: hi22:10
kristianpaulCan you point me examples of using asm for the Ben Xburst?22:11
kristianpauldo we have datasheets for the Xbusrt 4720 btw?22:13
kristianpauli need find out more info about some electrincal characteristics..22:13
kristianpauloh nv22:21
xiangfukristianpaul: here is one: http://projects.qi-hardware.com/index.php/p/openwrt-xburst/source/tree/xburst/package/uboot-xburst/files/arch/mips/cpu/xburst/usbboot.S22:40
kristianpaulxiangfu: ahh uboot is the clue ! :)22:41
qi-bot[commit] Juan64Bits: Kernel image uploading http://qi-hw.com/p/nn-usb-fpga/1ef32f423:03
--- Wed Aug 25 201000:00

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