Admin: Protected "Kernel changes for custom hardware" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2020-10-19T18:50:29Z

Protected "Kernel changes for custom hardware" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Admin: Created page with "

Touchscreens

*1. Resistive: No changes needed. *2. Capacitive: Transfer is made thru i2c and interrupt pin is AT91_PIN_PA27. Make sure you compile the proper support..."

2020-10-19T18:50:14Z

Created page with "<h2>Touchscreens</h2> *1. Resistive: No changes needed. *2. Capacitive: Transfer is made thru i2c and interrupt pin is AT91_PIN_PA27. Make sure you compile the proper support..."

New page

<h2>Touchscreens</h2>

*1. Resistive: No changes needed.
*2. Capacitive: Transfer is made thru i2c and interrupt pin is AT91_PIN_PA27. Make sure you compile the proper support for your capacitive panel chip in kernel and you supply the proper interrupt pin to the driver.

<h2>How to compile kernel for a 7" touchscreen</h2>

By defaults kernels are compiled for 4.3" LCD. For 7" you will need to compile a new kernel or use the kernel from Android 4.0 build and overwrite the kernel from Android 2.3 built for example.
If you want to compile a new kernel you wil have to add:

#define PICOSAM9G45_BIG_DISPLAY [http://gitorious.org/picopc-kernel/kernel/blobs/minibox-picopc-android-3.1/arch/arm/mach-at91/board-picosam9g45.c#line206 here]

<h2>Using another LCD</h2>
You will need to recompile the kernel and setup the monitor and resolution from our board definition files.<br>
To do this, follow this steps:

*1. Download kernel and toolchain from our gitorious repository as explained on [[Kernel_Building|Kernel building]] page.
*2. Edit the file ''kernel/arch/arm/mach-at91/board-picosam9g45.c'' and change the struct:<br>"''fb_videomode at91_tft_vga_modes''" and "''fb_monspecs at91fb_default_monspecs''" to match your display configuration from the display datasheet.To understand translation between display datasheet naming and kernel read [[Linux_LCD_timing_handling_and_interfacing|here]]
*3. Recompile the kernel and put it on your microSD BOOT partition.

<h2> Adding a GPIO as a key in kernel </h2>
*1. Edit ''arch/arm/mach-at91/board-picosam9g45.c'' and add on the struct ''struct gpio_keys_button picosam9g45_buttons[]'':

{ /* J14 USR2 pin 1 gnd + pin 6*/
.code = KEY_UP,
.gpio = AT91_PIN_PC20,
.active_low = 1,
.desc = "Up Arrow",
},

The gpio-keys driver will automatically send KEY_UP event when USR2 pin is put to ground

<h2> Adding a GPIO as a led in kernel </h2>
*1. Edit ''arch/arm/mach-at91/board-picosam9g45.c'' and add on the struct ''struct gpio_led picosam9g45_leds[]'':
{ /* "usr3" led */
.name = "usr3",
.gpio = AT91_PIN_PC21,
.active_low = 1,
.default_trigger = "none",
},

The led can be controlled by writing 0 or 1 to ''/sys/class/leds/usr3''

<h2>Working with GPIOs</h2>
For GPIOs that aren't bound in kernel to a device/key/led, you can control them from ''sysfs'' interface from ''/sys/class/gpio/''<br>
There you have multiple gpiochip<nnn> each corresponding to the A,B,C,D,E peripheals.<br>
For example PC is gpiochip96<br>

To export PC19 (which you will find it as USR1 on J14 pin 5) do:
echo "115" > export

which means 96+19.

a directory will appear in /sys/class/gpio/gpio115/ with 2 files (direction and value)
echo out > direction
echo 0 > value

To set output of GPIO to 0<br>

Example setting a GPIO as input

cd /sys/class/gpio/
echo "115" > /sys/class/gpio/export
cd /sys/class/gpio/gpio115/
echo in > direction
cat value

<h2>Working with Analog-to-Digital Converter (ADC)</h2>

The ADC in picoSAM9G45 board provides 7 channels. 3 of these are used for
the resistive touchscreen, the rest of 4 channels (available through J16) have a 10-bit resolution and
can be used to perform analog to digital conversions.

