**** BEGIN LOGGING AT Wed Jul 11 02:59:58 2012 Jul 11 20:51:55 I recently bought a GuruPlug, and I've been very happy with it -- until I bricked it by upgrading to the latest Debian (Squeezy) Jul 11 20:52:18 Apparently (as I'm sure you all know -- but I didn't) -- because of the arch number reported by the original boot loader, this of course bricks the device. Jul 11 20:52:29 So I'm trying to de-brick my device, and running into some issues. Jul 11 20:52:47 debrick? Jul 11 20:52:49 huh? Jul 11 20:52:50 I have the USB JTAG board, and I've got it connected to my device with openocd Jul 11 20:52:54 Well, un-brick my device Jul 11 20:53:20 I've gathered that I need to somehow load a new boot loader on my device before the guru plug will be able to boot from a vanilla ARM kernel -- is that correct? Jul 11 20:53:35 By "brick", I just mean that my device is currently a brick -- it doesn't boot, and I can't SSH into it or anything. Jul 11 20:54:09 you just need to tell uboot how to boot Jul 11 20:54:41 you do that by accessing the serial console while the gplug boots Jul 11 20:54:48 I can do that Jul 11 20:54:59 (access it) Jul 11 20:55:12 But how do I want to tell uboot to boot differently? Jul 11 20:55:29 Or rather, how do I want it to boot instead of its current method? Jul 11 20:55:42 you probably want to tell uboot to boot in a way that works :) Jul 11 20:56:05 If I let it go its normal way, in the serial console I get a normal Linux boot-up log, and then it starts going into a huge spam of near-endless "udevd[635]: unable to receive ctrl connection: Function not implemented" messages Jul 11 20:56:32 maybe you just need to set mainlineLinux and arcNumber Jul 11 20:56:59 Oh I can do hat from within uboot at runtime? I assumed I needed to recompile to set those. Jul 11 20:57:08 no no Jul 11 20:57:10 just setenv Jul 11 20:57:20 oh nice Jul 11 20:57:35 indeed Jul 11 21:03:37 Hmmm, now it doesn't give me the error messages, but it hangs on Uncompressing Linux..... done, booting the kernel. Jul 11 21:03:54 are you sure you set up those two correctly? Jul 11 21:04:03 did you tell the kernel how to mount /? Jul 11 21:04:55 I set the machid and the mainlineLinux and the arcNumber Jul 11 21:05:08 But no, didn't change any variables for the mount points Jul 11 21:05:21 maybe those changed Jul 11 21:06:10 LoadAddress and EntryPoint are both 00008000 Jul 11 21:08:40 http://pastebin.com/jpQftGBh Jul 11 21:08:43 There is my printenv Jul 11 21:11:53 well, where is the system installed? Jul 11 21:14:10 As far as the file system? I didn't change the installation location from the default when it was shipped to me -- I think the only thing that broke it was that I did a apt dist-upgrade **** ENDING LOGGING AT Thu Jul 12 02:59:58 2012