My MS Windows ownCloud clients were complaining about OPI server being too old, and recently fully refused to synchronize. This pushed me towards OPI-to-Kinguard upgrade. I tried to do it yesterday:
- backup of OPI was made on USB memory
- new SD card with Kinguard image was prepared
- Kinguard SD card was booted, but the system failed to install and operate
The behavior of fresh new Kinguard was a bit strange. LEDs on the device were flashing for 3-4 minutes, then ... the device powered off itself. Further reboots ended the same way.
I managed to solder serial console connector (see below for tech.details) and connected to it. For reading only, because OPI seems to have 3.3V serial, and my USB-RS232 converter is 5V.
But thanks to the serial console I could observe the boot sequence:
The beginning was promising, although a bit buggy (I doubt these errors had any influence on the ultimate failure of the upgrade):
Code: Select all
U-Boot SPL 2018.01 (Mar 07 2018 - 11:50:50)
Trying to boot from MMC2
*** Warning - bad CRC, using default environment
reading u-boot.img
reading u-boot.img
U-Boot 2018.01 (Mar 07 2018 - 11:50:50 +0100)
CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - bad CRC, using default environment
Code: Select all
Starting logging: OK
Initializing random number generator... done.
Starting haveged: OK
Starting network:
[ 2.535997] net eth0: initializing cpsw version 1.12 (0)
[ 2.619182] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=-1)
[ 2.638277] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc: started, v1.27.2
udhcpc: sending discover
[ 4.724319] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 4.743608] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 5.625825] random: crng init done
udhcpc: sending discover
udhcpc: sending select for 192.168.13.138
udhcpc: lease of 192.168.13.138 obtained, lease time 864000
Starting dropbear sshd: OK
However, then a series of unusual messages appeared, every after approx. 10 seconds. Once they were done, the device ... started to power off automatically. See the log:
Code: Select all
[ 26.019885] ttyS ttyS0: tty_port_close_start: tty->count = 1 port count = 2
[ 36.058090] ttyS ttyS0: tty_port_close_start: tty->count = 1 port count = 2
[...]
[ 246.936624] ttyS ttyS0: tty_port_close_start: tty->count = 1 port count = 2
[ 256.960576] ttyS ttyS0: tty_port_close_start: tty->count = 1 port count = 2
Usage: /etc/init.d/S60keepinstall {start}
Stopping dropbear sshd: OK
Stopping network: OK
Stopping haveged: stopped /usr/sbin/haveged (pid 103)
OK
Saving random seed... done.
Stopping logging: OK
umount: devtmpfs busy - remounted read-only
[ 259.933379] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system poweroff
[ 261.952735] reboot: Power down
[ 261.956143] omap_poweroff!!
How can I troubleshoot the upgrade process further to ensure that my OPI upgrades to Kinguard?
TECHNICAL DETAILS
OPI serial console: https://www.kinguardproject.org/wiki/in ... al_console
Voltage: 3.3V (your 5V USB-RS232 converter might damage the OPI if you connect converter's Tx pin to OPI)
PINS: Ground=1, Rx=5 (this is Receive for USB converter, which means Tx for OPI)
Best regards,
-DarS