• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2
1  Linux Stuff / Kernel / Really funky characters when booting kernel on: February 18, 2012, 09:24:53 PM
I have recently upgraded the uboot on my globalscale sheevaplug. I'm attempting to get a kernel working, but there seems to be a gremlin somewhere inside the plug.

Here is my enviroment:
Code:
Marvell>> printenv
arcNumber=2097
baudrate=115200
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw
bootargs_console=console=ttyS0,115200
bootargs_root=root=/dev/mtdblock2 ro
bootcmd=nand read 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_mmc=mmc init; ext2load mmc 0:1 0x00800000 /uImage; ext2load mmc 0:1 0x01100000 /uInitrd
bootdelay=3
ethact=egiga0
ethaddr=02:50:43:c1:74:d6
fileaddr=800000
filesize=15E630
ipaddr=192.168.1.200
mainlineLinux=yes
serverip=192.168.1.65
stderr=serial
stdin=serial
stdout=serial

Environment size: 614/131068 bytes
Marvell>>

I've set up a tftp server with uImage and uInitrd in it.
Code:
Marvell>> tftpboot 0x01100000 uInitrd
Marvell>> tftpboot 0x00800000 uImage
Both seem to work

Code:
Marvell>> bootm 0x00800000 0x01100000

Gets me to a screen that looks like it is an installer, but the text is garbled. Completely unreadable. Any ideas?
2  Hardware and U-Boot firmware / U-Boot stuff / Bricked plug? on: February 12, 2012, 12:11:30 PM
So it looks as if upgrading from my old uboot was unsuccessful.
Now, the plug appears to be bricked.

screen tty.usbserial-FTTMHG5DB 115200


U-Boot 2011.12 (Jan 08 2012 - 21:53:47)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
NAND read from offset 60000 failed -74
*** Warning - readenv() failed, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-2.6.22.18
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2106696 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


Kernel never booted. Reset power to sheevaplug. Now screen gets me to a big black nothing with blinking cursor. What happened to the matrix, man? I'm on OSX 10.7, which seems to have some interesting quirks in terminal. Any ideas?
3  General Category / General Discussion / Re: Getting back into the swing of things on: February 12, 2012, 12:55:04 AM
Took quite a bit of trial and error to figure out what was going wrong. I had an error on line 26. Load, touch and the plug shows up in /dev/
4  General Category / General Discussion / Re: Getting back into the swing of things on: February 11, 2012, 11:53:47 PM
sudo dmesg returns:

Darwin Kernel Version 11.2.0: Tue Aug  9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASE_X86_64
vm_page_bootstrap: 1006556 free pages and 33828 wired pages
kext submap [0xffffff7f8072e000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff800072e000]
zone leak detection enabled
standard timeslicing quantum is 10000 us
mig_table_max_displ = 73
AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
calling mpo_policy_init for TMSafetyNet
Security policy loaded: Safety net for Time Machine (TMSafetyNet)
calling mpo_policy_init for Sandbox
Security policy loaded: Seatbelt sandbox policy (Sandbox)
calling mpo_policy_init for Quarantine
Security policy loaded: Quarantine policy (Quarantine)
Copyright (c) 1982, 1986, 1989, 1991, 1993
   The Regents of the University of California. All rights reserved.

