2010-10-01 00:53 wpwrak: making progress, ben-wpan goes through fine now 2010-10-01 00:54 with xue, I am running into two problems 2010-10-01 00:54 first, it complains about 4 missing libraries (k8001, micron_mobile_ddr, ...) 2010-10-01 00:54 even though the paths in xue-rnc.pro look good (../library/) 2010-10-01 00:55 then, there is a GUI warning "deleted stale lockfile /home/schhist/eeschema-schhist" 2010-10-01 00:55 the GUI warning may be a consequence of the library problems, so I'll focus on those frst 2010-10-01 01:14 wpwrak: ah, I forgot the -S parameter... 2010-10-01 01:41 wpwrak: in schhist2web, line 138, doesn't it have to be $2 when parsing the -c option? 2010-10-01 04:19 hey bartbes, which version of physfs should i take for nlove? physfs-1.1.1.tar.gz or physfs-2.0.1.tar.gz 2010-10-01 04:57 wolfspraul: that does indeed look more likely :-) 2010-10-01 05:00 [commit] Werner Almesberger: Fixed use of argument of -c. http://qi-hw.com/p/eda-tools/b94f1b2 2010-10-01 05:00 fixed, thanks ! 2010-10-01 05:15 bartbes, i get an error compiling nlove. nlove-0.0.2/modules/image/sdl/Image.cpp: In constructor 'love::i 2010-10-01 05:15 mage::sdl::Image::Image()': 2010-10-01 05:15 nlove-0.0.2/modules/image/sdl/Image.cpp:36: error: 'IMG_INIT_JPG 2010-10-01 05:15 ' was not declared in this scope 2010-10-01 06:09 wpwrak: I had one additional idea, since we have all the data already, we should also make one PDF that includes all schematics pages in one file, for each commit (I mostly see the need only for the 'latest' full schematics PDF, but since all the data is there we might as well create it for each commit) 2010-10-01 06:11 @ bartbes, well i fixed 2 problems, now i have a nlove binary :) 2010-10-01 06:11 bartbes : but nlove-0.0.2/modules/image/sdl/Image.cpp:36: error: 'IMG_INIT_JPG   <- is indeed an error 2010-10-01 06:13 wolfspraul: look at the result page, top line, above the commits :) 2010-10-01 06:14 ok will do :-) 2010-10-01 06:16 i dind't generate a full PDF set at each commit, though. 2010-10-01 06:24 wpwrak: the scripts are holding up nicely, not checking output yet though 2010-10-01 06:25 I have added blinkenlights, milkymist jtag/serial cable, SIE 2010-10-01 06:25 with the AVT2 board it runs into an error 2010-10-01 06:25 "cannot open function_block.sch" 2010-10-01 06:25 I think we may have committed some things in a step by step way that creates this broken dependency in a particular commit 2010-10-01 06:26 eek. what's the project called ? 2010-10-01 06:26 it's in the board-qi-avt2 project, main schematic is main/Qi_AVT2.sch 2010-10-01 06:28 let's see what happens there ... 2010-10-01 06:29 we may have simply committed broken stuff at some point in the history 2010-10-01 06:29 how about that -S sanitize option, can't that just always be on? 2010-10-01 06:30 yes, -S can always be on. if there's no problem, then it does nothing 2010-10-01 06:30 not sure whether it would help here, but it did help me with some missing library dependencies 2010-10-01 06:30 but i'm not sure if it catches missing sheets 2010-10-01 06:30 yes, it does track libraries 2010-10-01 06:30 if -S is safe to always be on, can't you just remove the option and leave the code always running? 2010-10-01 06:31 sometimes, you may want to see the errors 2010-10-01 06:32 (Failed to open ...) i get it, too 2010-10-01 06:32 and -S doesn't help, as expected 2010-10-01 06:34 btw, the eeschema segfault came from not having an X server, and even when I had one the missing DISPLAY variable will segfault eeschema 2010-10-01 06:34 a bit rough, it should handle missing DISPLAY or missing X server more gracefully 2010-10-01 06:35 aah ! yes, it doesn't like that at all. how did you solve it ? 2010-10-01 06:35 I have now installed a permanently running VNC session on the buildhost 2010-10-01 06:35 solution: tightvncserver, DISPLAY=:0 :-) 2010-10-01 06:35 (rough) well, the only case in which it makes sense to run eeschema without display would be my --plot patch :) 2010-10-01 06:35 perfect ;-) 2010-10-01 06:35 yes but a segfault is not nice 2010-10-01 06:37 and the problem is indeed that function_block.sch wasn't committed. guess we need a sanitize-schem, too 2010-10-01 06:52 should be fixed RSN ... 2010-10-01 06:53 take your time I need a long time anyway to hook everything up etc. 2010-10-01 06:59 whoa. lots of libraries it can't find :-( 2010-10-01 06:59 some of the revisions won't look pretty ... 2010-10-01 07:01 yeah I can imagine 2010-10-01 07:01 this was our first KiCad projet 2010-10-01 07:01 but for me it's also important that the schhist scripts are as robust as possible, and always generate something 2010-10-01 07:01 an ugly diff is better than no diff 2010-10-01 07:02 because people will look at it and then work with cleaner commits 2010-10-01 07:03 yes, it's important that the scripts can handle some mistakes. missed commits are unfortunately all too common 2010-10-01 07:04 the AVT2 revisions do actually loop pretty good. now let's see what happened with those problems ... 2010-10-01 07:07 also some mystery diffs - in the FETs, the font style changed. my detection algorithm finds this, but it's invisible in the "for viewing" images. (you can figure it out with the before/after PDFs) 2010-10-01 07:10 heh, and the line width for capacitors :) you need to zoom into the pdf to see *that* ;-) 2010-10-01 07:15 (missing libs) the bug is in sanitize-profile. yet another $1 vs. $2 2010-10-01 07:16 interestingly, eeschema didn't mind. probably because also Qi_AVT2.cache.lib is in git, so it never had to actually look for these items. 2010-10-01 07:26 [commit] Werner Almesberger: New script sanitize-schem to remove subsheets for which no file can be found. http://qi-hw.com/p/eda-tools/75a4ea8 2010-10-01 07:26 [commit] Werner Almesberger: sanitize-profile accidently ignored LibDir, causing many incorrect "corrections" http://qi-hw.com/p/eda-tools/d4405e4 2010-10-01 07:26 much better now 2010-10-01 07:59 wpwrak: yes it runs through now, great! congrats! 2010-10-01 08:00 I need to do more plumbing, make it all robust and automatic. will probably continue tomorrow. 2010-10-01 08:02 good. so you locate the projects automatically or do you just keep a list/Makefile of them ? 2010-10-01 08:03 s/so/do/ 2010-10-01 08:04 locate? 2010-10-01 08:05 I try to automate it as much as possible, but also I want to get it up and running asap 2010-10-01 08:05 in the end even hooking up a new project to the commit bot is manual right now 2010-10-01 08:05 hooking it up to the kicad schhist is also manual 2010-10-01 08:06 plus, like in the case of ben-wpan, there can be multiple schhist histories per project 2010-10-01 08:06 that's just fine right now, no need to automate this as the amount of work to automate it would not be recouped any time soon 2010-10-01 08:06 even if we expect 100 more KiCad project in the next year 2010-10-01 08:06 100 * 2 minutes = 200 minutes 2010-10-01 08:06 not worth automating further 2010-10-01 08:07 I'm writing a little script and cronjob on the buildhost, plus a little plumbing here and there 2010-10-01 08:07 will all be documented as usual 2010-10-01 08:08 once it's setup, adding another KiCad project to schhist will be < 2 minutes 2010-10-01 08:08 that's the plan 2010-10-01 08:08 makes sense? 2010-10-01 08:09 yup, sounds good. when you add projects manually, you can also run a quick check to see if everything is well. 2010-10-01 08:10 sure 2010-10-01 08:10 I know the real costs of automation :-) 2010-10-01 08:10 hehe ;-) 2010-10-01 09:03 [commit] Niels: add menu to show/hide layers http://qi-hw.com/p/nanomap/8daff26 2010-10-01 09:05 NanoMap! my favorite app 2010-10-01 09:36 wpwrak: here is the script I'm using on the buildhost 2010-10-01 09:36 http://en.qi-hardware.com/wiki/Server_setup#KiCad.2C_fped.2C_schhist 2010-10-01 09:36 (go down to the schhist section) 2010-10-01 09:37 I'm sure it could be shorter & more elegant, but I think for now it works 2010-10-01 09:37 a git push on the projects server will set a flag, then git pull runs on the buildhost, then your scripts 2010-10-01 09:38 now what's missing is to make it accessible from Apache, working on that next... 2010-10-01 10:06 [commit] Carlos Camargo: Adding evolvable hardware example http://qi-hw.com/p/nn-usb-fpga/1f2712e 2010-10-01 10:14 Hi, I've been looking into nupdf 2010-10-01 10:15 Is there source code available for libfitz etc? 2010-10-01 10:17 Ah, it's part of mupdf 2010-10-01 10:17 My bad 2010-10-01 11:47 @ bartbes, after some work i can successfully run love2d files on dingoo. everytime i have to adjust the screensizes and disable mouse, sound. 2010-10-01 15:17 hard drive not getting identified on comp? 2010-10-01 16:00 ? 2010-10-01 16:02 hey 2010-10-01 16:30 SiENcE: have you tried npong and urandom__'s snake? 2010-10-01 16:34 hey bartbes 2010-10-01 16:34 mh no. where can i get them? 2010-10-01 16:34 i have problems with some functions 2010-10-01 16:34 http://dl.dropbox.com/u/440010/nlove/npong.love 2010-10-01 16:35 http://dl.dropbox.com/u/440010/nlove/snake.love 2010-10-01 16:35 maybe it has todo with some functions i had to remove for compile 2010-10-01 16:35 you removed some functions?! 2010-10-01 16:35 yep wait 2010-10-01 16:36 nlove-0.0.2\modules\image\sdl\Image.cpp 2010-10-01 16:36 this was all unknown 2010-10-01 16:36 IMG_Init(IMG_INIT_JPG | IMG_INIT_PNG | IMG_INIT_TIF); 2010-10-01 16:36 IMG_Quit(); 2010-10-01 16:36 i cant find the references 2010-10-01 16:37 it's in SDL_Image 2010-10-01 16:37 really? 2010-10-01 16:37 yes 2010-10-01 16:37 let me check the headers 2010-10-01 16:40 SDL_image.h ? 2010-10-01 16:42 ah 2010-10-01 16:42 its a newer one 2010-10-01 16:42 i use 2010-10-01 16:42 #define SDL_IMAGE_MAJOR_VERSION 1 2010-10-01 16:42 #define SDL_IMAGE_MINOR_VERSION 2 2010-10-01 16:42 #define SDL_IMAGE_PATCHLEVEL 7 2010-10-01 16:42 but you use 2010-10-01 16:42 #define SDL_IMAGE_MAJOR_VERSION 1 2010-10-01 16:42 #define SDL_IMAGE_MINOR_VERSION 2 2010-10-01 16:42 #define SDL_IMAGE_PATCHLEVEL 10 2010-10-01 16:45 so what can i do to use the old one? 2010-10-01 16:50 I have no idea 2010-10-01 16:50 ;) 2010-10-01 16:51 mh 2010-10-01 16:51 do i need to initialize this? 2010-10-01 16:51 i ask because some lua functions did not worked 2010-10-01 16:52 but maybe this has todo with old demos 2010-10-01 16:52 love.graphics.getWidth() did not worked 2010-10-01 16:53 and i get an segfault when starting nlove alone 2010-10-01 16:54 and i have to disable the sound module 2010-10-01 16:57 bartbes, Pong works 2010-10-01 16:58 Snake also works 2010-10-01 16:58 :) 2010-10-01 19:20 Hello. 2010-10-01 19:25 Is it easy to transfer files from one's computer to the Ben Nanonote? 2010-10-01 19:26 (what I'm first thinking about are simple text files) 2010-10-01 19:27 yes 2010-10-01 19:28 well 2010-10-01 19:28 are you familiar with scp? 2010-10-01 19:29 scp, could it be something I found in a ssh tutorial, I'm not sure. (to transfer files) 2010-10-01 19:32 well, I can easily regain some basic knowledge about how to use scp, I just found one of the tutorials available. 2010-10-01 19:33 I've used it just as it was stated in one tutorial I tried in the past and I successfully copied files from and to another networked computer. 2010-10-01 19:35 Greek_o_nikos: does your computer run Windows or Linux or something else? 2010-10-01 19:36 mth: gNewSense on the Lemote Yeeloong. 2010-10-01 19:36 with GNOME or KDE? 2010-10-01 19:36 GNOME. 2010-10-01 19:37 in either case, you can probably use sftp:// URLs in the file manager 2010-10-01 19:37 I know it works in KDE, but afaik GNOME has the same feature 2010-10-01 19:37 mth: but first I have to setup an ftp server, I think if I want that method? 2010-10-01 19:38 if you're using a windows desktop, grab winscp 2010-10-01 19:38 ftp-clientish 2010-10-01 19:38 uses scp 2010-10-01 19:38 drag and drop files to your ben 2010-10-01 19:38 if you are using gnome, make an SSH bookmark 2010-10-01 19:38 open with nautilus 2010-10-01 19:38 drag and drop files to your ben 2010-10-01 19:38 Greek_o_nikos: not needed: SFTP is part of the SSH protocol 2010-10-01 19:39 mth: ok. I didn't know. 2010-10-01 19:39 oh, I see 2010-10-01 19:39 gnome 2010-10-01 19:39 at least with OpenSSH it's available by default, I'm not sure if the NanoNote uses OpenSSH 2010-10-01 19:39 Places -> Connect to Server -> 2010-10-01 19:39 enter the nanonote ip address 2010-10-01 19:39 opens in nautilus 2010-10-01 19:40 save as a bookmark while you're in thar 2010-10-01 19:40 While service type: Public FTP? 2010-10-01 19:41 There's also an option for SSH there. 2010-10-01 19:41 (on service type) 2010-10-01 19:43 I live in Greece. When I got the Lemote Yeeloong it was shipped from the Netherlands. I'll check now where I can get a Ben Nanonote device. 2010-10-01 19:44 ssh 2010-10-01 19:48 Is there any image of the ben nanonote which shows what the usb port looks like? 2010-10-01 20:02 I found it by searching: mini-USB 2.0 2010-10-01 22:18 :D 2010-10-01 23:25 what for VNC server is fidelio? 2010-10-01 23:26 kristianpaul: I installed it as part of the schhist setup 2010-10-01 23:26 which is just finished, btw, check it out http://projects.qi-hardware.com/schhist/ 2010-10-01 23:26 oh ok 2010-10-01 23:26 click 2010-10-01 23:26 that's live from now on, any KiCad project on projects.qi-hardware.com can be hooked into it, and every commit will automatically generate an update to the visual schematics history! 2010-10-01 23:27 great 2010-10-01 23:27 oh even avt2 ! 2010-10-01 23:28 of course 2010-10-01 23:28 from now on we will hook every KiCad project into this 2010-10-01 23:28 next step: visual layout diffs! :-) 2010-10-01 23:28 :O 2010-10-01 23:35 wpwrak: I think the schhist setup is complete now http://projects.qi-hardware.com/schhist/ 2010-10-01 23:35 thanks a lot for your excellent work on this, I only did the plumbing! 2010-10-01 23:35 I will try to make sure the scripts keep working, next time someone does a KiCad commit we should watch out 2010-10-01 23:38 I've just booted my NanoNote into USB mode for the first time, to update u-boot. 2010-10-01 23:38 Things seem to be fine now, but how do I shut the machine down? 2010-10-01 23:43 it seems I had to unplug the device and take my battery out. 2010-10-01 23:43 I'd love a better suggestion when anyone passes by and reads this. 2010-10-01 23:45 aisa: you can try the hardware reset pin, the little hole on the bottom of the device 2010-10-01 23:45 Indeed, I will next time. 2010-10-01 23:45 I rarely (never) use it, but I think it's the equivalent of unplugging USB cable and removing the battery 2010-10-01 23:46 Is that how one exits USB BOOT mode? 2010-10-01 23:46 exit in which sense? 2010-10-01 23:46 turn the machine off, or reboot it. 2010-10-01 23:46 USB boot mode is a state the CPU is in, it waits for commands over USB 2010-10-01 23:47 what do I do when I'm done issuing commands over USB and want my screen back?  :-) 2010-10-01 23:47 so in that sense 'usb boot mode' is already exited when you run usbboot, especially when usbboot loads and executes binaries in the NanoNote RAM 2010-10-01 23:47 I unplug the USB cable, replug it 2010-10-01 23:47 you can also try the hardware reset button 2010-10-01 23:47 awesome, thank you wolfspraul! 2010-10-01 23:52 I'm trying to update my NanoNote using MicroSD. 2010-10-01 23:52 I believe I've copied the uImage, root.ubi, and untarred the rootfs on an ext2 MicroSD card. 2010-10-01 23:52 I boot by using Power+M, and I get the following error: 2010-10-01 23:52 ** File not found /boot/uImage 2010-10-01 23:52 Wrong Image Format for bootm command 2010-10-01 23:53 ERROR: can't get kernel image! 2010-10-01 23:53 I think I should believe the first message, 2010-10-01 23:53 how big is your microSD card? 2010-10-01 23:53 and that "Wrong Image Format" is essentially saying "zero sized file. 2010-10-01 23:53 16gb, I believe. 2010-10-01 23:53 there is a bug in u-boot's ext2 handling 2010-10-01 23:53 yes, won't work 2010-10-01 23:53 filesystem bug in u-boot's ext2 2010-10-01 23:53 dang.  how small should I be to avoid this bug? 2010-10-01 23:54 xiangfu is on it, but we have many bugs and unfortunately it also has been hard for us so far to get patches back upstream... 2010-10-01 23:54 would reformatting and copying uImage early in the process work, 2010-10-01 23:54 hmm 2010-10-01 23:54 or do I need to get a smaller microSD card? 2010-10-01 23:54 I think cards up to 4 gb will always work 2010-10-01 23:54 good, ok.  Time to go purchase a new card :-) 2010-10-01 23:54 you can also try to make a small partition on your 16gb card 2010-10-01 23:54 that is a good idea. 2010-10-01 23:54 try a small partition first 2010-10-01 23:54 at the beginning 2010-10-01 23:54 2 gb 2010-10-01 23:54 Worth trying, it will be mucch faster 2010-10-01 23:54 this is a bug in the ext2 filesystem codes of u-boot 2010-10-01 23:55 we just haven't gotten aroudn to tracking it down and fixing it yet 2010-10-01 23:56 they even have 32 gb microSD cards now, but I was too lazy/stingy to buy one and test :-) 2010-10-01 23:56 Indeed.  I've been sitting on flashing my NanoNote for way too long. 2010-10-01 23:56 I needed like several hours to sit and work on it, 2010-10-01 23:56 and finally made time tonight. 2010-10-01 23:56 I'm really looking forward to getting this process done, 2010-10-01 23:57 because I want to be faster at it so I can go find some of these problems. 2010-10-01 23:57 well thanks for your patience 2010-10-01 23:57 oh you can help us with that kind of low level bugs? 2010-10-01 23:57 It's all fun.  :-) 2010-10-01 23:57 that would be awesome! 2010-10-01 23:57 Indeed, I'm a long way from being an expert, 2010-10-01 23:57 but I generally understand how the kernel runs, 2010-10-01 23:57 u-boot is a bit troublesome, we have been unsuccessful in getting some patches upstream, and quickly fixing some bugs such as this one 2010-10-01 23:57 have a really strong notion of how libc works, 2010-10-01 23:57 well try the 2gb partition idea first, let's see whether it helps you 2010-10-01 23:57 and know almost nothing about MIPS. 2010-10-01 23:58 it may also have to do with block sizes or so and then maybe the bug will always show on a large card, even if you have a small partition on it 2010-10-01 23:58 got it.  I'll find out.  Is there an open ticket I should append information to? 2010-10-01 23:58 I'm updating the wiki. 2010-10-01 23:59 I'm about to stop working on it tonight, but will come back to it.