This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:jethub_d1 [2022/01/22 11:06] Dmitriy [1-Wire] |
en:jethub_d1 [2022/02/08 21:00] (current) Aleksandr Kazantsev [Communications] |
||
---|---|---|---|
Line 11: | Line 11: | ||
==== General characteristics ==== | ==== General characteristics ==== | ||
- | * Quad-core Amlogic A113X (ARM Cortex-A53) processor with an operating frequency | + | * Quad-core Amlogic A113X (ARM Cortex-A53) processor with an operating frequency |
* RAM 512 MB or 1 GB DDR3; | * RAM 512 MB or 1 GB DDR3; | ||
- | * Non-volatile memory eMMC flash 8 GB or 16 GB. | + | * Non-volatile memory eMMC flash 8 GB, 16 GB or 32GB. |
Equipment options: | Equipment options: | ||
* 512MB RAM / 8GB eMMC; | * 512MB RAM / 8GB eMMC; | ||
- | * 1GB RAM / 16GB eMMC. | + | * 1GB RAM / 16GB eMMC; |
+ | * 1GB RAM / 32GB eMMC; | ||
==== Communications ==== | ==== Communications ==== | ||
- | * Integrated dual-band (2.4GHz and 5GHz) AMPAK AP6255 WiFi/ | + | * Integrated dual-band (2.4GHz and 5GHz) AMPAK AP6255 WiFi/ |
* Ethernet IEEE 802.3 10/100 Mbps; | * Ethernet IEEE 802.3 10/100 Mbps; | ||
* TI CC2538 + CC2592 or TI CC2652P1 ZigBee wireless module with output power up to 20dBm and supports ZigBee 3.0 standard. | * TI CC2538 + CC2592 or TI CC2652P1 ZigBee wireless module with output power up to 20dBm and supports ZigBee 3.0 standard. | ||
Line 107: | Line 108: | ||
Appearance and elements of the controller: | Appearance and elements of the controller: | ||
- | {{:: | + | {{: |
On the top side of the controller are: | On the top side of the controller are: | ||
Line 262: | Line 263: | ||
===== 1-Wire ===== | ===== 1-Wire ===== | ||
- | |||
- | To implement the 1-Wire bus on the JetHome JetHub D1 controller, use the 1-Wire controller [https:// | ||
- | |||
- | Expansion connector pins used to connect to the 1-Wire controller (see A113 Processor Module Expansion Connector Description): | ||
- | |||
- | ^ Expansion connector pin ^ Purpose ^ Processor port ^ | ||
- | | 17 | I2C_SCK | GPIOAO_10/ | ||
- | | 18 | I2C_SDA | GPIOAO_11/ | ||
- | |||
**Starting from revision 1.5 of the controller, a 3-pin terminal with a pitch of 3.5mm is used to connect the 1-Wire bus.** Purpose of the 1-Wire terminal pins: | **Starting from revision 1.5 of the controller, a 3-pin terminal with a pitch of 3.5mm is used to connect the 1-Wire bus.** Purpose of the 1-Wire terminal pins: | ||
Line 278: | Line 270: | ||
| 2 | data | Data bus 1-Wire | | | 2 | data | Data bus 1-Wire | | ||
| 3 | GND | Common wire | | | 3 | GND | Common wire | | ||
+ | |||
+ | For reliable operation of 1-Wire devices, it is recommended to connect them to the controller using a three-wire circuit (with power from +5V output). | ||
**In controller revisions up to 1.5, the 1-Wire bus is routed to an external RJ22 connector (4P4C).** RJ22 1-Wire connector pin assignment: | **In controller revisions up to 1.5, the 1-Wire bus is routed to an external RJ22 connector (4P4C).** RJ22 1-Wire connector pin assignment: | ||
- | {{:: | + | {{: |
^ Pin number ^ Purpose ^ Description ^ | ^ Pin number ^ Purpose ^ Description ^ | ||
Line 290: | Line 284: | ||
When connecting passively powered 1-Wire devices, use pins 3 and 4 of this connector. | When connecting passively powered 1-Wire devices, use pins 3 and 4 of this connector. | ||
- | To protect against electrostatic interference, a specialized TVS diode DS9503 | + | |
+ | **Starting with revision 1.8 of the JetHome JetHub D1 controller, GPIOA_14 of the Amlogic A113X processor is used to implement the 1-Wire bus.** | ||
+ | |||
+ | **In revisions of the JetHome JetHub D1 controller up to 1.8, a 1-Wire chip [[https:// | ||
+ | |||
+ | Expansion connector pins used to connect to the 1-Wire controller (see A113 Processor Module Expansion Connector Description): | ||
+ | |||
+ | ^ Expansion connector pin ^ Purpose ^ Processor port ^ | ||
+ | | 17 | I2C_SCK | GPIOAO_10/ | ||
+ | | 18 | I2C_SDA | GPIOAO_11/ | ||
===== Linux 1-Wire example ===== | ===== Linux 1-Wire example ===== | ||
- | A description of working with 1-wire devices in Linux can be found, for example, [[https:// | + | A description of working with 1-wire devices in Linux can be found, for example, [[https:// |
- | To initialize the 1-Wire DS2482 driver on the controller, you need to execute the following commands (by default, in JetHome Armbian, the 1-Wire bus is configured at system boot and no additional configuration | + | To initialize the 1-Wire DS2482 driver |
< | < | ||
Line 303: | Line 307: | ||
</ | </ | ||
- | After that, the 1-wire devices connected to the bus will be available in the / | + | 1-wire devices connected to the bus will be available in the / |
< | < | ||
Line 347: | Line 351: | ||
=====Zigbee Wireless Module===== | =====Zigbee Wireless Module===== | ||
- | The JetHome JetHub D1 controller has a Zigbee wireless communication module based on the TI CC2538 + CC2592 or TI CC2652P1 chip. See module description: | + | The JetHome JetHub D1 controller has a Zigbee wireless communication module based on the TI CC2538 + CC2592 or TI CC2652P1 chip. See module description: |
The module is connected to the UARTAO_B port of the processor (the device is displayed in the system as / | The module is connected to the UARTAO_B port of the processor (the device is displayed in the system as / | ||
Line 368: | Line 372: | ||
To flash the module, a two-row 10-pin connector (2x5) with a pin pitch of 1.27mm (WM DBG) is installed on the board, designed for debugging and flashing the wireless module using the JTAG interface: | To flash the module, a two-row 10-pin connector (2x5) with a pin pitch of 1.27mm (WM DBG) is installed on the board, designed for debugging and flashing the wireless module using the JTAG interface: | ||
- | {{:: | + | {{: |
Connecting the pins of the "WM DBG" connector to the wireless module: | Connecting the pins of the "WM DBG" connector to the wireless module: | ||
Line 440: | Line 444: | ||
=== Module firmware === | === Module firmware === | ||
- | To flash the ZigBee CC2538 module, you can use the python utility [[https:// | + | To flash the ZigBee CC2538 module, you can use the python utility [[https:// |
- | See [[::cc2538_firmware]] or [[::cc2652p_firmware]] for recommended firmware | + | See [[cc2538_firmware]] or [[cc2652p_firmware]] for recommended firmware |
** Procedure for firmware: ** | ** Procedure for firmware: ** | ||
Line 465: | Line 469: | ||
</ | </ | ||
- | ===== Светодиоды | + | ===== LEDs ===== |
- | На лицевой панели контроллера установлено два светодиода: один для индикации наличия напряжения питания, второй | + | There are two LEDs on the front panel of the controller: one to indicate the presence of supply voltage, the second is a custom two-color LED. |
+ | ==== Controlling LEDs from Linux ==== | ||
- | ==== Управление светодиодами из Linux ==== | + | Linux GPIO numbers to which custom LEDs are connected: |
- | Номера | + | ^ LED ^ Processor pin ^ GPIO number in Linux ^ Number in gpiolib ^ Active Low ^ |
+ | | Red | GPIOA_0 | 452 | 26 | 1 (YES) | | ||
+ | | Green | GPIOA_1 | 453 | 27 | 1 (YES) | | ||
- | ^ Светодиод ^ Вывод процессора ^ Номер GPIO в Linux ^ Номер в gpiolib ^ Active Low ^ | + | The LEDs are turned on by a low logic level on the processor pin. |
- | | Красный | + | |
- | | Зеленый | + | |
- | Светодиоды включаются низким логическим уровнем на выводе процессора. | + | An example of initialization and control of the red LED. |
- | Пример инициализации и управления красным светодиодом. | + | GPIO initialization |
- | + | ||
- | Инициализация | + | |
< | < | ||
Line 490: | Line 493: | ||
</ | </ | ||
- | Включение и выключение светодиода | + | Turning the LED on and off (0 - turn off the LED, 1 - turn on the LED): |
< | < | ||
# echo 1 > gpio452/ | # echo 1 > gpio452/ | ||
Line 496: | Line 499: | ||
</ | </ | ||
- | Настройка и управление зеленым светодиодом производится аналогичным образом. | + | The green LED is configured and controlled in the same way. |
+ | ===== Custom Button ===== | ||
- | ===== Пользовательская кнопка ===== | + | There is one user button on the front panel of the controller. |
+ | ==== Reading custom button state from Linux ==== | ||
- | На лицевой панели контроллера установлена одна пользовательская кнопка. | + | GPIO number in Linux to which the button is connected: |
- | ==== Чтение состояния пользовательской кнопки из Linux ==== | + | ^ Button ^ Processor pin ^ GPIO number in Linux ^ Number in gpiolib ^ |
+ | | Custom | GPIOZ_10 | 436 | 10 | | ||
- | Номер | + | GPIO pin and button status: |
- | ^ Кнопка | + | ^ Button state ^ Processor pin state ^ |
- | | Пользовательская | + | | Not pressed |
+ | | Pressed | ||
- | Состояние вывода GPIO и кнопки: | + | An example of initializing and reading the state of a custom button. |
- | ^ Состояние кнопки ^ Состояние вывода процессора ^ | + | GPIO initialization |
- | | Не нажата | + | |
- | | Нажата | + | |
- | + | ||
- | Пример инициализации и чтения состояния пользовательской кнопки. | + | |
- | + | ||
- | Инициализация | + | |
< | < | ||
# cd / | # cd / | ||
Line 525: | Line 526: | ||
</ | </ | ||
- | Чтение состояния кнопки: | + | Reading button state: |
< | < | ||
Line 532: | Line 533: | ||
</ | </ | ||
- | Вывод команды в случае, | + | Command output in case the input is configured as " |
- | + | ===== Real Time Clock (RTC) ===== | |
- | + | ||
- | ===== Часы реального времени | + | |
- | В качестве часов реального времени (RTC) используется микросхема | + | The [[https:// |
- | Для питания | + | To power the RTC, a 3 V lithium battery of CR1220 |
- | === Работа с RTC из Linux === | + | === Working with RTC from Linux === |
- | Чтение информации из RTC: | + | Reading information from RTC: |
< | < | ||
Line 550: | Line 549: | ||
</ | </ | ||
- | или | + | or |
< | < | ||
- | # timedatectl | + | # |
- | Local time: Вт 2020-09-01 15:35:48 MSK | + | Local time: Tue 2020-09-01 15:35:48 MSK |
- | | + | |
- | RTC time: Вт 2020-09-01 12: | + | RTC time: Tue 2020-09-01 12:35:49 |
Time zone: Europe/ | Time zone: Europe/ | ||
- | System clock synchronized: | + | System clock synchronized: |
- | NTP service: active | + | NTP service: active |
RTC in local TZ: no | RTC in local TZ: no | ||
</ | </ | ||
- | ВНИМАНИЕ! На новом контроллере информация о времени и дате может быть еще не сохранена в микросхеме | + | ATTENTION! On a new controller, the time and date information may not yet be stored in the RTC chip. Therefore, when trying to read data from it, an error message will be displayed. To fix this error, you need to write the date and time information to the RTC chip. |
- | Запись в RTC информации о текущих системных дате и времени выполняется командой: | + | Writing information about the current system date and time to the RTC is performed by the command: |
< | < | ||
Line 571: | Line 570: | ||
</ | </ | ||
- | Предварительно системное время должно быть правильно установлено. Контроллер настроен на синхронизацию времени через Интернет по протоколу | + | The system time must be set correctly beforehand. The controller is configured to synchronize time over the Internet using the NTP protocol. If the controller has Internet access and the correct time zone is set, then nothing needs to be configured. |
- | Если контроллер не имеет доступ в Интернет, то установить часовой пояс можно командой: | + | If the controller does not have Internet access, then you can set the time zone with the command: |
< | < | ||
Line 579: | Line 578: | ||
</ | </ | ||
- | (список доступныых часовых поясов можно посмотреть командой | + | (the list of available time zones can be viewed with the " |
< | < | ||
# timedatectl set-time ' | # timedatectl set-time ' | ||
</ | </ | ||
+ | ===== Processor Module Expansion Slot ===== | ||
- | ===== Разъем расширения процессорного модуля ===== | + | As an expansion connector, a pin connector with a pin pitch of 1.27mm, the number of pins is 40. |
- | + | ||
- | В качестве разъема расширения используестя штырьевой разъем с шагом контактов | + | |
- | Сигналы, | + | Signals output to the expansion connector: |
- | * Ethernet (x4 линии | + | * Ethernet (x4 PHY lines); |
- | * Ethernet LED (х2 линии); | + | * Ethernet LED (x2 lines); |
- | * USB (х2 линии); | + | * USB (x2 lines); |
- | * SPI (х4 линии); | + | * SPI (x4 lines); |
- | * I2C (х2 линии); | + | * I2C (x2 lines); |
- | * x2 UART (х4 линий); | + | * x2 UART (x4 lines); |
- | * x11 GPIO; | + | *x11GPIO; |
* CPU RESET; | * CPU RESET; | ||
- | * +5В. | + | * +5V. |
- | === Назначение выводов разъёма расширения | + | === Expansion connector pin assignments |
- | ^ Вывод разъема | + | ^ Connector pin ^ Connector pin assignment |
- | | 1 | +5.0V | | | | + | | 1 | +5.0V | | | |
- | | 2 | +5.0V | | | | + | | 2 | +5.0V | | | |
- | | 3 | GND | | | | + | | 3 | GND | | | |
- | | 4 | GND | | | | + | | 4 | GND | | | |
- | | 5 | ETH_TXN | | | | + | | 5 | ETH_TXN | | | |
- | | 6 | ETH_TXP | | | | + | | 6 | ETH_TXP | | | |
- | | 7 | ETH_RXN | | | | + | | 7 | ETH_RXN | | | |
- | | 8 | ETH_RXP | | | | + | | 8 | ETH_RXP | | | |
- | | 9 | ETH_LED3 | | | | + | | 9 | ETH_LED3 | | | |
- | | 10 | ETH_LED0 | | | | + | | 10 | ETH_LED0 | | | |
- | | 11 | GND | | | | + | | 11 | GND | | | |
| 12 | SPI_MOSI | GPIOX_17/ | | 12 | SPI_MOSI | GPIOX_17/ | ||
| 13 | SPI_CS | GPIOX_16/ | | 13 | SPI_CS | GPIOX_16/ | ||
| 14 | SPI_MISO | GPIOX_18/ | | 14 | SPI_MISO | GPIOX_18/ | ||
| 15 | SPI_CLK | GPIOX_19/ | | 15 | SPI_CLK | GPIOX_19/ | ||
- | | 16 | GND | | | | + | | 16 | GND | | | |
| 17 | I2C_SCK | GPIOAO_10/ | | 17 | I2C_SCK | GPIOAO_10/ | ||
| 18 | I2C_SDA | GPIOAO_11/ | | 18 | I2C_SDA | GPIOAO_11/ | ||
- | | 19 | GND | | | | + | | 19 | GND | | | |
| 20 | UART1_RX | GPIOAO_1/ | | 20 | UART1_RX | GPIOAO_1/ | ||
| 21 | UART1_TX | GPIOAO_0/ | | 21 | UART1_TX | GPIOAO_0/ | ||
| 22 | UART2_TX | GPIOAO_4/ | | 22 | UART2_TX | GPIOAO_4/ | ||
| 23 | UART2_RX | GPIOAO_5/ | | 23 | UART2_RX | GPIOAO_5/ | ||
- | | 24 | GND | | | | + | | 24 | GND | | | |
| 25 | GPIO1 | GPIOA_14 | | | | 25 | GPIO1 | GPIOA_14 | | | ||
| 26 | GPIO2 | GPIOA_16 | | | | 26 | GPIO2 | GPIOA_16 | | | ||
- | | 27 | GND | | | | + | | 27 | GND | | | |
| 28 | GPIO3 | GPIOA_19 | Discrete input 2 | | | 28 | GPIO3 | GPIOA_19 | Discrete input 2 | | ||
| 29 | GPIO4 | GPIOA_18 | Discrete input 3 | | | 29 | GPIO4 | GPIOA_18 | Discrete input 3 | | ||
Line 636: | Line 634: | ||
| 31 | GPIO6 | GPIOA_15 | Zigbee module reset | | | 31 | GPIO6 | GPIOA_15 | Zigbee module reset | | ||
| 32 | GPIO7 | GPIOA_17 | Discrete input 4 | | | 32 | GPIO7 | GPIOA_17 | Discrete input 4 | | ||
- | | 33 | GPIO8 | GPIOA_3 | Relay 2 | | + | | 33 | GPIO8 | GPIOA_3 | relay 2 | |
| 34 | GPIO9 | GPIOA_4 | Relay 1 | | | 34 | GPIO9 | GPIOA_4 | Relay 1 | | ||
| 35 | GPIO10 | GPIOA_10 | Zigbee module boot | | | 35 | GPIO10 | GPIOA_10 | Zigbee module boot | | ||
- | | 36 | GPIO11 | + | | 36 | GPIO11 | GPIOA_2 | Relay 3 | |
- | | 37 | CPU_RESET | | | | + | | 37 | CPU_RESET | | | |
- | | 38 | GND | | | | + | | 38 | GND | | | |
| 39 | USB_DN | USB_DN | USB data - | | | 39 | USB_DN | USB_DN | USB data - | | ||
| 40 | USB_DP | USB_DP | USB data + | | | 40 | USB_DP | USB_DP | USB data + | | ||
- | {{:: | + | {{: |
+ | ===== UART Console ===== | ||
+ | The UART console is routed to a 3-pin male connector located on the controller' | ||
- | ===== UART-консоль ===== | + | The controller cover must be opened to access the connector. To connect to a computer, you can use any USB-UART interface converter: |
- | UART-консоль выведена на 3-х контактный штырьевой разъем, | + | {{: |
- | Для доступа к разъему необходимо открыть крышку контроллера. Для подключения к компьютеру можно использовать любой преобразователь интерфейсов USB-UART: | + | Port configuration: |
+ | * Speed 115200 bps; | ||
+ | * Data length 8 bits; | ||
+ | * Stop bit 1; | ||
+ | * Parity is not used; | ||
+ | * Hardware flow control is not used. | ||
+ | ===== Controller Firmware ===== | ||
- | {{:: | + | === Flashing from Windows using Amlogic Burning Tool === |
- | Конфигурация порта: | + | To flash the software image, you can use the Amlogic Burning Tool program (see [[burning_tool_manual|Instructions for using the Burning Tool]]). |
- | * Скорость 115200 бит/ | + | |
- | * Длина данных 8 бит; | + | |
- | * Стоп-бит 1; | + | |
- | * Контроль четности не используется; | + | |
- | * Аппаратное управление потоком не используется. | + | |
- | ===== Прошивка контроллера ===== | + | The latest JetHome Armbian firmware can be downloaded at http:// |
- | === Прошивка из Windows с помощью Amlogic Burning Tool === | + | **<color # |
- | Для прошивки образа ПО можно использовать программу Amlogic | + | The controller firmware is performed in the following order: |
+ | * Install and prepare the program USB Burning Tool; | ||
+ | * In the Burning Tool, open the menu " | ||
+ | * Power off the controller; | ||
+ | * Press and hold down the " | ||
+ | * While holding down the " | ||
+ | * In the window of the running Burning Tool program, if the bootloader built into the controller is successfully launched and the controller is connected to the computer, the inscription " | ||
+ | * Release the " | ||
+ | * Press the " | ||
+ | * The firmware procedure will begin, which may take a long time; | ||
+ | * Upon completion of the firmware procedure, press the " | ||
+ | * Disconnect the USB cable from the controller. | ||
- | Последнюю прошивку JetHome Armbian можно скачать по адресу http:// | + | === Firmware from Ubuntu Linux === |
- | **<color # | + | For flashing from Linux, you can use the burn-tool utility from the repository [[https:// |
- | Прошивка контроллера выполняется в следующем порядке: | + | Documentation for using the utility [[https://docs.khadas.com/ |
- | * Установите и подготовьте к работе программу USB Burning Tool; | + | |
- | * В программе Burning Tool откройте меню " | + | |
- | * Отключите питание контроллера; | + | |
- | * Нажмите и удерживайте нажатой кнопку " | + | |
- | * Удерживая кнопку " | + | |
- | * В окне запущенной программы Burning Tool при успешном запуске встроенного в контроллер загрузчика и подключении контроллера к компьютеру будет выведена надпись " | + | |
- | * Отпустите кнопку " | + | |
- | * Нажмите кнопку " | + | |
- | * Начнется процедура прошивки, | + | |
- | * По завершению процедуры прошивки нажмите кнопку " | + | |
- | * Отключите кабель USB от контроллера. | + | |
- | === Прошивка из Ubuntu Linux === | + | To install the utility, run the following commands: |
- | + | ||
- | Для прошивки из Linux можно воспользоваться утилитой burn-tool из репозитария [[https:// | + | |
- | + | ||
- | Документация по использованию утилиты [[https:// | + | |
- | + | ||
- | Для установки утилиты выполните команды: | + | |
< | < | ||
$ git clone https:// | $ git clone https:// | ||
Line 699: | Line 694: | ||
</ | </ | ||
- | Для прошивки контроллера переведите его в режим загрузчика способом, описанным выше. Далее выполните команду: | + | To flash the controller, put it into bootloader mode using the method described above. Next, run the command: |
< | < | ||
- | burn-tool -i < | + | burn tool -i < |
</ | </ | ||
- | где | + | where < |
- | Примерный вывод программы: | + | Sample program output: |
< | < | ||
$ burn-tool -i ~/ | $ burn-tool -i ~/ | ||
Line 713: | Line 708: | ||
Unpacking image [OK] | Unpacking image [OK] | ||
Initializing ddr ........[OK] | Initializing ddr ........[OK] | ||
- | Running u-boot ........[OK] | + | Running u-boot........[OK] |
Create partitions [OK] | Create partitions [OK] | ||
Writing device tree [OK] | Writing device tree [OK] | ||
Writing bootloader [OK] | Writing bootloader [OK] | ||
- | Wiping | + | Wiping data partition [OK] |
- | Wiping | + | Wiping cache partition [OK] |
- | Writing | + | Write boot partition [OK] |
Writing rootfs partition [OK] | Writing rootfs partition [OK] | ||
Resetting board [OK] | Resetting board [OK] | ||
Line 726: | Line 721: | ||
</ | </ | ||
- | === Возможные проблемы при прошивке контроллера | + | === Possible problems with controller firmware |
- | + | ||
- | Программа USB Burning Tool не определяет подключенный контроллер. | + | |
- | * Убедитесь, | + | |
- | * Подключайте кабель USB быстро и до упора. Разъем USB устроен так, что при подключении кабеля сначала подключаются контакты питания, | + | |
- | * Используйте кабель USB 2.0 вместо кабеля USB 3.0. | + | |
- | + | ||
- | + | ||
- | ===== Первый запуск JetHome Armbian ===== | + | |
- | + | ||
- | Настройка контроллера при его первом запуске или после его перепрошивки может осуществляться следующими способами: | + | |
- | * По сети Ethernet; | + | |
- | * Через UART-консоль. | + | |
- | Для настройки нонтроллера по сети Ethernet подключите контроллер к локальной сети с настроенным и работающим сервером DHCP. Определите новый IP-адрес контроллера | + | The USB Burning Tool does not detect the connected controller. |
+ | * Make sure the " | ||
+ | * Connect the USB cable quickly and fully. The USB connector is designed so that when you connect the cable, the power contacts are connected first, then the data contacts. In this case, a situation may arise when, when the power is turned on, the boot process has already begun, and the USB data lines have not yet been connected; | ||
+ | * Use a USB 2.0 cable instead of a USB 3.0 cable. | ||
+ | ===== First launch of JetHome Armbian ===== | ||
- | Для подключения через | + | Setting up the controller at its first start or after flashing it can be done in the following ways: |
+ | * Via Ethernet network; | ||
+ | * Via UART console. | ||
- | По-умолчанию пароль для пользователя " | + | To configure the controller over Ethernet, connect the controller to a local area network with a configured and running DHCP server. Determine the new IP address of the controller (the MAC address of the controller is located on the bottom of the controller case). For example, in Mikrotik routers, this can be done in the menu IP -> DHCP Server |
- | При первом запуске будет предложено: | + | To connect via the UART console, connect the controller to the computer using any USB-UART converter |
- | * Задать новый пароль для пользователя root; | + | |
- | * Если контроллер подключен к сети с доступом в сеть Internet, то будет автоматически определен часовой пояс, язык для системы и раскладка клавиатуры; | + | |
- | * Далее будет предложено зарегистрировать в системе нового пользователя и задать для него пароль | + | |
+ | The default password for the " | ||
- | ===== Полезные ссылки | + | On first launch, you will be prompted for: |
+ | * Set a new password for the root user; | ||
+ | * If the controller is connected to a network with access to the Internet, the time zone, language for the system and keyboard layout will be automatically determined; | ||
+ | * Next, you will be prompted to register a new user in the system and set a password for him (it is recommended to do this). User data entry can be skipped by pressing the Enter key when prompted for the user's full name. | ||
+ | ===== Useful Links ===== | ||
* [[hassio-addon-jethub-mqtt-io]] | * [[hassio-addon-jethub-mqtt-io]] | ||
* [[mqtt-io]] | * [[mqtt-io]] |