Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| ru:toh:tp-link:tl-wr1043nd [2015/02/25 20:21] – [Failsafe mode] gw3rty | ru:toh:tp-link:tl-wr1043nd [2018/06/11 17:35] – link fixed tmomas | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== TP-Link TL-WR1043ND ====== | ||
| + | Одно из недорогих устройств, | ||
| + | ===== Поддерживаемые версии ===== | ||
| + | ^ Версия/ | ||
| + | | v1.1 | - | - | | Backfire 10.03 | Как в WR941ND.| | ||
| + | | v1.4 | - | - | | Backfire 10.03 | Same v1 board as v1.1| | ||
| + | | v1.5 | - | - | | Backfire 10.03 | Same v1 board as v1.1| | ||
| + | | v1.6 | - | - | | Backfire 10.03 | Аналогично | | ||
| + | | v1.7 | - | - | | Backfire 10.03.1-rc4 | Аналогично | | ||
| + | | v1.8 | - | - | | Backfire 10.03.1-rc6 or [[http:// | ||
| + | | (DE)v1.0 | - | - | | Backfire 10.03.1-rc4 | Аналогично, | ||
| + | | v2.1 | - | 2013-06-18 | | Barrier Breaker 14.07 | | | ||
| + | |||
| + | ^ HW V1.x ^ HW V2.x ^ | ||
| + | | {{media: | ||
| + | |||
| + | ===== Основные технические характеристики ===== | ||
| + | ^ HW Версия ^ Процессор ^ Память ^ Флеш ^ Network ^ Gigabit ^ USB ^ Serial ^ JTag ^ | ||
| + | | 1.x | Atheros AR9132@400MHz | ||
| + | | 2.x | Qualcomm Atheros QCA9558@720MHz | 64MB | 8MB | 4x1 | Да | Да | Да | Нет | | ||
| + | |||
| + | See paragraphs [[toh/ | ||
| + | |||
| + | ===== Установка ===== | ||
| + | - [[: | ||
| + | - [[docs: | ||
| + | * Самый // | ||
| + | * Wi-Fi работает сразу после установки прошивки. | ||
| + | * Самый // | ||
| + | * Внимание! Этот образ прошивки **не имеет** модулей поддержки Wi-Fi. Вы можете легко установить недостающие пакеты на раздел jffs2 позже: '' | ||
| + | * Вы всегда можете [[docs: | ||
| + | |||
| + | It appears that in order to use the " | ||
| + | |||
| + | |||
| + | ==== Flash Layout ==== | ||
| + | Для лучшего понимания, | ||
| + | |||
| + | Теперь рассмотрим краткую характеристику разделов флеш-памяти конкретного устройства: | ||
| + | |||
| + | ^ | ||
| + | ^ Layer0 | ||
| + | ^ Layer1 | ||
| + | ^ Size in KiB | 128KiB | ||
| + | ^ Name | ||
| + | ^ mountpoint | ||
| + | ^ filesystem | ||
| + | ^ | ||
| + | ^ Offset | ||
| + | ^ x64KiB Blocks | ||
| + | ^ | ||
| + | ^ Layer0 | ||
| + | ^ Layer1 | ||
| + | ^ Layer2 | ||
| + | ^ <color magenta> | ||
| + | ^ filesystem | ||
| + | ^ Layer3 | ||
| + | ^ Size in KiB | 128KiB | ||
| + | ^ Name | ||
| + | ^ <color magenta> | ||
| + | ^ filesystem | ||
| + | |||
| + | ART = Atheros Radio Test - раздел, | ||
| + | |||
| + | ==== Простая установка OEM-способом ==== | ||
| + | |||
| + | Установите openwrt-ar71xx-tl-wr1043ndv1-squashfs-factory.bin используя " | ||
| + | |||
| + | ==== Массовая перепрошивка OEM-способом ==== | ||
| + | |||
| + | Перепрошивать десятки или сотни устройств вручную через веб-интерфейс непрактично. В этом случае можно использовать следующий скрипт: | ||
| + | |||
| + | < | ||
| + | #!/bin/bash | ||
| + | |||
| + | # Файл с образом прошивки -- первый и единственный аргумент командной строки. | ||
| + | # | ||
| + | # Второй вызов curl возвращается с ошибкой таймаут, | ||
| + | # После завершения работы скрипта можно отключить Ethernet-кабель | ||
| + | # и начать перепрошивку следующего устройства, | ||
| + | # включенным ПИТАНИЕ, | ||
| + | # успешной перепрошивки раутер сбрасывается автоматически (все светодиоды | ||
| + | # одновременно высвечиваются один раз примерно на полсекунды). | ||
| + | |||
| + | curl \ | ||
| + | --user admin:admin \ | ||
| + | --user-agent ' | ||
| + | --referer ' | ||
| + | --form " | ||
| + | http:// | ||
| + | |||
| + | sleep 1 | ||
| + | |||
| + | curl \ | ||
| + | --max-time 2 \ | ||
| + | --user admin:admin \ | ||
| + | --user-agent ' | ||
| + | --referer ' | ||
| + | http:// | ||
| + | </ | ||
| + | |||
| + | ==== OEM installation using the TFTP and RS232 method ==== | ||
| + | |||
| + | If you want to upgrade using TFTP you follow these steps (as an alternative to the above install process). | ||
| + | |||
| + | Quick howto recover from bad flash. ([[.: | ||
| + | |||
| + | Requirements: | ||
| + | * terminal program (e.g. minicom) set to **115200 8N1**, no flow control | ||
| + | * file named // | ||
| + | * tftpd server with an address 192.168.0.5 (configurable with '' | ||
| + | |||
| + | The simplest tftpd server to use is dnsmasq. Install and run with '' | ||
| + | |||
| + | Commands: | ||
| + | |||
| + | After you see '' | ||
| + | |||
| + | < | ||
| + | erase 0xbf020000 +7c0000 # 7c0000: size of the firmware (be aware that you may have a different size thus bricking your router) | ||
| + | tftpboot 0x81000000 code.bin | ||
| + | cp.b 0x81000000 0xbf020000 0x7c0000 | ||
| + | bootm 0xbf020000 | ||
| + | </ | ||
| + | |||
| + | ==== OEM installation using the Kermit and RS232 method ==== | ||
| + | |||
| + | If you do not want to bother with running a tftpd server on your computer, especially considering the security concerns, you can also use a Kermit client to transfer the new image. It may take forever and a half (15-20min) to copy, but it's easier and more secure than running a tftpd server. These instructions assume you're using a Linux system, but they will give you all you need to do the same on a Windows box. | ||
| + | |||
| + | Requirements: | ||
| + | * terminal program (e.g. minicom) set to **115200 8N1**, no flow control | ||
| + | * file named // | ||
| + | * Kermit client (these instructions will involve using C-Kermit under Linux) | ||
| + | |||
| + | In your terminal program you type: | ||
| + | |||
| + | < | ||
| + | erase 0xbf020000 +7c0000 # 7c0000: size of the firmware (be aware that you may have a different size thus bricking your router) | ||
| + | loadb 0x81000000 | ||
| + | </ | ||
| + | |||
| + | |||
| + | Hint: After you see Autobooting in 1 seconds type tpl and hit enter to get into command promt. | ||
| + | |||
| + | |||
| + | Fire up C-Kermit and run the following commands (or configure your Kermit client to these parameters): | ||
| + | < | ||
| + | set line / | ||
| + | set speed 115200 | ||
| + | set carrier-watch off | ||
| + | set handshake none | ||
| + | set flow-control none | ||
| + | robust | ||
| + | set file type bin | ||
| + | set file name lit | ||
| + | set rec pack 1000 | ||
| + | set send pack 1000 | ||
| + | set window 5 | ||
| + | send code.bin # Make sure you include a proper path to the file. That's why I just kept it in /home/$user | ||
| + | </ | ||
| + | |||
| + | After the 15-20min file transfer, the new firmware should be on your router and you can continue in terminal: | ||
| + | < | ||
| + | cp.b 0x81000000 0xbf020000 0x7c0000 | ||
| + | bootm 0xbf020000 | ||
| + | </ | ||
| + | |||
| + | |||
| + | ==== Обновление OpenWrt ==== | ||
| + | -> [[docs: | ||
| + | |||
| + | |||
| + | ==== Назад, к родной прошивке ==== | ||
| + | -> [[docs: | ||
| + | |||
| + | {{page> | ||
| + | |||
| + | In case of the WR1043ND there is a catch: You download the stock firmware from the OEM: http:// | ||
| + | |||
| + | * in case the file name of this firmware file does not contain the word **//" | ||
| + | * in case the file name of this firmware file does contain the word **//" | ||
| + | |||
| + | An example of an image file with the word " | ||
| + | |||
| + | Cut the first 0x20200 (that is 131,584 = 257*512) Bytes from original firmware: | ||
| + | < | ||
| + | dd if=orig.bin of=tplink.bin skip=257 bs=512 | ||
| + | </ | ||
| + | |||
| + | This has been confirmed by [[https:// | ||
| + | |||
| + | |||
| + | ===== Основные настройки ===== | ||
| + | После прошивки, | ||
| + | Сконфигурируйте ваше Интернет-соединение, | ||
| + | |||
| + | ===== Специальные настройки ===== | ||
| + | ==== Интерфейс ==== | ||
| + | Сетевые настройки по-умолчанию: | ||
| + | ^ Имя интерфейса ^ Описание ^ Настройки по-умолчанию ^ | ||
| + | | br-lan | LAN & WiFi | 192.168.1.1/ | ||
| + | | eth0 | LAN ports (1 to 4) + WAN | Нет | | ||
| + | | wlan0 | WiFi | Отключен | | ||
| + | |||
| + | |||
| + | ==== Порты коммутатора для VLAN (hw ver 1.x) ==== | ||
| + | |||
| + | Порты коммутатора с 1 по 4 подключены к внешним портам LAN(1-4), как они помечены на корпусе, | ||
| + | 5 порт подключен внутри к самому роутеру. | ||
| + | Это иллюстрирует таблица ниже: | ||
| + | |||
| + | ^ Порт ^ Порт коммутатора ^ | ||
| + | | Internet (WAN) | 0 | | ||
| + | | LAN 1 | 1 | | ||
| + | | LAN 2 | 2 | | ||
| + | | LAN 3 | 3 | | ||
| + | | LAN 4 | 4 | | ||
| + | | [[wp> | ||
| + | |||
| + | ==== Порты коммутатора для VLAN (hw ver 2.x) ==== | ||
| + | В апп. версии 2, у процессора два независимых порта, каждый из которых может быть использован для создания trunk, или access-интерфейса. | ||
| + | Соответствие внутренних портов внешним разъёмам и портам процессора показано на рисунке ниже: | ||
| + | |||
| + | {{: | ||
| + | |||
| + | Некоторые нюансы, | ||
| + | |||
| + | ==== Безопасный режим ==== | ||
| + | -> [[docs: | ||
| + | |||
| + | Включите ваш маршрутизатор. После того, как индикатор ' | ||
| + | |||
| + | ==== Восстановление через последовательную консоль ==== | ||
| + | |||
| + | Вы увидите что-то подобное: | ||
| + | |||
| + | < | ||
| + | No valid address in Flash. Using fixed address | ||
| + | : cfg1 0xf cfg2 0x7114 | ||
| + | eth0 up | ||
| + | eth0 | ||
| + | Autobooting in 1 seconds | ||
| + | </ | ||
| + | |||
| + | Введите | ||
| + | < | ||
| + | tpl | ||
| + | </ | ||
| + | в течении 1 секунды. Затем используйте этот метод - [[#OEM installation using the TFTP and RS232 method]] | ||
| + | |||
| + | |||
| + | ===== Аппаратная часть ===== | ||
| + | ==== Общая информация ==== | ||
| + | | **[[wp> | ||
| + | | **Vendor: | ||
| + | | **[[docs: | ||
| + | | **[[docs: | ||
| + | | **[[docs: | ||
| + | | **Flash-Chip: | ||
| + | | **Flash size: | ||
| + | | **RAM: | ||
| + | | **Wireless: | ||
| + | | **Ethernet: | ||
| + | | **Internet: | ||
| + | | **USB: | ||
| + | | **[[docs: | ||
| + | | **[[docs: | ||
| + | |||
| + | |||
| + | Микросхема Realtek [[http:// | ||
| + | |||
| + | ==== Производительность ==== | ||
| + | See -> [[docs: | ||
| + | |||
| + | ==== Потребляемая мощность ==== | ||
| + | |||
| + | Измерения дешевым ваттметром показали, | ||
| + | |||
| + | ==== Фотографии ==== | ||
| + | |||
| + | {{media: | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | ==== Разборка и сборка корпуса (v1) ==== | ||
| + | |||
| + | Обратите внимание: | ||
| + | |||
| + | * Верхняя часть корпуса (белая, | ||
| + | * Нижняя часть (белая, | ||
| + | * Фронтальная панель (прозрачная, | ||
| + | * Внешняя рамка (черная, | ||
| + | |||
| + | Устройство крепится с помощью двух винтов (винты находятся под резиновыми ножками). | ||
| + | Верх и низ корпуса соединяются с помощью двух защелок и системы направляющих, | ||
| + | |||
| + | - Снимите все антенны. | ||
| + | - Отклейте резиновые ножки сзади роутера, | ||
| + | - Открутите все гайки в разьеме антенны и аккуратно протолкните разьем внутрь корпуса. Не применяйте черезмерной силы, если у вас не получилось, | ||
| + | - Push one of the bottom screws back into place to lift the top cover, and keep it that way using a finger. | ||
| + | - With the top slightly open, push the bottom cover away. Use a screwdriver if you can't reach it with your fingers. | ||
| + | - If you have unscrewed the antenna connectors, now you can remove outer frame. Otherwise just carefully slide it out of the way: this will expose the clips that keep the top and bottom covers together. | ||
| + | - With a flathead screwdriver or similar tool, gently pry the two front clips apart. Each clip has two latches and is located near the corners, next to the black front. Put your screwdriver behind the latches and push it towards | ||
| + | - Now the top cover can slide out the vertical guides on the black front. | ||
| + | - The black front also has three plastic hooks that go into matching holes in the bottom cover. To remove it, pull the front away and then push it down. | ||
| + | |||
| + | Фото вы можете найти [[http:// | ||
| + | |||
| + | === Сборка корпуса === | ||
| + | |||
| + | - Place the board on the bottom cover, so that the two plastic pins at the front keep it in place. | ||
| + | - If you undid the antenna connectors, put them back in and tighten the nuts. | ||
| + | - Place the outer frame behind the board and make sure it sits flush to the connectors. | ||
| + | - Insert the hooks of the front into the holes in the bottom cover, don't push it in yet. | ||
| + | - Make the top cover slide into the vertical guides on the front. Don't push it down yet. | ||
| + | - Push the front towards the back so the hooks are engaged, then push down the top cover. | ||
| + | - Fasten the screws and re-apply the rubber feet. | ||
| + | |||
| + | ==== Serial ==== | ||
| + | -> [[docs: | ||
| + | How to connect to Serial Port: | ||
| + | |||
| + | Solder a header as shown in the picture or wires with a connector directly. The device uses TTL @ 3.3V and not a standard RS-232 Serial that operates between 3 and 15V, so do not try to connect it to a common serial adapter: you will certainly fry the serial circuit or even the whole board. There are plenty of USB to TTL and RS-232 to TTL available on the market, just be careful with the voltage: the standard is 5V and it may also damage your board. Look for the ones with 3.3V or with both voltages and a way to switch between them. | ||
| + | |||
| + | Don’t forget that the **TX pin** of the serial port must linked to the **RX pin** of the router and the RX to TX! | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ==== JTAG ==== | ||
| + | -> [[docs: | ||
| + | |||
| + | {{: | ||
| + | |||
| + | JTAG Line: | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | |||
| + | Software: | ||
| + | |||
| + | Download EJTAG Debrick Utility 3.0.1 | ||
| + | |||
| + | Backup: | ||
| + | |||
| + | Backup wholeflash: | ||
| + | |||
| + | < | ||
| + | tjtag3.exe -backup: | ||
| + | </ | ||
| + | |||
| + | Backup UBoot: | ||
| + | |||
| + | < | ||
| + | tjtag3.exe -backup: | ||
| + | </ | ||
| + | |||
| + | Резервная копия Прошивки(firmware): | ||
| + | |||
| + | < | ||
| + | tjtag3.exe -backup: | ||
| + | </ | ||
| + | |||
| + | | {{: | ||
| + | |||
| + | ==== GPIOs ==== | ||
| + | -> [[docs: | ||
| + | The AR913x platform provides 22 GPIOs. Some of them are used by the router for status LEDs, buttons and to communicate with the RTL8366RB. The table below shows the results of some investigation: | ||
| + | |||
| + | ^ ^ | ||
| + | ^ GPIO ^ Common Name ^ PCB Name ^ gpioX/ | ||
| + | | 0 | | ||
| + | | 1 | USB | D18=D9 | ||
| + | | 2 | SYS | D19=D8 | ||
| + | | 3 | RESET | SW6 | ||
| + | | 4 | | ||
| + | | 5 | QSS | D31=D10 | ||
| + | | 6 | | ||
| + | | 7 | QSS-Button | ||
| + | | 8 | Setting data direction to output and value to 0 causes hard reset of the SoC | ||
| + | | 9 | WLAN | ||
| + | | 10 | P1-Tx | | | ||
| + | | 11 | | ||
| + | | 12 | | ||
| + | | 13 | P1-Rx | | 3.3V | 0V | 0 | 0 | 1 | | ||
| + | | 14 | | ||
| + | | 15 | | ||
| + | | 16 | | ||
| + | | 17 | | ||
| + | | 18 | Data line of the RTL8366RB | ||
| + | | 19 | Clock line of the RTL8366RB | ||
| + | | 20 | | ||
| + | | 21 | | ||
| + | |||
| + | To make the GPIOs available via sysfs, the required ones have to be exported to userspace, as it is explained on a page of the [[http:// | ||
| + | |||
| + | ==== Светодиоды ==== | ||
| + | Пример конфигурации светодиодов смотрите в секции LED в [[docs: | ||
| + | |||
| + | | ||
| + | |||
| + | ^ Имя ^ Надпись ^ Внутреннее имя ^ Trigger ^ | ||
| + | | Power | PWR | tl-wr1043nd: | ||
| + | | System | SYS | tl-wr1043nd: | ||
| + | | Wireless LAN | WLAN | tl-wr1043nd: | ||
| + | | LAN Port 4 | 4 | unknown | N/A | | ||
| + | | LAN Port 3 | 3 | unknown | N/A | | ||
| + | | LAN Port 2 | 2 | unknown | N/A | | ||
| + | | LAN Port 1 | 1 | unknown | N/A | | ||
| + | | Wide Area Network | WAN | tl-wr1043nd: | ||
| + | | Universal Serial Bus | USB | tl-wr1043nd: | ||
| + | | Quick Security Setup | QSS | tl-wr1043nd: | ||
| + | |||
| + | Модуль управления светодиодами // | ||
| + | |||
| + | ==== Кнопки ==== | ||
| + | см. [[docs: | ||
| + | |||
| + | У TP-Link TL-WR1043ND V1.х есть две кнопки: | ||
| + | ^ Кнопка ^ Событие ^ | ||
| + | | Reset | reset | | ||
| + | | Quick Security Setup | QSS | | ||
| + | |||
| + | У TP-Link TL-WR1043ND V2.x есть две кнопки: | ||
| + | ^ Кнопка ^ Событие ^ | ||
| + | | Wireless On/Off | ? | | ||
| + | | WPS/Reset | ? | | ||
| + | |||
| + | В апп. версии 1.х, кнопка ' | ||
| + | |||
| + | В апп. версии 2.х, обе кнопки расположены сзади, возле портов, | ||
| + | ===== Восстановление ===== | ||
| + | -> [[docs: | ||
| + | |||
| + | **Примечание: | ||
| + | - Отпаяйте Spansion SPI-Flash ([[http:// | ||
| + | - Найдите способ подключить | ||
| + | - Прошейте bootloader на флеш-память. Я взял bootloader с аналогичного wr1043nd. | ||
| + | - Припаяйте чип назад на роутер, | ||
| + | - The router shall now be unbricked. | ||
| + | |||
| + | ===== Bootloader Mods ===== | ||
| + | - you could read about [[docs: | ||
| + | - the uboot version you find on the 1043 is a fork of mainline U-Boot version 1.1.4 from 2005-12-17 [[ftp:// | ||
| + | - also see [[ftp:// | ||
| + | - you may be able to cross compile the code with the OpenWrt [[wp> | ||
| + | - :!: **'' | ||
| + | |||
| + | ==== Making bootloader partition writable ==== | ||
| + | |||
| + | Look at target/ | ||
| + | <code c> | ||
| + | static struct mtd_partition tl_wr1043nd_partitions[] = { | ||
| + | { | ||
| + | .name = " | ||
| + | .offset | ||
| + | .size = 0x020000, | ||
| + | .mask_flags = MTD_WRITEABLE, | ||
| + | } , { | ||
| + | .name = " | ||
| + | .offset | ||
| + | .size = 0x140000, | ||
| + | } , { | ||
| + | .name = " | ||
| + | .offset | ||
| + | .size = 0x690000, | ||
| + | } , { | ||
| + | .name = " | ||
| + | .offset | ||
| + | .size = 0x010000, | ||
| + | .mask_flags = MTD_WRITEABLE, | ||
| + | } , { | ||
| + | .name = " | ||
| + | .offset | ||
| + | .size = 0x7d0000, | ||
| + | } | ||
| + | }; | ||
| + | </ | ||
| + | Remove the line | ||
| + | <code c> | ||
| + | .mask_flags = MTD_WRITEABLE, | ||
| + | </ | ||
| + | for the partition named " | ||
| + | |||
| + | ==== Смена MAC адреса ==== | ||
| + | |||
| + | * Сделайте дамп uboot раздела этой командой <code bash>cat /dev/mtd0 > / | ||
| + | * На смещении 0x1FC00 Обычно находится MAC-адрес. Вы можете изменить его с помощью любого hex-редактора. Я использую [[http:// | ||
| + | * После изменения MAC-адреса и убедившись, | ||
| + | |||
| + | ===== Аппаратный моддинг ===== | ||
| + | |||
| + | | {{: | ||
| + | |||
| + | ==== Мод 64MB памяти ==== | ||
| + | Устройство использует DDR1 16Mbit x 16bit (16Mibit*16=256 mebibit. 256 mebibit/ | ||
| + | |||
| + | Проверенные микросхемы памяти: | ||
| + | * Hynix HY5DU121622DTP-D43 (From Mustang DDR-SODIMM 512 MB) | ||
| + | * Infineon HYB25D512160BE (From Infineon DDR-SODIMM 512 MB) | ||
| + | |||
| + | **Также могут работать: | ||
| + | |||
| + | '' | ||
| + | |||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | '' | ||
| + | |||
| + | {{: | ||
| + | |||
| + | **Убедитесь, | ||
| + | < | ||
| + | 1.nvram set sdram_init=0x0013 | ||
| + | 2.nvram commit | ||
| + | 3.reboot | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | root@OpenWrt: | ||
| + | total used free shared buffers | ||
| + | Mem: 62104 17472 44632 0 1392 | ||
| + | Total: 62104 17472 44632 | ||
| + | </ | ||
| + | |||
| + | ==== Мод I²C GPIO ==== | ||
| + | |||
| + | An I²C-bus can easily be added using the GPIO-lines of the AR913x-SoC. So far, the only usable ones which have been confirmed to work are GPIO 5 (the QSS-LED, easily solderable at D10,left pin with ' | ||
| + | {{ : | ||
| + | Unfortunately the precompiled packages don't seem to work properly, so building from sources is most likely necessary. Therefore, make sure the apropriate part of your OpenWRT-config file looks like that: | ||
| + | |||
| + | < | ||
| + | # | ||
| + | # I2C support | ||
| + | # | ||
| + | CONFIG_PACKAGE_kmod-i2c-core=y | ||
| + | CONFIG_PACKAGE_kmod-i2c-algo-bit=y | ||
| + | # CONFIG_PACKAGE_kmod-i2c-algo-pca is not set | ||
| + | # CONFIG_PACKAGE_kmod-i2c-algo-pcf is not set | ||
| + | CONFIG_PACKAGE_kmod-i2c-gpio=y | ||
| + | CONFIG_PACKAGE_kmod-i2c-gpio-custom=y | ||
| + | </ | ||
| + | |||
| + | Besides that, check in the kernel-config, | ||
| + | < | ||
| + | CONFIG_I2C_CHARDEV=m | ||
| + | </ | ||
| + | To load the kernel module, do a: | ||
| + | < | ||
| + | insmod i2c-gpio-custom bus0=0,5,20 | ||
| + | </ | ||
| + | In many cases, GPIO 5 will already be occupied by the leds-gpio kernel module - causing the above command to fail. In case you don't need the leds at all, you can just unload the leds-gpio kernel module, remove the package or disable it in the OpenWRT-configuration. As an alternative, | ||
| + | |||
| + | ==== Мод I²C Tiny-USB ==== | ||
| + | |||
| + | Though not really a modification of the internal hardware, the [[docs: | ||
| + | |||
| + | ===== Теги ===== | ||
| + | {{tag> | ||