**** BEGIN LOGGING AT Sun Jun 14 02:59:57 2009
Jun 14 03:53:40 <horndude77> I can't get the usb serial device (/dev/ttyUSB1) to show up
Jun 14 03:54:07 <horndude77> I've done 'modprobe usbserial' and 'modprobe ftdi_sio'
Jun 14 03:54:27 <horndude77> anything ideas?
Jun 14 03:58:15 <roxfan> i see some mentions of /dev/usb/tts/0
Jun 14 04:02:32 <horndude77> I guess I should mention that I'm on Ubuntu 9.04
Jun 14 04:02:43 <horndude77> I don't even have a /dev/usb/
Jun 14 04:11:55 <DDevine> Fixing the logger now.
Jun 14 10:11:28 <Super_Roach> hey all - just wondering if the usb to serial drivers would work for debugging on vista 64bit? I'm looking at trying to use the windowsterraterm drivers that come with the cd
Jun 14 10:12:03 <sonic74> they work for me.
Jun 14 10:13:15 <Super_Roach> ah ok. Did you try to manually install the drivers sonic74? They appear to not show for me.
Jun 14 10:13:49 <sonic74> sorry, I don't remember.
Jun 14 10:14:52 <sonic74> I have some other USB2serial adapters, perhaps it was already installed.
Jun 14 10:15:24 <Super_Roach> I might try install some of those. Nifty idea, thanks
Jun 14 13:55:03 <matthiasr> hello, has anyone gotten the osx-pl2303 serial driver to work with the sheevaplug? i don't want to use the ftdi one because of the kernel panic bug.
Jun 14 13:55:27 <matthiasr> so far, i have managed to make it recognise one port if the sheevaplug
Jun 14 13:55:39 <matthiasr> unfortunately, the wrong one.
Jun 14 13:56:27 <matthiasr> the driver does not seem to honor the <key>bInterfaceNumber</key><integer>1</integer> in the Info.plist
Jun 14 14:01:14 <matthiasr> here's my current Info.plist: http://drop.io/sheevaosxserial/asset/info-plist
Jun 14 14:08:38 <SuperRoach> gold: http://www.facebook.com/default.aspx
Jun 14 14:46:46 <ShadowJK> ooh, my plug shipped
Jun 14 14:47:04 <Super_Roach> awesomejk
Jun 14 14:47:24 <Super_Roach> i love mine but bricked the stock install lol
Jun 14 22:55:36 <SDuensin> Hey all.  The Wiki says to use this to TFTP/NFS boot the plug...
Jun 14 22:55:37 <SDuensin> setenv bootcmd tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);bootm 0x2000000
Jun 14 22:56:09 <SDuensin> That works, but how do I save that?  The ending "bootm" command makes it boot immediately.  I'd like to make it so the plug boots from NFS at powerup without me messing with it.
Jun 14 22:57:27 <sonic74> saveenv
Jun 14 22:58:22 <SDuensin> But you don't get a chance.  It boots!
Jun 14 22:58:40 <sonic74> leave out the bootm
Jun 14 22:58:49 <SDuensin> I put it in double quotes, it boots.  I put it in single quotes and it seems to take it.  However, it doesn't do the tftp then.
Jun 14 22:59:04 <SDuensin> If I leave out the bootm, it won't boot next time I power it up?
Jun 14 22:59:22 <sonic74> it's a command, no setting.
Jun 14 22:59:50 <SDuensin> Yea, I know.  But isn't it a part of the variable so the plug executes it on power up?
Jun 14 22:59:58 <timtimred> put single quotes arounds it
Jun 14 23:00:06 <sonic74> no, the ";" is the delimiter.
Jun 14 23:00:13 <timtimred> setenv command 'blah;blah;blah'
Jun 14 23:00:20 <timtimred> saveenv
Jun 14 23:00:35 <SDuensin> timtimred - I did that, but then it doesn't take the $(image_name) correctly.
Jun 14 23:00:48 <timtimred> set that too first
Jun 14 23:00:55 <timtimred> setenv image_name blah
Jun 14 23:01:02 * SDuensin did.
Jun 14 23:01:08 <timtimred> dunno then :)
Jun 14 23:01:13 <SDuensin> hehe
Jun 14 23:01:48 <sonic74> I thought you can divide this line into multiple lines.
Jun 14 23:02:14 <SDuensin> Hey, I'm happy I got NFS working.  :-)
Jun 14 23:03:27 <sonic74> sorry, I got it wrong. you could just evaluate the $() variables yourself.
Jun 14 23:04:53 <SDuensin> Yea, I know.  What's the fun of that?  :-P
Jun 15 00:31:25 <_socket> Hi, I've had my SheevaPlug for a couple days and out of no where I'm getting a Bad Magic Number ## Booting image at 00800000 ...
Jun 15 00:32:59 <_socket> Is this a corrupted uboot? I'm able to use a tftp to boot the OS.
Jun 15 00:34:02 <Md> are you sure it's not a corrupted kernel?
Jun 15 00:34:41 <_socket> I think it might be, how could I tell that? It boots when I set it to boot from tftp
Jun 15 00:35:05 <Md> if it can boot the on-flash kernel then looks like it's uboot
Jun 15 00:35:13 <Md> try reflashing it using the instructions from http://plugcomputer.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux
Jun 15 00:35:27 <_socket> I set the ip and then I do this:tftpboot 0x8000000 /uImage.sheeva.20090319
Jun 15 00:35:28 <_socket> bootm 0x8000000
Jun 15 00:35:30 <_socket> and it boots
Jun 15 00:35:35 <Md> beware: you can use openocd to reflash it only if you installed from svn or the debian/unstable package
Jun 15 00:36:06 <Md> right, uboot is loaded at 800000 and the kernel at 8000000
Jun 15 00:37:39 <_socket> does that mean it's the kernal if I load tftpboot at 0x8000000?
Jun 15 00:38:06 <Md> nevermind...
Jun 15 00:38:13 <Md> uboot is loaded at *0x600000*
Jun 15 00:38:31 <Md> wait...
Jun 15 00:38:46 <Md> you are obviously loading the kernel using tftp, so you are not using the on-flash kernel
Jun 15 00:38:55 <_socket> correct
Jun 15 00:39:15 <Md> so unless both the kernel and uboot sectors have gone bad you should be able to tftpload the kernel using the on-flash uboot
Jun 15 00:39:25 <Md> did you actually try getting to the prompt at boot time?
Jun 15 00:40:16 <_socket> your speaking of the Marvell prompt
Jun 15 00:40:19 <Md> yes
Jun 15 00:40:31 <Md> if you get there then u-boot has been loaded
Jun 15 00:40:34 <_socket> yes, that is where I configure it to boot from tftp. It takes me there after the failed boot
Jun 15 00:41:02 <Md> so you are not uploading uboot using openocd, just tftp'ing the kernel
Jun 15 00:41:33 <_socket> ok, makes sense, so how can I re-flash the kernel?
Jun 15 00:41:33 <Md> it should be obvious at this point that u-boot is working fine
Jun 15 00:42:17 <Md> cat image > /dev/mtd1 should work if you do not have bad sectors
Jun 15 00:42:45 <_socket> can that be done from the prompt or once linux is booted?
Jun 15 00:43:10 <Md> I don't remember if u-boot can flash the kernel as well, and I do not know if the original install has the correct program
Jun 15 00:43:35 <Md> you could use something like flash kernel > /dev/mtd1 but this will only work if your flash does not have any bad sector
Jun 15 00:44:31 <_socket> ok, which is the sheevaplug kernal image from the cd?
Jun 15 00:44:42 <_socket> it's not the uimage file is it?
Jun 15 00:45:47 <SDuensin> One of the wiki examples has the wrong bootm address that causes the error you mentioned.
Jun 15 00:45:51 * SDuensin did that last night.
Jun 15 00:45:59 <Md> SDuensin: where?
Jun 15 00:46:07 <SDuensin> Checking
Jun 15 00:46:50 <_socket> Md: am I doing flash uImage.sheeva.20090319 > /dev/mtd1?
Jun 15 00:47:51 <Md> _socket: no, you will first double check everything (e.g. that mtd1 is actually the kernel partition)
Jun 15 00:48:21 <SDuensin> Maybe I dreamt that.  :-/  I don't see anything wrong on the pages I've been using.
Jun 15 00:48:24 <_socket> Md: the kernel, is on one partition, correct?
Jun 15 00:56:40 <_socket> Md: console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw
Jun 15 00:57:31 <_socket> Md: is what it says when it boots
Jun 15 01:07:49 <_socket> Md: root@debian:/etc# cat /proc/mtd
Jun 15 01:07:49 <_socket> dev:    size   erasesize  name
Jun 15 01:07:49 <_socket> mtd0: 00400000 00020000 "uImage"
Jun 15 01:07:50 <_socket> mtd1: 1fb00000 00020000 "rootfs"
Jun 15 01:08:00 <_socket> is mtd0 the kernel?
Jun 15 01:10:28 <Md> yes
Jun 15 01:14:51 <_socket> so I should do flash_eraseall /dev/mtd0
Jun 15 01:17:33 <_socket> Md: thanks, that fixed it!
Jun 15 01:18:08 <_socket> flash_erase /dev/mtdblock0
Jun 15 01:18:08 <_socket> flash_erase /dev/mtd0
Jun 15 01:18:09 <_socket> cat uImage.sheeva.20090319 > /dev/mtdblock0
Jun 15 01:22:13 <_socket> Md: it says Empty flash at 0x0ffce01c ends at 0x0ffce800 right after eth0: link up, full duplex, speed 1 Gbps and then it boots..
**** ENDING LOGGING AT Mon Jun 15 02:59:57 2009