The kernel will provide the following files to read values from the each
ADC channel (note that this functionality is not yet in the releases images see [https://gitorious.org/picopc-kernel/kernel/commit/eb3afc5d044b384b4f2204a1cca3ab2f1298e793 atmel_adc])

/sys/devices/platform/atmel_adc/ani0
/sys/devices/platform/atmel_adc/ani1
/sys/devices/platform/atmel_adc/ani2
/sys/devices/platform/atmel_adc/ani3

How to read and interpret the values:

cat /sys/devices/platform/atmel_adc/ani0

should output an integer value, that will need to be scaled as:
(ani value) * max voltage range / bit resolution.

For ani0 and ani1 (voltage in 0V-50V range): (ani0 value) * 50/1023 <br>
For ani2 and ani3 (voltage in 0V-5V range): (ani2 value) * 5 /1023

Note: The value for ani0 will always be the voltage that powers the picoSAM9G45 board.

The reads are rate limited to work concurrently with the resistive touchscreen.
If a resistive touchscreen is not used the rate limit can be disabled by editing the
driver source code.

'''J16 connector''' from pico-SAM9G45 board.<br>
<span style="dispayl: block; float: left; text-align: center; width: 30px; margin-top: 5px; padding: 0px; border:0px;">http://arm.mini-box.com/images/J16-connector.jpg<br>GND</span>
<span style="dispayl: block; float: left; text-align: center; width: 30px; margin-top: 5px; padding: 0px; border:0px;">http://arm.mini-box.com/images/J16-connector.jpg<br>ani0<br>Vin</span>
<span style="dispayl: block; float: left; text-align: center; width: 30px; margin-top: 5px; padding: 0px; border:0px;">http://arm.mini-box.com/images/J16-connector.jpg<br>ani1</span>
<span style="dispayl: block; float: left; text-align: center; width: 30px; margin-top: 5px; padding: 0px; border:0px;">http://arm.mini-box.com/images/J16-connector.jpg<br>ani2</span>
<span style="dispayl: block; float: left; text-align: center; width: 30px; margin-top: 5px; padding: 0px; border:0px;">http://arm.mini-box.com/images/J16-connector.jpg<br>ani3</span>
<div style="clear: both;"></div>

<h2>Power cycle/Reset miniPCI-E cards or USB devices</h2>
Some miniPCI-E cards might not work after power-on. To fix this issue a software "reset" is needed:

cd /sys/bus/usb/devices
ls -l

Notice the folders with 1-2, 2-2 etc, to identify the product do:
cat 1-2/product
and repeat for all folders till you identify the card

To reset issue:
echo 0 > 1-2/authorized
echo 1 > 1-2/authorized

<h2>Working with SPI interface</h2>

SPI interface can be accessed from userspace through spidev kernel driver.<br>
As of 12 Oct 2011 the spidev is included in [[Releases|binary releases]].<br><br>
By default the SPI devices from [[J7 connector|J7 Connector] and [[J9 Connector|J9 Connector] (SPI0.0 and SPI1.0) are bound to this spidev driver.<br>
If you need to bound a spi device to another kernel driver edit ''arch/arm/mach-at91/board-picosam9g45.c'' around line 135 (SPI devices) and change ''.modalias'' to your driver name.<br><br>
For testing [https://gitorious.org/picopc-tools/picopc-tools/blobs/master/hardware-tools/spi-test/ spidev_test] can be used.<br>
A sample output is:

root@picosam9:~# /spidev_test -s 14814814 -D /dev/spidev0.0
spi mode: 0
bits per word: 8
max speed: 14814814 Hz (14814 KHz)
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00

''/dev/spidev0.0'' means the spi device on bus 0 chipselect 0 (SPI0 SPI0_CS0 in schematics for [[J7 connector|J7 connector]])
<h2>Working with I²C interface</h2>

I²C interface can be accessed from userspace through [http://www.kernel.org/doc/Documentation/i2c/dev-interface i2c-dev kernel driver].<br>

For testing i2c-dev communication [https://gitorious.org/picopc-tools/picopc-tools/trees/master/hardware-tools/qtouch-control qtouch-control] can be used as an example.<br>
More advanced tools can be found [http://www.lm-sensors.org/wiki/I2CTools here]

<h2>Using the buzzer</h2>
You have to assign values between 0( which is no sound) to 255 to:

echo 200 > /sys/devices/platform/leds-atmel-pwm/leds/buzzer/brightness

<h2>Change USART to RS-485 mode</h2>
by user Minsc04 from [http://www.at91.com/forum/viewtopic.php/f%2c12/t%2c12783/ AT91SAM Community Forum]<br>
To change each USART in RS-485 mode, add this line in '''linux/drivers/serial/atmel_serial.c''' , in function '''atmel_set_termios''', just before the instruction "UART_PUT_MR(port, mode);" that configures the USART mode.

mode |= ATMEL_US_USMODE_RS485; //Take effect for all USART that you configure

or if you want filter for a specific USART, use a dedicated IRQ number :

if (port->irq == AT91SAM9260_ID_US2) // USART2 is a rs485
{
mode |= ATMEL_US_USMODE_RS485;
}

<h2>Booting kernel from U-Boot</h2>
*1. Disable direct kernel loading from bootstrap by changing DIRECT_BOOT to off in compile.sh. Reference commit in bootstrap: [https://gitorious.org/picopc-kernel/bootstrap-sdcard/commit/b1f4da58cc8feb977fb35535b46163488696652d Direct Kernel loading]
*2. It will expect uboot.bin actually be named linux.bin but that can be changed with FILE_NAME option in compile.sh.
*3. Use a Atmel patched uboot source from here: [http://www.at91.com/linux4sam/bin/view/Linux4SAM/U-Boot#U_boot_1_3_4_experimental_source uBoot for Atmel]
*4. Compile the sources with: make CROSS_COMPILE=<your toolchain location> at91sam9m10g45ek_config
*5. Optionally you can apply a patch to automatically enable 256Mb on picoPC.Patch is [[File:0001-add-support-for-both-banks-of-memory-on-Atmel-G45-bo.patch]].
*6. Copy the newly compiled BOOT.BIN (from step 1), uboot.bin (from step 4) to microSD card BOOT partition (the FAT partition). The BOOT partition should contain: BOOT.BIN (the bootstrap) uboot.bin (uboot) uImage (the kernel in uimage format)

<br><br>
<h2>picoSAM9G45 board schematics</h2><br>
{{Schematics}}

← Older revision	Revision as of 18:50, 19 October 2020
(No difference)

Kernel changes for custom hardware - Revision history

Admin: Protected "Kernel changes for custom hardware" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Admin: Created page with "

Touchscreens