**** BEGIN LOGGING AT Wed Jan 19 02:59:57 2011 Jan 19 03:20:32 anyone know anything about utilizing the efuses on th eplug? Jan 19 16:47:22 My SheevaPlug is one year old now. One year of continuous use. :) Jan 19 17:03:08 happy birthday! Jan 19 17:10:37 uptime: 80 days Jan 19 17:14:14 uptime 84 days --- accidentally unplugged the hard drive it is booting from or would of been up longer Jan 19 17:14:29 18 months old sheevaplug Jan 19 17:15:08 4 days :< Jan 19 17:15:19 4 days after a kernel panic or something :< Jan 19 17:15:44 openrd client uptime 87 days - need to put F13 on its hard drive Jan 19 17:16:09 and build the latest kernel from stable Jan 19 17:17:42 8 days here, but only because i issued ``reboot'' into the wrong terminal XD Jan 19 17:17:45 had 27 before that Jan 19 17:18:32 ha Jan 19 17:31:48 hah Jan 19 17:31:58 anyone good with C++ here? Jan 19 18:01:57 Kuifje111: what's the question? Jan 19 18:02:12 I already got an answer, thanks Jan 19 18:07:37 great Jan 19 18:12:30 you're welcome! Jan 19 18:43:59 Hello Jan 19 18:44:03 hi Jan 19 18:44:10 I keep seeing references to boot into the debug board Jan 19 18:44:21 on the guruplug or sheevaplug? Jan 19 18:44:21 What is the debug board? Jan 19 18:44:24 sheeva Jan 19 18:44:43 I got my kernel to run on the device but can't flash the memory Jan 19 18:44:49 the sheevaplug came included with a mini-usb cable; plug that cable into the side of the sheevaplug, and the other end into your laptop/desktop Jan 19 18:44:58 the serial console you get from that is the debug Jan 19 18:45:07 before uboot? Jan 19 18:45:18 I get a uboot console from that Jan 19 18:45:21 right Jan 19 18:45:25 ah Jan 19 18:45:42 you can push a temporary uboot into memory, if you brake the one that's stored Jan 19 18:47:44 hmm the u-boot menu always pops up before I can get to the debug menu Jan 19 18:48:51 you have 3 seconds to press any key to get the uboot prompt Jan 19 18:49:20 ok I'm at the uboot prompt. how do I get to the debug board? Jan 19 18:49:46 ahh " Initially boot the debug board from NFS location where uImage and jffs2 images are stored. Jan 19 18:49:47 " Jan 19 18:50:15 so the debug board are the images Jan 19 18:51:24 I really sucks because the documentation mentions files I can't get find or download it seems.. ugh Jan 19 18:51:40 yeah, the sheeva docs are a bit dated Jan 19 18:51:45 what are you looking to do with your plug? Jan 19 18:52:03 I created my own kernel and my own UBIFS root img Jan 19 18:52:23 cool Jan 19 18:52:24 I ahve custom software that will run and utilize the usb port to communicate with serial devices Jan 19 18:52:40 neat Jan 19 18:53:16 I compilied my kernel with all the neccesarry options and I got it to work but it VFS panics because I ahve no way of flashing mtd Jan 19 18:53:31 I guess I could put my entire root on nfs Jan 19 18:53:50 but I don't have these flash scripts the documentation is talking about Jan 19 18:54:02 sh-3.2# flash_eraseall -j /dev/mtd1 Jan 19 18:55:57 if you're just looking to flash to the mtd, you can use the sheevaplug_installer_v1.0 Jan 19 18:56:42 just put your filesystem into a .tar.gz and use it instead of the provided rootfs.tar.gz Jan 19 18:56:53 (you can use your custom kernel as well) Jan 19 18:57:22 it runs with php? Jan 19 18:57:54 yes, but i've rewritten the script to bash, if you want it Jan 19 18:58:06 oh awesome Jan 19 18:58:10 I'd rather have that Jan 19 19:00:16 http://sprunge.us/CABW Jan 19 19:00:37 it's functionally identical to the php one when run with the same arguements Jan 19 19:01:13 ofc, i added some features, such as skipping burning the whole uboot binary (takes a long time, and unneeded if you have a working uboot) Jan 19 19:01:25 (the -e flag ^) Jan 19 19:01:43 yea I made my uboot ahead of getting the device Jan 19 19:01:55 and tried pushing that but the header was invalid Jan 19 19:01:57 so... Jan 19 19:01:59 lol Jan 19 19:02:02 meh not a big issue Jan 19 19:11:48 hmm Jan 19 19:12:05 openocd/openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory Jan 19 19:12:11 I have the library installed Jan 19 19:48:40 ugh the sheevainstaller uses 32 bit libs and won't laod with my 64bit libftdi Jan 19 19:49:17 I tried recompiling openocd and libftdi but says it doens't support the nand drivers Jan 19 19:49:31 oh what fun! Jan 19 19:52:05 i have a 64bit openocd i compiled Jan 19 19:52:14 (if you don't mind running a binary) Jan 19 19:52:38 well my openocd works but I get the nand driver not found when running it Jan 19 19:52:49 I wonder if I missed a configure option Jan 19 22:36:31 none of the provided kernel images even work Jan 19 22:36:58 Everytime I attempt to load a prebuilt image it just hangs on uncompressing kernel image Jan 19 22:39:12 dotblank: did you set mainlinelinux and archnum? Jan 19 22:39:26 yea Jan 19 22:39:40 well to which? Jan 19 22:39:48 because it can be slightly confusing Jan 19 22:40:15 mainlinelinux = yes, and archnum = some 3 digit number, don't remember off the top of my head Jan 19 22:42:02 setenv mainlineLinux yes; setenv arcNumber 2097 Jan 19 22:42:06 4 digit* Jan 19 22:42:11 dotblank: ^ Jan 19 22:42:48 also, if you're looking for kernel images to boot from (that are known to work), you can get them from http://sheeva.with-linux.com/sheeva/ Jan 19 22:43:02 (in the folder is the uImage) Jan 19 22:46:12 hmm interesting Jan 19 22:46:27 It spits out random chars when it loads the kernel Jan 19 22:46:41 you probably didn't pass console=blah Jan 19 22:46:45 in bootargs Jan 19 22:47:25 console=ttyS0,115200 Jan 19 22:48:15 http://pastebin.com/PamsWcKx Jan 19 22:48:21 yea I already had all that Jan 19 22:48:31 thats my environment Jan 19 22:49:05 oh wait the arcNumber got unset Jan 19 22:50:19 yeah, you not only have to saveenv after setting arcNumber/MainLineLinux, but you have to reboot for them to take effect (instead of just running ``boot'') Jan 19 22:51:33 well its still a no go with the terminal Jan 19 22:54:12 I think my uboot got flashed Jan 19 22:54:33 when I tried to use the sheeva installer Jan 19 22:55:25 it just fails on multiple cpus Jan 19 23:47:21 dotblank: did you solve your lack of NAND driver problem? Jan 19 23:51:52 dotblank: did you solve your lack of NAND driver problem? Jan 20 00:04:18 Tootoot222, no I havn't yet Jan 20 00:04:28 well it turns out I did have nand support Jan 20 00:04:46 and on 32 bit linux the tool segfaults anyway even though it does find the nand flash **** ENDING LOGGING AT Thu Jan 20 02:59:57 2011