Beagleboard second uart and spi

[WingZero]

Hi, I recently migrated to Archlinux on my beagle board because i need i higher kernel. Thing is i can't seem to get the second uart and spi working and i don\t see the options when recompiling the kernel to select the beagleboard as my platform. Could i get some help on enabling these features?

[android]

Hi There,

I know this is quite an old thread, but for the record, I thought I'd reply.

If you're using a 3.4 omap kernel, you can enable spidev by simply including a line in uEnv.txt:$this->bbcode_second_pass_code('', ' buddy=spidev')

Then these divices will appear:
[root@apm001 johnea]# ls -l /dev/spi*
crw-rw---- 1 root uucp 153, 0 Jan 6 2000 /dev/spidev3.0
crw-rw---- 1 root uucp 153, 1 Jan 6 2000 /dev/spidev3.1
crw-rw---- 1 root uucp 153, 2 Jan 6 2000 /dev/spidev4.0

I include these lines in /etc/rc.local to adjust permissions:$this->bbcode_second_pass_code('', '
# spidev set to group uucp and writable
chown :uucp /dev/spidev*
chmod g+rw /dev/spidev*
')

I've run the spidev_test from the directory linux-git/Documentation/spi/spidev_test.c against these devices and observed the transfers on a logic analyzer. It works!

The uart on the expansion connector: /dev/ttyO1, worked out of the box on 3.2 omap kernels. However on 3.4 omap kernels this device is not present, and I still haven't figured out how to get it back.

The ttyO2 uart is connected to the DB-9 connector, it is still present in 3.4 kernels.

All of the old kernel patching to enable spidev is no longer necessary with 3.4, now if we can jsut get ttyO1 and DVI video working again...

android

[amdintel2000]

Dear android,

i try to set up the parameter buddy=spidev on uEnv.txt and boot .scr,
and build on BeagleBoard RevC5, boot by SD Card...

$this->bbcode_second_pass_code('', '
U-Boot 2011.06-dirty (Jul 19 2011 - 17:30:34)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0
In: serial
Out: serial
Err: serial
Beagle Rev C4
Recognized Tincantools Zippy board (rev 0 0)
Die ID #06900004000000000403a1f30301d012
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
reading boot.scr

222 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage

4557184 bytes read
## Booting kernel from Legacy Image at 80300000 ...
Image Name: Linux-3.4.4-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4557120 Bytes = 4.3 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...
')

But i don't get the spidev in /dev/spidev*

$this->bbcode_second_pass_code('', '
[ 0.224395] omap2_mcspi omap2_mcspi.1: master is unqueued, this is deprecated
[ 0.224975] omap2_mcspi omap2_mcspi.2: master is unqueued, this is deprecated
[ 0.225524] omap2_mcspi omap2_mcspi.3: master is unqueued, this is deprecated
[ 0.226013] omap2_mcspi omap2_mcspi.4: master is unqueued, this is deprecated
')

But omap2_mcspi didn't work!
The buddy=spidev for enable spi be canceled now ? Thanks

with Best Reagards,
ShinFu

$this->bbcode_second_pass_quote('android', 'H')i There,

I know this is quite an old thread, but for the record, I thought I'd reply.

If you're using a 3.4 omap kernel, you can enable spidev by simply including a line in uEnv.txt:$this->bbcode_second_pass_code('', ' buddy=spidev')

Then these divices will appear:
[root@apm001 johnea]# ls -l /dev/spi*
crw-rw---- 1 root uucp 153, 0 Jan 6 2000 /dev/spidev3.0
crw-rw---- 1 root uucp 153, 1 Jan 6 2000 /dev/spidev3.1
crw-rw---- 1 root uucp 153, 2 Jan 6 2000 /dev/spidev4.0

I include these lines in /etc/rc.local to adjust permissions:$this->bbcode_second_pass_code('', '
# spidev set to group uucp and writable
chown :uucp /dev/spidev*
chmod g+rw /dev/spidev*
')

I've run the spidev_test from the directory linux-git/Documentation/spi/spidev_test.c against these devices and observed the transfers on a logic analyzer. It works!

The uart on the expansion connector: /dev/ttyO1, worked out of the box on 3.2 omap kernels. However on 3.4 omap kernels this device is not present, and I still haven't figured out how to get it back.

The ttyO2 uart is connected to the DB-9 connector, it is still present in 3.4 kernels.

All of the old kernel patching to enable spidev is no longer necessary with 3.4, now if we can jsut get ttyO1 and DVI video working again...

android

[gdamjan]

Just for the record, the current 3.5.4-1-ARCH kernel "sees" 4 UARTs
$this->bbcode_second_pass_code('', '
[ 0.516540] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
[ 0.517089] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
[ 0.517730] omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2
[ 0.559204] console [ttyO2] enabled
[ 0.559722] omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 80) is a OMAP UART3
')
haven't checked if they are all working physically though.