• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 [3]
31  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 15, 2009, 07:54:10 AM
Im now trying to build a kernel following these instructions:  http://plugcomputer.org/plugwiki/index.php/Compiling_Linux_Kernel_for_the_Plug_Computer


This seems fairly involved, and I am taking a slightly different track (simpler?)

There is a cross-compile toolchain, mkimage binary, and kernel source provided with the devkit. The docs i have found state that you have to use their kernel image due to some custom patches they did for this device. Not sure if that's true or not.

i have found that I can unpack these and use them to compile a kernel, with very little hassle. (once i found the right 'default' kernel config file, anyways.. 'make mv88f6281_defconfig')

I may still want to create my own mkimage binary, to modify the banner, but we'll see.

I should also caveat this and say i haven't actually tried my new kernel yet Smiley

Once i do, i'll post my steps. My plan is to 'QA' the new kernel via NFS before i flash it.

-tmk
32  Hardware and U-Boot firmware / U-Boot stuff / Re: boot menu or similar? for u-boot on: April 15, 2009, 07:44:55 AM
I've configured something like a multiboot on my plug.  Take a look at the post here : http://openplug.org/plugforum/index.php?topic=36.msg264#msg264

yep, that's where i got the idea to begin with.. i liked the concept, but wanted something more user-friendly :)

There is no way (that I know of) to actually create and display a bootmenu, but you can get into the U-Boot environment and execute a 'run boot_sd' or 'run boot_nfs' with the way I have it configured.  If you could find a method to stop autoboot and run a few echo commands after initialization I suppose it would work as a makeshift bootmenu but I have not seen such functionality in the documentation.  However you will probably want to leave autoboot enabled and a default bootcmd set, otherwise you will need the console connected everytime the plug boots.

I was afraid of that. I notice there's a pretty big banner when u-boot starts, and i'm guessing one can probably edit that banner, since we are creating a new u-boot image as part of the kernel installation. It wouldn't be quite as 'dynamic' as one would like, but i would think it would allow autoboot to be enabled, as well as provide the appropriate instructions.

Anyone familliar enough with u-boot to know where that lives? I'll get out the hex-editor if i have to, but would prefer not to :)

-tmk
33  Hardware and U-Boot firmware / U-Boot stuff / boot menu or similar? for u-boot on: April 12, 2009, 11:12:26 PM
Hi,

I'm new to u-boot and ARM in general. I'm just about to embark on some customization, and i'd like to be able to set up a grub or lilo style boot menu to ease the pain of switching between boot locations.

Any tips? How can i make it print out a list of options, eg:

Code:
type "run local" to boot local, or wait 3 seconds
type "run nfs" to boot from nfs
type "run nfs-unstable" to boot from nfs, using unstable kernel
type "run sd" to boot from sd
type "run usb" to boot from usb

... and have those options do the right thing?

if someone has a url explaining it, that would be great as well.

thanks
-tmk
34  General Category / General Discussion / Re: Instructions: Getting the serial console to work on a MAC on: April 11, 2009, 08:35:00 PM
one other thing to mention.. the way i access it is:

Code:
screen /dev/cu.usbserial-FTS06TZ5B 115200

note that it's the B channel, not the A

-tmk
35  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 11, 2009, 08:53:15 AM
maybe answering my own question here.

this appears to be the default config for the processor i think we're using here:

arch/arm/configs/mv88f6281_defconfig

-tmk
36  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 11, 2009, 08:24:42 AM
I have not tried any customizations yet but I did successfully setup the cross compiler and build the kernel code in the default configureation. 

did you try the kernel?

how did you determine the default configuration ('make defconfig'?)

-tmk
37  Linux Stuff / Kernel / anyone compile a custom kernel yet? on: April 11, 2009, 01:18:41 AM
Hi folks,

I've been trying to get a custom, modular kernel built using the packaged LSP kernel and gcc compiler.

So far, i can get it almost all the way built, with the following problems:

marvell MMC driver won't compile: SUSPEND_DISABLE undeclared
dallas 1wire won't compile: no clk_get function defined

I don't see any GPIO options available in the menuconfig also..

Anyone have a working .config file? or even the .config that was used to build the packaged kernel?

I'd like the MMC stuff to work (it works in the packaged one), and i really want i2c / gpio / dallas 1w working.

I picked the Feroceon-KW system type, since that's what /proc/cpuinfo tells me it is.