MAC Framework successfully initialized
using 16384 buffer headers and 10240 cluster IO buffer headers
IOAPIC: Version 0x20 Vectors 64:87
ACPI: System State [S0 S3 S4 S5] (S3)
PFM64 (36 cpu) 0xf10000000, 0xf0000000
[ PCI configuration begin ]
console relocated to 0xf10030000
PCI configuration changed (bridge=5 device=1 cardbus=0)
[ PCI configuration end, bridges 7 devices 17 ]
AppleIntelCPUPowerManagement: (built 21:08:10 Aug  9 2011) initialization complete
FireWire (OHCI) TI ID 8025 built-in now active, GUID 002241fffe5a43d4; max speed s800.
mbinit: done [64 MB total pool size, (42/21) split]
Pthread support ABORTS when sync kernel primitives misused
USBMSC Identifier (non-unique): 574D41593030333439363537 0x1058 0x1021 0x2002
com.apple.AppleFSCompressionTypeZlib kmod start
com.apple.AppleFSCompressionTypeDataless kmod start
2.4.1 Little Snitch: starting
com.apple.AppleFSCompressionTypeZlib load succeeded
com.apple.AppleFSCompressionTypeDataless load succeeded
AppleIntelCPUPowerManagementClient: ready
BTCOEXIST off
wl0: Broadcom BCM4328 802.11 Wireless Controller
5.10.131.36
USBMSC Identifier (non-unique): 604010020819 0xd49 0x3210 0x77f8
[IOBluetoothHCIController::setConfigState] calling registerService
USBF:   1.896   [0xffffff800bcfc200] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 7 of Hub at 0xfa200000)
rooting via boot-uuid from /chosen: 064304DC-DD73-3CA9-BCF6-FD0E704C2658
Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Hitachi HTS722020K9SA00 Media/IOGUIDPartitionScheme/Mac disk@2
BSD root: disk0s2, major 14, minor 2
Kernel is LP64
AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RX_MAX_LE 1024, TX_MAX_LE 768, ST_MAX_LE 3328
USBF:   8.105   [0xffffff800bcfc200] The IOUSBFamily has successfully enumerated the device.
USBMSC Identifier (non-unique): 604010020819 0xd49 0x3210 0x77f8
Waiting for DSMOS...
yukon: Ethernet address 00:22:41:2e:e1:ba
AirPort_Brcm43224: Ethernet address 00:21:e9:e6:4a:08
IO80211Controller::dataLinkLayerAttachComplete():  adding AppleEFINVRAM notification
macx_swapon SUCCESS
AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
NVDANV50HAL loaded and registered.
Previous Shutdown Cause: 3
WARNING - ACPI_SMC_CtrlLoop::initCPUCtrlLoop - no sub-config match for MacBookPro4,1 with 8 p-states, using default stepper instead
DSMOS has arrived
Ethernet [AppleYukon2]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug [796d,6c08,0de1,0200,41e1,4000]
nstat_lookup_entry failed: 2
nstat_lookup_entry failed: 2
nstat_lookup_entry failed: 2
en1: 802.11d country code set to 'US'.
en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
2.4.1 Little Snitch: connection deferred for:/usr/local/dyndns/DynDNSUpdaterService uid:0 to:216.146.38.70 :80
2.4.1 Little Snitch: connection deferred for:/usr/local/dyndns/DynDNSUpdaterService uid:0 to:216.146.38.70 :80
         0 [Level 7] [ReadUID 0] [Facility messagetracer] [com.apple.message.domain com.apple.kernel.external_modification] [com.apple.message.signature FinderLoadBundle(887B8EEE-2832-4334-B101-6F7CFF9E55A0)] [com.apple.message.signature2 Finder(548C24A0-975C-3167-88AA-036CEFBE3F9D)] [com.apple.message.result noop]
IOSurface: buffer allocation size is zero
Resetting IOCatalogue.
       0        0 AppleUSBCDC: start - initDevice failed
       0        0 AppleUSBCDC: start - initDevice failed
