• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3
16  Hardware and U-Boot firmware / U-Boot stuff / Re: can't find ftdi device from ubuntu on: August 07, 2009, 10:44:55 PM
The link works for me, but just for good measure:
looks like the last batch of sheevaplugs changed vendor and product id. Modified scripts-linux/openocd/config/interface/sheevaplug.cfg to

interface ft2232
ft2232_layout sheevaplug
ft2232_vid_pid 0x0403 0x6010
#ft2232_vid_pid 0x9e88 0x9e8f
#ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"
jtag_khz 2000

17  Hardware and U-Boot firmware / U-Boot stuff / Booting From a USB Hard Drive Enclosure on: August 07, 2009, 10:05:00 PM
Okay, so I have a 250GB drive in a Rosewill USB SATA enclosure, and I want to try to get U-Boot to load the uImage from it. "fdisk -l" looks like this:
Code:
$ sudo fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x97073300

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14       30401   244091610   83  Linux

sda1 is a 100MB ext2 partition that I planned to mount as /boot
sda2 is a giant ext4 partition that I planned to mount as / (I was still deciding whether I had a reason to split the filesystem more than that)

U-Boot recognizes the drive in the enclosure as a mass storage device, then it claims that my partitions are invalid. Here's a log of one of my attempts:

Code:
Hit any key to stop autoboot:  0
Marvell>> usb start
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... T 1 Storage Device(s) found
Marvell>>  ext2load usb 0:1 0x800000 /uImage
** Bad partition 1 **
Marvell>> usb storage
  Device 0: Vendor: Maxtor 6 Prod.: B250S0           Rev:
            Type: Hard Disk
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
Marvell>> usb tree

Device Tree:
  1  Hub (480MBit/s, 0mA)
  |  Marvell EHCI
  |
  +-2  Mass Storage (480MBit/s, 2mA)
       Sunplus Technology Co.,Ltd. USB to Serial-ATA bridge FAFFFF06B2B60FFFFF

Marvell>> usb dev 0

USB device 0:
    Device 0: Vendor: Maxtor 6 Prod.: B250S0           Rev:
            Type: Hard Disk
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
... is now current device
Marvell>> usb part
print_part of 0
## Unknown partition table

print_part of 1
## Unknown partition table

print_part of 2
## Unknown partition table

print_part of 3
## Unknown partition table

print_part of 4
## Unknown partition table
Marvell>> usb info
1: Hub,  USB Revision 2.0
 - Marvell EHCI
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage,  USB Revision 2.0
 - Sunplus Technology Co.,Ltd. USB to Serial-ATA bridge FAFFFF06B2B60FFFFF
 - Class: (from Interface) Mass Storage
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x04fc  Product 0x0c25 Version 1.18
   Configuration: 1
   - Interfaces: 1 Self Powered 2mA
   - String: ""
     Interface: 0
     - Alternate Settings 0, Endpoints: 2
     - Class Mass Storage, Transp. SCSI, Bulk only
     - String: ""
     - Endpoint 1 In Bulk MaxPacket 512
     - Endpoint 2 Out Bulk MaxPacket 512

The "T" after "scanning bus for storage devices" is printed while U-Boot waits for the drive to spin up. It also takes at least a few seconds for "usb info" to print info on the hard drive, but the drive is already spinning by then.
I'm hoping I'm missing something obvious and U-Boot isn't at fault.
18  Hardware and U-Boot firmware / U-Boot stuff / Re: can't find ftdi device from ubuntu on: August 07, 2009, 09:53:30 PM
I had this problem as well, see http://plugcomputer.org/plugforum/index.php?topic=355.msg3246#msg3246 .
19  General Category / General Discussion / Re: Sheevaplug installer - alpha-6 release - Testers needed on: August 06, 2009, 02:49:13 PM
This is the same problem I had, see http://plugcomputer.org/plugforum/index.php?topic=355.msg3246#msg3246 .
20  General Category / General Discussion / Re: Sheevaplug installer - alpha-6 release - Testers needed on: August 05, 2009, 03:28:23 PM
When I run runme.sh, I get this:
Code:
# ./runme.sh
 ****   Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 453:

 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

