FDI LP3180, User Manual, Page: 22 / 40

FDI
NXP LPC3180 Demo
User’s Manual
FDI
Rev 2 Page 22 9/7/2007
echo "cs=1,client=wlan,cs_pin=GPO_21,flags=1,mbx_int=36,mbx_pin=
gpi_11" > /sys/devices/platform/spi-pnx1/cs_table
cat /sys/devices/platform/spi-pnx1/cs_table
The module itself can be found in the kernel module repository
(/lib/modules/2.6.10/kernel/drivers/net/ga_linuxdrv_211_pnx4008_spi.ko), but is not
loaded in the same manner as the other drivers due to the necessity of the two above
commands. To facilitate driver setup and configuration, a startup script called
“startWIFI.sh” is created and placed within the /nv directory on the LPC3180 board. By
default, each script is setup to statically assign the IP and MAC addresses of the board
according to the serial number on the board. For example, if the board’s serial number is
32, its IP address is 192.168.1.32 and the MAC address is aabbccd7ea32. Please note
that if the serial number is only 1 or 2 digits, the place-holder for the 100’s and 10’s digit
in the MAC address is replaced with the letter ‘a’. The ESSID, MODE, and WEP key are
left unmodified in the script to be configured by the user. Standard ‘wireless-tools’
commands are used to configure WIFI within the scripts.
8.4 Bluetooth
Each LPC3180 board is equipped with the NXP BGB203 Bluetooth module programmed
with version 1.2.4 of the NXP 1SPP firmware.
For correct operation, a modified version of the pshs_uart.ko kernel module must be used
which raises the reset line to the BGB203 upon initialization. Also, the pshs_uart.ko
module creates three high-speed UART devices according to the layout of the LPC3180.
The BGB203 is connected to UART2 which corresponds to /dev/ttyPSHS0 within the
device filesystem. Communication with the BGB203 is accomplished with modem
commands sent over the UART. Please consult the 1SPP user’s manual for more
information.
8.5 Framebuffer
The included GUI board comes equipped with an LCD panel controlled by the Solomon
Systech SSD1783U2 LCD Controller. For access within Linux, a framebuffer kernel
module was written and is included in the kernel patch file.
The following table shows a list of files and their purpose as they relate to the
framebuffer module. Each file is placed into the kernel tree after the linux-2.6.10-
lpc3180_FDI.patch file is applied.
File Location Description
ssdfb.c ${LINUX}/drivers/video The framebuffer driver code.
This code interacts with the linux
kernel to create and manipulate
the framebuffer device.