5  General Category / General Discussion / Re: Getting back into the swing of things on: February 11, 2012, 11:09:15 PM
kextfind -nd returns:
Can't record kext in identifier lookup dictionary; no identifier.
Can't record kext in identifier lookup dictionary; no identifier.
6  General Category / General Discussion / Re: Getting back into the swing of things on: February 11, 2012, 07:26:28 PM
And now when trying to print with my lexmark e232, it says the printer is not connected. It certainly is hooked up to USB. I navigated to the FTDIUSBDriver.kext, checked the contents and found the info.plist file. It is waaay longer than I remembered it being. Please take a gander and let me know if you see anything that is out of the ordinary:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>idVendor</key>
           <integer>1027</integer>
        </dict>
       <key>SheevaPlug JTAGKey FT2232D A</key>
       <dict>
          <key>CFBundleIdentifier</key>
          <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
          <key>IOClass</key>
          <string>FTDIUSBSerialDriver</string>
          <key>IOProviderClass</key>
          <string>IOUSBInterface</string>
          <key>bConfigurationValue</key>
          <integer>1</integer>
          <key>bInterfaceNumber</key>
          <integer>0</integer>
          <key>idProduct</key>
          <integer>258</integer>
          <key>idVendor</key>
          <integer>7180</integer>
       </dict>
       <key>SheevaPlug JTAGKey FT2232D B</key>
       <dict>
          <key>CFBundleIdentifier</key>
          <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
          <key>IOClass</key>
          <string>FTDIUSBSerialDriver</string>
          <key>IOProviderClass</key>
          <string>IOUSBInterface</string>
          <key>bConfigurationValue</key>
          <integer>1</integer>
          <key>bInterfaceNumber</key>
          <integer>1</integer>
          <key>idProduct</key>
          <integer>258</integer>
          <key>idVendor</key>
          <integer>7180</integer>
       </dict>
     </dict>
     <key>OSBundleLibraries</key>
     <dict>

   <key>CFBundleDevelopmentRegion</key>
   <string>English</string>
   <key>CFBundleExecutable</key>
   <string>FTDIUSBSerialDriver</string>
   <key>CFBundleIdentifier</key>
   <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
   <key>CFBundleInfoDictionaryVersion</key>
   <string>6.0</string>
   <key>CFBundleName</key>
   <string>I/O Kit Driver for FTDI USB Devices</string>
   <key>CFBundlePackageType</key>
   <string>KEXT</string>
   <key>CFBundleShortVersionString</key>
   <string>2.2.16</string>
   <key>CFBundleSignature</key>
   <string>Huh?</string>
   <key>CFBundleVersion</key>
   <string>2.2.16</string>
   <key>IOKitPersonalities</key>
   <dict>
      <key>485USBTB-4W</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>44084</integer>
         <key>idVendor</key>
         <integer>2134</integer>
      </dict>
      <key>AMC232USB01</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>65280</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>AMC232USBDH</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>65281</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>ARC AM VM Mono</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>257</integer>
         <key>idVendor</key>
         <integer>1607</integer>
      </dict>
      <key>ARC Filterwheel</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>259</integer>
         <key>idVendor</key>
         <integer>1607</integer>
      </dict>
      <key>ARC Inspectrum Mono</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>258</integer>
         <key>idVendor</key>
         <integer>1607</integer>
      </dict>
      <key>ARC Instrument</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>256</integer>
         <key>idVendor</key>
         <integer>1607</integer>
      </dict>
      <key>ARC SpectraHub</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>260</integer>
         <key>idVendor</key>
         <integer>1607</integer>
      </dict>
      <key>ATSI D689</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>54921</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>ATTO</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>62064</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>AXE027 PICAXE USB</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>48528</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>Abaxis Blood Chemistry Analyzer</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>ConfigData</key>
         <dict>
            <key>LatencyTimer</key>
            <integer>8</integer>
         </dict>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>52504</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>Actimetrics F528</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>62760</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>Actisense USG USB Serial Converter</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>55721</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>Active Robots RTM</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>58696</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>Alti-2 USB</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>24577</integer>
         <key>idVendor</key>
         <integer>7113</integer>
      </dict>
      <key>Apox Controls USB-CAN4</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>63928</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>AtelierRobin D4C8</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>54472</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>AtelierRobin D4C9</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>54473</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>AtelierRobin D4CA</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>54474</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>AtelierRobin D4CB</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>54475</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>AtelierRobin D4CC</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>54476</integer>
         <key>idVendor</key>
         <integer>1027</integer>
      </dict>
      <key>AtelierRobin D4CD</key>
      <dict>
         <key>CFBundleIdentifier</key>
         <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
         <key>IOClass</key>
         <string>FTDIUSBSerialDriver</string>
         <key>IOProviderClass</key>
         <string>IOUSBInterface</string>
         <key>bConfigurationValue</key>
         <integer>1</integer>
         <key>bInterfaceNumber</key>
         <integer>0</integer>
         <key>idProduct</key>
         <integer>54477</integer>
         <key>idVendor</key>
         <integer>1027</integer>
   // (lots omitted -- beyond forum's character limit)