The Sheevaplug is connected and I can connect to the Linux host on /dev/ttyUSB1. Rebooting the plug made no difference. The kernel logs show this:
Code:
Aug  5 16:50:45 Reno kernel: usb 4-2: new full speed USB device using ohci_hcd and address 7                 
Aug  5 16:50:45 Reno kernel: usb 4-2: configuration #1 chosen from 1 choice                                 
Aug  5 16:50:45 Reno kernel: ftdi_sio 4-2:1.0: FTDI USB Serial Device converter detected                     
Aug  5 16:50:45 Reno kernel: usb 4-2: Detected FT2232C                                                       
Aug  5 16:50:45 Reno kernel: usb 4-2: FTDI USB Serial Device converter now attached to ttyUSB0               
Aug  5 16:50:45 Reno kernel: ftdi_sio 4-2:1.1: FTDI USB Serial Device converter detected                     
Aug  5 16:50:45 Reno kernel: usb 4-2: Detected FT2232C                                                       
Aug  5 16:50:45 Reno kernel: usb 4-2: FTDI USB Serial Device converter now attached to ttyUSB1

Should I try recompiling OpenOCD on my non-ARM linux box?
It looks like I have libftdi and not libftdi2xx, would that cause problems? OpenOCD didn't have any errors about dynamic library loading...
Actually, could Bad Things (TM) be happening because I'm running this on 64 bit Linux? I'll try it on a 32 bit system...
On the 32 bit system, openocd segfaulted almost instantly. Ergh, I guess I'll try recompiling it.

Okay, it looks like it's working from my 64 bit box with fragfutter's modifications to interface.cfg.
21  General Category / General Discussion / Re: Only one USB serial is showing up! on: August 05, 2009, 03:01:23 PM
Are you using the standard kernel26 package? I'm on Arch, and when I connect my plug, two USB ttys show up and I can't seem to get OpenOCD to access JTAG. I'm not sure what could be different.
22  Hardware and U-Boot firmware / U-Boot stuff / Re: I Seem to Have Built a Bad Kernel on: August 04, 2009, 09:57:27 PM
I saw that, and the config that's labeled for 2.6.30.4 is actually from 2.6.30.3, but I guess there were no changes in options that affected it. I generated a patch from the kirkwood_defconfig to that config, and I'll be looking through it tomorrow to see what significant changes are in there.
I'll probably wind up just using the uImage from that link or the one from the recovery/install system, but it'll be interesting to see what's different.

EDIT:
Here's what the problem was:
Code:
####### change bootargs, replace nand_mtd with orion_nand and add rootfstype=jffs2
# setenv bootargs rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=192.168.1.9:192.168.1.4:192.168.1.4:255.255.255.0:DB88FXX81:eth0:none
# saveenv

After doing that, my kernel boots.
23  Hardware and U-Boot firmware / U-Boot stuff / Re: I Seem to Have Built a Bad Kernel on: August 04, 2009, 08:55:27 PM
That didn't do the trick.
Reading the above log, it seems like the root partition in the flash is now /dev/mtdblock2, but it was originally /dev/mtdblock1, but changing that doesn't make a difference either. I can see JFFS2 loading from the kernel boot log, so I'm not sure what's causing the issues.
My bootargs in U-Boot is currently "console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock2 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none rootfs=jffs2"
I haven't modified the flash partition sizes, so that part should still be correct.
The boot fails, ending in these lines:
Code:
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "<NULL>" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<c002a810>] (unwind_backtrace+0x0/0xdc) from [<c0309a90>] (panic+0x48/0x12c)
[<c0309a90>] (panic+0x48/0x12c) from [<c0008f30>] (mount_block_root+0x1d4/0x21c)
[<c0008f30>] (mount_block_root+0x1d4/0x21c) from [<c000919c>] (prepare_namespace+0x120/0x180)
[<c000919c>] (prepare_namespace+0x120/0x180) from [<c00085ac>] (kernel_init+0xbc/0xec)
[<c00085ac>] (kernel_init+0xbc/0xec) from [<c0039694>] (do_exit+0x0/0x6e0)
[<c0039694>] (do_exit+0x0/0x6e0) from [<df82a300>] (0xdf82a300)

Here's where it scans the flash:
Code:
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 554 at 0x000004540000
Bad eraseblock 895 at 0x000006fe0000
Bad eraseblock 1038 at 0x0000081c0000
Bad eraseblock 1202 at 0x000009640000
Bad eraseblock 1739 at 0x00000d960000
Bad eraseblock 1856 at 0x00000e800000
Bad eraseblock 1908 at 0x00000ee80000
Bad eraseblock 3012 at 0x000017880000
Bad eraseblock 3225 at 0x000019320000
Bad eraseblock 3238 at 0x0000194c0000
Bad eraseblock 3243 at 0x000019560000
Bad eraseblock 3311 at 0x000019de0000
Bad eraseblock 3317 at 0x000019ea0000
Bad eraseblock 3529 at 0x00001b920000
Bad eraseblock 3576 at 0x00001bf00000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"

Here's the line where the JFFS2 system initializes:
Code:
JFFS2 version 2.2. (NAND) 2001-2006 Red Hat, Inc.


