https://archlinuxarm.org/platforms/armv ... l/clearfog
Unfortunately, Arch did not boot. I did get Debian:Jessie running from the official image on the ClearFog (SolidRun) website. I'm not sure how to get to the console on this device. I don't have a JTAG/serial connector. I've found some blog posts that show the console output to minicom, but no one really explains how they get to it. Is the console accessible via just the microUSB port? When I plug it in I don't get a $this->bbcode_second_pass_code('', '/dev/ttyUSB*'). I tried loading my usbserial module on my Linux box with the product/vendor ID of this device that shows up when I plug in the ClearFog:
$this->bbcode_second_pass_code('', '
[177718.717421] usb 1-2: new full-speed USB device number 28 using xhci_hcd
[177718.888730] usb 1-2: New USB device found, idVendor=0403, idProduct=6015
[177718.888735] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[177718.888738] usb 1-2: Product: FT230X Basic UART
[177718.888741] usb 1-2: Manufacturer: FTDI
[177718.888743] usb 1-2: SerialNumber: DJ00H8I7
[178821.088029] usb 1-2: USB disconnect, device number 28
[178824.290288] usb 1-2: new full-speed USB device number 29 using xhci_hcd
[178824.461396] usb 1-2: New USB device found, idVendor=0403, idProduct=6015
[178824.461399] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[178824.461401] usb 1-2: Product: FT230X Basic UART
[178824.461402] usb 1-2: Manufacturer: FTDI
')
..but still no ttyUSB.
Anyway, the big issue. I can get Arch working. I load Debian:Jessie (solidrun's official port), keep /boot, /boot.scr and /boot.script, delete the rest, and then unpack the Arch zip (except for /boot obviously). Using the Jessie kernel and bootloader, I can boot arch.
I'd like to diagnose what's wrong with the Arch instructions/kernel. I went through that wiki line by line 2 or 3 times. I always install the bootloader in PCI/PCI mode. The only change I have to make is changing /sd/sd* to /dev/mmcblk* (my laptop's SD card reader shows sd cards as /dev/mmcblk*) and I use bash instead of sh on the uboot install script (sh causes an infinite loop; issue on the read command I think).
The other thing, I have an M.2 SSD I attached to this board. I copied the same setup (debian kernel + Arch base) to my M.2 and flipped the dip switches to boot from M2. It didn't work and I realized in the docks you need to use a different boot loader ... and de-solder a resistor (What the...?! Seriously? Come on!) and you still need the SD card for the environment variables anyway.
So instead, I thought maybe I can use the SDcard just for booting and have it mount my M.2 as root? When I boot to either Jessie or Arch, it can read/mount the M.2, so that should work? I tried modifying /boot.scr and /boot.script so root was /dev/sda1 instead of /dev/mmcblk0p1. That didn't work. Also, what is the difference between boot.scr and boot.script? One looks to be the boot.script with some binary/bootstrapping stuff at the top? If I run file, I get
$this->bbcode_second_pass_code('', 'boot.scr: u-boot legacy uImage, , Linux/ARM, Script File (Not compressed), 710 bytes, Tue Jul 5 22:42:57 2016, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0xF106DBC5, Data CRC: 0xF42DBC86')
..so it's u-boot with is vars attached after it? Do I edit boot.script and run something to generate boot.scr?
TL;DR:
- Can I get a console from my Linux box to the ClearFog Pro via microUSB (and if so how)?
Are there any known issues with the current Wiki/Install docs and Arch kernel/uboot for this board? (Why does the Debian/Jessie kernel work but not the one in the arch instructions).
Can I boot from SD and mount root (/) from my M.2 card?