JetHome wiki

User Tools

Site Tools

You are here: JetHome - оборудование для умного дома » JetHome - smart home equipment » JetHub D1
Trace:
en:jethub_d1  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
en:jethub_d1 [2022/01/22 11:13]
Dmitriy [Разъем расширения процессорного модуля] 		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 of 1.4GHz;+   * Quad-core Amlogic A113X (ARM Cortex-A53) processor with an operating frequency up to 1.4GHz;
    * 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/Bluetooth wireless module (Broadcom BCM43455). Supports IEEE 802.11a/b/g/n/ac WiFi standards as well as Bluetooth 4.2 or;+   * Integrated dual-band (2.4GHz and 5GHz) AMPAK AP6255 WiFi/Bluetooth wireless module (for controllers with 8GB and 16GB eMMC) or AMPAK AP6256 (for controllers with 32GB eMMC). Supports IEEE 802.11a/b/g/n/ac WiFi standards as well as Bluetooth 4.2 or Bluetooth 5.0 (for controllers with 32GB eMMC);
    * 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:
  
-{{::d1_elements.png?400|}}+{{:d1_elements.png?400|}}
  
 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://datasheets.maximintegrated.com/en/ds/DS2483.pdf|DS2483S-100]], connected to the I2C bus of the processor module (in Linux - i2c-0 bus). I2C controller address 1-Wire 0x18. 
- 
-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/I2C_SCK_AO | 
-| 18 | I2C_SDA | GPIOAO_11/I2C_SDA_AO | 
- 
  
 **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:
  
-{{::1wire_connector.png?150|}}+{{:1wire_connector.png?150|}}
  
 ^ 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 is installed on the 1-Wire bus.+ 
 +**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://datasheets.maximintegrated.com/en/ds/DS2483.pdf|DS2483S-100]] is used to implement the 1-Wire bus**, connected to the I2C bus of the processor module (in Linux - i2c-0 bus). I2C controller address 1-Wire 0x18. 
 + 
 +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/I2C_SCK_AO | 
 +| 18 | I2C_SDA | GPIOAO_11/I2C_SDA_AO | 
  
 ===== Linux 1-Wire example ===== ===== Linux 1-Wire example =====
Line 296: Line 300:
 A description of working with 1-wire devices in Linux can be found, for example, [[https://seahu.webnode.cz/_files/200000083-58f3659ef7/How%20to%20use%201-Wire%20bus-5.pdf|here]]. A description of working with 1-wire devices in Linux can be found, for example, [[https://seahu.webnode.cz/_files/200000083-58f3659ef7/How%20to%20use%201-Wire%20bus-5.pdf|here]].
  
-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 is required):+To initialize the 1-Wire DS2482 driver (on the controller of revision up to 1.8), you must execute the following commands (by default, in JetHome Armbian, the 1-Wire bus is configured at system boot and this operation is not required):
  
 <code> <code>
Line 303: Line 307:
 </code> </code>
  
-After that, the 1-wire devices connected to the bus will be available in the /sys/bus/w1/devices/ directory. For instance:+1-wire devices connected to the bus will be available in the /sys/bus/w1/devices/ directory. For instance:
  
 <code> <code>
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: [[::zb3cx_v1]] or [[::zb6c_v1]]+The JetHome JetHub D1 controller has a Zigbee wireless communication module based on the TI CC2538 + CC2592 or TI CC2652P1 chip. See module description: [[zb3cx_v1]] or [[zb6c_v1]]
  
 The module is connected to the UARTAO_B port of the processor (the device is displayed in the system as /dev/ttyAML2, in some cases as /dev/ttyAML1), hardware receive/transmit control (RTS and CTS lines) is not used. It is possible to control the hardware reset of the wireless module (RESET line) and control its boot mode (BOOT line) using the GPIO processor. The module is connected to the UARTAO_B port of the processor (the device is displayed in the system as /dev/ttyAML2, in some cases as /dev/ttyAML1), hardware receive/transmit control (RTS and CTS lines) is not used. It is possible to control the hardware reset of the wireless module (RESET line) and control its boot mode (BOOT line) using the GPIO processor.
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:
  
-{{::jtag_connector_pinout_mini.png?200|}}+{{:jtag_connector_pinout_mini.png?200|}}
  
 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://github.com/JelmerT/cc2538-bsl|cc2538-bsl]]. See manual [[::cc2538_bsl_manual]]+To flash the ZigBee CC2538 module, you can use the python utility [[https://github.com/JelmerT/cc2538-bsl|cc2538-bsl]]. See manual [[cc2538_bsl_manual]]
  
-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 639: Line 643:
 | 40 | USB_DP | USB_DP | USB data + | | 40 | USB_DP | USB_DP | USB data + |
  
-{{::a113x_cpu_module_ext_connector_pinout.png?262|}} +{{:a113x_cpu_module_ext_connector_pinout.png?262|}} 
-=====  UART-консоль =====+===== UART Console =====
  
-UART-консоль выведена на 3-х контактный штырьевой разъем, расположенный на периферийной плате контроллера и отмеченный как "CONSOLE". Назначение контактов разъема также нанесено на плату контроллера.+The UART console is routed to a 3-pin male connector located on the controller's peripheral board and labeled "CONSOLE". The pin assignment of the connector is also printed on the controller board.
  
-Для доступа к разъему необходимо открыть крышку контроллера. Для подключения к компьютеру можно использовать любой преобразователь интерфейсов USB-UART:+The controller cover must be opened to access the connector. To connect to a computer, you can use any USB-UART interface converter:
  
-{{::usb_to_uart_converter.jpg?195|}}+{{:usb_to_uart_converter.jpg?195|}}
  
-Конфигурация порта: +Port configuration: 
-  * Скорость 115200 бит/сек; +  * Speed ​​115200 bps; 
-  * Длина данных 8 бит; +  * Data length 8 bits; 
-  * Стоп-бит 1; +  * Stop bit 1; 
-  * Контроль четности не используется; +  * Parity is not used; 
-  * Аппаратное управление потоком не используется.+  * Hardware flow control is not used. 
 +===== Controller Firmware =====
  
-===== Прошивка контроллера =====+=== Flashing from Windows using Amlogic Burning Tool ===
  
-=== Прошивка из Windows с помощью 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]]).
  
