TS-7250-V3 PC104 bus: Difference between revisions

From embeddedTS Manuals
No edit summary
No edit summary
Line 1: Line 1:
The TS-7250-V3 includes an ISA bus for compatibility with PC104 peripherals.  ARM itself has not traditionally had an ISA bus as part of its architecture, so this behaves differently than on X86 where ISA is typically used.  The FPGA has two memory windows, one for the kernel, and one for userspace. The FPGA will handle locking between these two accesses. In the kernel the driver will handle locking between different kernel accesses to this bus. Under userspace this is the user's responsibility.
The TS-7250-V3 includes an ISA bus for compatibility with PC104 peripherals.  ARM itself has not traditionally had an ISA bus as part of its architecture, so this behaves differently than on X86 where ISA is typically used.   
 
To access the PC104 bus in userspace, access files here:
/sys/devices/soc0/soc/2100000.aips-bus/21b8000.weim/21b8000.weim:fpga@50000000/50004000.syscon/50004050.fpgaisa/


{| class=wikitable
{| class=wikitable
! Memory Window Address
! File
! Description
! Description
|-
|-
| 0x50004050
| io8
| Used by the kernel only
| 8-bit strobes on IOR/IOW
|-
| io16
| 16-bit strobes on IOR/IOW
|-
| ioalt16
| 16-bit strobes on IOR/IOW with an [[#PC104 16-bit alternate pinout|alternate pinout]]
|-
| mem8
| 8-bit strobes on MEMR/MEMW
|-
| mem16
| 16-bit strobes on MEMR/MEMW
|-
|-
| 0x50004054
| memalt16
| Used by userspace only.
| 16-bit strobes on MEMR/MEMW with an [[#PC104 16-bit alternate pinout|alternate pinout]]
|}
|}


In the Linux kernel, see the header at include/linux/tspc104_bus.h for various bus accesses.
Any programming language can interface with these using standard file IO.  Open a file descriptor to one or more of these files, and seek to the offset of the address you are accessing.  Use read/write calls to access data on these busses.
 
For 16-bit accesses the address must always be aligned to an even byte, and reads/writes must always access multiple of 2 bytes at a time.
 
For C, or languages with a foreign function interface, we provide a library / header which can be used to handle these accesses.
* [https://github.com/embeddedarm/ts7100-utils/blob/master/src/pc104.h pc104.h]
* [https://github.com/embeddedarm/ts7100-utils/blob/master/src/pc104.c pc104.c]
 
There is also a command line utility to access the pc104 bus:
<console>
root@tsimx6:~# pc104_peekpoke
Usage pc104_peekpoke <io/mem> <8/16/alt16> <address> [value]
Eg: pc104_peekpoke io 8 0x140
</console>
 
For kernel access to the PC104 bus see the header [https://github.com/embeddedarm/linux-4.9.y/blob/ded418526890c6bb1977bc7f7547793566506d91/include/linux/tspc104_bus.h here]. Using the existing kernel driver will handle locking between userspace and any kernel drivers such as PC104 based UARTs.
 
We strongly recommend using the methods described above for accessing the PC104 bus.  For users needing to understand the implementation, the registers are described below.


In most cases users should use our abstraction to PC104, or the existing kernel drivers, but the memory window at either location follows this register format:
The FPGA presents a 32-bit memory window at 0x50004050 which follows this format:
{| class=wikitable
{| class=wikitable
! Bits
! Bits

Revision as of 12:07, 4 March 2020

The TS-7250-V3 includes an ISA bus for compatibility with PC104 peripherals. ARM itself has not traditionally had an ISA bus as part of its architecture, so this behaves differently than on X86 where ISA is typically used.

To access the PC104 bus in userspace, access files here: /sys/devices/soc0/soc/2100000.aips-bus/21b8000.weim/21b8000.weim:fpga@50000000/50004000.syscon/50004050.fpgaisa/

File Description
io8 8-bit strobes on IOR/IOW
io16 16-bit strobes on IOR/IOW
ioalt16 16-bit strobes on IOR/IOW with an alternate pinout
mem8 8-bit strobes on MEMR/MEMW
mem16 16-bit strobes on MEMR/MEMW
memalt16 16-bit strobes on MEMR/MEMW with an alternate pinout

Any programming language can interface with these using standard file IO. Open a file descriptor to one or more of these files, and seek to the offset of the address you are accessing. Use read/write calls to access data on these busses.

For 16-bit accesses the address must always be aligned to an even byte, and reads/writes must always access multiple of 2 bytes at a time.

For C, or languages with a foreign function interface, we provide a library / header which can be used to handle these accesses.

There is also a command line utility to access the pc104 bus: 

root@tsimx6:~# pc104_peekpoke 
Usage pc104_peekpoke <io/mem> <8/16/alt16> <address> [value]
	Eg: pc104_peekpoke io 8 0x140

For kernel access to the PC104 bus see the header here. Using the existing kernel driver will handle locking between userspace and any kernel drivers such as PC104 based UARTs.

We strongly recommend using the methods described above for accessing the PC104 bus. For users needing to understand the implementation, the registers are described below.

The FPGA presents a 32-bit memory window at 0x50004050 which follows this format:

Bits Description
31 Busy/Go [1]
30 1 = IO, 0 = MEM [2]
29 1 = 8-bit, 0 = 16-bit
28 1 = read cycle, 0 = write cycle
27 0 = standard pinout, 1 = TS Pinout [3]
26:0 Address or Data [4]
  1. ↑ On read, a 1 indicates the existing transaction is already busy. A 0 indicates it is available. If written to 0 then bits 26:0 specify address. If written to 1 this starts the bus cycle.
  2. ↑ Cycle type indicates if we use IOW/IOR pins, or MEMR/MEMW.
  3. ↑ The TS pinout is used on some platforms to remove the need for the 40-pin connnector while still supporting 16-bit peripherals. This does not affect 8-bit accesses. When enabled this uses these pins for the upper 16-bit.
    PC104 pin Data bit
    B4 8
    B17 9
    B18 10
    B25 11
    B20 12
    B26 13
    B14 14
    B28 15
  4. ↑ Accepts a written addr when BUSY/GO = 0. This is data on a write when Busy/GO=1, or on a read after BUSY/GO reads 0 after being written to 1.
Retrieved from "http://docs.embeddedTS.com/index.php?title=TS-7250-V3_PC104_bus&oldid=11482"