2008-09-08 10:31:26 USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 61784
Has anyone successfully used the 527 0.2 silicon with a USB Host device with the
musb driver? I have been waiting for the 0.2 silicon and the update to the musb
to support DMA and now that I have them I can't get them to work. I'm not using
the new DMA code right now since I thought I would try to get the PIO mode
working first (one thing at a time and all...). The failure mode that I see is
that the musb host mode driver fails to enumerate the USB device properly. It
ends up in a continuous re-try loop. Interestingly enough, with the 0.1
silicon, where the USB doesn't work, the enumeration completes without
incident. With the 0.2 silicon we also have new copper so it is entirely
possible that the rev of the 527 has nothing to do with the failure that I am
seeing. I would like to hear from anyone in the community who has used the 527
0.2 silicon in host mode, at least then I can focus on the copper as the problem
and not the silicon.
Thanks,
Greg
P.S. I am using the exact same code that works with the 526, albiet without USB DMA.
QuoteReplyEditDelete
2008-09-08 13:46:56 Re: USB Host Mode on 527
Robin Getz (UNITED STATES)
Message: 61790
Greg:
>Has anyone successfully used the 527 0.2 silicon with a USB Host device with the
>musb driver?
Nope. (or at least not I)
No one has tried it yet due to lack of avalible hardware. There was a board shipped to the developer today - but there are outstanding hardware issues that currently look like they are problems with the USB implmentation in hardware & have no suggested workarounds for. Have a look at the bug tracker.
-Robin
QuoteReplyEditDelete
2008-09-08 14:41:30 Re: USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 61795
Well that is actually a surprise, we were under the impression that the developer had 527 0.2 silicon long ago (certainly before we had it).
In any case, it looks like all of these bugs relate to general USB data corruption / data loss on a number of processors. It is possible that we are seeing that during the enumeration phase (when musb loads) but there is a difference in that we see nothing but this error whereas these bugs indicate sporadic errors. Also, we don't see the enumeration errors with a 526 or 0.1 527 (we only use the USB with the 526 given the 0.1 527 problems but we load the host controller driver in any case).
Where does looking into the 527 0.2 silicon USB fall in priorities for the developer? As I'm sure you can imagine, having this working on the new silicon is very important to us since I still have to get the device driver working and integrated with the DMA mode of the new host controller driver with the 2.6.24 kernel release (required for the DMA mode).
Thanks,
Greg
QuoteReplyEditDelete
2008-09-08 21:01:04 Re: USB Host Mode on 527
Robin Getz (UNITED STATES)
Message: 61801
Greg:
>we were under the impression that the developer had 527 0.2 silicon long ago
Nope. It is pretty common (although unfortuante) that many people get chips/platforms before we do.
>Where does looking into the 527 0.2 silicon USB fall in priorities for the developer?
zero until they get the board. (which normally takes a week to ship/clear customs/etc). After they get the board - high.
-Robin
QuoteReplyEditDelete
2008-09-12 12:33:27 Re: USB Host Mode on 527
Adam Cook (UNITED STATES)
Message: 62063
I am not the developer, but I did get my hands on a BF527 Rev 0.2 board to compare to my Rev 0.0 and these are the results I observed using the same kernel on both targets (kernel built for Rev 0.0):
Results with BF527 Rev 0.0 board (seems to work fine):
root:/> usb 1-1: new high speed USB device using musb_hdrc and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
scsi 0:0:0:0: Direct-Access SanDisk U3 Cruzer Micro 6.51 PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: [sda] 2014271 512-byte hardware sectors (1031 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 2014271 512-byte hardware sectors (1031 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
root:/> cd dev
root:/dev> ls
1-1 otp ram14 ram9 usbdev1.1_ep00
console ptmx ram15 random usbdev1.1_ep81
fb0 pts ram2 rtc0 usbdev1.2
full ram0 ram3 sda usbdev1.2_ep00
kmem ram1 ram4 sda1 usbdev1.2_ep02
kmsg ram10 ram5 tty usbdev1.2_ep81
log ram11 ram6 ttyBF0 watchdog
mem ram12 ram7 urandom zero
null ram13 ram8 usbdev1.1
root:/dev>
Results with Rev 0.2 board (the device does not seem to be recognized):
root:/>
root:/> cd dev
root:/dev> ls
console otp ram13 ram7 usbdev1.1
fb0 ptmx ram14 ram8 usbdev1.1_ep00
full pts ram15 ram9 usbdev1.1_ep81
kmem ram0 ram2 random watchdog
kmsg ram1 ram3 rtc0 zero
log ram10 ram4 tty
mem ram11 ram5 ttyBF0
null ram12 ram6 urandom
root:/dev>
QuoteReplyEditDelete
2008-09-12 17:17:57 Re: USB Host Mode on 527
Robin Getz (UNITED STATES)
Message: 62081
Adam:
Did you recompile with the silicon set to 0.2? or just run the 0.0 on it? (both should work, so it does look like there is an issue if the switches were all correct) - but until we get the hardware in front of the developer - it is pretty difficult to say what is going on.
-Robin
QuoteReplyEditDelete
2008-09-15 08:45:51 Re: USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 62170
Compiling for 0.0 vs 0.2 cannot matter, if it does there are more significant issues to discuss like backward compatibility. It cannot be that code compiled for 0.0 will not work correctly on 0.1 or 0.2 silicon. Even if it is required to re-compile pre-supposes that the tool set recognizes 0.2 silicon...and then we (all developers, that is) would have to contend with 0.0, 0.1 and 0.2 flavors of code for processors that are "in the wild". That just cannot be.
Greg
QuoteReplyEditDelete
2008-09-15 09:47:20 Re: USB Host Mode on 527
Robin Getz (UNITED STATES)
Message: 62173
Greg:
>Compiling for 0.0 vs 0.2 cannot matter,
There have been many times in the past where existing anomaly workarounds cause problems on newer silicon (where the anomaly has been fixed) - this is mostly true on versions we have not seen yet. It is the goal to make sure that things compiled for 0.0 will run on 0.2, but since we have not yet seen 0.2 yet - this is a possibility for the existing codebase.
That is just a fact of life. We can make things backwards compatible - but we need to know what we are making things comaptable with
For now - can somone answer the question? were things compiled for 0.2 or 0.0 for the tests?
QuoteReplyEditDelete
2008-09-15 12:20:56 Re: USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 62176
I can tell you that I have not compiled anything specifically for v0.2 silicon, in fact, my tool set doesn't even support v0.2 as an option. The only choices that I have in menuconfig are 0.0, 0.1, Any and None; I use Any.
12:06 PM greg@GPS-Linux >bfin-linux-uclibc-gcc -v
Using built-in specs.
Target: bfin-linux-uclibc
Configured with: /usr/local/src/blackfin/svn/toolchain/trunk/gcc-4.1/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=bfin-linux-uclibc --prefix=/usr/local/src/blackfin/toolchains/20071025/out-linux-uclibc --enable-threads=posix --enable-shared --with-sysroot=/usr/local/src/blackfin/toolchains/20071025/out-linux-uclibc/bfin-linux-uclibc/runtime --disable-libstdcxx-pch --disable-symvers --disable-libssp --enable-version-specific-runtime-libs --enable-__cxa_atexit
Thread model: posix
gcc version 4.1.2 (ADI svn)
12:08 PM greg@GPS-Linux >bfin-uclinux-gcc -mcpu=bf527-0.2 hello.c
cc1: error: -mcpu=bf527-0.2 has invalid silicon revision
cc1: error: unrecognized command line option "-mcpu=bf527-0.2"
QuoteReplyEditDelete
2008-09-15 13:07:53 Re: USB Host Mode on 527
Mike Frysinger (UNITED STATES)
Message: 62178
you're talking about the ideal situation. Robin is talking about reality. yes, the ideal situation is as you describe, but if reality doesnt match it, then we need to fix it. and as Robin said, we currently cannot test reality. we can attempt to code for the ideal situation, but without a way to test, all you get is reality.
QuoteReplyEditDelete
2008-09-15 13:25:28 Re: USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 62179
I can appreciate that but where does that leave us in terms of product development? If we ship product with 0.x silicon and then subsequently ship product with 0.y silicon we then have to build unique code packages with separate distributions and make sure that a device with 0.x never gets the code intended for 0.y rather than always building for 0.x and being able to use that everywhere? It sounds like you are saying that we need to be prepared for this situation, is that what you mean?
Greg
QuoteReplyEditDelete
2008-09-15 13:34:33 Re: USB Host Mode on 527
Mike Frysinger (UNITED STATES)
Message: 62180
you're asking us to guarantee that code we write today and test against 0.0 to 0.x will always work for 0.x+1 to 0.y ? that isnt reasonable by any stretch of the word.
we *attempt* to do that, but there is absolutely no way to guarantee it. anyone who says they guarantee it is lying through their teeth.
QuoteReplyEditDelete
2008-09-15 13:39:42 Re: USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 62181
I'm not talking about code at all. This thread started by the assumption that a kernel compiled with gcc set to generate code for the 0.0 silicon isn't guaranteed to work for 0.2 silicon. That's like saying if I distribute a Windows program that I can't be sure that the next Intel processor will run that same binary. I think it is eminently reasonable to expect binary compatibility with previous processors.
Greg
QuoteReplyEditDelete
2008-09-15 13:44:20 Re: USB Host Mode on 527
Mike Frysinger (UNITED STATES)
Message: 62182
it isnt the same at all. an Intel processor is just a processor. it is not a SoC like the Blackfin which means it does not have peripherals.
QuoteReplyEditDelete
2008-09-15 13:44:55 Re: USB Host Mode on 527
Mike Frysinger (UNITED STATES)
Message: 62183
oh, and we arent talking about userspace programs here. we're talking about kernel drivers.
QuoteReplyEditDelete
2008-09-15 15:27:28 Re: USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 62188
I guess maybe we are not talking about the same thing. I'm talking about using a kernel/application *binary image* built for 0.0 silicon and expecting that, without re-compiling, it will work *the same* on 0.2 silicon.
Greg
QuoteReplyEditDelete
2008-09-15 15:37:35 Re: USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 62189
What I am saying is that I would expect the binary image to perform *the same* in the case where the underlying hardware has not been augmented with new features. That is, if I have a kernel / application image that uses the core and peripherals and functions as desired I would not expect that I would need to re-compile that code to the new processor silicon version for anything other than features that are available only on the new silicon. In the case of this thread if a USB device works on the 0.0 silicon there should be no reason to re-compile it specifically for the 0.2 silicon.
Greg
QuoteReplyEditDelete
2008-09-15 18:05:29 Re: USB Host Mode on 527
Robin Getz (UNITED STATES)
Message: 62190
Greg:
Yes - you are correct - if things stay the same, they work. However - what we are talking about did not stay the same. The 527 0.2 USB is not the same as the USB on 0.1 - or 0.0 - it changed. So things break - that is expected - and like Mike said - reality.
All we say when it comes to future proofing - is that we test on _existing_ avalible silicon. We make sure code that is compiled for earlier versions will work on avalible/existing parts which we can test on. (In this specific case - this is still not true - since we do not have 0.2 avalible today - (currently stuck in customs)). We don't know what effects the "fixes" will have - and in some cases - "fixes" for issue A, creates issue B.
Sometimes is it just mistakes on our part - (workarounds that are not conditional) - and we don't notice since we are always testing on silicon with the anomalies on them. When things get fixed - functionality changes - so the software breaks. Just like you said was OK.
-Robin
QuoteReplyEditDelete
2008-09-15 18:09:45 Re: USB Host Mode on 527
Robin Getz (UNITED STATES)
Message: 62191
Greg:
>I'm talking about using a kernel/application *binary image* built for 0.0 silicon and expecting that, without re-compiling,
>it will work *the same* on 0.2 silicon.
It's not the same. If it was, it would still be 0.0 - like I said before - sometimes fixes in hardware anomalies cause the software problems. Is this what we want to happen - no - but like Mike said - this is what has happened in the past, is likely is happening now, and will happen in the future. There isn't much to be done about it.
You are asking us to create software for hardware that doest yet exist.
-Robin
QuoteReplyEditDelete
2008-09-16 02:39:55 Re: USB Host Mode on 527
Bryan Wu (CHINA)
Message: 62204
Hi Greg,
As I did not found any information about your test environment, I tried the 08R1.5 kernel and uClinux-dist on the latest bf527 0.2 silicon ezkit board which arrived at last weekend. 08R1.5 works fine on my side:
----
Linux version 2.6.22.19-ADI-2008R1.5-svn5296 (roc@roc-desktop) (gcc version 4.1.2 (ADI svn)) #5 Tue Sep 16 14:25:43 CST 2008
early printk enabled on early_BFuart0
Hardware Trace Active and Enabled
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF527 Rev 0.0
Warning: Compiled for Rev 0, but running on Rev 2
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 525 MHz core clock and 131 MHz System Clock
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
text = 0x00001000-0x0012afc0
rodata = 0x0012b000-0x00184cf0
data = 0x00185000-0x0019c000
stack = 0x00186000-0x00188000
init = 0x0019c000-0x008c8000
bss = 0x008c8000-0x008d7c10
available = 0x008d7c10-0x03eff000
DMA Zone = 0x03f00000-0x04000000
On node 0 totalpages: 16127
DMA zone: 125 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 16002 pages, LIFO batch:3
Normal zone: 0 pages used for memmap
NOMPU: setting up cplb tables for global access
Instruction Cache Enabled
Data Cache Enabled (write-through)
Built 1 zonelists. Total pages: 16002
Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600 ip=192.168.0.66:192.168.0.55:192.168.0.1:255.255.255.0:bf527-ezkit:eth0:off
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
console handover: boot [early_BFuart0] -> real [ttyBF0]
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Kernel managed physical pages: 16127
Memory available: 54876k/65536k RAM, (7344k init code, 1191k kernel code, 516k data, 1024k dma, 584k reserved)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Data A SRAM: 16 KB (15 KB free)
Blackfin Data B SRAM: 16 KB (16 KB free)
Blackfin Instruction SRAM: 48 KB (42 KB free)
Calibrating delay loop... 1046.52 BogoMIPS (lpj=2093056)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
stamp_init(): registering device resources
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, pio, host, debug=0
musb_hdrc: ConfigData=0x00 (UTMI-8)
musb_hdrc: kernel must blacklist external hubs
musb_hdrc: hw_ep 0shared, max 64
musb_hdrc: hw_ep 1tx, max 128
musb_hdrc: hw_ep 1rx, max 128
musb_hdrc: hw_ep 2tx, max 128
musb_hdrc: hw_ep 2rx, max 128
musb_hdrc: hw_ep 3tx, max 128
musb_hdrc: hw_ep 3rx, max 128
musb_hdrc: hw_ep 4tx, max 128
musb_hdrc: hw_ep 4rx, max 128
musb_hdrc: hw_ep 5tx, max 1024
musb_hdrc: hw_ep 5rx, max 1024
musb_hdrc: hw_ep 6tx, max 1024
musb_hdrc: hw_ep 6rx, max 1024
musb_hdrc: hw_ep 7tx, max 1024
musb_hdrc: hw_ep 7rx, max 1024
musb_hdrc: USB Host mode controller at ffc03800 using PIO, IRQ 59
musb_hdrc musb_hdrc.0: MUSB HDRC host driver
musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
bfin-t350mcqb: 320x240 24-bit RGB FrameBuffer initializing...
dma_alloc_init: dma_page @ 0x03af0000 - 256 pages at 0x03f00000
bfin-otp: initialized
bfin-wdt: initialized: timeout=20 sec (nowayout=0)
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 31) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
bfin_mac_mdio: probed
bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:03, irq=-1, mdc_clk=2500000Hz(mdc_div=25)@sclk=131MHz)
bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver
bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@7
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Setting up Blackfin MMR debugfs
rtc-bfin rtc-bfin: setting the system clock to 1970-01-01 01:26:33 (5193)
IP-Config: Complete:
device=eth0, addr=192.168.0.66, mask=255.255.255.0, gw=192.168.0.1,
host=bf527-ezkit, domain=, nis-domain=(none),
bootserver=192.168.0.55, rootserver=192.168.0.55, rootpath=
Freeing unused kernel memory: 7344k freed
PHY: 0:03 - Link is Up - 100/Full
root:/>
root:/> usb 1-1: new high speed USB device using musb_hdrc and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
scsi 0:0:0:0: Direct-Access PEN DISK 2.00 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 512000 512-byte hardware sectors (262 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 512000 512-byte hardware sectors (262 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
root:/>
root:/>
root:/> ls /dev/
1-1 otp ram14 ram9 usbdev1.1_ep00
console ptmx ram15 random usbdev1.1_ep81
fb0 pts ram2 rtc0 usbdev1.2
full ram0 ram3 sda usbdev1.2_ep00
kmem ram1 ram4 sda1 usbdev1.2_ep02
kmsg ram10 ram5 tty usbdev1.2_ep81
log ram11 ram6 ttyBF0 usbdev1.2_ep83
mem ram12 ram7 urandom watchdog
null ram13 ram8 usbdev1.1 zero
root:/> mount /dev/sda1 /mnt/
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
root:/> df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda1 251671 10294 228590 4% /mnt
root:/> cd /mnt/
root:/mnt> ls
10m.bin lost+found
root:/mnt> rm 10m.bin
root:/mnt> cd ..
root:/> umount /mnt/
root:/>
root:/> uname -a
Linux blackfin 2.6.22.19-ADI-2008R1.5-svn5296 #5 Tue Sep 16 14:25:43 CST 2008 blackfin unknown
root:/> release
release: not found
root:/> version
kernel: Linux release 2.6.22.19-ADI-2008R1.5-svn5296, build #5 Tue Sep 16 14:25:43 CST 2008
toolchain: bfin-uclinux-gcc release gcc version 4.1.2 (ADI svn)
user-dist: release svn-7060, build #4 Tue Sep 16 14:25:22 CST 2008
----
I guess you're trying the svn trunk. A patch to workaround the silicon USB DMA issue is not checked into svn trunk because we want to find more elegant solutions.
Thanks,
-Bryan
QuoteReplyEditDelete
2008-09-16 08:59:07 Re: USB Host Mode on 527
Greg Semeraro (UNITED STATES)
Message: 62252
I think all of this wouldn't exist if the anomoly fixes were run-time evaluations of the processor stepping. That is the way that the rest of world does things. Compile-time selection of the processor stepping is the root of the problem.
Greg
QuoteReplyEditDelete
2008-09-16 13:51:59 Re: USB Host Mode on 527
Mike Frysinger (UNITED STATES)
Message: 62258
not really. silicon revision selection dictates the oldest revision you want to work with. people who select 0.2 dont want workarounds for older silicon.
QuoteReplyEditDelete
2008-09-16 14:02:53 Re: USB Host Mode on 527
Robin Getz (UNITED STATES)
Message: 62261
Greg:
It doesn't matter if it is run time or compile time - the issue is that you are asking us to verify something that doesn't exist. We can't do that. it is impossible.
-Robin
QuoteReplyEditDelete
2008-09-18 06:53:06 Re: USB Host Mode on 527
Bryan Wu (CHINA)
Message: 62378
I also tested latest the svn trunk kernel, it works fine on BF527 0.2 silicon EZKIT.
----
Linux version 2.6.26.5-ADI-2009R1-pre-svn5311 (roc@roc-desktop) (gcc version 4.1.2 (ADI svn)) #6 Thu Sep 18 18:49:19 CST 2008
console [early_BFuart0] enabled
early printk enabled on early_BFuart0
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
fixedcode = 0x00000400-0x00000490
text = 0x00001000-0x001498d0
rodata = 0x001498e0-0x001b3c94
bss = 0x001b3ca0-0x001c60b8
data = 0x001c60b8-0x001dc000
stack = 0x001da000-0x001dc000
init = 0x001dc000-0x00819000
available = 0x00819000-0x03eff000
DMA Zone = 0x03f00000-0x04000000
Hardware Trace Active and Enabled
Reset caused by Software reset
Blackfin support (C) 2004-2008 Analog Devices, Inc.
Compiled for ADSP-BF527 Rev 0.2
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 525 MHz core clock and 131 MHz System Clock
boot memmap: 0000000000819000 - 0000000003eff000 (usable)
On node 0 totalpages: 16127
DMA zone: 126 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 16001 pages, LIFO batch:3
Normal zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
NOMPU: setting up cplb tables for global access
Instruction Cache Enabled
Data Cache Enabled (write-through)
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 16001
Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600 ip=192.168.0.66:192.168.0.55:192.168.0.1:255.255.255.0:bf527-ezkit:eth0:off
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x25
console [tty0] enabled
console handover: boot [early_BFuart0] -> real [ttyBF0]
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Kernel managed physical pages: 16127
Memory available: 55632k/65536k RAM, (6388k init code, 1314k kernel code, 586k data, 1024k dma, 588k reserved)
Calibrating delay loop... 1046.52 BogoMIPS (lpj=2093056)
Security Framework initialized
Mount-cache hash table entries: 512
Blackfin Scratchpad data SRAM: 4 KB
Blackfin L1 Data A SRAM: 16 KB (15 KB free)
Blackfin L1 Data B SRAM: 16 KB (16 KB free)
Blackfin L1 Instruction SRAM: 48 KB (42 KB free)
net_namespace: 192 bytes
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
stamp_init(): registering device resources
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, pio, host, debug=0
musb_hdrc: ConfigData=0x00 (UTMI-8)
musb_hdrc: hw_ep 0shared, max 64
musb_hdrc: hw_ep 1tx, max 128
musb_hdrc: hw_ep 1rx, max 128
musb_hdrc: hw_ep 2tx, max 128
musb_hdrc: hw_ep 2rx, max 128
musb_hdrc: hw_ep 3tx, max 128
musb_hdrc: hw_ep 3rx, max 128
musb_hdrc: hw_ep 4tx, max 128
musb_hdrc: hw_ep 4rx, max 128
musb_hdrc: hw_ep 5tx, max 1024
musb_hdrc: hw_ep 5rx, max 1024
musb_hdrc: hw_ep 6tx, max 1024
musb_hdrc: hw_ep 6rx, max 1024
musb_hdrc: hw_ep 7tx, max 1024
musb_hdrc: hw_ep 7rx, max 1024
musb_hdrc: USB Host mode controller at ffc03800 using PIO, IRQ 59
musb_hdrc musb_hdrc.0: MUSB HDRC host driver
musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
Setting up Blackfin MMR debugfs
msgmni has been set to 108
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
bfin-t350mcqb: 320x240 24-bit RGB FrameBuffer initializing...
dma_alloc_init: dma_page @ 0x039a6000 - 256 pages at 0x03f00000
Console: switching to colour frame buffer device 40x30
bfin-otp: initialized
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 31) is a BFIN-UART
brd: module loaded
bfin_mac_mdio: probed
bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:03, irq=-1, mdc_clk=2500000Hz(mdc_div=25)@sclk=131MHz)
bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1
Driver 'sd' needs updating - please use bus_type methods
bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@7
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
bfin-wdt: initialized: timeout=20 sec (nowayout=0)
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
rtc-bfin rtc-bfin: setting system clock to 1970-01-01 00:10:05 UTC (605)
IP-Config: Complete:
device=eth0, addr=192.168.0.66, mask=255.255.255.0, gw=192.168.0.1,
host=bf527-ezkit, domain=, nis-domain=(none),
bootserver=192.168.0.55, rootserver=192.168.0.55, rootpath=
Freeing unused kernel memory: 6388k freed
PHY: 0:03 - Link is Up - 100/Full
root:/>
root:/>
root:/> version
kernel: Linux release 2.6.26.5-ADI-2009R1-pre-svn5311, build #6 Thu Sep 18 18:49:19 CST 2008
toolchain: bfin-uclinux-gcc release gcc version 4.1.2 (ADI svn)
user-dist: release svn-7077, build #985 Thu Sep 18 18:48:46 CST 2008
root:/> uname -a
Linux blackfin 2.6.26.5-ADI-2009R1-pre-svn5311 #6 Thu Sep 18 18:49:19 CST 2008 blackfin unknown
root:/>
root:/> usb 1-1: new high speed USB device using musb_hdrc and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
scsi 0:0:0:0: Direct-Access PEN DISK 2.00 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 512000 512-byte hardware sectors (262 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 512000 512-byte hardware sectors (262 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
root:/>
root:/> mount /dev/sda1 /mnt/
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
root:/> ls /mnt/
lost+found
root:/> umount /mnt/
root:/> usb 1-1: USB disconnect, address 2
----
-Bryan