-Для прошивки образа ПО можно использовать программу Amlogic Burning Tool (см. [[burning_tool_manual|Инструкцию по использованию Burning Tool]]).+The latest JetHome Armbian firmware can be downloaded at http://update.jethome.ru/armbian/
  
-Последнюю прошивку JetHome Armbian можно скачать по адресу http://update.jethome.ru/armbian/ +**<color #ed1c24>JetHub D1 controller requires Armbian firmware variant with «j100» suffix</color>**
  
-**<color #ed1c24>Для контроллера JetHub D1 необходим вариант прошивки Armbian с суффиксом "j100"</color>**+The controller firmware is performed in the following order: 
 +  * Install and prepare the program USB Burning Tool; 
 +  * In the Burning Tool, open the menu "File" - "Import image" and select the firmware file (for D1 controllers, the firmware file must have the j100 suffix); 
 +  * Power off the controller; 
 +  * Press and hold down the "BOOT" button on the front panel of the controller (the button is accessed through a hole on the front panel of the controller); 
 +  * While holding down the "BOOT" button, connect the controller with a USB cable to a computer running the USB Burning Tool; 
 +  * 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 "Connect" will be displayed; 
 +  * Release the "BOOT" button; 
 +  * Press the "Start" button in the Burning Tool; 
 +  * The firmware procedure will begin, which may take a long time; 
 +  * Upon completion of the firmware procedure, press the "Stop" button in the program; 
 +  * Disconnect the USB cable from the controller.
  
-Прошивка контроллера выполняется в следующем порядке: +=== Firmware from Ubuntu Linux ===
-  * Установите и подготовьте к работе программу USB Burning Tool; +
-  * В программе Burning Tool откройте меню "File" - "Import image" и выберите файл прошивки (для контроллеров D1 файл прошивки обязательно с суффиксом j100); +
-  * Отключите питание контроллера; +
-  * Нажмите и удерживайте нажатой кнопку "BOOT" на лицевой панели контроллера (доступ к кнопке осуществляется через отверстие на лицевой панели контроллера); +
-  * Удерживая кнопку "BOOT" нажатой, подключите контроллер с помощью кабеля USB к компьютеру с запущенной программой USB Burning Tool; +
-  * В окне запущенной программы Burning Tool при успешном запуске встроенного в контроллер загрузчика и подключении контроллера к компьютеру будет выведена надпись "Connect"; +
-  * Отпустите кнопку "BOOT"; +
-  * Нажмите кнопку "Start" в программе Burning Tool; +
-  * Начнется процедура прошивки, которая может занять продолжительное время; +
-  * По завершению процедуры прошивки нажмите кнопку "Stop" в программе; +
-  * Отключите кабель USB от контроллера.+
  
