WORK IN PROGRESS
| Connector | Function |
|---|---|
| X19 | Microphone |
| X20 | Line In |
| X21 | Line Out |
Play Audio on
A simple test sound can be played with the commandline tool speaker-test.
Headphones or active speakers have to be connected to X21 on .
speaker-test --channels 2 --test wav -D sysdefault:CARD=tqtlv320aic32x
You can also play your own audio files using aplay
aplay <file>
e.g.
aplay test.wav
Record Audio via Line-In on
arecord -f cd test.wav
amixer or alsamixer
“}}
In U-Boot eth0 is configured as default interface. The IP configuration can be done statically or by a DHCP server in the network.
IP configuration via DHCP
For a configuration via a DHCP server, use the dhcp command in U-Boot.
Static IP configuration For a static IP configuration the following, U-Boot environment variables must be set:
setenv ipaddr <ipaddr> (e.g.: setenv ipaddr 192.168.100.111) setenv netmask <netmask> (e.g.: setenv netmask 255.255.255.0)
Both Ethernet interfaces are activated and configured by systemd-network. The configuration file for the eth0 interface is located in /lib/systemd/network/ these configuration file can be altered to customize the default interface configuration. A documentation of the configuration files can be found here.
For a temporary static configuration the ip command can be used, below some useful ip commands are listed:
Activate a specific interface
e.g. eth0
ip link set eth0 up
Disable a specific interace
e.g. eth0
ip link set eth0 down
Show ip address for a specific interface
e.g. eth0
ip addr show eth0
Show statistic for a specific interface
e.g. eth0
ip -s link show eth0
Set ip address for a specific interface
e.g. eth0
ip addr add 192.168.1.100/24 dev eth0
Show statistic of all interfaces
ip -s link
Set default gateway for a specific interfaces
e.g. set gateway ip 192.168.1.1 for eth0
ip route add default via 192.168.1.1 dev eth0
If a DHCP server is available in the network environment the ip configuration can be received from it. To do so execute the udhcpc command, by default eth0 is used.
To configure another interface via dhcp the parameter -i followed by the interface name e.g. eth1 must be given.
e.g. eth1
udhcpc -i eth1
An overview of the onboard i2c devices is available here
Select i2c bus device
i2c dev 3
Show all devices connected to the i2c bus currently selected:
i2c probe
Detect all devices connected to a i2c bus:
i2cdetect 3
TQ offers an optional LVDS Display kit for the . Each Display can be used on its own by using the corresponding device tree. To allow reusage, the support for each display is separated in a dtsi fragment.
To bring up the display the U-Boot environment has to be adapted accordingly.
setenv fdt_file
- Save the envrionment by executing the saveenv'' commandTo set the hardware clock to the actual time and date use the following commands:
date -s [YYYY.]MM.DD-hh:mm[:ss] hwclock -w
The has one SPI interfaces. They can be found on the extension headers and can be tested with a loopback test.
| Interface | linux filesystem |
|---|
For the loopback test you need a bridge between SPI_MOSI and SPI_MISO:
echo -n -e "\x01\x0F" | spi-pipe -d <spi interface> -s 10000000 | hexdump (e.g. echo -n -e "\x01\x0F" | spi-pipe -d /dev/spidev1.0 -s 10000000 | hexdump)
With lsusb you can see all connected usb devices. To mount a partition of an usb stick you can excute mount /dev/<partition> <mount dir> (e.g. mount /dev/sdb1 /mnt). This will mount the first partition of sdb to /mnt. To unmount the device execute umount <mount dir> (e.g. umount /mnt).
| Reference | LED name | color | linux filesystem |
|---|
The user LED's are located in .
To change the behaviour a specific LED, the value in the file trigger must be overwritten.
The following values are valid:
For example set the trigger of to heartbeat
echo heartbeat >
“|location=”/sys/devices/soc0/gpio-leds/leds”|example=“/sys/class/leds/led1/trigger”}}