</dict>
</plist>
7  General Category / General Discussion / Re: Getting back into the swing of things on: February 11, 2012, 05:09:10 PM
A little more info: In addition to being plugged into USB, the Sheevaplug is plugged into my router, but is not showing up under the router settings.
8  General Category / General Discussion / Getting back into the swing of things on: February 11, 2012, 11:53:55 AM
It has been many months since I distracted myself with other projects and I'm wanting to get my sheevaplug working for a home server. When I put it all away, I had serial access and could SSH to the device from outside easily. Now, I have forgotten everything. (and installed osx lion, which seems to have some strange quirks in terminal)

When I plug the sheevaplug in, I am able to see it in hardware profiler. USB SheevaPlug JTAGKey FT2232D B. Right, well that makes sense.
But... I go into terminal and look for and entry in /dev/ and don't see it.
I think... hmm, maybe FTDIUSBSerial isn't working? Well, that doesn't make sense because everything else with an FTDI chip seems to work fine.
So, I try to sudo kextload /System/Library/Extensions/FTDIUSBSerialDriver.kext
And: /System/Library/Extensions/FTDIUSBSerialDriver.kext failed to load - (libkern/kext) not found; check the system/kernel logs for errors or try kextutil(Cool
Uh. Oh. Something is not right.

tail -f /var/log/kernel.log nets me the following:

Feb 10 23:31:45 aurelius kernel[0]: 0        0 AppleUSBCDC: start - initDevice failed
Feb 11 05:48:02 aurelius kernel[0]: USBF:   496156.623   AppleUSBEHCI[0xffffff800bbb8000]::Found a transaction past the completion deadline on bus 0xfa, timing out! (Addr: 9, EP: 0)
Feb 11 08:55:27 aurelius kernel[0]: IOSurface: buffer allocation size is zero
Feb 11 08:58:28 aurelius kernel[0]: Resetting IOCatalogue.
Feb 11 09:30:50 aurelius kernel[0]: Resetting IOCatalogue.
Feb 11 09:37:32 aurelius kernel[0]: Resetting IOCatalogue.
Feb 11 09:39:40 aurelius kernel[0]: 0        0 AppleUSBCDC: start - initDevice failed
Feb 11 10:26:39 aurelius kernel[0]: 0        0 AppleUSBCDC: start - initDevice failed
Feb 11 10:38:47 aurelius kernel[0]: IOSurface: buffer allocation size is zero


And I'm not sure where to go from here. Any ideas?
9  Hardware and U-Boot firmware / U-Boot stuff / Re: Upgrading uboot on Globalscale Sheevaplug on: March 21, 2011, 02:18:03 PM
#I have successfully upgraded uboot by using TFTP Server. However, run bootcmd still returns 'bad partition 1' and
'bad magic number'. I'm thinking that perhaps I have formatted and partitioned the stick wrong. There are many options within Ubuntu's disk utility for formatting options. I selected Master Boot Record and FAT 16. Perhaps something else would work better?
10  Hardware and U-Boot firmware / U-Boot stuff / Re: Upgrading uboot on Globalscale Sheevaplug on: March 20, 2011, 08:39:02 AM
#So I downloaded ubuntu and booted the macbook from the cd. I reformatted the usb stick, with 3 partitions, SDA1, SDA2 & SDA3. (1.0 Gig, 1.5Gig and 1.5 Gig, respectively)All are FAT 16 and SDA1 is bootable.

usb start 

#gives: (Re)start USB...
USB:   scanning bus for devices... T
      USB device not responding, giving up (status=80000000)
2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 00800000 ...
Bad Magic Number
11  Hardware and U-Boot firmware / U-Boot stuff / Re: Upgrading uboot on Globalscale Sheevaplug on: March 17, 2011, 04:40:04 PM
# I'm thinking that the problem may be that OSX's disk utility formats to FAT32, hence the bad partition. So I used to Disk Utility to simply erase the existing partitions and reformat the drive to FAT32 "Unfortunately, when I try to repartition the USB thumb drive with:

diskutil partitiondisk /dev/disk2 1 MBRFormat "MS-DOS FAT16" "SDA1" 1000M

#I get the following error:

Started partitioning on disk2
Unmounting disk
Creating partition map
[ \ 0%..10%..20%......................................... ]
Waiting for disks to reappear
Formatting disk2s1 as MS-DOS (FAT16) with name SDA1
Error: -9962: The chosen size is not valid for the chosen filesystem

#I was thinking that the size might be too big, so I tried the same command with 250M, but got the same -9962 error.  Any ideas?



12  Hardware and U-Boot firmware / U-Boot stuff / Re: Upgrading uboot on Globalscale Sheevaplug on: March 16, 2011, 07:27:02 PM
# So I went back in & replaced ext2load with fatload as follows:

setenv bootargs_console console=ttyS0,115200
setenv bootargs_root 'root=/dev/sda2 rootdelay=10'
setenv bootcmd_usb 'usb start; fatload usb 0:1 0x0800000 /uImage; fatload usb 0:1 0x01100000 /uInitrd'
setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; bootm 0x0800000 0x01100000'
saveenv

#run bootcmd returns the following:


Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:1 **
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:1 **
## Booting image at 00800000 ...
Bad Magic Number

#The SanDisk USB flash drive with the 3 fat partitions created in OSX's disk utility begins blinking it's LED.
#Also, "fatload usb 0:1 0x080000 uboot.bin" returns:

** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **


#Huh?
13  Hardware and U-Boot firmware / U-Boot stuff / Re: Upgrading uboot on Globalscale Sheevaplug on: March 09, 2011, 07:53:24 PM
run fatload returns "## Error: "fatload" not defined"
14  Hardware and U-Boot firmware / U-Boot stuff / Upgrading uboot on Globalscale Sheevaplug on: March 08, 2011, 11:14:20 PM
I've got uboot 1.1.4 (Jul 14 2009 - 06:46:57) Marvell version: 3.4.16 & I'm looking to upgrade via usb.
Using OSX disk utility, I've formatted my 4 gig usb thumb drive with 3 Fat partitions named sda1, sda2 and sda3. On SDA1, I placed the files from Sheevaplug installer 1.0 2 and uboot.bin there as well.
I interrupt the boot process and get the Marvell>> prompt and type:
 fatload usb 0:1 0x08000000 uboot.bin

I've entered:
setenv mainlineLinux yes
setenv arcNumber 2097
saveenv
reset

and

setenv bootargs_console console=ttyS0,115200
setenv bootargs_root 'root=/dev/sda2 rootdelay=10'
setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x0800000 /uImage; ext2load usb 0:1 0x01100000 /uInitrd'
setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; bootm 0x0800000 0x01100000'
saveenv

run bootcmd returns the following:

(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 00800000 ...
Bad Magic Number


I don't know where to go from here re: the bad partition & I'm confused where 008000000 is coming from, shouldn't it be 08000000?



15  General Category / Success stories / Re: Using the plug as a full PC with an external display (usb2vga) on: March 02, 2011, 11:51:56 AM
For those of us who are not experts, can you provide info on how you updated the kernel to recognize the usb/vga adapter, keyboard and mouse?
Pages: [1] 2