Release notes - Armbian - Version 20.02
I've been using the 1MB D1 Mini lite clones with WLED..... it's been a bit of a challenge to get them to flash properly. Especially when compling my own build of the firmware
esphomeflasher defaults to using the qio method. DOUT seems to work..
esptool --port /dev/ttyUSB0 write_flash --flash_mode dout --flash_size 1MB 0x000 esp01_1m/firmware.bin
#!/bin/bash | |
cd /sys/fs/cgroup/memory | |
while [[ /bin/true ]];do | |
date | |
for item in $(ls memory.*usage*); do echo $item $(echo echo $(echo $(cat $item) /1024/1024 |bc))M;done | |
echo "container count $(docker ps -a|wc -l)" | |
echo | |
sleep 10s | |
done |
This will eliminate bridge networking, and move DHCP explicity to the WAN interface (port next to usb3) on the espressobin. Approach can be applied to the lan interfaces as well
caveat: TODO: need to double check mac addresses are probaly assigned to the interfaces and not just duplicating eth0 This involves setting MACs correctly in u-boot environment
systemctl disable NetworkManager
I gave up. vyos docker + maclan looks much more managable
- checkout vyos build
- checkout all submodules
## do this before hand | |
## vyatta will try to eval show under the wrong circumstances | |
show dhcp leases > /tmp/leases.txt | |
### dump below in a file, execute with bash | |
MY_INTERNAL_DOMAIN=your_internal_domain.local | |
IFS=$'\n' | |
for line in $(printf "$(cat /tmp/leases.txt|tail -n +3|awk '{print $6, $1, $2}')") | |
do |
I haven't tried mainline kernel. just 4.4.x. Seems to work with Xenial and Jessie
make note of the MAC addresseses on the switch ports.. the 2 close together will be LAN1 and LAN2 in the OS. eth1addr and ethaddr2 in u-boot. The 3rd address will be for WAN in the OS aka ethaddr in u-boot
the WAN port is in-line with the SDcard slot on the board.... use that as your primary NIC for now.
Use my branch, or hopefully igor's once my merge request has been added. Standard armbian building expertise applies.
Use my fork of the Wiring-Pi Python library which checks out the WiringOP fork of the WiringPi library as a submodule to build everything. yes that's a little confusing
The WiringPI library is the original C library that RaspGPIO is somewhat based on. WiringPi was built to replicate arduino GPIO functions
In Raspberry Pi Land there are 2 normal python paths for GPIO. One is Raspi.GPIO and the other is WiringPI