I guess the first thing I should ask is whether there's a patch that fixes this behavior because this image is the 2.6.30.4 kernel compiled from the kirkwood_defconfig with no patches and no modifications to the config.
The second thing I should ask is whether this is worth diagnosing because I can just get a premade image elsewhere. If I've configured something wrong though, it could be a good learning experience.
24  Hardware and U-Boot firmware / U-Boot stuff / I Seem to Have Built a Bad Kernel on: August 04, 2009, 06:55:06 PM
Well, I tried building 2.6.30.4 of the mainline kernel today, using the kirkwood_defconfig, and now I'm getting this when I reboot:
Code:
List of all partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (driver?)
No filesystem could mount root, tried:  ext3 ext2 cramfs vfat msdos
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1)
[<c002a810>] (unwind_backtrace+0x0/0xdc) from [<c0309a90>] (panic+0x48/0x12c)
[<c0309a90>] (panic+0x48/0x12c) from [<c0008f30>] (mount_block_root+0x1d4/0x21c)
[<c0008f30>] (mount_block_root+0x1d4/0x21c) from [<c000919c>] (prepare_namespace+0x120/0x180)
[<c000919c>] (prepare_namespace+0x120/0x180) from [<c00085ac>] (kernel_init+0xbc/0xec)
[<c00085ac>] (kernel_init+0xbc/0xec) from [<c0039694>] (do_exit+0x0/0x6e0)
[<c0039694>] (do_exit+0x0/0x6e0) from [<df82a300>] (0xdf82a300)
eth0: link up, 1000 Mb/s, full duplex, flow control disabled

I assumed that the defconfig would have jffs2 support, but apparantly this isn't the case. Do I have to get uBoot to boot from TFTP now if I want to get it running again? Where can I find a good kernel uImage to start from?
25  General Category / General Discussion / Re: Received yours yet? on: August 03, 2009, 02:32:03 PM
Ordered June 13, shipped today (July 29). Hopefully they'll give me a tracking number, but I've learned not to rely on tracking services. UPS and FedEx are more worried about getting the package there than letting you watch as it goes through shipping hubs.

Arrived on my doorstep today (August 3). I knew the Sheevaplug was small, but for some reason I was expecting a larger box.
26  General Category / General Discussion / Re: Received yours yet? on: July 29, 2009, 09:25:56 PM
Ordered June 13, shipped today (July 29). Hopefully they'll give me a tracking number, but I've learned not to rely on tracking services. UPS and FedEx are more worried about getting the package there than letting you watch as it goes through shipping hubs.
27  General Category / Application ideas and development Q/A / Re: Webcam - Video Encoding Load? on: July 22, 2009, 05:04:59 AM
I'm not sure where floating point operations are and aren't used, but I do know that lossy codecs tend to use them, and basically any significant floating point use will kill the plug. It's floating point performance is probably below that of the original Pentium (although it doesn't have a division glitch like the Pentium had).
28  General Category / Application ideas and development Q/A / Re: Networked Backup Solution? on: July 21, 2009, 11:48:28 AM
I don't even have a SD card; my plan is to have it boot from the onboard flash and use an external hard drive for bulk storage.
The trick is that I maintain two linux boxes in a network of Windows boxes, and I need to be able to backup both types, which AMANDA doesn't do well. If I remember correctly, it can backup Windows boxes if you share the hard drive with SMB, which just doesn't seem like something I want to do.
I did, however, get Bacula working on Vista, and I'm looking into getting scheduled backups running. It's not as simple as just making a tar.lzma of my entire root filesystem, but it'll work for everything.
29  General Category / Application ideas and development Q/A / Re: Webcam - Video Encoding Load? on: July 21, 2009, 11:43:18 AM
The problem isn't CPU power, the problem is that there is no hardware FPU (Floating Point Unit) to process floating point values quickly. As a consequence, the CPU must do floating point calculations, which is much much slower. Lossy encoding, such as video encoding, generally uses floating point values.
30  General Category / General Discussion / Re: Sheevaplug - 32 or 64 bit? on: July 19, 2009, 10:46:30 PM
I'm not sure what your point is. I've already stated that I doubt many 32 bit systems will still be in operation, and I used the embedded device example just to show that changing the currently used date format isn't possible in many scenarios. I never said we were all doomed; this is just a problem on the horizon. It will probably cause some problems in the next 20 years, but due to the 64 bit move, I doubt there will be any immensely serious consequences.
In case it wasn't clear before, 64 bit Posix operating systems do store the time in a 64 bit signed integer, which will overflow in a few million years. Applications compiled for these systems also store the date in 64 bits. Ironically enough, the open source world is pretty much perfectly safe.
Pages: 1 [2] 3