DHCOR STM32MP1 Linux: Difference between revisions
From Wiki-DB
Jump to navigationJump to search
| Line 89: | Line 89: | ||
| <tt>/dev/i2c-2</tt> | | <tt>/dev/i2c-2</tt> | ||
| I2C4 | | I2C4 | ||
|} | |||
=== GPIOs === | |||
:{| class="wikitable" | |||
! style="background-color:#efefef; width: 150px; text-align:left" | 96Boards Name | |||
! style="background-color:#efefef; width: 150px; text-align:left" | Linux Name | |||
! style="background-color:#efefef; width: 150px; text-align:left" | Hardware Name | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|- | |||
| A | |||
| tt>gpiochip0 14</tt> | |||
| PA14 | |||
|} | |} | ||
Revision as of 11:22, 22 July 2020
CAUTION! THIS PAGE IS UNDER CONSTRUCTION!
Linux Userspace Commands
Unsing the internal RTC
- Read out the current date and time of the system (not the RTC itself)
# date
- Set a specific system time
# date -s "2020-01-30 10:00:00"
- Save the current system time to the RTC of the STM32MP1
# hwclock -w
- When you allready have stored a date on the RTC and you want to read it out, use the next command. This command only gives back the time, but does not synchronize it with the system time. This is done in the next step.
# hwclock -r
- The system time can be synchronised to the RTC by this command:
# ??????????????????
Kernel Userspace Interfaces to Access Hardware
The pinmuxing of the DHCOR STM32MP1 can be configured just as needed by you as a customer and therefore the interfaces used in each configuration might be different. However, to give you an easy way to start developing with the DHCOR STM32MP1 you can use the Avenger96 Board, which is the reference design for our DHCOR module. Thus, the interfaces described here, are the configuration for the Avenger96.
Serial (UART) Interfaces
96Boards Name Linux Name Hardware Name UART 0 /dev/ttySTM0 UART 7 UART 1 /dev/ttySTM1 UART 4
I²C Interfaces
96Boards Name Linux Name Hardware Name I2C0 /dev/i2c-1 I2C2 I2C1 /dev/i2c-0 I2C1 OnBoard /dev/i2c-2 I2C4
microSD and eMMC
96Boards Name Linux Name Hardware Name I2C0 /dev/i2c-1 I2C2 I2C1 /dev/i2c-0 I2C1 OnBoard /dev/i2c-2 I2C4
GPIOs
96Boards Name Linux Name Hardware Name A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14 A tt>gpiochip0 14 PA14