-=== Прошивка из Ubuntu Linux ===+For flashing from Linux, you can use the burn-tool utility from the repository [[https://github.com/khadas/utils]]
  
-Для прошивки из Linux можно воспользоваться утилитой burn-tool из репозитария [[https://github.com/khadas/utils]]+Documentation for using the utility [[https://docs.khadas.com/vim1/UpgradeViaUSBCable.html#Upgrade-On-Ubuntu]]
  
-Документация по использованию утилиты [[https://docs.khadas.com/vim1/UpgradeViaUSBCable.html#Upgrade-On-Ubuntu]] +To install the utility, run the following commands:
- +
-Для установки утилиты выполните команды:+
 <code> <code>
 $ git clone https://github.com/khadas/utils khadas-utils $ git clone https://github.com/khadas/utils khadas-utils
Line 691: Line 694:
 </code> </code>
  
-Для прошивки контроллера переведите его в режим загрузчика способом, описанным выше. Далее выполните команду:+To flash the controller, put it into bootloader mode using the method described above. Next, run the command:
 <code> <code>
-burn-tool -i <FIRMWARE_IMAGE_FILE>+burn tool -i <FIRMWARE_IMAGE_FILE>
 </code> </code>
  
-где <FIRMWARE_IMAGE_FILE> - файл прошивки+where <FIRMWARE_IMAGE_FILE> is the firmware file
  
-Примерный вывод программы:+Sample program output:
 <code> <code>
 $ burn-tool -i ~/firmware/D1/JetHome_1.0.14_Armbian_20.08_Arm-64_focal_current_5.7.16_j100.img $ burn-tool -i ~/firmware/D1/JetHome_1.0.14_Armbian_20.08_Arm-64_focal_current_5.7.16_j100.img
Line 705: 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  data partition [OK] +Wiping data partition [OK] 
-Wiping  cache partition [OK] +Wiping cache partition [OK] 
-Writing boot partition [OK]+Write boot partition [OK]
 Writing rootfs partition [OK] Writing rootfs partition [OK]
 Resetting board [OK] Resetting board [OK]
Line 718: Line 721:
 </code> </code>
  
-=== Возможные проблемы при прошивке контроллера === +=== Possible problems with controller firmware ===
- +
-Программа USB Burning Tool не определяет подключенный контроллер. +
-  * Убедитесь, что в момент подключения кабеля USB кнопка "BOOT" нажата. Не рекомендуется использовать для этого острые предметы (иголки и т.д.), используйте предметы с тупым концом (скрепки и т.д.); +
-  * Подключайте кабель USB быстро и до упора. Разъем USB устроен так, что при подключении кабеля сначала подключаются контакты питания, затем контакты для передачи данных. При этом может возникать ситуация когда при подаче питания процесс загрузки уже начался, а линии передачи данных USB еще не были подключены; +
-  * Используйте кабель USB 2.0 вместо кабеля USB 3.0. +
- +
- +
-===== Первый запуск JetHome Armbian ===== +
- +
-Настройка контроллера при его первом запуске или после его перепрошивки может осуществляться следующими способами: +
-  * По сети Ethernet; +
-  * Через UART-консоль.+
  
-Для настройки нонтроллера по сети Ethernet подключите контроллер к локальной сети с настроенным и работающим сервером DHCP. Определите новый IP-адрес контроллера (MAC-адрес контроллера указан на нижней части корпуса контроллера). Например, в маршрутизаторах Mikrotik это можно сделать в меню IP -> DHCP Server -> Leases. Далее подключитесь к контроллеру с помощью любого ssh-клиента, например, Putty под ОС Windows.+The USB Burning Tool does not detect the connected controller. 
 +  * Make sure the "BOOT" button is pressed when connecting the USB cable. It is not recommended to use sharp objects for this (needles, etc.), use objects with a blunt end (paper clips, etc.); 
 +  * 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 =====
  
-Для подключения через UART-консоль подключите контроллер к компьютеру с помощью любого преобразователя USB-UART (см. п. "UART консоль").+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.
  
-По-умолчанию пароль для пользователя "root" - "1234".+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 -> Leases. Next, connect to the controller using any ssh client, for example, Putty under Windows OS.
  
-При первом запуске будет предложено: +To connect via the UART console, connect the controller to the computer using any USB-UART converter (see p. "UART console").
-  * Задать новый пароль для пользователя root; +
-  * Если контроллер подключен к сети с доступом в сеть Internet, то будет автоматически определен часовой пояс, язык для системы и раскладка клавиатуры; +
-  * Далее будет предложено зарегистрировать в системе нового пользователя и задать для него пароль (рекомендуется это сделать). Ввод данных о пользователе можно пропустить, нажав клавишу Enter на запрос о полном имени пользователя.+
  
 +The default password for the "root" user is "1234".
  
-===== Полезные ссылки =====+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]]
en/jethub_d1.1642839205.txt.gz · Last modified: 2022/01/22 11:13 by Dmitriy

Page Tools