Lastly, assuming i can get it compiled, how would one go about booting it? i don't see the usual vmlinuz file anywhere on the filesystem. My current plan is to try and NFS boot it.
38  General Category / General Discussion / Instructions: Getting the serial console to work on a MAC on: April 10, 2009, 10:39:45 PM
Someone helped me with this, thought i'd pass it along:

First, install the mac OS X driver from here: http://www.ftdichip.com/Drivers/VCP.htm

I have only tested on the intel version. Should work on others though, one would think.

It makes you reboot. Lame.

Ok, after the reboot, patch your Info.plist file as follows (make a backup first, just in case):

Code:
--- Info.plist.orig 2009-04-07 22:34:29.000000000 -0700
+++ /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist 2009-04-07 23:03:28.000000000 -0700
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
  <key>CFBundleDevelopmentRegion</key>
@@ -4341,6 +4341,40 @@
  <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>40591</integer>
+ <key>idVendor</key>
+ <integer>40584</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>40591</integer>
+ <key>idVendor</key>
+ <integer>40584</integer>
+ </dict>
  <key>SI Lambda 10-3</key>
  <dict>
  <key>CFBundleIdentifier</key>


once this is done, you should do a :
Code:
sudo touch /System/Library/Extensions

This rebuilds the dependencies i believe, or somesuch.

Then plug in the USB and you should be golden.

If it doesn't work, make sure your Info.plist is the new one (compare it to the backup you made, it shouldn't match)

You can also try unloading and re-loading the driver
Code:
sudo kextunload /System/Library/Extensions/FTDIUSBSerialDriver.kext
sudo kextload /System/Library/Extensions/FTDIUSBSerialDriver.kext
39  Hardware and U-Boot firmware / Hardware / Re: i2c and/or GPIO? on: April 09, 2009, 08:37:24 AM
-GPIO are in the SD slot, which means you have to choose SD or GPIO.

BTW, check this file: http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf

very nice! The SDIO section was not that useful, but it appears that the MPP pins are each addressable via a set of registers (see page 773). The diagram shows MPP 12-17 as being connected here.

Finally, looking at the diagram you linked to, it looks like the TWSI should be inside at some flex connector (in the dev board), so maybe if you open it there is some pin or pad where you can connect to.

Yea, the diagram shows it, but the schematics either don't have the flex connector on them, or there is no TWSI on it.

the "Sheeva_JTAG Schematic.pdf" page 1 shows an "FPC connector", which according to google is a flex-connector, so i'm guessing that's the one.

There are 30 pins shown, but all are MPP pins, Jtag pins, and some power. no i2c looking stuff.

-tmk
40  Hardware and U-Boot firmware / Hardware / i2c and/or GPIO? on: April 08, 2009, 11:12:20 PM
Hi folks,

I've been poring over the documentation, and i'm trying to figure out how to get at the i2c bus and/or the GPIO pins.

I have some dallas 1 wire temp sensors i want to get at, and i have an i2c->dallas converter. I'm also OK with going straight to dallas 1-wire via the GPIO pins.


So, questions:

Regarding GPIO: The docs all say that you can use the 4 SDIO data pins as GPIO. Any tips on how to address them, and if i need a custom kernel / modules for that?

I don't see a "/sys/class/gpio/" directory, so i'm assuming some things are missing.



Regarding i2c:

dmesg shows the following:
Code:
i2c /dev entries driver

but (after installing i2c-tools), i2cdump says:
Code:
Error: No I2C busses found!
Be sure you have done 'modprobe i2c-dev'
and also modprobed your i2c bus drivers

I'm ok with prying it open (only 30 day warranty anyhow), but i want to be sure the i2c bus is available. Anyone know if there is really i2c on this thing? Do i need to build my own kernel?

Also, the "TWSI" (two wire serial interface, aka i2c) is shown as being on the header on the following graphic:
http://www.globalscaletechnologies.com/skins/skin_1/images/Sheeva_Plug_BlockDiagram.png

but the header diagram on page 10 (top right) of the "Sheeva-final Schematic.pdf" file doesn't show the i2c pins.

The only mention i can find of 'TWSI' in the "Sheeva-final Schematic.pdf" file is on page 5, and it's only 1 pin (MPP1.. i2c needs 2 pins), labeled "TWSI Serial ROM Initialization Disble"


cheers
-tmk
Pages: 1 2 [3]